Age | Commit message (Collapse) | Author |
|
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: Mark Hatle <mark.hatle@xilinx.com>
|
|
Machines: Move baremetal machines to meta-xilinx-standalone
Layers:
- Add new meta-xilinx-standalone-experimental
This layer may require components that may not yet be available to the
general public. It will contain various experiemntal integration work.
- meta-xilinx-standalone
This layer should be functional and contain the necessary items to build a
baremetal toolchain that can use libxil (replacement to libgloss) from
the Xilinx embeddedsw components. (Note, libxil is NOT built as part of
this work!)
The layer also contains the buildable components for the various firmware
components required to startup various Xilinx FPGAs.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Adding xxd as a host tool as it's a dependent tool when uboot is
configured to use a default environment file
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Inserting a '-' in between board and boardvariant to align with the
format of soc and soc family
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Previously machine override for a soc variant was SOC_VARIANT appended
to SOC_FAMILY. A '-' was included in between to align with how versal
handles machine overrides. Updating machine overrides to match this
format
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Removing the need to prepend a '-' to SOC_VARIANT for versal variants
for ex. '-ai-core'
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Defining UBOOT_MACHINE as microblaze-generic_defconfig and setting
UBOOT_INITIAL_ENV to empty to be able to compile uboot as microblaze
env/common.o doesn't have default_environment section
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@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>
|
|
Fix machine name being passed to zcu102-zynqmp qemu boot arg.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Using BOARD level hierarchy to rewire ultra96 specific overrides.
Each package using BOARD override has to also redefine PACKAGE_ARCH
using BOARD_ARCH
Signed-off-by: Jaewon Lee <jaewon.lee@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>
|
|
Fixing arch variables, removing SOC_ for BOARD_ARCH and
BOARDVARIANT_ARCH variables
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
If there is a _ in the package arch, the sstate-control files are written
with a _. However, when they are used they somehow get translated to a
-, triggering a warning message. The warning though means that the
sstate component was not actually staged into the recipe-sysroot, causing
a later build failure.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
git cherry-pick b80c6d4
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Introducing an include file to add levels of hiearchy to PACKAGE_ARCH,
namely BOARD and BOARD_VARIANT
To use this, future confs will need to have the following line:
require conf/machine/include/xilinx-board.inc
Along with BOARD/BOARD_VARIANT definitions
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>
|
|
microblaze-pmu
zynqmp-pmu is renamed to microblaze-pmu. Update the PMU_FIRMWARE_DEPLOY_DIR
path to look under correct path.
Set weakest assignment in local.conf.sample for the above variables.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Enable runqemu for vmk180-versal
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Updating tenzing machine SOC_VARIANT to "-ai-core"
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
Setting vck190-versal board's SOC_VARIANT to ai-core
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
Default versal SOC_FAMILY is changed to "prime" from "s80"
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
Users have to manually copy pmu-rom.elf to DEPLOY_DIR when using runqemu.
Enable PMU_ROM line within local.conf to use pmu from /proj/yocto/pmu-rom/
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Set default PREFERRED_PROVIDER for qemu as qemu-xilinx within
machine-xilinx-qemu.inc. This eliminates the need to use PNBLACKLIST within
local.conf
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
fragment from kernel-cache
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Set layer compat to dunfell and gatesgarth
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
MACHINE_ESSENTIAL_EXTRA_RDEPENDS"
This reverts commit ee6d2b039501f63098831bbff141a9d1ef1ae645.
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
Adding device-tree to MACHINE_ESSENTIAL_EXTRA_RDEPENDS for all xilinx
machines, this will install dtb/dtbo files into the rootfs.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Machine support for versal targetting the vck500 Alveo evaluation card
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>
|
|
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
Issue: CR-1061420
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Issue: CR-1061420
The init-ifupdown will choose alternative network interface configuration
files based on the FILESOVERRIDE setting, which usually includes a
machine name. If an alternative is selected, then the package should
become machine specific.
The BSPs were setting the files override, but were NOT settings the
required machine override. Fix this by setting the necessary
machine override, ensuring the init-ifupdown IS now machine specific.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
For Linux based builds, it should be set to sysv. This will result
in the system using a supported hash type. (GNU hash is not supported
on Microblaze., so sysv will be used instead.)
For baremetal, set the value to "". This will result in no value set,
and the system will use the compiler and linker default.
Signed-off-by: Mark Hatle <mark.hatle@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 machine can be used with xilinx-standalone-nolto and
xilinx-standalone distros to build standalone components for
zynq.
Signed-off-by: Mubin Usman Sayyed <mubin.usman.sayyed@xilinx.com>
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>
|
|
All xilinx BSPs that support qemu should use the machine-xilinx-qemu.inc
file. So move all references to the -multiarch extension into that
location.
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>
|
|
Enable qemuboot for qemu-zynq7 machine using qemu-xilinx provider
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Enable qemuboot for zc702-zynq7 machine using qemu-xilinx provider
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|