summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-standalone
Commit message (Collapse)AuthorAgeFilesLines
...
* xilinx-standalone: Add staticdev packages for newlib and libgloss to ↵Alejandro Enedino Hernandez Samaniego2019-12-091-0/+3
| | | | | | | | | | | dependencies For the cross canadian toolchain we need to have both the libc.a and libgloss.a. We add them to the LIBC_DEPENDENCIES which are wired in core to be added to the sdk via the TOOLCHAIN_TARGET_TASK variable Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* xilinx-standalone: switch override and appendAlejandro Enedino Hernandez Samaniego2019-12-094-8/+12
| | | | | | Instead of overriding the append, we need to append the override. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* Adds MACHINE.conf containing default tune for Cortex A72Alejandro Enedino Hernandez Samaniego2019-12-091-0/+54
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* toolchain: Provide specific configuration for cross(-canadian) gcc and binutilsAlejandro Enedino Hernandez Samaniego2019-12-096-14/+149
| | | | | | | | | | | | | | | Since we need specific configuration for the SDK toolchain, we need to override the configuration coming from oe-core, this configuration needs to be per MACHINE. Use GCC_CONFIGURE_COMMON_XILINX_STANDALONE to define the default config shared amongst MACHINES, and use a GCC_CONFIGURE_<MACHINE> variable to append to this common configuration options on each MACHINE that we want. Use the same procedure for binutils Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* Adds MACHINE.conf containing default tune for Cortex A53Alejandro Enedino Hernandez Samaniego2019-12-091-0/+14
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* Adds MACHINE.conf containing default tune for Cortex R5Alejandro Enedino Hernandez Samaniego2019-12-091-0/+13
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* gcc-cross: Dont override EXTRA_OECONF unless DISTRO is xilinx-standaloneAlejandro Enedino Hernandez Samaniego2019-12-091-1/+1
| | | | | | | | | For the xilinx-standalone DISTRO, we need to keep some of the configure options that we lose when setting TCLIBC=newlib, although this should only happen when we are selecting xilnx-standalone as the DISTRO, otherwise, we would be overriding the configure options for GCC when this bbappend is parsed Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* Move recipes to use _%.bb instead of versionSai Hari Chandana Kalluri2019-12-092-0/+0
| | | | | | | The changes in these recipes are version independent. Hence move them to _%.bb Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* versal-mb.conf: Add machine configuration to support standalone buildSai Hari Chandana Kalluri2019-12-091-0/+11
| | | | | | | | for versal components like plm, psm-firmware versal-mb.conf supports versal SOC standalone component builds such as plm, psm-firmware. It provides required configuration to use microblaze toolchain needed for the builds.
* psm-firmware_2019.2.bb: Create psm-firmware recipe for standalone buildSai Hari Chandana Kalluri2019-12-091-0/+71
| | | | | | | | Create psm-firmware recipe for standalone build. PSM is a PS Management unit responsible for controlling the power islands, error processing and other control functions within the PS. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* plm_2019.2.bb: recipe to build plm standaloneSai Hari Chandana Kalluri2019-12-091-0/+71
| | | | | | | | Add recipe to build plm as standalone component. plm is platform loader and manager for versal devices.It performs boot and configuration of the Versal ACAP device. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* newlib: export CC_FOR_TARGET as CCAlejandro Enedino Hernandez Samaniego2019-12-091-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Newlibs Makefiles use a variable CC_FOR_TARGET to build libraries for the TARGET machine (as opposed to CC_FOR_BUILD). We pass CC on our compile function, which is normally use to build, although in this case, the configure script is trimming CC and using simply gcc for the target machine, basically taking out the TUNE variables we pass in CC as well, such as march, mfloat-abi and such. This causes errors when building applications since CC will try to use hard floating point for example whereas the libc.a from newlib will contain libraries built with the defaults which could be soft floating point for example. e.g.: $ ${CC} a.c real-ld: error: a.out uses VFP register arguments, /usr/lib/libg.a(lib_a-stdio.o) does not. Analizing the object files we can see that one of them uses soft (library) and the other one uses hard floating point (program): $ readelf -A a.out | grep VFP Tag_ABI_VFP_args: VFP registers $ readelf -A usr/lib/libc.a | grep VFP Hence why the linker complains. Pass CC_FOR_TARGET with the contents of CC to override the trimming from the configure script and build newlib with the correct tune. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* zynqmp-pmu.conf: Update to Microblaze v11.0Alejandro Enedino Hernandez Samaniego2019-12-091-1/+1
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* zynqmp-pmu.conf: Upgrade tune to use Microblaze v10.0Alejandro Enedino Hernandez Samaniego2019-12-091-1/+1
| | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* Update recipes for 2019.2 releaseJaewon Lee2019-12-094-4/+5
| | | | | | | | | | | Update u-boot, kernel, ATF, QEMU, pmu-firmware, multimedia recipes for 2019.2 release. The patch also upgrades gcc microblaze, newlib and libgloss versions. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* Add me to the maintainers listSai Hari Chandana Kalluri2019-11-191-0/+1
| | | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Add me to the maintainers listMark Hatle2019-11-181-0/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* meta-xilinx-standalone: Update layer compatibility to warrior releaseAlejandro Enedino Hernandez Samaniego2019-08-161-1/+1
| | | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* Update recipes for Xilinx v2019.1 releaseJaewon Lee2019-08-151-6/+3
| | | | | | | | | | | | | | Update components for 2019.1 release - u-boot-xlnx - linux-xlnx - arm-trusted-firmware - QEMU - recipes-multimedia/vcu - xrt and zocl - pmu-firmware Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* pmu-firmware: Fix pmu-firmware build to include backend code for ZynqMP FPGA ↵Andreas Galauner2019-03-041-0/+3
| | | | | | | | | | | | | | configuration Move the appropriate backend code for the ZynqMP FPGA configuration from the interface subdirectory of the xilfpga library into the src directory so that the files are picked up by the Makefile. Otherwise the FPGA configuration code is non-functional. Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net> Tested-by: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Andreas Galauner <andreas@galauner.de> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* pmu-firmware: Port pmu-firmware recipeAlejandro Enedino Hernandez Samaniego2019-01-011-0/+71
| | | | | | | | | | | | | This patch ports the pmu-firmware recipe from meta-xilinx-bsp to be used with the standalone/baremetal toolchain and also upgrades it to the latest release at this point. The recipe was trimmed down, and a few changes had to be made to make it compatible with the baremetal layer, DEPENDS, pass include dir, license and such. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* newlib: Add xilinx linker to newlib and libglossAlejandro Enedino Hernandez Samaniego2019-01-012-0/+10
| | | | | | | | Modifies the CC variable so the Xilinx linker is found correctly when building newlib and libgloss. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libgloss: Copy libgloss as libxil to avoid linking issuesAlejandro Enedino Hernandez Samaniego2019-01-011-0/+4
| | | | | | | | | | | Upstream gcc expects to have libxil available when linking, we can get the required symbols (weak) from libgloss. We copy libgloss as libxil to comply with upstream behavior and avoid linking errors. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* Adds gcc bbappend to fix configure options, and enable --sysroot behaviorAlejandro Enedino Hernandez Samaniego2019-01-011-0/+18
| | | | | Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* meta-xilinx-standalone: Create layer, distro and machine to build standalone ↵Alejandro Enedino Hernandez Samaniego2019-01-014-0/+92
components This layer is meant to augment Yocto/OE functionality to provide a toolchain to build standalone components for Xilinx architectures. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>