summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/conf/machine/include
Commit message (Collapse)AuthorAgeFilesLines
* k3: set console parameter to KERNEL_CONSOLERandolph Sapp22 hours2-2/+2
| | | | | | | | | | | | | | | | | | Set the default value of TI_WKS_BOOTLOADER_APPEND to "console=${KERNEL_CONSOLE}" to populate the kernel cmdline console variable for all k3 devices. Also define SERIAL_CONSOLES for am64xx.inc, since it was previously overriding TI_WKS_BOOTLOADER_APPEND directly for this functionality. The KERNEL_CONSOLE variable provided by openembedded-core is a sane default console parameter automatically populated by the first value in the SERIAL_CONSOLES variable. Their UKI and EFI flows already use this variable to ensure the kernel cmdline console value is set to something machine appropriate. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Make ti-6_18 the default BSPRyan Eatmon2026-02-251-1/+1
| | | | | | | Our initial testing is nearing completion and 6.18 is ready to be our default kernel along with 2026.01 uboot. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* trusted-firmware-a: Updates for am62lRyan Eatmon2026-02-191-1/+2
| | | | | | | | | | Change the branch for am62l to ti-tfa-2.14y and change the TFA_PLATFORM for am62l. License-Udpate: am62l branch is now in line with master, so the md5sum changed to match. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-*: Migrate GPU driver version 25.2 -> 25.3Antonios Christidis2026-02-191-0/+4
| | | | | | | | New recipes for GPU DDK 25.3. Update BSP configuration file to package driver, which now supports kernel 6.18. Signed-off-by: Antonios Christidis <a-christidis@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: Change weak assignment of IMAGE_BOOT_FILESRyan Eatmon2026-02-174-4/+4
| | | | | | | | | | | | | Rather than using ?= to default the value of IMAGE_BOOT_FILES, instead use += to add the files we want to the probably empty value. We ran into an issue where the recent ti-core-initramfs changes used += and overrode the ?= in k3.inc, resulting in no boot files being packaged in the wic boot partition. This addresses the issue by ensuring that we never have a situation where the required files are not in the final list. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-core-initramfs: Add TI_CORE_INITRAMFS_EXTRA_INSTALLRyan Eatmon2026-02-121-1/+2
| | | | | | | | | Add TI_CORE_INITRAMFS_EXTRA_INSTALL variable that another layer can use to install additional packages/changes into the initramfs. Setting this variable will also turn on the initramfs even if the platform does not have kernel modules to include. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-core-initramfs: Rework logicRyan Eatmon2026-02-125-28/+32
| | | | | | | | | | | | | | | | | | | | Clean up the logic of the new ti-core-initramfs to reduce the impact on downstream layers. - Flip the logic in the machine .conf files to track the list of required kernel modules for that platform, but if the variable is set to "" then the ti-core-initramfs will not be created. - Redo the logic of when we require creation/usage of the initramfs to just platforms that need it (ie that set TI_CORE_INITRAMFS_KERNEL_MODULES). - Add a big switch to disable the initramfs entirely. In that case, the user is on their own to make sure that the kernel has everything it needs to boot either via config fragments to turn on the needed modules, or by using the TI_CORE_INITRAMFS_KERNEL_MODULES variable to populate their own initramfs. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* j721e: Disable ti-vxe-vde-driver for 6.18Ryan Eatmon2026-01-171-0/+1
| | | | | | | | The ti-vxe-vxd-driver recipe is not building with the 6.18 kernel. Once a new version that addresses this is available we can turn this back on. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: Add support for bsp-ti-6_18 to ti-core-initramfsRyan Eatmon2026-01-124-2/+8
| | | | | | | With the 6.18 we are moving to using an initramfs to provide non-default modules for booting. So add that override to the machines that need it. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Add ti-6_18 for LTS developmentRyan Eatmon2025-12-191-1/+10
| | | | | | | | | | Add entries for ti-6_18 for the upcoming LTS development effort. This includes: kernel: 6.18 u-boot: 2026.01 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti/all: Merge omap-a15.inc into am57xx.incAndrew Davis2025-12-192-53/+47
| | | | | | | | | | As am57xx.inc is now the only user of omap-a15.inc, merge the content of omap-a15.inc into am57xx.inc and remove omap-a15.inc. As we no longer have this common include, also remove "omap-a15" and use "am57xx" in its place. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti/all: Make DRA7xx support a subset of AM57xx supportAndrew Davis2025-12-192-5/+0
| | | | | | | | | | | | | As AM57xx already defined both "dra7xx" and "am57xx" as SOC_FAMILY the AM57xx was effectively a superset MACHINE. Although not all features of AM57xx are needed for DRA7xx, make DRA7xx-EVM use the AM57xx definition. This allows us to still support DRA7xx as the only differences that impact device function are the selection of U-Boot defconfig, DTBs, and OPTEE, all handled by the MACHINE conf file which is left unchanged. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3r5: Remove per-board SYSFW_ variablesAndrew Davis2025-12-191-2/+1
| | | | | | | | | | | | | | These were used back when each board had to select the correct tiboot3.bin to become the default for that board's image. Two things have changed since then, first we deploy all options for tiboot3.bin generated by U-Boot. And second, U-Boot's binman tool now symlinks the most appropriate version of this file for us for the selected U-Boot defconfig file. These are no longer needed so drop them. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3r5: Use UBOOT_BINARY for R5 U-Boot ImageAndrew Davis2025-12-191-6/+2
| | | | | | | | | | | | | | | | As R5 only builds one working image (tiboot3.bin), define this as the "UBOOT_BINARY", even though it was technically build using the SPL build pass in U-Boot. This allows some simplification and removes deploying of a dummy file (u-boot-spl.bin) which is not a usable boot file. It was only deployed as UBOOT_BINARY is not optional and so something needed to be set here. BeagleBone-AI64 already did something similar to this so the overrides in that MACHINE conf can now be removed. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* am62axx.inc: Add TPS6594 regulator and core modules to initramfs imageMoteen Shah2025-12-191-2/+2
| | | | | | | | | Add TPS6594 core and regulator driver modules in the initramfs image so that the SD card can be probed for am62axx as it is dependent on regulator to get the SD card probing and eventually boot from it. Signed-off-by: Moteen Shah <m-shah@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-*: Migrate GPU driver version 24.2 -> 25.2Antonios Christidis2025-11-201-2/+2
| | | | | | | | | | | | | | New recipes for GPU DDK 25.2. Update BSP configuration files with new preferred recipe versions. For the driver recipe, specifically unset the CC variable due to yocto appending CROSS_COMPILE and CC, resulting in a warning for the do_compile task: make[1]: aarch64-oe-linux-aarch64-oe-linux-gcc: No such file or directory Signed-off-by: Antonios Christidis <a-christidis@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* k3: Move from UBOOT_SIGN_ENABLE to KERNEL_FITIMAGE_SIGN_ENABLERyan Eatmon2025-10-281-3/+3
| | | | | | | | | | | A recent change in oe-core [1] allowed for signing the fitImage without signing the uboot files. Since we use binman to sign all of the uboot files, we do not want oe-core to re-sign themm, but we do want the fitImage signed. [1] https://git.openembedded.org/openembedded-core/commit/?id=313ff06fdfec36a09328dbd60471bd53127fabe3 Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* am62axx: Add whitespace to append assignmentRyan Eatmon2025-10-241-2/+2
| | | | | | | Add missing whitespace on append assignment since the list is space separated. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* packagegroup-ti-core-initramfs: ensure TI_INITRAMFS_KERNEL_MODULES is setRyan Eatmon2025-10-241-2/+0
| | | | | | | | | | | | | TI_INITRAMFS_KERNEL_MODULES gets set only for TI platfroms and ends up being undefined otherwise, which breaks parsing in yocto-check-layer and/or in multi-BSP setups. Ensure the variable is defined in the packagegroup, if not already set by the machine configuration. Remove the previous default assignment since we put it in the wrong location. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: conf: machine: include: Build initramfs for all TI SoCs.Moteen Shah2025-10-211-1/+17
| | | | | | | | | Trigger build for initramfs image and package it in the boot partition of all TI SoC's whenever an image recipe is built with upstream kernel(mainline or mainline-next). Signed-off-by: Moteen Shah <m-shah@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: conf: machine: include: Add common module variable for TI ↵Moteen Shah2025-10-214-0/+11
| | | | | | | | | | | Initramfs image Add a new variable in ti-soc.inc which would be populated by individual platforms with the required modules which would later be packaged inside the initramfs image. Signed-off-by: Moteen Shah <m-shah@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add pruprp-fw for AM64xxMD Danish Anwar2025-09-301-1/+1
| | | | | | | | AM64x supports PRP. Add pruprp-fw to AM64xx so that this can be packaged for AM64xx Signed-off-by: MD Danish Anwar <danishanwar@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-extras: Clean upRyan Eatmon2025-09-262-1/+2
| | | | | | | | | | | | | | | | | | | The TI_EXTRAS infrastructure needs a little tweaking to support turning on multiple extra options at the same time. 1) Since TI_EXTRAS can be a space separated list and not a single fixed value, we need to change how we detect when to include the TI_EXTRA values. 2) The tie-jailhouse overrides were being a little too heavy handed. All of the variables that are changed for any given extra feature needs to use the proper variable override. This was most important for the COMPATIBLE_MACHINE settings. 3) Move the ti-extras out of specific machine configs and into the ti-soc so that all machines can use the extras. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa-pvr: Remove need for PVR/SGX display aliasesAndrew Davis2025-09-183-3/+0
| | | | | | | | | | Update mesa-pvr which includes a default set of display controller aliases for the supported display controllers. This means we do not have to manually set the alias for each device here in the integration layer. Remove that here. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Use same version for both UM and KM driverAndrew Davis2025-09-181-8/+2
| | | | | | | | The DRIVER and matching UMLIBS must always match, no need to define a version number for both. Keep this simple and remove the extra defines. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Do not remove gpu MACHINE_FEATURE conditionally on BSP versionAndrew Davis2025-09-1814-21/+13
| | | | | | | | | | | | | | | Setting or removing the gpu MACHINE_FEATURE does not actually change if the GPU driver is built or not. That is done based on the setting of the BSP_{SGX,ROGUE}_{DRIVER,UMLIBS}_{PROVIDER,VERSION} vars. These are default empty for BSP versions without supported GPU drivers, which will correctly cause a fallback to SW rendering when the GPU driver is not available. As the "gpu" MACHINE_FEATURE now has no uses, remove it from all the machine config include files. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Include merged device trees in the list of generated dtbsTelukula Jeevan Kumar Sahu2025-08-262-0/+12
| | | | | | | | | | | | Add support for dtbs that are generated by merging multiple .dtb and .dtbo files in the /boot directory of the root filesystem.These merged device trees are defined in ti-linux-kernel Makefile[1]. Include them using the KERNEL_DEVICETREE_DTBMERGE variable. [1]: https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/tree/arch/arm64/boot/dts/ti/Makefile?h=ti-linux-6.12.y Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-rtos-messageq-test-fw: Add a recipe to package prebuilt IPC firmwareBeleswar Padhi2025-08-211-1/+1
| | | | | | | | | | | | | | | | | The messageq IPC firmware example for AM57xx SoCs is available in ti-linux-firmware repository. Add a recipe to package the prebuilt messageq firmware into the rootfs. Additionally, make sure the firmware for IPU1 rproc is copied into boot partition by updating the dependency in omap-a15 machine conf to the above recipe. This is needed for Early Boot use cases and gets rid of dependency on meta-ti-extras layer. There is no need to deploy the vayu IPC firmware anymore. Remove the deploy task from ti-ipc-rtos recipe. Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add all tiboot3.bin and sysfw.itb variants by wildcardAndrew Davis2025-08-1915-133/+5
| | | | | | | | | | U-Boot generates all the valid versions of tiboot3.bin and sysfw.itb based on the given defconfig. The defaults are also picked based on the board's binman files. No need to duplicate this logic here, simply deploy what U-Boot generates. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-pka-fw: Add a recipe to package prebuilt PKA firmwareBeleswar Padhi2025-08-061-0/+1
| | | | | | | | 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>
* linux-ti-*: Move KERNEL_BASE_CLASS defaultRyan Eatmon2025-08-011-3/+0
| | | | | | | | 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>
* meta-ti-bsp: convert DTB prefix matching into classcicd.master.202507300100Denys Dmytriyenko2025-07-251-0/+8
| | | | | | | | | | | 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 Dmytriyenko2025-07-254-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 Dmytriyenko2025-07-251-0/+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>
* meta-ti: Remove bsp-ti-6_1 and bsp-bb_org-6_1 supportAndrew Davis2025-07-252-22/+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 Eatmon2025-07-251-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 Eatmon2025-07-252-0/+4
| | | | | | | | | | | 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 Eatmon2025-07-251-0/+3
| | | | | | | | | | | | 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>
* 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>
* meta-ti-bsp, meta-beagle: switch to the new FIT image wrapperDenys Dmytriyenko2025-07-122-4/+4
| | | | | | | | | | | 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>
* meta-ti-bsp: linux: Remove extra dtc flags for DT OverlaysAndrew Davis2025-07-121-1/+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>
* conf: machine: move UBOOT_*ADDRESS to top level ti-socAnshul Dalal2025-06-272-4/+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: 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>
* linux: Temporarily backport previous fitimage classesRyan Eatmon2025-06-102-2/+2
| | | | | | | | | | | | | | | 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: 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>
* meta-ti-bsp : Add build support for am62dxx-evmParesh Bhagat2025-05-141-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | The AM62D SoC is a high-performance Digital Signal Processing (DSP) device with a quad-core Cortex-A53 cluster, dual Cortex-R5F cores, and a Cx7 DSP core with Matrix Multiplication Accelerator (MMA). It features a range of peripherals, including multichannel audio serial ports, Ethernet, UARTs, SPI, I2C, USB, and more. This SoC is part of K3-AM62x family, which includes the AM62A and AM62P variants. While the AM62A and AM62D are largely similar, the AM62D is specifically targeted for general-purpose DSP applications, whereas the AM62A focuses on edge AI workloads. A key distinction is that the AM62D does not include multimedia components such as the video encoder/decoder, MJPEG encoder, Vision Processing Accelerator (VPAC) for image signal processing, or the display subsystem. Additionally, the AM62D has a different pin configuration compared to the AM62A, which impacts embedded software development. The EVM board is a low-cost, expandable platform designed for the AM62D2 SoC, having 4GB LPDDR4 RAM, Gigabit Ethernet expansion connectors, audio jacks, USB ports, and more. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: k3: Add OP-TEE firmware TPM example TAAndrew Davis2025-05-131-1/+1
| | | | | | | | | | | This OP-TEE fTPM is a TA from Microsoft containing the reference implementation of the TPM 2.0 Specification. As K3 OP-TEE now has the necessary features supported to run this fTPM, enable it here. This will serve as an example of using OP-TEE on K3 as a TPM without needing an external harware TPM. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-linux-fw: Split firmware in to machine packagesAndrew Davis2025-05-134-4/+4
| | | | | | | | | | | | | | | | | | Firmware, like kernel modules, may be only relevant to a small subset of hardware. Shipping all firmware for all hardware can waste space. For this reason modules are split out into packages, and the same should be done for firmware. What we do currently is change the content of the package itself based on what device we are building for. Having a package change content for each machine means we cannot generate one image that supports multiple machines, nor host a common machine agnostic package repo. Instead we can generate different packages for the different firmwares and only include the firmware packages needed for each machine. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* bsp: u-boot: deploy tispl_falcon.bin to rootfsAnshul Dalal2025-05-131-0/+1
| | | | | | | | | | | | | Falcon boot requires tispl_falcon.bin to be on the same filesystem partition as the fitImage. This patch creates a new u-boot package called 'u-boot-ti-staging-falcon' that is included in IMAGE_INSTALL when ti-falcon is enabled which allows us to deploy the required files to rootfs. 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 2026-03-20 17:02:54 +0000