| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
The fsbl has been renamed to fsbl-firmware, and some adjustments to the
build method are required to match how standalone and xsct version work.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
| |
only for standalone configuration
psu_init* files installation is valid only for standalone configuration
update the do_install for the same.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Install psu_init files for zynqmp machines these files
are needed for building fsbl for corter5 processor use case as well.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
Move to meta-xilinx-tools layer and combine with original recipe
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Updated COMPATIBLE_MACHINE, DTBFILE, XSCTH_PROC
and some other variables related to CMAKE build system.
Signed-off-by: Mubin Usman Sayyed <mubin.usman.sayyed@xilinx.com>
Rebase for updated esw/compatible machine changes.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
This patch updates the COMPATIBLE_MACHINE and DTBFILE
variables to compile esw use cases for cortexr5 processor
on versal platform.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
Some of the components have been moved to internal configuration layers
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Following the example of base.bbclass in OE-Core, a new COMPATIBLE_OS
variable is defined. Similar to COMPATIBLE_MACHINE, it is a regex that
can be used to declare TARGET_OS string compatibility on a per-recipe
basis. Either the distro configuration or the recipes themselves will
need to inherit this class.
By default the class assumes we're building a Linux based system, and
thus any recipe who has not declared compatibility is compatible with
Linux. The default compatible field was copied from bitbake.conf to
ensure there are no surprised.
Additionally, enable the usage of this class throughout
meta-xilinx-standalone layer.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
meta-xilinx-standalone is only for baremetal work. Theoretically the
newlib items can be used on other configurations, so move the microblaze
newlib/libgloss work into meta-xilinx-bsp. This mirrors how other
microblaze specific work has been handled.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The deocupling device-tree repo does not currently work with
machines like the zcu102-zynqmp, while the default repo does
work fine.
Set overrides for the decoupling working machines, while keeping
the REPO as it was by default for other machines to avoid this
error.
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
This patch updates the COMPATIBLE_MACHINE and DTBFILE
variables to compile esw use cases for cortexr5 processor
on ZynqMP platform.
This patch also updates the TUNE_CCARGS in the cortexr5-zynqmp.conf
file as per baremetal requirements.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
|
|
|
|
| |
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
|
|
|
|
|
| |
cortexa72 processor machine name changed from cortexa72 to coretexa72-versal
update the naming convention in the recipes for the same.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
|
|
|
|
|
|
|
| |
This patch updates the COMPATIBLE_HOST and COMPATIBLE_MACHINE
and DTBFILE variables to compile esw use cases for cortexa72 processor.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This layer has been used as testing for the decoupling effort
hence there was (and still is) code that needed to be cleaned up
in general.
Put #TODO on things that are still left to do, either clean up
code, move machine confs to the bsp layer or remove the
deprecated pmu-firmware recipe and handle dependencies correctly
by bitbake'
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
There was a typo in the patch that installed the psu_init code
which initially tried to install files on the /var directory.
Since this is a baremetal component, there is basically no
convention on where files should be installed, for now
to comply a bit more with bitbake, install these files on
includedir to fix the install-vs-shipped issue.
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
|
|
|
| |
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
zynqmp-pmu to microblaze-pmu
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Distro Changes:
When building a multilib, we need to disable configsite cache. Otherwise
the system will fail to generate the SDK as there are no configsite entries
due to newlib based multilibs.
Recipe Changes:
gcc - globally disable multilib configuration
- Disable Linux specific configurations (EXTRACONFFUNCS)
gcc-cross-canadian - enable multilib on a recipe specific basis
libgcc - add a noop override to do_multilib_install to avoid Linux specific
multilib processing
newlib - arm/v6+m/nofp and arm/v8-m.base/nofp do not have newlib trap
implementations. libgloss contains these, workaround by
disabling builtin trap syscall handler.
- misc workarounds for multilib installs
libgloss - Allow MLPREFIX for newlib dependencies
meta-toolchain - adjust to install only the items we want/need
packagegroup-newlib-standalone-sdk-target - new pkggroup for the
custom baremetal SDK to select the right set of packages
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
zynqmp-pmu to microblaze-pmu
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
recipes-bsp
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|