summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-standalone/conf
Commit message (Collapse)AuthorAgeFilesLines
...
* | Remove gatesgarth from LAYERSERIES_COMPATJohn Toomey2022-02-041-1/+1
| | | | | | | | | | | | | | | | We do not build, test or support gatesgarth in any of our layers so it makes sense to remove this for the various layer.conf files Signed-off-by: John Toomey <jtoomey@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* | meta-xilinx-standalone: Remove obsolete machinesMark Hatle2022-01-237-37/+0
| | | | | | | | | | | | | | These machines are no longer necessary, as the regular "generic" machine with an alterantive DEFAULTTUNE should be used instead. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* | meta-xilinx-standalone: Move from cortexr5f to cortexr5Mark Hatle2022-01-142-2/+2
| | | | | | | | | | | | | | After moving from Xilinx specific cortex r5 turning file, the 5f is no longer defined. Move to the now standard 'cortexr5' definition. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* | Remove cortexrm tune, as Yocto Project now has cortex-r tunesMark Hatle2022-01-141-27/+37
| | | | | | | | | | | | | | armrm override is now replaced by armv7r and armv8r overrides. Adjust recipes to match the new usage. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* | Move baremetal include to meta-xilinx-standaloneMark Hatle2022-01-141-0/+7
| | | | | | | | | | | | | | This was missed in the prior move of the components to meta-xilinx-standalone layer. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* | aarch32-tc.conf: Fix reference to cortex-a9 tune fileMark Hatle2022-01-141-1/+1
|/ | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* aarch64-tc: Fix cortexa72-cortexa53 referenceMark Hatle2021-11-011-1/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-standalone: various fixes for override syntax changesMark Hatle2021-10-251-2/+2
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Convert to new override syntaxSai Hari Chandana Kalluri2021-09-2810-440/+440
| | | | | | | | | | 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>
* meta-xilinx-standalone: Sync standalone to latest embeddedswMark Hatle2021-09-282-2/+2
| | | | | | | | | | | | The latest embeddedsw components no longer need integration workarounds, other then the couple of patches being applied. This simplifies eliminates the custom do_configure, and simplifies the do_compile. EXTRA_COMPILER_FLAGS is now different then the default version. The versal defaults were also adjusted to match the expected output. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-standalone: Fix typo in versal-fw multiconfig commentMark Hatle2021-09-281-1/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-standalone: Update microblaze configMark Hatle2021-09-282-2/+2
| | | | | | | Update the PMU machine and multiconfig files to match the current version of the embeddedsw. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* xilinx-standalone.inc: add PREFERRED_VERSION for open-amp in case of ↵Ben Levinsky2021-09-281-0/+1
| | | | | | | | | | | standalone target In case of open-amp, there are multiple version of open-amp. For case of standalone, specify usage of meta-standalone-experimental layer for BSP that is provided. Signed-off-by: Ben Levinsky <ben.levinsky@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* xilinx-standalone.inc: add PREFERRED_VERSION for libmetal in case of ↵Ben Levinsky2021-09-281-0/+2
| | | | | | | | | | | standalone target In case of libmetal, there are multiple version of libmetal. For case of standalone, specify usage of meta-standalone-experimental layer for BSP that is provided. Signed-off-by: Ben Levinsky <ben.levinsky@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* distro: xilinx-standalone: Use Os option along with Link Time Optimization flagsAppana Durga Kedareswara rao2021-09-271-1/+1
| | | | | | | | Default Link Time Optimization flags should contain Os option along with flto and ffat-lto-objects flags to inline with the regular esw default compiler flags. Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com>
* Update XILINX_VER_MAIN to 2021.2Sai Hari Chandana Kalluri2021-09-271-1/+1
| | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* layer.conf: Add honister hardknott LAYER COMPATSai Hari Chandana Kalluri2021-07-151-1/+1
| | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* *.conf: set XILINX_VER to 2021.1Sai Hari Chandana Kalluri2021-07-141-1/+1
| | | | | | Set XIlINX_VER to 2021.1 Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* xlnx-embeddedsw.bbclass: Change the way in-progress overrides are handledMark Hatle2021-07-141-5/+0
| | | | | | | | | | Instead of hardcoding the values, we move to a format that is compatible with the system bblcass. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com> cherry-pick: 46f5f35 Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Update commit ids for 2021 releaseSai Hari Chandana Kalluri2021-07-141-1/+1
| | | | | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> cherry-pick: 3d9b301 Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Update commit id for 2021 releaseSai Hari Chandana Kalluri2021-07-141-1/+1
| | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* update commit ids for 2021 releaseSai Hari Chandana Kalluri2021-07-141-1/+1
| | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* embeddedsw.inc: Add embeddedsw.inc as one stop to change SRCREV & BRANCHSai Hari Chandana Kalluri2021-07-141-0/+5
| | | | | | Use embeddedsw.inc to update SRCREV and BRANCH for all recipes are based on embeddedsw Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* fsbl/fsbl-firmware: Split the packaging and building of the fsblMark Hatle2021-07-141-0/+5
| | | | | | | | | | | | | | | | | | | | | 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>
* layer.conf: compatible with gatesgarth onlyMark Hatle2021-07-141-1/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* embeddedsw: Rework plm/pmu/psm firmware and Linux packagingMark Hatle2021-07-142-0/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* xilinx-standalone.inc: Don't require uninativeMark Hatle2021-07-141-3/+0
| | | | | | | | 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>
* meta-xilinx-standalone machines: Update to match embeddedswMark Hatle2021-07-144-22/+16
| | | | | | | | | | | | | 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>
* Reorganize the various layer componentsMark Hatle2021-07-1413-9/+1097
| | | | | | | | | | | | | | | | | | | | 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>
* meta-xilinx-standalone: Prevent user error, when meta-microblaze is requiredMark Hatle2021-02-031-0/+1
| | | | | | | | | | | | 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>
* update XILINX_VER_MAIN to 2020.2Sai Hari Chandana Kalluri2020-11-171-1/+1
| | | | | git cherry-pick b80c6d4 Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* layer.conf: Set layer compat to dunfell & gatesgarthSai Hari Chandana Kalluri2020-08-111-1/+1
| | | | | | Set layer compat to dunfell and gatesgarth Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* xilinx-standalone.conf: Switch default from -Os to -O2Mark Hatle2020-07-081-1/+1
| | | | | | | | 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>
* Define COMPATIBLE_HOST to prevent mix of Linux and Baremetal recipesMark Hatle2020-03-261-0/+7
| | | | | | | | | | | | | | | The key is using COMPATIBLE_HOST to declare, for each recipe, which OS they are compatible with. This is a regex, so we need to carefully specify the arch/vendor wild cardscomponents so that we match only the OS parts. In the distro configuration, default to the standard Linux HOST_SYS setting. In the various baremetal recipes (or esw class) set the specific compatibility to allow baremetal recipes to build. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Revert "xlnx-compatible-os.bbclass: Class to allow recipes to list OS ↵Mark Hatle2020-03-261-2/+0
| | | | | | | | compatibility" This reverts commit 4f3edb6da405ffff957d6f194bc7db7bdd9f1463. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* xilinx-standalone.conf: Add workaround for microblaze -Os bugMark Hatle2020-03-201-0/+3
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-standalone: classes: Update CMAKE_SYSTEM_NAME for FreertosAnirudha Sarangi2020-03-161-0/+1
| | | | | | | | This patch updates the CMAKE_SYSTEM_NAME variable for freertos. Signed-off-by: Anirudha Sarangi <anirudha.sarangi@xilinx.com> Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-standalone: conf: distro: Add new distro for freertosAnirudha Sarangi2020-03-161-0/+8
| | | | | | | | | This patch adds new distro xilinx-freertos for compiling esw freertos use cases in yocto flow. Signed-off-by: Anirudha Sarangi <anirudha.sarangi@xilinx.com> Signed-off-by: Appana Durga Kedareswara rao <appana.durga.rao@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* xilinx-standalone.inc: Replace qemu dependency with mingw32 specific recipeMark Hatle2020-03-031-1/+2
| | | | | | | | | | | Commit fb62f071f94fc45444357865665fec6d4b11d1ca added a workaround for a mingw runtime issue, but did not label it as mingw32 specific. QEMU may cause failures in some non-linux configurations. Make this option mingw32 specific, and also avoid qemu making the dependency on the missing mingw32 component explicit. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* xilinx-standalone: sync distrosMark Hatle2020-03-032-8/+8
| | | | | | | | Both xilinx-standalone (w/ lto) and xilinx-standalone-nolto need to use a common set of system settings. A few settings were missed in the merge of the decoupling work. Move these to the common settings file. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* xlnx-compatible-os.bbclass: Class to allow recipes to list OS compatibilityMark Hatle2020-02-271-0/+8
| | | | | | | | | | | | | | | | | | 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>
* xilinx-standalone: When building for cortexr5, add -DARMR5 for CCARGSMark Hatle2020-02-271-0/+3
| | | | | | | | The embeddedsw expects -DARMR5 when building for a cortexr5. Enable this globally within the distribution configuration. This ensures that the tunings remain generic. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* xilinx-standalone: Add buildhistory to the DISTRO to avoid cooker errorsAlejandro Enedino Hernandez Samaniego2020-02-271-0/+2
| | | | | | | | | | | | | | | | There is a bug upstream, which explains this problem further [1], but basically when there are several multiconfigs they could be polluted with the events of each other, in this specific case, a multiconfig that uses the DISTRO=petalinux which itself inherits the buildhistory class will cause an error on the multiconfig that builds xilinx-standalone, while the correct fix is t fix this upstream I have not had the time to do that, and currently an easy and not very conflicting workaround is to simply inherit the builhistory class on the xilinx-standalone DISTRO as well. [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=13071 Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* distr/xilinx-standalone: Switch default optimization from ESW to DistroMark Hatle2020-02-272-3/+3
| | | | | | | | | | | Instead of using ESW_CFLAGS for the optimization level, fall back to the default Yocto Project method of 'FULL_OPTIMIZATION' and 'SELECTED_OPTIMIZATION'. FULL_OPTIMIZATION is moved from -O2 to -Os, the other components retain the default Yocto Project setitng of '-pipe ${DEBUG_FLAGS}'. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* distro/xilinx-standalone: Make LTO optionalMark Hatle2020-02-273-12/+31
| | | | | | | | | | Some builds may require LTO, while others do not want it. The LTO components are only enabled when using the esw.bbclass and the xilinx-standalone distro. A second xilinx-standalone-nolto was added specifically to provide a default where LTO was disabled. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Increase layer priorityAlejandro Enedino Hernandez Samaniego2020-02-271-1/+1
| | | | | | | | We need to increase the layer priority for meta-xilinx-standalone, otherwise its not possible to set a branch for decoupling on the DTG flow, since meta-xilinx-internal overrides our changes Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* xilinx-standalone.conf: Adding qemu to TOOLCHAIN_HOST_TASKJaewon Lee2020-02-101-0/+2
| | | | | | | | | | | | | When running gcc built for xilinx-standalone using mingw sdk machine, it would throw an error saying the winpthread dll was missing. this is because in tclibc-newlib, TOOLCHAIN_HOST_TASK was being overwritten and omitting nativesdk-packagegroup-sdk-host which pulled in the appropriate package nativesdk-mingw-w64-winpthreads. Manually adding the following to TOOLCHAIN_HOST_TASK to bypass this issue: nativesdk-qemu-xilinx Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Alejandro Enedino Hernandez Samaniegoi <alejandr@xilinx.com>
* Enable multilib baremetal toolchainsMark Hatle2020-01-311-1/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* meta-xilinx-bsp: Unify machine confsAlejandro Enedino Hernandez Samaniego2020-01-307-101/+0
| | | | | | | | Unify the meta-xilinx-bsp and meta-xilinx-standalone layers by moving the machine confs to the BSP layer and keeping the standalone layer as a DISTRO layer Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* cortexa72: To keep up with a standard rename cortexa72 to add its SOC_FAMILY ↵Alejandro Enedino Hernandez Samaniego2020-01-301-0/+0
| | | | | | to its name Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-23 06:02:59 +0000