summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-core/conf
Commit message (Collapse)AuthorAgeFilesLines
...
| * | meta-xilinx-core: layer.conf: Add AIE preferred versionsMark Hatle2024-04-191-0/+13
| | | | | | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | meta-xilinx-core: xrt: Rename and add older versionsMark Hatle2024-04-191-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Version/rename XRT for the current version. Zocl is tied to XRT, and to the kernel sources. So provide an older XRT/Zocl combination to allow for older configurations. Note, 2022.1 -> 2023.1 do not currently work. Zocl builds, but XRT fails due to issues with gcc 12 and beyond. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | meta-xilinx-conf: Add kernel module preferred versionsMark Hatle2024-04-191-0/+23
| | | | | | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | | meta-xilinx-core: layer.conf: Add AIE preferred versionsMark Hatle2024-04-181-0/+15
| | | | | | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | | meta-xilinx-core: xrt: Add older versionsMark Hatle2024-04-181-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Zocl is tied to XRT, and to the kernel sources. So provide an older XRT/Zocl combination to allow for older configurations. Note, 2022.1 -> 2023.1 do not currently work. Zocl builds, but XRT fails due to issues with gcc 12 and beyond. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | | meta-xilinx-conf: Add kernel module preferred versionsMark Hatle2024-04-171-0/+22
| | | | | | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | | Merge remote-tracking branch 'xilinx/rel-v2024.1' into master-nextMark Hatle2024-04-164-1/+15
|\ \ \ | | |/ | |/| | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | versal-ai-edge-generic: Fix QEMU boot issueSandeep Gundlupet Raju2024-04-091-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | VEK280 SDT QEMU doesn't come up with PLM, this to default QEMU_HW_DTB_PS used from versal-generic.conf file doesn't work for VEK280 machine conf file. Fix QEMU PLM boot issue by setting the right QEMU_HW_DTB_PS to board-versal-ps-vek280.dtb and also adjust the QB_MEM to 12GB to match with board dtsi file, we need set same in QB_MEM for QEMU boot. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | versal-hbm-generic: Fix QEMU boot issueSandeep Gundlupet Raju2024-04-081-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | VHK158 SDT QEMU doesn't come up with PLM, this to default QEMU_HW_DTB_PS used from versal-generic.conf file doesn't work for VHK158 machine conf file. Fix QEMU PLM boot issue by setting the right QEMU_HW_DTB_PS to board-versal-ps-vmk158.dtb and also adjust the QB_MEM to 32GB as versal-vhk158-reva.dts has 32GB set, we need set same in QB_MEM for QEMU boot. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | versal-prime-generic: Fix QEMU PLM boot issueSandeep Gundlupet Raju2024-04-081-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | QEMU PLM error code are observed as shown below. [13422.262]**************************************** [13422.490]Xilinx Versal Platform Loader and Manager [13422.508]Release 2024.1 Mar 30 2024 - 14:13:53 [13422.562]Platform Version: v0.0 PMC: v0.0, PS: v0.0 [13422.588]BOOTMODE: 0x5, MULTIBOOT: 0xF0000000 [13422.608]**************************************** [13427.899]Non Secure Boot [13441.028]PLM Initialization Time [13441.090]***********Boot PDI Load: Started*********** [13441.191]Loading PDI from SD1 [13441.218]Monolithic/Master Device [14850.660]1409.510 ms: PDI initialization time [14850.719]+++Loading Image#: 0x1, Name: lpd, Id: 0x04210002 [14850.755]---Loading Partition#: 0x1, Id: 0xC [14892.625] 41.831 ms for Partition#: 0x1, Size: 11360 Bytes [14893.706]---Loading Partition#: 0x2, Id: 0x0 [14902.163] 7.679 ms for Partition#: 0x2, Size: 65104 Bytes PSM Firmware version: 2024.1 [Build: Mar 30 2024 14:13:53 ] [15013.595]+++Loading Image#: 0x2, Name: pl_cfi, Id: 0x18700000 [15014.589]---Loading Partition#: 0x3, Id: 0x3 [21947.779]Polling 0xF11A0000 Mask: 0xFFFFFFFF ExpectedValue: 0x14CAA093 [21949.039]MaskPoll: Addr: 0x0F11A0000, Mask: 0xFFFFFFFF, ExpVal: 0x14CAA093, Timeout: 1000000, RegVal: 0x14CA8093 ...ERROR [21951.067]CMD: 0x00040101 execute failed, Processed Cdo Length 0x84 [21952.260]CMD Payload START, Len:0x00000004 0x00000000F20000A8: 0xF11A0000 0xFFFFFFFF 0x14CAA093 0x00000001 0x00000000F20000B4: [21954.516]CMD Payload END [21955.035]Error loading PL data: CFU_ISR: 0x00000000, CFU_STATUS: 0x0000080C PMC ERR1: 0x00000000, PMC ERR2: 0x00000000 [21957.810]PLM Error Status: 0x21010001 [21958.489]============Register Dump============ [21959.269]PMC_TAP_IDCODE: 0x14CA8093 [21959.887]EFUSE_CACHE_IP_DISABLE_0(EXTENDED IDCODE): 0x00004000 [21960.901]PMC_TAP_VERSION: 0x03000000 [21961.516]CRP_BOOT_MODE_USER: 0x00000005 [21962.179]CRP_BOOT_MODE_POR: 0x00000005 [21962.823]CRP_RESET_REASON: 0x00000202 [21963.462]PMC_GLOBAL_PMC_MULTI_BOOT: 0xF0000000 [21964.242]PMC_GLOBAL_PWR_STATUS: 0x00000000 [21964.946]PMC_GLOBAL_PMC_GSW_ERR: 0x00000000 [21965.666]PMC_GLOBAL_PLM_ERR: 0x00000000 [21966.342]PMC_GLOBAL_PMC_ERR1_STATUS: 0x00000000 [21967.136]PMC_GLOBAL_PMC_ERR2_STATUS: 0x00000000 [21967.917]PMC_GLOBAL_GICP0_IRQ_STATUS: 0x20000000 [21968.713]PMC_GLOBAL_GICP1_IRQ_STATUS: 0x00000000 [21969.507]PMC_GLOBAL_GICP2_IRQ_STATUS: 0x00000000 [21970.307]PMC_GLOBAL_GICP3_IRQ_STATUS: 0x00000000 [21971.113]PMC_GLOBAL_GICP4_IRQ_STATUS: 0x00000000 [21971.921]PMC_GLOBAL_GICP_PMC_IRQ_STATUS: 0x00000000 [21972.767]============Register Dump============ This is due to default QEMU_HW_DTB_PS used from versal-generic.conf file doesn't work for VMK180 machine conf file. Fix QEMU PLM boot issue by setting the right QEMU_HW_DTB_PS to board-versal-ps-vmk180.dtb. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | versal-generic.conf: Update QEMU_HW_DTB_PMCSandeep Gundlupet Raju2024-04-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | Update QEMU_HW_DTB_PMC to use board-versal-pmc-virt.dtb instead of board-versal-pmc-vc-p-a2197-00.dtb as board-versal-pmc-vc-p-a2197-00.dtb dtb targets tenzing board. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | | Merge remote-tracking branch 'xilinx/rel-v2024.1' into HEADMark Hatle2024-04-041-0/+4
|\| | | | | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | machine-xilinx-default.inc: Set default libmetal and openamp providerSandeep Gundlupet Raju2024-03-281-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | Building libmetal and openamp using poky core-image-minimal requires providers, Hence set default libmetal and openamp provider. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | | kernel-module-mali: Version based to match linux-xlnx kernelMark Hatle2024-03-271-0/+3
| | | | | | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | | qemu: Remove versions older then 8.1, no longer compatibleMark Hatle2024-03-271-9/+5
| | | | | | | | | | | | | | | | | | Versions older then 8.1 are no longer compatible with the runqemu. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | | Merge remote-tracking branch 'xilinx/rel-v2024.1' into master-nextMark Hatle2024-03-266-5/+42
|\| | | |/ |/| | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * machine-xilinx-default.inc: use u-boot.elf for MB and ZynqVaralaxmi Bingi2024-03-181-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | For microblaze u-boot not booting on qemu or hw after moving to u-boot 2024.1 rebase branch. Reason explained below: u-boot will provide output files as u-boot.elf, u-boot, u-boot.bin, u-boot-nodtb.bin etc.. For Microblaze and Zynq we are using u-boot output file For aarch64 family we are using u-boot.elf u-boot: which has no relocation inside, then we apply relocation (rela section) over binary. and then copying as u-boot.elf and using it. u-boot.elf: It will relocation inside it and without debug symbols. After recent relocation changes in u-boot we should use u-boot.elf only for all platforms. Signed-off-by: Varalaxmi Bingi <varalaxmi.bingi@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * u-boot: Update version to 2024.01John Toomey2024-02-131-1/+1
| | | | | | | | | | | | | | | | Switch to latest commit on release branch. Also remove unused microblaze header file for 2024.1 release. Signed-off-by: John Toomey <john.toomey@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * linux-xlnx: Move 2024.1 to release branch and commitMark Hatle2024-02-091-1/+1
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * soc-tune-include: Add cortex-r5{,2}hf and cortex-a78 supportMark Hatle2024-02-071-2/+5
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * machine/include/arm: Backport tune files from masterMark Hatle2024-02-073-0/+31
| | | | | | | | | | | | | | | | | | | | Backport the tune files from poky master as of commit: dd4c941e9fe9e0f1b73a934d9ecd0d165ee85474 This adds support for cortex-r5 and cortexr-r52 hard float ABI, as well as cortex-a78. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * linux-xlnx_2023.2: Update to more recent LTS versionMark Hatle2024-01-311-1/+1
| | | | | | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com> (cherry picked from commit 79335c2a8a9a6cfef521a3bddb24865def036050) Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * meta-xilinx-core: virtualization_layer: qemuMark Hatle2024-01-221-0/+3
| | | | | | | | | | | | | | | | | | | | | | Rework the meta-virtualization qemu extensions implemented in the meta-xilinx-core layer. It was found that is a bug in the langdale meta-virtualization. Due to this, we need to use BBMASK to exclude the changes from that layer, and then repeat them, but only for qemu 7.1. qemu 8.1 work is taken from the current master version of meta-virtualization. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * qemu: Add target qemu 8.1.2Mark Hatle2024-01-221-0/+1
| | | | | | | | | | | | | | | | | | | | Backport the QEMU 8.1.x integration from current poky (commit 4bb222e0d71a4cb159b8a4f1a90b65b1af32ac10). Split the additional xen/tpm patches by version, disable Xen patches on the 8.1.2 version, not yet supported. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * qemu: Update to qemu 8.1.0Mark Hatle2024-01-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | Backport the QEMU 8.1.x integration from current poky (commit 4bb222e0d71a4cb159b8a4f1a90b65b1af32ac10). Add Xilinx specific integration. Add required libslirp recipe from current poky. Also update the qemu-devicetree to the latest version. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * Revert "meta-xilinx-core: layer.conf: Temporarily disable kernel-modules-dp"Mark Hatle2024-01-221-2/+0
| | | | | | | | | | | | This reverts commit 6fd65d4b54258e3fe10c8d960fe33af51504f9d4. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * meta-xilinx-core: layer.conf: Temporarily disable kernel-modules-dpMark Hatle2024-01-181-0/+2
| | | | | | | | | | | | | | This module does not currently compile with Linux 6.6. Disable until it works. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * Revert "meta-xilinx-core: layer.conf: Temporarily disable ↵Mark Hatle2024-01-181-3/+0
| | | | | | | | | | | | | | | | kernel-modules-{hdmi,dp}" This reverts commit d26f98b857e30992f43f182c2a07f4b6ef6b3068. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * layer.conf: Move to prefer linux-xlnx 6.6.0Sandeep Gundlupet Raju2024-01-161-1/+1
| | | | | | | | | | | | | | | | linux-xlnx was moved forward to the 6.6.0 version. Adjust the PREFERRED_VERSION to match. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * meta-xilinx-core: layer.conf: Temporarily disable kernel-modules-{hdmi,dp}Mark Hatle2024-01-161-0/+3
| | | | | | | | | | | | | | These two modules do not currently compile with Linux 6.6. Disable until they do work. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * soc-tune-include.inc: Enable tune files for Cortex-R52 processorSandeep Gundlupet Raju2024-01-141-0/+1
| | | | | | | | | | | | | | Enable tune files for Cortex-R52 processor. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * arm-trusted-firmware: update branch and version for 2024.xAkshay Belsare2023-12-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The upstream release versioning is changed from v3.0 to v2.10. Last upstream revision was v2.9. Refer to: https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?h=integration&id=2226b4533c5f1a331f1893b2b3ff09a59c0041dd Updating the TF-A (aka ATF) branch to xlnx_rebase_v2.10 and release version to v2.10 Signed-off-by: Akshay Belsare <akshay.belsare@amd.com> Also change the PREFERRED_VERSION to 2.10. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * meta-xilinx-core: linux-xlnx: Reset 2024.1 for developmentMark Hatle2023-10-311-1/+1
| | | | | | | | | | | | | | 2024.1 has been reset back to 6.1.0 version, but is otherwise functionally similar to the 6.1.30 release from 2023.2. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * meta-xilinx-core: layer.conf: Move to prefer ATF 3.0Mark Hatle2023-10-051-1/+1
| | | | | | | | | | | | | | arm-trusted-firmware was moved forward to the 3.0 version. Adjust the PREFERRED_VERSION to match. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * README: Update README on using ATF_CONSOLESandeep Gundlupet Raju2023-09-071-1/+1
| | | | | | | | | | | | | | Update README on using ATF_CONSOLE instead of ATF_CONSOLE_DEFAULT. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * meta-xilinx-core: Move preferred versions to 2024.1 integrationMark Hatle2023-08-291-1/+5
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | layer.conf: Move from nanbield to scarthgapMark Hatle2024-03-191-1/+1
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | soc-tune-include: Add cortex-r5{,2}hf and cortex-a78 supportMark Hatle2024-03-181-0/+4
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | linux-xlnx_2023.2: Update to more recent LTS versionMark Hatle2024-01-301-1/+1
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | meta-xilinx-core: layer.conf: Default to qemu for arm (32)Mark Hatle2024-01-301-1/+4
| | | | | | | | | | | | | | | | Normally we default to qemu-xlnx (the AMD/Xilinx QEMU fork). However, this fork depends on some functionality not present on 32-bit arm. For on-target qemu we need to use the stock QEMU instead. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | meta-xilinx-core: zynqmp-generic.conf: Use default QB_XILINX_SERIALMark Hatle2023-12-121-1/+3
| | | | | | | | | | | | | | A default (blank) QB_XILINX_SERIAL will fall back to the runqemu default which works correctly for this board. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | layer.conf: Set to nanbieldMark Hatle2023-11-081-1/+1
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | versal-generic.conf: Remove obsolete DTBsMark Hatle2023-10-261-3/+0
| | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | various machines: Change qemu serial port configuration for nanbieldMark Hatle2023-10-266-7/+58
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As of Yocto Project nanbield, if a -serial is pass in QB_OPT_APPEND the runqemu may add additional null entries (padding) or simply skip further setup. Due to this, emulated platforms where the first hardware serial port is not used in Linux need specific "-serial null" settings, but with the new rules also need the real serial port defined (this can no longer be assumed.) The downside of this new approach is all consoles must be defined, so we can not rely on runqemu adding "-serial mon:<device>", as now assume the primary usage is stdio (nographic/serial port) settings. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | meta-xilinx-core: zynq-generic: Remove gdb port usageMark Hatle2023-10-251-1/+0
| | | | | | | | | | | | | | | | | | While including a default gdb in the QEMU configuration might be useful, it does require a static port that will prevent multiple QEMU sessions from running in parallel. If the user wants GDB support, they will need to manually add this on the runqemu command line. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | zynqmp-generic: Ensure qemu-devicetrees is install for qemu usageMark Hatle2023-10-251-1/+1
| | | | | | | | | | | | | | | | testimage requires qemu, qemu requires qemu-devicetrees:do_deploy. Adjust the dependencies to specifically list do_deploy and not the authomatic do_install. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | versal-generic: Fix testimageMark Hatle2023-10-251-2/+2
| | | | | | | | | | | | | | | | qemu-devicetrees and the extracted cdo are required for QEMU booting. These are only populated after do_deploy, so make sure our dependency clearly depends on do_deploy and not the (automatic) do_install. Signed-off-by: Mark Hatle <mark.hatle@amd.com>
* | Merge remote-tracking branch 'origin/rel-v2023.2' into nanbieldMark Hatle2023-10-238-58/+135
|\ \ | | | | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | README: Update README on using ATF_CONSOLESandeep Gundlupet Raju2023-08-311-1/+1
| | | | | | | | | | | | | | | | | | | | | Update README on using ATF_CONSOLE instead of ATF_CONSOLE_DEFAULT. Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com> Signed-off-by: Mark Hatle <mark.hatle@amd.com>
| * | versal-net-generic: Make it clear versal-net is not supported in 2023.2Mark Hatle2023-08-311-0/+2
| |/ | | | | | | Signed-off-by: Mark Hatle <mark.hatle@amd.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-23 14:17:04 +0000