| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@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-1098191
The kernel-module recipes set PACKAGE_ARCH = "${SOC_FAMILY_ARCH}" which is broken
because kernel modules depend on the kernel which is MACHINE specific. The
assignment claims that you could use a kernel module built for some other board
for any other zynqmp board, which is not true since their kernel versions and
configuration will differ.
Remove the assignment so that the kernel module becomes MACHINE_ARCH again.
This solves issues with kernel modules that refuse to install during the
do_rootfs stage, and various setscene tasks running over and again when
switching between MACHINEs.
Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1098186
Without this change, a parse error may occur related to being unable to find
one or more local patches.
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>
|
|
|
|
|
|
|
|
|
| |
IMAGE_FEATURES should only control which package are getting included into the
image, it shouldnt control configuration/compile options. Keeping the
fpga-manager IMAGE_FEATURE but also using fpga-overlay DISTRO_FEATURE to
set FPGA_MNGR_RECONFIG_ENABLE which controls config options
Signed-off-by: Jaewon Lee <jaewon.lee@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>
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1096936
TOPDIR is only used to find the file to copy in the case of a multiconfig
build. However, even in this case the value of TOPDIR does not effect
the resulting build. Exclude this variable to avoid unnecessary
rebuilds of firmware in the eSDK.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
| |
We want meta-browser/meta-chromium to be used with ultra96 webapp
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Using weaker assignment for KBUILD_DEFCONFIG to override without
forcevariable.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
| |
Using weaker assingnment for UBOOT_MACHINE to update this value in
petalinux without _forcevariable.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
| |
meta-xilinx-tools and bootgen produced a version called 'fsbl-<machine>',
adjust the name to match expectations.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Match the behavior of the pmu, psm, and plm firmwares. Set the default
deployment directory, filename, and dependencies for the soc-zynq and
soc-zynqmp systems. FSBL is only present on thse two systems.
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 past using the if check in qspi/nand to check if user wants to use
fitimage/separate images default is fitimage, this leads to rebuild the boot.scr if user
wants to use separate images.
This patch will remove if check and use direct commands if proper image
found bootm will run and boots the kernel.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Having ramdisk images in FAT, rootfs extracted into EXT4 and want to
boot direct EXT4 boot without pivot is not working since the bootscript
is loading the ramdisk image from FAT. To avoid this adding env
variables to skip loading ramdisk images. These can be part of uEnv.txt
or uboot.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1062133
For some reason libgloss installs the crt*.o files with executable bit set,
this causes the build system to strip these as executables. However, it
makes it impossible to use the .o files to properly link applications later
on.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
This patch will add uEnv.txt support in bootscript.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
| |
The typecast is causing linking to not work properly, however it does cause
a compilation warning to return that a typecast is likely needed.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
|
|
|
|
| |
Issue reported by Daniel Mack via the meta-xilinx mailing list.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
|
|
|
|
| |
Set BOARD in MACHINE conf as workaround for build scripts not using
generic confs
Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
|
|
|
|
|
|
|
|
| |
Including xilinx-board.inc to add BOARD variables support for mb generic
machine.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
| |
We should be using IMAGE_VERSION_SUFFIX instead, but this requires that
the user either directory or indirectly inher image-artifact-names.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: SSW-773
Due to changing the order of the search paths in meta-petalinux to allow
us to override classes, the way we find the oe-core files needs to also
change. Instead of using a search approach, just assume that the files
we need will always come from oe-core itself.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
| |
Signed-off-by: ch vamshi krishna <chvamshi@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
| |
The new update has the latest eglplatform header from khronos.
Signed-off-by: Madhurkiran Harikrishnan <madhurkiran.harikrishnan@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
If the fw is pulling from the same config, we don't want to re-deploy the
firmware (it will fail.) Otherwise copy it from the other config into
our config, as other tools may look for it.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
| |
The restructure of the code missed the filename structure, the filenames
used by meta-xilinx-tools were intended to be the correct ones.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Use the ramdisk.cpio.gz.u-boot image for pxeboot when INITRAMFS_IMAGE has the image
name *initramfs*.
Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@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>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@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>
|