summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/conf/machine
Commit message (Collapse)AuthorAgeFilesLines
* k3: set console parameter to KERNEL_CONSOLERandolph Sapp26 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>
* conf: machine: am62-lp: Package ECAP Capture overlayJudith Mendez2 days1-0/+1
| | | | | | | | Package k3-am62x-sk-ecap-capture.dtbo for AM62 LP SK to enable ECAP in capture mode. Signed-off-by: Judith Mendez <jm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62a: Fix overlays in KERNEL_DEVICETREE_PREFIXJudith Mendez2 days1-1/+7
| | | | | | | | There have been changes in k3-am62x* overlays due to conflicts in DT, so update KERNEL_DEVICETREE_PREFIX for AM62A SK appropriately. Signed-off-by: Judith Mendez <jm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-beagle: move all beagle board configurationsRandolph Sapp2026-03-023-71/+0
| | | | | | | | | | | | | | | Move all beagle board configurations to meta-beagle. There are 2 skews currently: 1. A base TI configuration setting all the default variables required to use the device with meta-ti-bsp provided packages. 2. An override that uses meta-beagle BSP components. This includes all the values defined in the TI skew as well as any meta-beagle specific configuration. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am62dxx-evm: Package k3-am62a7-sk-e3-max-opp overlayParesh Bhagat2026-02-261-0/+1
| | | | | | | | Package k3-am62a7-sk-e3-max-opp.dtbo for AM62D2-EVM to configure C7x DSP to run at its maximum supported frequency of 1GHz. Signed-off-by: Paresh Bhagat <p-bhagat@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>
* conf: j722s: Add usbdfu tie-test-builds configRyan Eatmon2026-02-191-0/+8
| | | | | | | | Using the new UBOOT_CONFIG flow, enable a mode where additional uboot configurations can be built along side the main config. In this case, turning on USBDFU for a board for testing purposes. 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>
* conf: am64: Add ECDSA key signingRyan Eatmon2026-02-192-2/+31
| | | | | | Add support for signing the u-boot files with an ECDSA key. 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>
* recipes-bsp: Remove TI TAD5212 DAC firmware recipeParesh Bhagat2026-02-121-1/+1
| | | | | | | | | TAD5212 now uses a dedicated driver instead of the PCM6240 driver, making the firmware files no longer needed. So remove the recipe and corresponding changes. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* recipes-bsp: Add TI PCM6240 ADC firmware recipeVishnu Singh2026-02-121-1/+1
| | | | | | | | | Add PCM6240 ADC firmware recipe for am62dxx-evm to support 2 PCM6240 ADC's, each supporting 4 channel recording. Signed-off-by: Vishnu Singh <v-singh1@ti.com> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am62p: Add ECDSA key signingRyan Eatmon2026-02-022-5/+29
| | | | | | | Use the new framework to add alternative key signing for the am62p platform as an example. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am65: Add usbdfu tie-test-builds configRyan Eatmon2026-01-231-0/+6
| | | | | | | | Using the new UBOOT_CONFIG flow, enable a mode where additional uboot configurations can be built along side the main config. In this case, turning on USBDFU for a board for testing purposes. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am62: Add usbdfu tie-test-builds configsRyan Eatmon2026-01-234-0/+33
| | | | | | | | Using the new UBOOT_CONFIG flow, enable a mode where additional uboot configurations can be built along side the main config. In this case, turning on USBDFU for a board for testing purposes. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot: Adapt to upstream change to UBOOT_CONFIG flowRyan Eatmon2026-01-205-6/+6
| | | | | | | | | | A recent change to the UBOOT_CONFIG flow in oe-core [1], introduced support for UBOOT_FRAGMENTS. We need to stop using our internal UBOOT_CONFIG_FRAGMENTS and start using the new UBOOT_FRAGMENTS. [1] https://git.openembedded.org/openembedded-core/commit/?id=cd9e7304481b24b27df61c03ad73496d18e4d47c 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>
* beaglebadge-ti: Add support for BeagleBadgeJudith Mendez2025-12-191-0/+21
| | | | | | | | | Add support for the BeagleBadge which is an AM62L based device that requires new build configuration for U-Boot and TF-A sources. Signed-off-by: Judith Mendez <jm@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* am62xxsip-evm: Update for 6.18 and 2026.01Ryan Eatmon2025-12-192-0/+3
| | | | | | | | The name of the u-boot defconfig changed when it was upstreamed into 2026.01, and the name of the dtb changed to k3-am6254atl-sk.dtb in the kernel. 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-193-6/+1
| | | | | | | | | | | | | 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-1919-74/+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>
* u-boot: Remove defaults for UBOOT_SUFFIX and SPL_BINARYAndrew Davis2025-12-191-1/+0
| | | | | | | | | | | These were set to the defaults we would expect from OMAP class U-Boot, but as all board families set these including the OMAP class MACHINEs we can remove these defaults. This helps in the cases that we do not want to define one of these, such as SPL_BINARY in the case of OMAP-L138 which does not use SPL. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove remaining K3 HS machinesAndrew Davis2025-12-1910-86/+0
| | | | | | | | | | | | | | | Every MACHINE build deploys a tiboot3.bin file for all three K3 security types (GP, HS-FS, HS-SE). These extra MACHINE configs existed to select a different default. As U-Boot now selects a default for us this logic does not need to exist here. Instead if one wants to use a non-default security type for an EVM then can simply rename the tiboot3.bin file in the boot partition. Testing automation already handles this and Sitara- family devices have dropped the dedicated MACHINE configs, do the same for Jacinto-family devices. 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>
* conf: machine: j722s: Fix overlay name in KERNEL_DEVICETREE_PREFIXAnurag Dutta2025-11-171-1/+1
| | | | | | | | | | | Currently, the overlay mentioned in KERNEL_DEVICETREE_PREFIX in case of j722s is "k3-am625-sk-mcspi-loopback" which is incorrect as it has been renamed recently. Change the overlay to "k3-am62x-sk-mcspi-loopback" in order to carry out SPI loopback tests successfully. Fixes: 3b2097d72758 ("conf: machine: j722s: Change overlay in KERNEL_DEVICETREE_PREFIX") Signed-off-by: Anurag Dutta <a-dutta@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62dxx-evm: Package eHRPWM overlaycicd.master.202511060939Paresh Bhagat2025-11-051-0/+1
| | | | | | | | Package eHRPWM overlay for am62dxx-evm by reusing the existing overlay for am62a7-sk. Signed-off-by: Paresh Bhagat <p-bhagat@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>
* conf: machine: Include MCSPI overlay for am62p and am62 LPJudith Mendez2025-10-272-0/+2
| | | | | | | | | MCSPI overlay can be used for all am62* SK boards as well as am62p SK, so include the overlay for am62p and am62 LP SK builds since it is not included in the default configuration. Signed-off-by: Judith Mendez <jm@ti.com> 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>
* conf: am335x-evm and am437x-evm: Bump up max_leb_cntTelukula Jeevan Kumar Sahu2025-10-242-2/+2
| | | | | | | New features added require another increase to max_leb_cnt Signed-off-by: Telukula Jeevan Kumar Sahu <j-sahu@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62dxx-evm: Package overlaysParesh Bhagat2025-10-241-0/+1
| | | | | | | | Package overlays which are common for AM62 family of devices for am62dxx-evm by adding prefix string in KERNEL_DEVICETREE_PREFIX. Signed-off-by: Paresh Bhagat <p-bhagat@ti.com> 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>
* machine: Add FIT_CONF_DEFAULT_DTB for legacy platformsRyan Eatmon2025-10-103-0/+3
| | | | | | | | | | As of u-boot 2025.10, the fit image requires a value for the default configuration. The change [1] introduced the FIT_CONF_DEFAULT_DTB code to the legacy fitimage class, but failed to set values for the legacy platforms. This led to us putting default = "" in the .its file, which is now an error. 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-269-8/+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-1815-22/+14
| | | | | | | | | | | | | | | 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-266-0/+28
| | | | | | | | | | | | 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>
* meta-ti-bsp: conf: drop BL32_BASE override for am62lxx-evmBryan Brattlof2025-08-251-2/+0
| | | | | | | | The BL32_BASE address is properly set in TF-A to jump to OP-TEE's entrypoint for the am62lxx SoC family, so we can safily drop this. Signed-off-by: Bryan Brattlof <bb@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 20:48:53 +0000