| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
| |
We include base qemu, the toolchain, but nothing else. (Dummy package is
required to meet basic dependencies.)
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
| |
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
Due to the way the multilib xilinx-standalone works, one or more empty
directories under ${D}/lib may exist. This triggers a QA error about
unpackaged files. Use rmdir to delete these directories to ensure they
are empty.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rename the structure member from 'assert' to 'resetAssert to avoid a
compilation error:
| pm_reset.c: In function ‘PmResetDoAssert’:
| pm_reset.c:1905:36: error: macro “assert” passed 2 arguments, but takes just 1
| 1905 | reset->ops->assert(reset, action);
| | ^
| In file included from .../tmp/work/microblazeel-v11.0-bs-cmp-xilinx-elf/pmu-firmware/v2020.1+gitAUTOINC+e8db5fb118-r0/recipe-sysroot/usr/include/sys/reent.h:503,
| from .../tmp/work/microblazeel-v11.0-bs-cmp-xilinx-elf/pmu-firmware/v2020.1+gitAUTOINC+e8db5fb118-r0/recipe-sysroot/usr/include/string.h:11,
| from ../misc/zynqmp_pmufw_bsp/psu_pmu_0/include/xil_printf.h:9,
| from xpfw_debug.h:57,
| from xpfw_default.h:37,
| from pm_reset.c:36:
| .../tmp/work/microblazeel-v11.0-bs-cmp-xilinx-elf/pmu-firmware/v2020.1+gitAUTOINC+e8db5fb118-r0/recipe-sysroot/usr/include/assert.h:16: note: macro “assert” defined here
| 16 | # define assert(__e) ((__e) ? (void)0 : __assert_func (__FILE__, __LINE__, \
| |
| Makefile:37: recipe for target ‘pm_reset.o’ failed
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
|
|
|
|
|
| |
Move newlib/libgloss from 3.1.0 to 3.%
Move the gcc configuration for standalone to gcc 10.
Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
|
|
|
|
|
|
| |
Remove recipe bbappends pointing to older versions. The newer versions are available in meta-microblaze
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
| |
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
| |
git cherry-pick b80c6d4
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
| |
Update commitid and branch for the following components:
arm-trusted-firmware, vcu, linux-xlnx, qemu, u-boot-xlnx,xrt,zocl,bootgen
git cherry-pick 9f8d8d7
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use variable IMAGE_VERSION_SUFFIX variable instead of DATETIME. Using
IMAGE_VERSION_SUFFIX allows easier and more direct changes. The
variable is available since Yocto 2.6 and it is used also for other
name variables, e.g. IMAGE_NAME. It is set to "-${DATETIME}" per
default, so the naming does not change as long as IMAGE_VERSION_SUFFIX
is not overridden.
For more details, see:
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#migration-2.6-image-kernel-artifact-naming-changes
Signed-off-by: Joerg Hofrichter <joerg.hofrichter@ni.com>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
| |
Use standard variables to set the BRANCH, SRCREV, REPO instead of
EMBEDDEDSW_REPO, EMBEDDEDSW_SRCREV, EMBEDDEDSW_BRANCH variables
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
| |
Set layer compat to dunfell and gatesgarth
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1069415
Issue: CR-1069801
Linux based SDK toolchains need to disabled multilib support, similar to
the existing 0004-64-bit-multilib-hack.patch from OE. This will fix
compiling C++ applications, as well as potentially other multilib header
and library issues.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
| |
Based on performance measurements as well as recent presentations at ELC
it is believed the correct default should always be -O2. -Os should only
be selectively used per module instead of default.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
The configuration generation had a typo in 'divide-hard'.
Fixed a logic error with '!' table operator. Before fpu-soft
was effectively always on, even when it shouldn't be.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Issue: CR-1065455
Microblaze does not support initfini_array in a baremetal configuration.
This has previously been disabled in binutils, but it was missed in GCC and
related libraries.
This patch slightly restructures the baremetal configurations to move the
common configuration elements into a single configure set. This matches the
behavior from the Yocto Project gcc-configure-common.inc file.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
| |
based on the machine type
This patch adjusts the cflags variables based on the selected machine.
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>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the sysmon driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the xadcps driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the qspips driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the spips driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
examples
This recipe compiles the gpio driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the uartps driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the uartlite driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the mutex driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
examples
This recipe compiles the mbox driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the devcfg driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the nandpsu driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
driver examples
This recipe compiles the ipipsu driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
|
|
|
|
|
|
|
| |
examples
This recipe compiles the sdps driver examples.
Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|