| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fsbl, plmfw, pufw, and psmfw are reworked to provide earlier error messages,
and better handle multiconfig builds.
Also adjust MACHINE specific changes to use .* for compatibility based on the
SOC_FAMILY override. The system doesn't always set the SOC_FAMILY as
COMPATIBLE_MACHINE, so this avoids an error of incompatible machine.
Align all of the expected firmware filenames to be <firmware>-${MACHINE}.
The user can override as necessary.
The license moves to CLOSED as we don't know the license of the software being
provided by the user or other dependencies. It'll be up to the user to
reconcile it.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
| |
PACKAGE_ARCH should not be MACHINE_ARCH, unless a specific override is
being used for compatibility.
Signed-off-by: Mark Hatle <mark.hatle@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>
|
| |
|
|
|
|
|
|
| |
Different boards may configure their firmwares differently. One such
example is ZU67DR RFSoC which requires libmetal libraries in some
configurtions.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1087560
git version no longer requires most patches, so clear these.
bin generation was not working consistently for standalone (not xsct) build,
correct this behavior.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
| |
WHen processing for cmake, PARLLEL_MAKE is processed by a python chunk
and if empty returns 'None', instead of 1.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
| |
Issue: ER-6946
Different workflows may require a slightly different name.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The various *fw.bb Linux recipes need to exclude the PLM_DEPLOY_DIR from hash
calculations. This location can change, but the actual value does not
matter.
Move plm-firmware, psm-firmware, pmu-firmware to use IMAGE_VERSION_SUFFIX
(and the associate image-artifact-names class) by default. This matches
how modern deployed components should work.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
