| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Ensure that plm-firmware can run for any microblaze & versal configuration.
Ensure that psm-firmware can run for any microblaze & versal configuration.
Ensure that pmu-firmware can run for any microblaze & zynqmp configuration.
In each case, use EXTRA_OEMAKE to set the bsp_make_vars instead of
individual references. This allows meta-xilinx-tools to disable this.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
| |
Use -mcpu=v10.0 instead of indeterminate -mcpu=v.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
| |
Add a new plm/pmu/psm version (non-default) to track upstream embeddedsw for
easier development.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Move versal-mb conf to meta-xilinx-standalone
Sync to latest official patches for zynqmp_pmufw to deal with assert now
now being a macro.
Sync to latest official patches for copy_bsp.sh (standalone) configurations.
Delete versions that do NOT compile.
Update remaining versions to compile on current toolchain.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
| |
Change the order of embeddedsw and some of the variables used to allow
bbappending from meta-xilinx-tools
Add Description and Provide from meta-xilinx-tools versions.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
Create a new embeddedsw.inc file, This will contain all of the refereces
for SRCREV, and SRC_URI and other components that may be necessary.
Changing the filename or passing SRC_VER will switch the various source
version information. As new releases happen, they can be added to the list
while incompatible ones can be removed.
This now allows us to focus on adjusting the recipes as necessary.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
