summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* licenses: Add INSIDE-Secure LICENSEmaster-wipBeleswar Padhi24 hours2-1/+20
| | | | | | | | Add the INSIDE-Secure LICENSE and update the PKA recipe to use this license. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-pka-fw: Add a recipe to package prebuilt PKA firmwareBeleswar Padhi24 hours3-0/+25
| | | | | | | | Add a recipe to install the PKA firmware in root filesystem needed by sa2_ul driver for PKA operations across all K3 platforms. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-graphics: weston: Remove hyphen from package revisionAndrew Davis24 hours1-1/+1
| | | | | | | | | Seems having hyphens in the revision tag causes issues with RPM packaging. Remove this hyphen. Reported-by: Daniel Schultz <D.Schultz@phytec.de> Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-*: Move KERNEL_BASE_CLASS defaultRyan Eatmon6 days5-7/+8
| | | | | | | | If you are not building a TI machine then KERNEL_BASE_CLASS is not defined and you get a parse error. Move the default setting out of ti-soc.inc and into ti-kernel.inc. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202508010100cicd.master.202508010100LCPD Automation Script6 days4-4/+4
| | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV u-boot-ti-staging_2025.01: SRCREV linux-ti-staging-rt_6.12: SRCREV_ARM32 linux-ti-staging_6.12: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=f59a711599249ecac75fea38b7a15ef9137d650d..e89a348f4618a26812fb353a04ed9532ef890a2f u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=3bcfad6cee95403f7f62dd9d871cc3ea948c0761..743712b9ee4b33cc9739a3cbeb5a8f14ae2ccf35 linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=b5ee9420d81f46861c4f0a172154e477feda1980..60431d6c0e260d0b9404bcf325368a88daeef9ca linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=72f48d59b8f087fa0dd1f1e8c2c0b5bc0baa537c..ce4785d01a0b962c7d9cb12f56dbae02514213eb Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* recipes-graphics: Add weston fix for SGX from meta-aragoAndrew Davis7 days3-0/+106
| | | | | | | | | This change is needed due to the SGX driver, any distro, not just Arago, using a TI SoC with SGX will need this fix, so it should go in meta-ti. Signed-off-by: Andrew Davis <afd@ti.com> Acked-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: convert DTB prefix matching into classcicd.master.202507300100Denys Dmytriyenko13 days6-7/+14
| | | | | | | | | | | Convert devicetree prefix matching functionality into a generic class that can be used by the kernel and wic images. That way dynamically generated KERNEL_DEVICETREE list will be the same when populating /boot dir of rootfs and/or FAT boot partition of a wic image. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: generalize non-vendored DEVICETREE_FILESDenys Dmytriyenko13 days4-9/+6
| | | | | | | | Automatically generate non-vendored DTBs list in DEVICETREE_FILES from vendored KERNEL_DEVICETREE list for all platforms to use. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: move KERNEL_DTBVENDORED settingsDenys Dmytriyenko13 days2-5/+5
| | | | | | | | Move KERNEL_DTBVENDORED settings from the kernel to ti-soc.inc in the config scope. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* pru-icss_git.bb: update to PSSP v6.5.0cicd.master.202507290636Hari Nagalla13 days1-2/+2
| | | | | | | | update to PSSP release v6.5.0. This release is compatible to linux v6.12 and other fixes for RP message size. Signed-off-by: Hari Nagalla <hnagalla@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-beagle: beagle-bsp.inc: Fix versions in commentsAndrew Davis13 days1-5/+5
| | | | | | | | | Minor comment changes, fix versions listed for some items. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* meta-beagle: Remove selectable DT_VENDOR_PREFIXAndrew Davis13 days4-88/+84
| | | | | | | | | | This was used when the DT_VENDOR_PREFIX was different between supported BSP versions. All supported now use the new prefix so drop this var. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* meta-ti: Remove bsp-ti-6_1 and bsp-bb_org-6_1 supportAndrew Davis13 days44-1089/+1
| | | | | | | | | | | | | | | | Remove support for the v6.1 TI and Beagle BSPs. This was originally split into meta-ti-bsp and meta-beagle changes, but there are some hidden interdependencies that made that more painful than needed. Remove v6.1 support from both BSP layers here. This includes packages specific to those BSPs: - TI and BB.org v6.1 Linux kernel - TI and BB.org 2023.04 U-Boot - Rogue GPU driver 23.3 and Mesa 22.3.5 Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf: machine: am64xx: Cleanup assignment whitespaceRyan Eatmon13 days1-1/+1
| | | | | | | | | A recent change in bitbake requires that all variable assignments have whitespace between the variable, the operator and the value. FOO = "1" Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* wic: sdimage-2part-efi: Add variable for adding bootloader optionsRyan Eatmon13 days3-1/+5
| | | | | | | | | | | We have a need for some platforms to add kernel options to the bootloader during wic creation time. Create a new variable and add that to the sdimage-2part-efi.wks.in file so that a machine can override it if needed. Add an override for am64 to point the kernel at console=ttyS2. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-*: Fix support for building legacy HS platformsRyan Eatmon13 days9-4/+880
| | | | | | | | | | | | The legacy HS platforms (am335x-hs-evm, am437x-hs-evm, and am57xx-hs-evm) are not using the new fitImage flow, but the kernels all include the kernel.bbclass which disallows the old fitImage flow. Copy in the last version of the kernel.bbclass and name it kernel_legacyhs.bbclass, and update the machine configs to defined a variable to use as the KERNEL_BASE_CLASS to inherit. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* layer.conf: Drop walnascar compatibilityRyan Eatmon13 days3-3/+3
| | | | | | | Since meta-ti-bsp requires the new fitImage code, we are no longer backwards compatible with walnascar. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202507240100cicd.master.202507240100LCPD Automation Script2025-07-246-8/+8
| | | | | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_DM_FW_VERSION,TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV k3conf: SRCREV linux-ti-staging-rt_6.12: SRCREV_ARM32 linux-ti-staging_6.12: SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=373c2f5646e3947b3b4a340da729288ee3f07833..f59a711599249ecac75fea38b7a15ef9137d650d u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=827c35b4d141865e25d234e3d298614e6c47150c..3bcfad6cee95403f7f62dd9d871cc3ea948c0761 k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=e6abc1b87f1d5bc4c2ab5f1ebfbf5a70e437dcb4..6034420195cf763c9470fb2113810695e5e37a23 linux-ti-staging-rt_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=f0e4f5ca0905956c70779b31663f594c08c6a3bc..b5ee9420d81f46861c4f0a172154e477feda1980 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=78e6abff322081d53c5a685d927476086c9b2846..72f48d59b8f087fa0dd1f1e8c2c0b5bc0baa537c Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* ti-kernel-fitimage: Add missing SUMMARYRyan Eatmon2025-07-171-0/+2
| | | | Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* check_yocto_rules: Add new rules for recent changesRyan Eatmon2025-07-171-2/+3
| | | | | | | | | - The S change needs to skip the APPEND-2 check since S should never have a space in a path. - The UBOOT_VERSION bbappend does not need a guard since we are modifying our own layer. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "conf: machine: k3: disable all fit signing for uboot"Manorit Chawdhry2025-07-161-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | FIT signing was disabled in the past as it was interfering with multi DTB usecase in binman, and it was thought that the binman signing being done is equivalent to UBOOT_SIGN_ENABLE. Though looking at the sources, UBOOT_SIGN_ENABLE is actually used to sign the kernel FIT Image instead and the name UBOOT actually specifies that it's used in tandom with U-boot. During the signing process, mkimage from U-boot is used to pack the kernel FIT Image and along with that, one DTB from U-boot is also passed to the mkimage command. The DTB that gets passed gets the key embedded in it that is used to verify the kernel FIT image at runtime. Now this signed DTB is packed in U-boot by triggering a rebuild with EXT_DTB argument in the U-boot build process. However, this failed as there was a U-boot bug which was not looking at the packed sources properly with the multi DTB usecase. Now that a U-boot fix is available [0], revert that commit which disabled the FIT signing. This reverts commit 9656b79cb557a46d2611b67e7e51702f6da05594. [0]: https://lore.kernel.org/all/20250626-b4-upstream-fix-icssg-fit-v1-1-95eff1c853a4@ti.com/ Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-kernel-fitimage: Add ti-secdevRyan Eatmon2025-07-164-3/+2
| | | | | | | | | | | In order to turn the fitImage signing back on, we need to inherit the ti-secdev class to setup all of the needed signing variables. Remove the inherit ti-secdev from the kernel recipes since the fitImage signing is handled in the ti-kernel-fitimage recipe and not in the kernel recipes anymore. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging-rt_6.12: Need finer control for BRANCHRyan Eatmon2025-07-141-0/+3
| | | | | | | | | | | | | | | | | The CICD flow needs to control the value for BRANCH in order to have the recipe updated with the next SRCREV, but point to the CICD/next branch for initial build/test. With this split in linux-ti-staging-rt we cannot just have an override for BRANCH in the local.conf because it trumps the new BRANCH_ARM32 system. This patch creates an additional "default" variable BRANCH_ARM64 (or not arm32), which can be controlled separately by the CICD flow. Then BRANCH simply is picking between the two and so can be controlled by overrides in the recipe. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging-rt_6.12: Add PV tracking for ARM32Ryan Eatmon2025-07-141-0/+5
| | | | | | | | Since the kernel branches could theoretically drift apart, we need to track the PV of the kernel on the RT branch for the ARM32 platforms as well. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202507140938cicd.master.202507150100cicd.master.202507140938LCPD Automation Script2025-07-141-1/+1
| | | | | | | | Updated the value(s) for: atf: SRCREV_tfa:am62lxx linux-ti-staging-rt_6.12: PV_ARM32 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* u-boot-ti-mainline: Update to version: v2025.07LCPD Automation Script2025-07-121-2/+2
| | | | | | | | Updated the value(s) for: u-boot-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging-rt_6.12: Add ARM32 RT branchBeleswar Padhi2025-07-121-0/+11
| | | | | | | | | | While all ARM64 devices use the same branch for RT and non-RT builds, the ARM32 devices have a separate branch for RT Kernel which is "ti-rt-linux-6.12.y-arm32". Update the BRANCH and SRCREV for ARM32 devices for RT builds. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: u-boot: change tispl_falcon to tifalconAnshul Dalal2025-07-121-2/+2
| | | | | | | | | | | | | | The payload containing ATF, OP-TEE and DM in falcon mode was renamed from 'tispl_falcon.bin' to 'tifalcon.bin' when adapting upstream patches to ti-u-boot[1]. Therefore this patch fixes the same in meta-ti. [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/tree/configs/k3_r5_falcon.config?h=ti-u-boot-2025.01-next#n36 Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: update config fragment for ti-falconAnshul Dalal2025-07-124-4/+4
| | | | | | | | | | | | | The U-Boot config fragment used to enable falcon mode was renamed from 'am62x_r5_falcon.config' to the more generic 'k3_r5_falcon.config' when adapting upstream patches to ti-u-boot[1]. Therefore this patch fixes the same in meta-ti. [1]: 90d2e960b4c at ti-u-boot-2025.01-next Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* classes: remove unused snapshots of FIT image classesDenys Dmytriyenko2025-07-122-1708/+0
| | | | | | | | Remove no longer used snapshots of the kernel and kernel-fitimage classes that were used for the old FIT image processing. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* kernel-fitimage-legacyhs: rename kernel-uboot classDenys Dmytriyenko2025-07-122-1/+1
| | | | | | | | Rename old snapshot of the kernel-uboot.bbclass to indicate it is still being used by the FIT processing for the legacy HS devices. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp, meta-beagle: switch to the new FIT image wrapperDenys Dmytriyenko2025-07-1215-19/+19
| | | | | | | | | | | Switch all kernel recipes and K3 based platforms to use the new FIT image wrapper functionality. Update FIT default DTB entry to not contain vendor dubdir, as it is now handled through a conf prefix. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-kernel-fitimage: extend default FIT image wrapperDenys Dmytriyenko2025-07-121-0/+8
| | | | | | | | | | | | | | | OE-Core provides default FIT image wrapper, but we need to extend it with support for the dynamic devicetree prefix matching. While at it, also use the correct kernel version from PKGV. Both of these use the shared kernel sources tree, hence ensure it's available before any processing. Since old behavior was putting vendor subdir as a sanitized prefix for each DTB entry as "ti_", U-boot expects corresponding config entries to also contain the same - update conf prefix accordingly. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-kernel-devicetree-prefix: use shared kernel sources for prefix matchDenys Dmytriyenko2025-07-121-4/+2
| | | | | | | | | | | | Handle devicetree prefix matching inside the shared kernel sources tree, instead of ${S}. From the kernel recipe perspective, ${S} is just a symlink to the shared kernel sources. But since the new FIT image wrapper is a separate recipe now, it has its own different ${S}. To enable FIT image wrapper to support devicetree prefix matching, it also needs to access the same shared kernel sources. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* beagle-bsp: unset KERNEL_DEVICETREE_PREFIXDenys Dmytriyenko2025-07-121-0/+3
| | | | | | | | | | | | | | | | | | Beagle machines define both static KERNEL_DEVICETREE list and dynamic KERNEL_DEVICETREE_PREFIX matching. But BB.org kernel recipes only use the static list, while TI kernel recipes use dynamic prefix matching by default. Since devicetree lists now need to be used outside of the kernel build, specifically for the new FIT processing wrapper, explicitly unset KERNEL_DEVICETREE_PREFIX to disable dynamic devicetree prefix matching, when BB.org BSPs are selected. This way both kernel build and FIT image wrapper will have the same list of DTBs to handle, based on the BSP selection. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "meta-beagle: linux: Add INSANE_SKIP debug-deps"Denys Dmytriyenko2025-07-122-4/+0
| | | | | | | | | | | | This reverts commit 3e0b29d2e6780d31b1100cc11329601d6c3a8139. As debug-deps QA false-positives were recently fixed in OE-Core/master, we no longer need these INSANE_SKIP. https://git.openembedded.org/openembedded-core/commit/?id=1b85d84c736a0fa5cb27b8716ca37f181464c85a Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: linux: Remove extra dtc flags for DT OverlaysAndrew Davis2025-07-122-11/+0
| | | | | | | | | | This hides issues like missing flags that will cause issues for folks who build or re-build the kernel outside the Yocto environment. It is better to find these issues and fix them at the source in the Linux makefile, not mask issues here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: u-boot: Fix some odd indentingAndrew Davis2025-07-121-5/+5
| | | | | | | | | This file uses both spaces and tabs in different functions which needs fixed at some point. For now at least make sure they are consistent within the same function. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: ti-rtos-fw: Remove unused ti-sci-fw file extra pathAndrew Davis2025-07-121-3/+2
| | | | | | | | Looks to be left over from long ago, now completely unneeded. Remove it and fix some comments while here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-librpmsg-dma: mark it as compatible with K3 platformsDenys Dmytriyenko2025-07-121-0/+2
| | | | | | | | | | | | | As ti-librpmsg-dma depends on ti-rpmsg-char, which is only compatible with K3 platforms, ti-librpmsg-dma should also have the same limitations. This resolves yocto-check-layer failure: ERROR: Nothing PROVIDES 'ti-rpmsg-char' (but .../ti-librpmsg-dma_1.0.bb DEPENDS on or otherwise requires it) ti-rpmsg-char was skipped: incompatible with machine qemux86-64 (not in COMPATIBLE_MACHINE) Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Move UBOOT_VERSION into dynamic layerRyan Eatmon2025-07-103-4/+13
| | | | | | | | | | The gitpkgv class we are using to set UBOOT_VERSION is located in meta-openembedded. We do not want to depend on meta-openembedded to keep meta-ti-bsp as light as possible, and the naming of UBOOT_VERSION is not a requirement, just a nice to have. Dynamic layers allow us to use the class if it is available in the build, but not require it. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202507101051cicd.master.202507101051LCPD Automation Script2025-07-105-7/+7
| | | | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION atf: SRCREV_tfa:am62lxx u-boot-ti-staging_2025.01: SRCREV k3conf: SRCREV linux-ti-staging_6.12: PV,SRCREV Changelogs: ti-linux-fw: https://git.ti.com/cgit/processor-firmware/ti-linux-firmware/log/?qt=range&q=e594deb508a322d5681888d48fbb153953b06ca9..373c2f5646e3947b3b4a340da729288ee3f07833 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c99a1f082ba4970678c9cb5100d13a986e77817c..827c35b4d141865e25d234e3d298614e6c47150c k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=ea9938bf9cafd9c0cb05ef060a713ab4ac72270f..e6abc1b87f1d5bc4c2ab5f1ebfbf5a70e437dcb4 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=34d0b070130a8cd2cddd9260389ad974e8cb8468..78e6abff322081d53c5a685d927476086c9b2846 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* trusted-firmware-a: Bump to latest SHA on upstreamRyan Eatmon2025-07-091-1/+1
| | | | | | | | | We were waiting on a patch [1] to make it to master. Now that it has, move to point the SRCREV to the latest commit. [1] https://git.trustedfirmware.org/plugins/gitiles/TF-A/trusted-firmware-a/+/b1bca91e93d421a9c142c93f38933e0aa5f4bf58 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Move back to tfa upstream except for am62lxxRyan Eatmon2025-07-091-5/+12
| | | | | | | | | | | | | This moves all of the platforms back to the main TFA repository, but still points to the TI fork for the am62lxx platform while we continue to work on upstreaming the needed patches. With the the split into two repositories on two branches we need to also split the LIC_FILES_CHECKSUM into two since the license.rst file is slightly different between the two branches. The upstream master version is newer than the current am62l version. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: recipes-security: optee: Update OP-TEE components to 4.6.0Manorit Chawdhry2025-06-274-8/+8
| | | | | | | Updates optee_os, optee_test, optee_client, optee_examples to 4.6.0 Signed-off-by: Manorit Chawdhry <m-chawdhry@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: move UBOOT_*ADDRESS to top level ti-socAnshul Dalal2025-06-276-24/+6
| | | | | | | | | | Since all k3 and legacy platforms share common load addresses for kernel and initrd in the fitImage, move them to top level ti-soc.inc. No functional change is intended from this patch. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: update fitImage load addressAnshul Dalal2025-06-272-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | | In yocto, the UBOOT_ENTRYPOINT and UBOOT_*LOADADDRESS variables specify the entry point and load addresses for the kernel image and the DTB when creating the fitImage[1]. Currently the load address for the kernel is set to 0x81000000 and 0x83000000 for the DTB for all k3 platforms. However the region 0x80080000 to 0x81880000 is reserved for OPTEE on am62xxsip-evm, leading to boot failure[2] when using the fitImage. This patch fixes the issue by changing the addresses to 0x82000000 for kernel and 0x88000000 for the DTB. This also allows us to load kernel images > 32MiB in size when not using initrd while also making the falcon and standard boot addresses consistent. [1]: https://docs.yoctoproject.org/ref-manual/variables.html#term-UBOOT_ENTRYPOINT [2]: https://raw.githubusercontent.com/ArchUsr64/ti_boot_logs/HEAD/am62xxsip-evm/failures/fitImage_load_addr_issue.log Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62xxsip: update kernel dtbsAnshul Dalal2025-06-271-1/+3
| | | | | | | | | | The new kernel dtb for am62x SiP have been merged to ti-linux-kernel as of f9579207b081 ("arm64: dts: ti: Add support for AM6254xxl SiP SK") on ti-linux-6.12.y-cicd. This patch modifies FIT_CONF_DEFAULT_DTB to pick the new dtb instead. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: optee: add build flags for am62xxsip-evmAnshul Dalal2025-06-272-0/+5
| | | | | | | | | | | | CFG_TZDRAM_START in OPTEE defines it's load address and is used to configure the page tables accordingly. Due to 512MiB DDR limitation of am62x SiP, the memory map has been modified with OP-TEE moved to bottom of DDR after atf to 0x80080000, this requires modifications to the OPTEE's CFG_TZDRAM_START. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: tfa: add build flags for am62xxsip-evmAnshul Dalal2025-06-272-0/+10
| | | | | | | | | | | Due to 512MiB DDR limitation of am62x SiP, the memory map has been modified with OP-TEE moved to bottom of DDR after atf to 0x80080000, this requires modifications to ATF's BL32_BASE. PRELOADED_BL33_BASE has also been updated to 0x82000000 to reflect the updated SPL_TEXT_BASE from u-boot. Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-07 12:31:49 +0000