| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Create a new meta-xilinx-core, move core functionality to the core, keeping
board specific files in the bsp layer.
zynqmp-generic changed from require <board> to include, so if meta-xilinx-bsp
is not available it will not fail.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
use vck190 dts
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
This is the result of automated script (0.9.0) conversion:
oe-core/scripts/contrib/convert-overrides.py .
converting the metadata to use ":" as the override character instead of "_".
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
| |
Using += for MACHINE_FEATURES to allow addition to MACHINE_FEATURES in
confs using += and _append
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
| |
After the change to extract cdo from the boot.bin in deploy, the cdo is
deployed in a different directory. updating the location for runqemu
command
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
| |
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In order to allow standalone (meta-xilinx-standalone), XSCT
(meta-xilinx-tools), and future items to work in the same way
the recipes have been restructured.
A *-firmware recipe will generate the firmware and stage it to do_deploy.
A *fw recipe will take the deployed version and package it for the Linux
side of things. This allows the firmware generation to be easily extended
without requiring packaging knowledge. Similarly packaging can be
extended for alternative boot/upgrade mechanisms as required.
In all cases, the MACHINE configuration will specify the default way
the components are to be built, along with the names of the item in
the deploy directory.
The PLM/PSM/PMU_IMAGE_NAME is the name for the generated firmware.
PLM/PSM/PMU_DEPLOY_DIR is the path to the constructed firmware. This along
with the IMAGE_NAME above can be used to specify the location of an
externally generated set of firmware.
Addtionally the dependencies for building the plmfw/psmfw/pmufw can be
changed easily using PLM/PSM/PMU_DEPENDS and PLM/PSM/PMU_MCDEPENDS. The
former specifies dependencies in the same multiconfig, while the later
allows the component to require another multiconfig to have finihed.
The system has a referenced default, if multiconfig is enabled it will
automatically use it, otherwise it will try to use the recipe in the
main configuration. (This will fail unless meta-xilinx-tools is available.)
Also two multiconfigs hve been implemented: versal-fw and zynqmp-pmufw
They can be enabled using BBMULITCONFIG += "zynqmp-pmufw" or versal-fw.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
| |
Enable runqemu for BOARD vp1202-versal
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
| |
Pick correct QB_MACHINE name for each of the machine from
qemuboot-xilinx.bbclass. Remove QB_MACHINE from machine.conf
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Going to generic machine confs, we can no longer use machine overrides
for specific machine changes.
Adding BOARD and BOARD_VARIANT level hierarchy for packaging for
zynqmp/zynq/versal generic machines confs.
BOARD and BOARD_VARIANT must be set accordingly to use these hierarchy
levels properly
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
MACHINE_ESSENTIAL_EXTRA_RDEPENDS variable only for specific machines.
Add MACHINE_ESSENTIAL_EXTRA_RDEPENDS variable for zynqmp and versal platforms.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removing dtb fatload in boot.scr and removing unnecessary image, dtb,
rootfs loading in runqemu command
dtb is being loaded through boot.bin for versal so fatload through
boot.scr and loading into memory through runqemu commands are not
necessary (before this change dtb was essentially being loaded three
times)
image will be fatloaded through boot.scr (provided in sd image)
rootfs is provided through sd image
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
| |
Recent requirement for Versal has changed, we now we need to supply 8G
so changing QB_MEM to 8G from 4096. This will fix issue of runqemu
hanging at 'Starting Kernel'
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
By default the machines should not check and remove declared consoles
that are not available on first boot. It's up to the user to add this
to their build configuration.
The recommended user behavior is:
SERIAL_CONSOLES_CHECK = ${SERIAL_CONSOLES}
but the side effect of this is that if the device configuration changes
after the first boot, the additional devices will not be available.
(Note, this may result in warning messages with getty unable to connect
to certain devices.)
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
Usage of 'SERIAL_CONSOLE' was deprecarted in late 2013. Move to the
using 'SERIAL_CONSOLES', where the format is slightly different.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
This move syncronizes qemu call and DTB generation.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
Additionally ensure that all u-boot defconfigs use the common
configuration for each platform.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
Move IMAGE_CLASSES setting to common machine-xilinx-qemu.inc, also add
preferred provider for the xilinx specific qemu components.
Adjust the various BSPs to remove duplicate references to these and
non-Xilinx versions of qemu.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
The machine-xilinx-override is really just an extension to the standard
soc-family.inc file. So rename this, move the include of soc-family.inc
to this file, move the include to the soc includes to each soc file, and
finally adjust the machines to remove machine-xilinx-override as it's no
longer necessary.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
The tune files were really soc configuration files. Tune files should
only specify toolchain flags that affect optimiation and abi.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Add versal-generic machine configuration
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|