aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2019-01-01u-boot-zynq-uenv.bb: Handle IMAGE_BOOT_FILES wildcard patternsNathan Rossi
Handle IMAGE_BOOT_FILES having wildcard patterns for dtbs. This requires that the recipe depend on the deployment of the dtbs in order for the correct file names to be expanded. This change also improves the parsing of the IMAGE_BOOT_FILES variable and splits out the python functions for doing this into a separate image-wic-utils.bbclass file. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01machine-xilinx-qemu.inc: Remove KERNEL_DEVICETREE parsingNathan Rossi
Remove the parsing of KERNEL_DEVICETREE as by default those values will be populated into the IMAGE_BOOT_FILES variable. Also add a note describing why wildcard patterns work in the QB_DTB field. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01machine-xilinx-default.inc: Add dtb files for IMAGE_BOOT_FILESNathan Rossi
Add all available dtb sources to the IMAGE_BOOT_FILES variable. For device-tree recipe generated dtbs the files available are only known after they files are deployed, so a wildcard pattern is used for these files. Note that this pattern appears before the kernel device trees due to the preference to use custom non-kernel device trees where available. This ordering is needed so that recipes like u-boot-zynq-uenv can pick the first device tree to select as the default. The kernel device trees are specifically selected based on the value of KERNEL_DEVICETREE, this avoid the duplication of kernel image type prefixed files along side having the actual files that the kernel builds. Additionally remove all instances of "${MACHINE}.dtb" as they no longer need to be specified and are incorrect due to the nesting of the files in the `devicetree` directory. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01machine-xilinx-default.inc: Default IMAGE_BOOT_FILES using functionNathan Rossi
Replace the definition of IMAGE_BOOT_FILES in machine-xilinx-board.inc with the use of a function which automatically selects available images that should be included. This includes the existing implementation of `get_dtb_list` and replaces it with a function that covers all image files including the existing default for KERNEL_IMAGETYPE(S) and UBOOT_BINARY. Also remove the use of `get_dtb_list` from individual machines which is replaced by the default value. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01get_dtb_list function which formats the dtb files properly before adding to ↵Franz Forstmayr
IMAGE_BOOT_FILES Replaced the hard-coded devicetree files in IMAGE_BOOT_FILES with a function, which formats the KERNEL_DEVICETREE list properly. Signed-off-by: Franz Forstmayr <f.forstmayr@gmail.com> Reviewed-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01layer.conf: Add thud as LAYERSERIES_COMPATManjukumar Matha
Add thud as LAYERSERIES_COMPAT Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01tune-versal.inc: Add support for versal devicesManjukumar Matha
Add tune file supporting versal devices. Xilinx is introducing Versal, an adaptive compute acceleration platform (ACAP), built on 7nm FinFET process technology. Versal ACAPs combine Scalar Processing Engines, Adaptable Hardware Engines, and Intelligent Engines with leading-edge memory and interfacing technologies to deliver powerful heterogeneous acceleration for any application. The Versal AI Core series has five devices, offering 128 to 400 AI Engines. The series includes dual-core Arm Cortex™-A72 application processors, dual-core Arm Cortex-R5 real-time processors, 256KB of on-chip memory with ECC, more than 1,900 DSP engines optimized for high-precision floating point with low latency Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01machine-xilinx-default.inc: set libgles1, libgles2 and egl to libmali-xlnxVineeth Chowdary Karumanchi
zynqmpeg and zynqmpev devices has Mali400, overrides extended with mali400.This patch sets preferred providers to libmali-xlnx. Signed-off-by: Vineeth Chowdary Karumanchi <vineethchowz.chowdary@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01meta-xilinx-contrib/linux-firmware_%.bbappend: Remove license setupNathan Rossi
The cypress license setup and packaging is now available in the base recipe and does not need to be appended. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01meta-xilinx-contrib/u-boot: Remove minized appendsNathan Rossi
The minized board is supported in the v2018.07 of u-boot which is the default provided by oe-core/meta. This includes all the configuration provided by the patch. Note however that neither upstream u-boot nor the patch in meta-xilinx-contrib provided ps7 init files for this board which makes the HAS_PLATFORM_INIT incorrect, as it will result in a boot.bin being built which does not include ps7 init configuration and thus will not boot correctly. As such this change also removes the boot.bin setup and use in the machine configuration to prevent the dependency on platform init files which are not available. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01microzed-zynq7: Change to using device tree from kernelNathan Rossi
Change the microzed board to use the device tree from the kernel. This device tree was added in in kernel v4.10 and was pulled into the meta-xilinx layer to resolve some usb issues in commit 8e01359125. With all kernel recipes being at or beyond v4.10 using the kernel source is straight forward and removes any issues caused by differences between the in kernel and the copied version. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01conf/machine: Prepend 'devicetree' directory for device-tree usersNathan Rossi
Prepend the 'devicetree' subdirectory in IMAGE_BOOT_FILES for machines that use the device-tree recipe. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01device-tree: Consolidate device-tree recipe and appendNathan Rossi
With the introduction of devicetree.bbclass in oe-core/meta, remove the implementation of device tree compilation from device-tree.bb keeping the meta-xilinx specific information and licensing. Also consolidate the device-tree.bb and device-tree.bbappend. The only differences between the existing device-tree.bb implementation and the devicetree.bbclass implementation is the device trees are deployed in a "devicetree/" subdirectory within the deployed images directory. Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01*-zynqmp.conf: Add variables to provide paths of pmu-firmare deploymentManjukumar Matha
When building pmu firmware using multiconfig setup, the binaries can be deployed in different build directory. Provide variables to set the binaries in the required path for QEMU. Fix SPL dependency on pmu-firmware. Since the pmu-firmware is being built as a part of multiconfig provide variables to fetch appropriate pmu-firmware binaries. Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01zynqmp-pmu: Remove class that uses a multilib hack to build standalone ↵Alejandro Enedino Hernandez Samaniego
components The zynqmp-pmu class was being used to build standalone components (PMU) for several devices, with the introduction of the meta-xilinx-standalone layer and the xilinx-standalone distro, this is not necessary anymore. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01pmu-firmware: Port pmu-firmware recipeAlejandro Enedino Hernandez Samaniego
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>
2019-01-01newlib: Add xilinx linker to newlib and libglossAlejandro Enedino Hernandez Samaniego
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>
2019-01-01libgloss: Copy libgloss as libxil to avoid linking issuesAlejandro Enedino Hernandez Samaniego
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>
2019-01-01Adds gcc bbappend to fix configure options, and enable --sysroot behaviorAlejandro Enedino Hernandez Samaniego
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01meta-xilinx-standalone: Create layer, distro and machine to build standalone ↵Alejandro Enedino Hernandez Samaniego
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>
2019-01-01newlib: Remove recipes because they are on oe-coreAlejandro Enedino Hernandez Samaniego
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net> Tested-by: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2019-01-01binutils: rebase microblaze patches for binutils 2.31Alejandro Enedino Hernandez Samaniego
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-08-08u-boot_%.bbappend: Fix the breakage on platform init filesManjukumar Matha
Fix the following error for machines like microzed: ERROR: Nothing PROVIDES 'virtual/xilinx-platform-init' This happens because the contrib recipe is overriding the HAS_PLATFORM_INIT instead of appending the configuration for minized machine. This patch fixes the issue by adding an append. Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-07-18arm-trusted-firmware.inc: Add support for atf to use 2nd UARTJaewon Lee
Add ZYNQMP_CONSOLE flag to EXTRA_OEMAKE to add support for the 2nd UART. If ZYNQMP_CONSOLE is set to cadence or cadence0, it will use UART 0 and if set to cadence1, it will use UART 1. The default value is set to cadence. Change do_configure to perform make clean. Without this change,you must manually clean sstate before building with the new value of ZYNQMP_CONSOLE, which is not the desired behavior. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Bhargava Sreekantappa Gayathri <bhargava.sreekantappa-gayathri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-07-18picozed-zynq7.conf: fix the typo in the include fileNicholas Pillitteri
Fix the typo in the include file, it is missing require/include Signed-off-by: Nicholas Pillitteri <njpillitteri@gmail.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-07-18device-tree.bb: add missing include pathMartin Siegumfeldt
This patch adds a missing include path for generic kernel DTC includes. Signed-off-by: Martin Siegumfeldt <mns@gomspace.com> Reviewed-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-25README.md: Update README to include the newer board supportManjukumar Matha
Update README to include the newer board support Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-25README.building.md: Update the README for building the layerManjukumar Matha
Update the README for building the layer Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-25Update README with SD install steps for ZynqMPMartin Lund
Update README.booting.md to include SD install steps for ZynqMP. There are small but important differences compared to Zynq. Signed-off-by: Martin Lund <malu@gomspace.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-25libmali-xlnx.bb: Add recipe to support MALI 400 binariesManjukumar Matha
This recipe allows user to fetch the MALI 400 binaries from xilinx.com manually and use it with compatible machines based on UltraScale+ for libgles1/libgles2 and egl libraries. Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-21minized-zynq7: Add wireless supportClement Laigle
The Minized has a wireless connectivity (WiFi / Bluetooth). This recipes add drivers to use the murata wireless module. Signed-off-by: Clement Laigle <clement.laigle8@gmail.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-21minized-zynq7.conf: Add support for MiniZed development boardClement Laigle
MiniZed is a single-core Zynq 7Z007S development board Connectivity with Murata "Type 1DX" wireless module - Wi-Fi 802.11b/g/n - Bluetooth 4.1 - BLE (Bluetooth Low Energy) Memory - 512MB DDR3L - 128MB QSPI Flash - 8GB eMMC Interfaces - Dual Pmod (16 GPIO) - Arduino (22 GPIO) - USB 2.0 host Physical interface - Two user LED (Red/Green) - User button - User switch - Reset Only a single microUSB cable is required for power, programming, JTAG and serial terminal for debug. This patch adds machine configuration file for MiniZed board with required setting of board specific yocto variables needed. - linux-xlnx is the kernel provider - u-boot is the u-boot provider which will also generate SPL boot.bin Signed-off-by: Clement Laigle <clement.laigle8@gmail.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-21minized-zynq7: Add u-boot supportClement Laigle
Backport the u-boot MiniZed support from v2018.7 release. Signed-off-by: Clement Laigle <clement.laigle8@gmail.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-21minized-zynq7: Add device-treeClement Laigle
Signed-off-by: Clement Laigle <clement.laigle8@gmail.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-21recipes-multimedia/vcu/*: Set package arch to SOC_FAMILYManjukumar Matha
Set package arch of VCU to SOC_FAMILY. Even though VCU hwcodec is available only in ev devices, we are enabling the package for all MPSoC devices. gstreamer is the application used for video pipelining. When the VCU HW is not found, the behaviour will default to using software based gstreamer (in case of cg and eg devices). By making package arch common for all zynqmp devices, we can use the same sstate-cache and RPM feeds for gstreamer components. Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-21kernel-module-mali.bb: Set compatible and package arch according to SOC_VARIANTManjukumar Matha
MALI 400 is available only for eg and ev devices. Set compatible string and package arch to reflect the same. Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-11conf/machine/*.conf: Add SOC_VARIANT for each machineVineeth Chowdary Karumanchi
Add appropriate SOC_VARIANT for each machine configuration. This is required from the introduction of overrides based on SOC_VARIANT. Available SOC_VARIANT's for UltraScale+ MPSoC: "cg" - Zynq UltraScale+ CG Devices "eg" - Zynq UltraScale+ EG Devices "ev" - Zynq UltraScale+ EV Devices Add SOC_VARIANT to zcu102 board. Default variant is EG device. Add SOC_VARIANT to zcu104 board. Default variant is EV device. Add SOC_VARIANT to zcu106 board. Default variant is EV device. Available SOC_VARIANT's for zynq: "7zs" - Zynq-7000 Single A9 Core "7z" - Zynq-7000 Dual A9 Core Add SOC_VARIANT to zc702 board. Default variant is 7z device. Add SOC_VARIANT to zc706 board.Default variant is 7z device. Add SOC_VARIANT to microzed board.Default variant is 7z device. Add SOC_VARIANT to picozed board.Default variant is 7z device. Add SOC_VARIANT to zedboard board.Default variant is 7z device. Add SOC_VARIANT to zybo board.Default variant is 7z device. Add SOC_VARIANT to qemu-zynq7 board.Default variant is 7z device. Signed-off-by: Vineeth Chowdary Karumanchi <vineethchowz.chowdary@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-11tune-zynq.inc: Set SOC_VARIANT for zynq devices to 7zVineeth Chowdary Karumanchi
zynq-7000 devices are mainly shipped in 2 variants. https://www.xilinx.com/products/silicon-devices/soc/zynq-7000.html#productTable Available SOC_VARIANT's for zynq: "7zs" - Zynq-7000 Single A9 Core "7z" - Zynq-7000 Dual A9 Core This will extend MACHINEOVERRIDES for each device variant as: 7zs --> zynq7zs 7z --> zynq7z This patch sets the default value of SOC_VARIANT to 7z. This can be overriden in machine configuration to match the intended FPGA device. Signed-off-by: Vineeth Chowdary Karumanchi <vineethchowz.chowdary@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-11tune-zynqmp.inc: Set default SOC_VARIANT to egVineeth Chowdary Karumanchi
UltraScale MPSoC is shipped in 3 device variants. https://www.xilinx.com/products/silicon-devices/soc/zynq-ultrascale-mpsoc.html#productTable Available SOC_VARIANT's for zynqmp: "cg" - Zynq UltraScale+ CG Devices "eg" - Zynq UltraScale+ EG Devices (MALI 400) "ev" - Zynq UltraScale+ EV Devices (MALI 400 + VCU) This will extend MACHINEOVERRIDES for each device variant as: cg --> zynqmpcg eg --> zynqmpeg ev --> zynqmpev This patch sets the default value of SOC_VARIANT to eg. This can be overriden in machine configuration to match the intended FPGA device. Signed-off-by: Vineeth Chowdary Karumanchi <vineethchowz.chowdary@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-11machine-xilinx-overrides.inc: Provide override mechanism depending on SoC ↵Alejandro Enedino Hernandez Samaniego
features This patch enables to add overrides depending on the SoC capabilities. UltraScale+ FPGA has different variants of silicon to support different features like MALI400, VCU. Categorically there are three variants: cg devices, eg devices(MALI 400) and ev devices (MALI 400+ VCU) See: https://www.xilinx.com/products/silicon-devices/soc/zynq-ultrascale-mpsoc.html#productTable dr devices are based for UltraScale+ RFSoC This patch allows machineoverides to be extended as zynqmp(cg|eg|ev|dr) and mali400/vcu (based on functionality). This helps in grouping of settings for similar SoC This patch also adds packages to be a part of the feed based on SOC_FAMILY and SOC_VARIANT Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Vineeth Chowdary Karumanchi <vineethchowz.chowdary@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-07zcu104-zynqmp.conf: Add support for ZCU104 evaluation boardJaewon Lee
The ZCU104 Evaluation Kit enables designers to jumpstart designs for embedded vision applications such as surveillance, Advanced Driver Assisted Systems (ADAS), machine vision, Augmented Reality (AR), drones and medical imaging. This kit features a Zynq® UltraScale+™ MPSoC EV device with video codec and supports many common peripherals and interfaces for embedded vision use case. The included ZU7EV device is equipped with a quad-core ARM® Cortex™-A53 applications processor, dual-core Cortex-R5 real-time processor, Mali™-400 MP2 graphics processing unit, 4KP60 capable H.264/H.265 video codec, and 16nm FinFET+ programmable logic. This patch adds machine configuration file for ZCU104 Evaluation Kit with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider which will also generate SPL boot.bin - hwcodec is provided by libomxil-xlnx recipe, this will pull in additional dependencies of VCU kernel modules, control software, firmware binaries Depending on the application need you may want to pass the appropriate CMA size in bootargs or set CONFIG_CMA_SIZE_MBYTES in kernel. While using SPL flow, you may need to provide additional hack to pass the PMU config object. This is similar to all ZU+ boards, due to gap in SPL flow unable to load PMU config object. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-06-07zcu106-zynqmp.conf: Add support for ZCU106 Evaluation KitDevarsh Thakkar
The ZCU106 Evaluation Kit enables designers to jumpstart designs for video conferencing, surveillance, Advanced Driver Assisted Systems (ADAS) and streaming and encoding applications. This kit features a Zynq® UltraScale+™ MPSoC EV device and supports all major peripherals and interfaces, enabling development for a wide range of applications. The included ZU7EV device is equipped with a quad-core ARM® Cortex™-A53 applications processor, dual-core Cortex-R5 real-time processor, Mali™-400 MP2 graphics processing unit, 4KP60 capable H.264/H.265 video codec, and 16nm FinFET+ programmable logic. This patch adds machine configuration file for ZCU106 Evaluation Kit with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider which will also generate SPL boot.bin - hwcodec is provided by libomxil-xlnx recipe, this will pull in additional dependencies of VCU kernel modules, control software, firmware binaries Depending on the application need you may want to pass the appropriate CMA size in bootargs or set CONFIG_CMA_SIZE_MBYTES in kernel. While using SPL flow, you may need to provide additional hack to pass the PMU config object. This is similar to all ZU+ boards, due to gap in SPL flow unable to load PMU config object. Signed-off-by: Devarsh Thakkar <devarsht@xilinx.com> Tested-by: Maulik Desai <maulik.desai@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-05-28layer.conf: Add LAYERSERIES_COMPAT for sumo releaseManjukumar Matha
Add LAYERSERIES_COMPAT for sumo release Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-05-28layer.conf: Add LAYERSERIES_COMPAT for sumo releaseManjukumar Matha
Add LAYERSERIES_COMPAT for sumo release Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-05-28u-boot-xlnx.inc: Remove deploying u-boot-spl.bin for runqemuManjukumar Matha
Due to this change 54e2729ed43f82b8cfd96395fb68e447a9b60f86, zcu102 runqemu does not depend on u-boot-spl.bin. It requires just ATF and u-boot to be present. Hence deploying of u-boot-spl.bin is no longer required. Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-05-28kc705-bitstream_2018.1.bb: Update kc705 bitstreamManjukumar Matha
Update kc705 bitstream for 2018.1 release Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-05-28u-boot-xlnx_2018.1.bb: Add support to build kc705 microblazeelManjukumar Matha
Add the wiring in u-boot-xlnx to compile kc705-microblazeel machine. Tested-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-05-28kc705-microblazeel.conf: Pin providers to Xilinx kernel and u-bootManjukumar Matha
kc705 is tested with Xilinx kernel tree and u-boot, set preferred provider to use the vendor tree rather than upstream version Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-05-28kc705-microblazeel.conf: Add UBOOT_MACHINE to kc705Manjukumar Matha
Due to changes in 1138c5623d3e0c415d18b109ccf6c4f301c173f6, the definiton of UBOOT_MACHINE was removed. This causes the following error ERROR: Nothing PROVIDES 'virtual/bootloader' u-boot-xlnx PROVIDES virtual/bootloader but was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the kc705-microblazeel machine configuration. u-boot PROVIDES virtual/bootloader but was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the kc705-microblazeel machine configuration. u-boot-xlnx-dev PROVIDES virtual/bootloader but was skipped: Either UBOOT_MACHINE or UBOOT_CONFIG must be set in the kc705-microblazeel machine configuration. This is a requried setting, set it to microblaze-generic_config Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
2018-05-25Update to newer commit supporting ATF in SPLManjukumar Matha
U-Boot is now able to boot to ARM Trusted Firmware (ATF). The boot flow is SPL(EL3) loads ATF and full u-boot and jump to ATF(EL3) which pass control to full u-boot(EL2). Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
generated by cgit 1.2.3-korg (git 2.39.0) at 2024-05-01 03:16:16 +0000