summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-bsp/recipes-bsp
Commit message (Collapse)AuthorAgeFilesLines
...
* device-tree: Ensure device-tree is board specificMark Hatle2021-07-141-0/+4
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* fsbl/pmufw/plmfw/psmfw: Switch to BOARDVARIANT_ARCHMark Hatle2021-07-144-8/+12
| | | | | | | | | Issue: CR-1099768 Each of these are really board specific, as each can be configured in many different ways. Switch this to be board specific to avoid conflicts. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* arm-trusted-firmware: Set package as board variant specificMark Hatle2021-07-141-0/+4
| | | | | | | | | Issue: CR-1099768 This package is specific to the BOARD VARIANT, as the console and memory configuration can be set externally of the recipe. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* uboot: These recipes are machine or board specificMark Hatle2021-07-142-2/+14
| | | | | | | | | Issue: CR-1096936 It's possible that the user is NOT using a machine that defines a board, so we need to either use the board(board_variant) or MACHINE outselves. Signed-off-by: Mark Hatle <mark.hatle@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>
* 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: 896584b 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 ids for 2021 releaseSai Hari Chandana Kalluri2021-07-141-1/+1
| | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* u-boot-xlnx: Update commit ids for 2021 releaseSai Hari Chandana Kalluri2021-07-141-2/+2
| | | | | | Update commit ids and branch for 2021 release Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* arm-trusted-firmware: Update commit ids and branch for 2021 releaseSai Hari Chandana Kalluri2021-07-142-3/+5
| | | | | | Update commit id and branch for 2021 release Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* bootgen: Update commit id and branch for 2021 releaseSai Hari Chandana Kalluri2021-07-141-2/+2
| | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Various: Fix eSDK hash changesMark Hatle2021-07-143-0/+3
| | | | | | | | | | | | 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>
* fsbl/fsbl-firmware: Split the packaging and building of the fsblMark Hatle2021-07-141-0/+67
| | | | | | | | | | | | | | | | | | | | | 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>
* u-boot-zynq-scr: update QSPI/NAND commandsRaju Kumar Pothuraju2021-07-142-35/+21
| | | | | | | | | | | 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>
* u-boot-zynq-scr: Add env variable support to skip loading ramdisk imagesRaju Kumar Pothuraju2021-07-142-3/+4
| | | | | | | | | | | 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>
* u-boot-zynq-scr: Add uEnv.txt support in bootscriptRaju Kumar Pothuraju2021-07-142-1/+19
| | | | | | | 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>
* various: Ensure that DATETIME is no usedMark Hatle2021-07-142-0/+4
| | | | | | | 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>
* plmfw/psmfw: Fix missing do_deploy addtask, and local checkMark Hatle2021-07-142-2/+9
| | | | | | | | 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>
* u-boot-zynq-scr.bb: Use ramdisk.cpio image when switch_root enabledRaju Kumar Pothuraju2021-07-141-1/+3
| | | | | | | | 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>
* embeddedsw; Fixups for missed plm and psm issuesMark 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-143-0/+192
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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>
* boot.cmd.sd.zynqmp: Remove duplicate bootargsSandeep Gundlupet Raju2021-07-141-1/+0
| | | | | | | | Removed duplicate bootargs for SD bootmode and more over this was hardcoded to SD0 controller instead we need to use SDBOOTDEV variable. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* u-boot-zynq-scr.bb: Add PRE_BOOTENV variableRaju Kumar Pothuraju2021-07-141-3/+6
| | | | | | | | | Add PRE_BOOTENV in uboot-zynq-scr to add boot commands into boot.scr. Defining FIT_IMAGE_OFFSET variables for QSPI and NAND. 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>
* u-boot-zynq-scr: Add microblaze support for boot.scrRaju Kumar Pothuraju2021-07-143-10/+23
| | | | | | | | | | Adding microblaze support for boot.scr and moving the generic boot script from petalinux to yocto layers. The generic boot script will read the boot_target variable on uboot and based on the bootmode it will execute the boot commands. Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* u-boot-zynq-scr: remove exit from boot scriptRaju Kumar Pothuraju2021-07-142-16/+0
| | | | | | | | | This patch removes the exit from boot script which is after the boot command. in successfull case boot command gives handoff to kernel and exit never executes. Signed-off-by: Swagath Gadde <swagath.gadde@xilinx.com> Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Rename u-boot-xlnx and linux-xlnx to 2021.1 versionMark Hatle2021-07-141-4/+0
| | | | | | | Both components now have in-development changes that are incompatible with gatesgarth 2020.2 version. Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Updating machine overrides to match new formatJaewon Lee2021-07-141-4/+4
| | | | | | | | | Previously machine override for a soc variant was SOC_VARIANT appended to SOC_FAMILY. A '-' was included in between to align with how versal handles machine overrides. Updating machine overrides to match this format Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* u-boot-zynq-scr.bb: Add PRE_BOOTENV variableRaju Kumar Pothuraju2021-07-141-3/+6
| | | | | | | | Add PRE_BOOTENV in uboot-zynq-scr to add boot commands into boot.scr. Defining FIT_IMAGE_OFFSET variables for QSPI and NAND. Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* u-boot-zynq-scr: Add microblaze support for boot.scrRaju Kumar Pothuraju2021-07-143-9/+273
| | | | | | | | | Adding microblaze support for boot.scr and moving the generic boot script from petalinux to yocto layers. The generic boot script will read the boot_target variable on uboot and based on the bootmode it will execute the boot commands. Signed-off-by: Raju Kumar Pothuraju <raju.kumar-pothuraju@xilinx.com>
* picozed-zynq7.dts: add marvell,88e1510 to eth phyDavid Roman2021-01-281-1/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
* meta-xilinx-bsp: Move uboot-device-tree to meta-xilinx-tools layerVaralaxmi Bingi2021-01-281-78/+0
| | | | | | | | | | | | This component requires xsct, provided by meta-xilinx-tools. It was determined that all components that make use of xsct should be located in meta-xilinx-tools. Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@xilinx.com> Reword commit message Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
* u-boot-xlnx: Fix build error by applying patch from upstream u-boot.Philip Balister2021-01-282-0/+32
| | | | | | | | Signed-off-by: Philip Balister <philip@balister.org> Adjusted where the append is added, and commented when to remove it. Signed-off-by: Mark Hatle <mark.hatle@kernel.crashing.org>
* bootgen: Update commit id for 2020.2 releaseSai Hari Chandana Kalluri2020-11-171-1/+1
| | | | | | | Update bootgen commit id for 2020.2 release git cherry-pick 73c70b5 Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Update commit id and branch for components for 2020.2 releaseSai Hari Chandana Kalluri2020-11-174-4/+4
| | | | | | | | 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>
* Add FPGA bitfile download support in the u-boot.scr.Adrian Fiergolski2020-09-303-1/+21
| | | | | | | It is inspired by u-boot-zynq-uenv.bb Signed-off-by: Adrian Fiergolski <adrian.fiergolski@fastree3d.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* u-boot-zynq-scr.bb: use IMAGE_VERSION_SUFFIX instead of DATETIMEJoerg Hofrichter2020-09-301-4/+2
| | | | | | | | | | | | | | | 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>
* arm-trusted-firmware.inc: use IMAGE_VERSION_SUFFIX instead of DATETIMEJoerg Hofrichter2020-09-301-2/+1
| | | | | | | | | | | | | | | 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>
* uboot-device-tree.bb: Adding building seperate u-boot.dtb supportVaralaxmi Bingi2020-09-081-0/+78
| | | | | | | | | This recipe will enable us to build seperate u-boot dtb from given design and given dtsi/dts file using UBOOT_DTS variable with space seperated. Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Assign a proper SD device to SDBOOTDEV variable.Adrian Fiergolski2020-08-112-0/+4
| | | | | | In case two SD controllers are used, the user can define a proper SDBOOTDEV variable in the machine configuration. Signed-off-by: Adrian Fiergolski <adrian.fiergolski@fastree3d.com>
* ZynqMP+: Use a proper SD device in U-Boot scripts (uEnv, scr).Adrian Fiergolski2020-08-112-6/+16
| | | | | | | | | | | | | | | | | It fixes the u-boot scripts in case a ZynqMP+ SoC comes with two SDHCI controllers. It requires a proper enumeration in the U-Boot Device tree, i.e. mmc0 = &sdhci0; mmc1 = &sdhci1; not mmc0 = &sdhci1; mmc1 = &sdhci0; The second enumeration being a workaround (always boot from mmc0), is not required anymore as u-boot for ZynqMP+ defines 'sdbootdev' environment variable. Moreover, the proper enumeration allows to select proper block device (mmcblk0p2 vs mmcblk1p2) passed as 'root' parameter to kernel. Signed-off-by: Adrian Fiergolski <adrian.fiergolski@fastree3d.com>
* Fix CONFIG_PMUFW_INIT_FILE extension.Adrian Fiergolski2020-08-111-3/+1
| | | | | | | | | The solution with the relative path doesn't work if devtool is involved: getVar returns value of S variable before it gets overwritten by devtool recipe which cause compilation failure. The solution is to use absolute path to the pmu firmware. Signed-off-by: Adrian Fiergolski <adrian.fiergolski@fastree3d.com>
* u-boot-xlnx.inc: Explicitly set builddir pathSai Hari Chandana Kalluri2020-08-111-0/+1
| | | | | | | | | | | | | | | | Previous Yocto releases, builddir path was set in u-boot.inc within poky layer. Since u-boot-xlnx.inc inherits u-boot.inc, makefile configures and compiles u-boot-xlnx in a build directory ( set by B) that is not the source directory. In Dunfell, build directory path is moved from u-boot.inc to u-boot-common.inc which is not inherited in u-boot-xlnx recipes. As a result, during the build, makefile configures and compiles u-boot-xlnx from source directory resulting in the following error: tmp/work/zcu102_zynqmp-xilinx-linux/u-boot-xlnx/v2020.01-xilinx-v2020.1+gitAUTOINC+86c84c0d0f-r0/git is not clean, please run 'make mrproper' To fix the error, set builddir path (B) explicitly within u-boot-xlnx.inc Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* arm-trusted-firmware.inc: Update package versionSai Hari Chandana Kalluri2020-05-181-1/+1
| | | | | | Update atf package version for 2020.1 Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* Update commit ids for 2020.1 releaseSai Hari Chandana Kalluri2020-05-184-8/+8
| | | | | | Update commit ids and branches for atf,u-boot,linux-xlnx,vcu Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* versal confs: cleaning up unnecessary file loading in runqemu commandJaewon Lee2020-05-081-1/+0
| | | | | | | | | | | | | | | | Removing dtb fatload in boot.scr and removing unnecessary image, dtb, rootfs loading in runqemu command dtb is being loaded through boot.bin for versal so fatload through boot.scr and loading into memory through runqemu commands are not necessary (before this change dtb was essentially being loaded three times) image will be fatloaded through boot.scr (provided in sd image) rootfs is provided through sd image Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* removing kc705 patchVaralaxmi Bingi2020-04-041-1137/+0
| | | | | | | | | | The original patch is intended for kc705-trd designs. Now xilinx is not supporting any kc705-trd designs and yocto/petalinux is not using this patch so, removing this patch from this layer. Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* u-boot-xlnx.inc:u-boot-xlnx_2020.1.bb: kc705 patchVaralaxmi Bingi2020-04-042-4/+0
| | | | | | | | This patch will remove the functionality which is adding kc705-trd patch. Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
* u-boot-xlnx:Updating defconfig for all zynq machinesJaewon Lee2020-03-021-5/+1
| | | | | | | Update UBOOT MACHINE defconfig to xilinx_zynq_virt_defconfig instead of using custom machine specifc defconfigs. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
* meta-xilinx-standalone: Add dependencies on python3-dtcMark Hatle2020-02-271-0/+2
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* arm-trusted-firmware.inc: installing elf with standard nameJaewon Lee2020-02-261-2/+3
| | | | | | | Installing the elf with a standard name with PN and SRCPV. Needed for update boot wiring Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-07 00:25:13 +0000