| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Following the example of the psm, pmu and plm, we split the FSBL into both
a packaging component (fsbl) and the build of the firmware (fsbl-firmware).
This also adds an additional multilib, fsbl-fw, that is used to handle the
multiconfig version, as the Linux and baremetal builds are done differently.
Typical build approach is:
Add to local.conf:
BBMULTICONFIG += "fsbl-fw"
then build using:
MACHINE=zynqmp-generic bitbake fsbl
Note, while 'zynq' is implemented, it does not currently function. To
build the fsbl for zynq, you must use the meta-xilinx-tools version.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| |
| |
| | |
If the distribution enables uninative, then in a multiconfig setting,
all distributions must use AND configure uninative support. This is
not desired and should only be enabled in the primary configuration.
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>
|
| |
| |
| |
| |
| |
| |
| | |
The actual version is 2019.2 according to the SRCREV. These components have
not yet been merged forward to 2020.2.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The system should never reference or build software that is above the 'S'
directory. So S being the top of the source tree, and B (build) being the
location where we are running out build components will work correctly and
meet the Yocto Project requirements.
This also has a side effect of allowing patching of components above the
build directory, if necessary.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
microblaze-pmu: Rename to microblaze-zynqmp-pmu
Also upon inspection of embeddedsw, it was setting the CPU version to v9.2.
Fix this.
versal-mb: Rename to microblaze-versal-fw
microblaze-plm: Remove (duplicate of above)
Also upon inspection of embeddedsw, it was setting the CPU version to v10.0.
Fix this.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
| |
| |
| |
| |
| |
| | |
This reverts commit 96f122efe48f239f7b5df4025acd5c98a61828b3.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the user chooses to build a microblaze target, the compiler can fail
to patch properly as a symptom. Users may think it's a simple patch failure,
but really they forgot to include the meta-microblaze layer itself.
Declare the meta-microblaze layer as a recommended layer, and verify in the
gcc-source bbappend that it has been included, if a microblaze target is being
built.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| |
| |
| |
| | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
|\ \
| | |
| | |
| | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Siva Addepalli <sivaprasad.addepalli@xilinx.com>
|