summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp
Commit message (Collapse)AuthorAgeFilesLines
* CI/CD Auto-Merger: cicd.master.202507240100HEADcicd.master.202507240100master-nextmasterHEADLCPD Automation Script8 hours6-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 Eatmon7 days1-0/+2
| | | | Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "conf: machine: k3: disable all fit signing for uboot"Manorit Chawdhry8 days1-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 Eatmon8 days4-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 Eatmon10 days1-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 Eatmon10 days1-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 Script10 days1-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 Script12 days1-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 Padhi12 days1-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 Dalal12 days1-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 Dalal12 days4-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 Dmytriyenko12 days2-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 Dmytriyenko12 days2-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 Dmytriyenko12 days12-16/+16
| | | | | | | | | | | 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 Dmytriyenko12 days1-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 Dmytriyenko12 days1-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>
* meta-ti-bsp: linux: Remove extra dtc flags for DT OverlaysAndrew Davis12 days2-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 Davis12 days1-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 Davis12 days1-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 Dmytriyenko12 days1-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 Eatmon14 days3-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 Script14 days5-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>
* conf: machine: am62xxsip: update u-boot defconfig to am6254xxlAnshul Dalal2025-06-272-3/+5
| | | | | | | | | | | | | | | | | | | As of 35df864a0c26 ("configs: add defconfigs for am6254xxl") in ti-u-boot, new SiP sepcific defconfigs have been added with updated memory maps and OP-TEE load address. This requires changing the UBOOT_MACHINE variables inside machine configs for am62xxsip-evm. Note that AM6254xxl is the OPN for am62x SiP and expands as follows: AM6254XXL |||| |||+-- Feature Lookup (L indicates 512MiB of integrated LPDDR4) ||+--- Clock Speed |+---- Silicon PG Revision +----- Core configuration (4 indicates A53's in Quad core config) Signed-off-by: Anshul Dalal <anshuld@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* pru*-fw: Add AM64x pru firmwaresMD Danish Anwar2025-06-274-1/+25
| | | | | | | | | | | | | | | | | | | Add support for packaging AM64x PRU firmwares separately Previously, AM64x platforms used the same PRU firmware binaries as AM65x (the "am65x-sr2-*" files). This patch updates the recipes to package dedicated AM64x PRU firmware binaries, ensuring that AM64x devices use the correct firmware files. The following changes are made: - Add AM64x-specific firmware binaries to the TARGET lists in the prueth-fw, pruhsr-fw, pruprp-fw, and prusw-fw recipes. - Update COMPATIBLE_MACHINE in pruprp-fw to include "am64xx". - Add new PRU PRP firmware binaries for AM64x, as AM64x now supports PRP mode. Signed-off-by: MD Danish Anwar <danishanwar@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202506251507cicd.master.202506251507LCPD Automation Script2025-06-254-6/+6
| | | | | | | | | | | | | | | Updated the value(s) for: ti-linux-fw: TI_LINUX_FW_SRCREV,TI_SYSFW_VERSION atf: SRCREV_tfa u-boot-ti-staging_2025.01: 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=1ea29f4b3ec17bdc1a3431a014ea5224962dc779..e594deb508a322d5681888d48fbb153953b06ca9 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=c9c21ce31fc557c2f43c4991fcc0a11b1fd90a12..c99a1f082ba4970678c9cb5100d13a986e77817c linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=20778f6c125dc24e62767dc4837d793a0f18c319..34d0b070130a8cd2cddd9260389ad974e8cb8468 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* recipes-bsp: Add TI TAD5212 DAC firmware recipeVishnu Singh2025-06-253-0/+20
| | | | | | | | | | | | | Add TAD5212 DAC firmware images for am62dxx-evm to support two DAC configurations: - tad5212_01.bin: Configures 1 DAC with stereo channel in i2s mode. - tad5212_04.bin: Configures 4 DAC with each having stereo channel support in i2s mode. Signed-off-by: Vishnu Singh <v-singh1@ti.com> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Reviewed-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: ti-rtos-fw: Update IPC firmwares for am62dxxParesh Bhagat2025-06-251-4/+15
| | | | | | | | | Previously, AM62d build reused AM62a's IPC firmwares. Now that dedicated AM62d IPC firmwares are being pushed to ti-linux-firmware repo, package the new IPC firmwares for echo test. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti/all: Remove S where not neededRyan Eatmon2025-06-251-1/+0
| | | | | | | The default setting for S works fine, there is no nead to change the value. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti/all: Handle S when building a subdir of the git repoRyan Eatmon2025-06-252-3/+3
| | | | | | | | | If a recipe is fetching an entire git repo and then just building a single dir, then we need to update S to lock into the sub directory. Easiest fix is to simply append the subdir to whatever the system wants to set S to by default. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti/all: remove S in recipes that fetch from git via setting ↵Ryan Eatmon2025-06-2522-44/+1
| | | | | | | | | | BB_GIT_DEFAULT_DESTSUFFIX Removing all the S = ${WORKDIR}/git assignments works because BB_GIT_DEFAULT_DESTSUFFIX is set to match S from bitbake.conf (which itself is set to match typical tarball releases). Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti/all: set S from UNPACKDIR in recipes that fetch prebuilt filesRyan Eatmon2025-06-251-2/+1
| | | | | | | | | There is no need to have two assignments; also setting S from UNPACKDIR (and not vice versa) is more logical as unpack task comes first, and tasks that come after unpack use S to access unpack results. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti/linux: Update for S changesRyan Eatmon2025-06-254-4/+4
| | | | | | | | | | | The kernel class operates a little differently. The kernel is downloaded and then moved to the "global" shared location and a symlink is created to point to that location. Since we cannot set S = "${WORKDIR}/git" anymore, just choose a new name under UNPACKDIR. The value for BB_GIT_DEFAULT_DESTSUFFIX is the subdir name that is used by default when fetching git repositories, so just use that name. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti: Move filenames to use PKGV instead of PVRyan Eatmon2025-06-251-8/+12
| | | | | | | | We would like to know the git commit for the build by looking at the filenames of u-boot files. Include the value for PKGV in the names of the files instead of PV. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp : ipc: Add RPMsg DMA libraryVishnu Singh2025-06-221-0/+14
| | | | | | | | | | | | | | | | This commit introduces the RPMsg DMA library: RPMsg DMA library (meta-ti-bsp/recipes-ti/ipc): - Provides librpmsg_dma.so shared library. - Includes APIs for: - RPMsg interface initialization - RPMsg-based send/receive communication - DMA heap buffer management - DSP firmware dynamic load/unload Signed-off-by: Vishnu Singh <v-singh1@ti.com> Reviewed-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62pxx: Add support for HS-SE variantTelukula Jeevan Kumar Sahu2025-06-221-0/+3
| | | | | | | | | | | Since ti-u-boot supports HS-SE variant builds[1], Add support in the machine configurations to package this HS-SE variant tiboot3 binary in the built images. [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2025.01&id=75602edad16c840b2611afb9fc0e2718c026bb8a Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti: layer.conf: add compatibility with the new whinlatter releaseHiago De Franco2025-06-221-1/+1
| | | | | | | | | | | | Update all layers with the new Yocto release, fixing the current build error: ERROR: Layer meta-ti-bsp is not compatible with the core layer which only supports these series: whinlatter (layer is compatible with styhead walnascar) Signed-off-by: Hiago De Franco <hiago.franco@toradex.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202506110100cicd.master.202506110100LCPD Automation Script2025-06-113-3/+3
| | | | | | | | | | | | | Updated the value(s) for: atf: SRCREV_tfa u-boot-ti-staging_2025.01: SRCREV linux-ti-staging_6.12: SRCREV Changelogs: u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=1d6ba4a32cdd8c987533d5789b5bc7b84c41fabe..c9c21ce31fc557c2f43c4991fcc0a11b1fd90a12 linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=b0afb35642d79e776a4cf940945367cef87ba127..20778f6c125dc24e62767dc4837d793a0f18c319 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* linux: Temporarily backport previous fitimage classesRyan Eatmon2025-06-1010-7/+1766
| | | | | | | | | | | | | | | A recent set of changes on oe-core has dramatically revamped the fitimage generation code. It is initially unclear how to fold those change into our flow, so in the short term we will copy the previous versions of the kernel bbclass files from a commit before [1] any changes to the class files. As soon as we figure it out, these files will be removed. This just help unblock anyone trying to build on master including meta-ti-bsp. [1] https://git.openembedded.org/openembedded-core/commit/?id=fdb0a51598156f99aa91f7495d7eada92a459e97 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: conf: Package overlay for am62dxx-evmParesh Bhagat2025-06-041-0/+1
| | | | | | | | Package k3-am62a7-sk-edgeai.dtso for am62dxx-evm image. This overlay is required for audio analytics for am62dxx-evm. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* CI/CD Auto-Merger: cicd.master.202505300836cicd.master.202505300836LCPD Automation Script2025-05-306-8/+8
| | | | | | | | | | | | | | | | | | Updated the value(s) for: cnm-wave-fw: LIC_FILES_CHKSUM ti-linux-fw: CNM_WAVE521_FW_VERSION,TI_LINUX_FW_SRCREV atf: SRCREV_tfa 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=c3ad8113c766bee7b8ddfae222e9b8017b565ea3..1ea29f4b3ec17bdc1a3431a014ea5224962dc779 u-boot-ti-staging_2025.01: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/log/?qt=range&q=70667128cb5b2c2a7621965ba948b5a56a2e756f..1d6ba4a32cdd8c987533d5789b5bc7b84c41fabe k3conf: https://git.ti.com/cgit/k3conf/k3conf/log/?qt=range&q=30a1d5b2d08c0da39d4e62b3ebee591a9882fa21..ea9938bf9cafd9c0cb05ef060a713ab4ac72270f linux-ti-staging_6.12: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/log/?qt=range&q=cdcaeac783e31f18edb6cb44b526228f44023b45..b0afb35642d79e776a4cf940945367cef87ba127 Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com>
* mesa-pvr: fold GL ES 3 packages into GL ES 2 onesRyan Eatmon2025-05-291-14/+4
| | | | | | | | | | | | This is a sideport of a patch against mesa in oe-core [1]. OpenGL ES 3 is closely tied to the OpenGL ES 2: there is no separate library, one can use GL ES 2 headers for GL ES 3 app, etc. Instead of having separate packages, merge GL ES 3 packages into GL ES 2 ones. [1] https://git.openembedded.org/openembedded-core/commit/?id=7c0e9c170db93d9af7cc505dcd71c4f3d6c4e9c5 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: am62lxx: Do not deploy extra tiboot3.bin copyAndrew Davis2025-05-281-3/+0
| | | | | | | | | | | For AM62L there is no GP and both HS sub-types are supported by the same TIFS. This means we do not need multiple versions of tiboot3.bin. So no need to deploy an additional version which is identical to the default tiboot3.bin already deployed. Signed-off-by: Andrew Davis <afd@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-24 13:34:27 +0000