u-boot.git/include/env/ti, branch master

env: ti: k3_dfu: use Kconfig options for addresses

2026-05-29T20:02:18Z

The load addresses for DFU download binaries were hardcoded for K3 devices which required redefinition of such env for boards that deviated from the expected K3 memory map (such as AM6254atl EMV). This patch replaces the hardcoded addresses with their corresponding Kconfig options making the k3_dfu.env more general. Signed-off-by: Anshul Dalal

env: ti: k3_dfu: load only the next stage binary

2026-05-29T20:02:18Z

In the TI's K3 bootflow of tiboot3.bin -> tispl.bin -> u-boot.img: (R5 SPL) (A53 SPL) We currently provide a common dfu_alt_info_ram for both R5 SPL and A53 SPL which is not intuitive in a regular bootflow where each binary should only request it's immediate next stage. This patch updates dfu_alt_info_ram such that the R5 SPL would only request for tispl.bin and A53 SPL would only request u-boot.img. Signed-off-by: Anshul Dalal

ti: Quote board_init in ti_common.env

2026-05-14T21:39:09Z

bootcmd_ti_mmc skips a per-board init hook with: if test -n ${board_init}; then run board_init; fi; The default case is "no board override", i.e. board_init unset. The expression then expands to 'test -n' with no operand and relies on a U-Boot 'test' quirk that treats a missing operand as false to skip the run. Quote the variable so an unset board_init expands to 'test -n ""' and the emptiness check is explicit. Fixes: 8b0619579b22 ("cmd: test: fix handling of single-argument form of test") Signed-off-by: Simon Glass

include: env: ti: move board specific scripts out of ti_common

2026-03-23T15:15:10Z

bootcmd_ti_mmc had cpsw0_qsgmii_phyinit related scripts even though this was only relevant for the j721e/j7200 SoCs. This patch instead factors out those scripts into a generic 'board_init' which is called as part of bootcmd_ti_mmc. This allows boards to more easily add custom behaviour to the ti_mmc bootflow instead of having to modify the ti_common.env file. Signed-off-by: Anshul Dalal

board: ti: j721e,j7200: fix do_main_cpsw0_qsgmii_phyinit

2026-02-16T17:52:02Z

Since commit 27cc5951c862 ("include: env: ti: add default for do_main_cpsw0_qsgmii_phyinit"), the value of the environment variable do_main_cpsw0_qsgmii_phyinit happened to remain '0' and couldn't be changed without user intervention. This behavior is due to the following cyclic dependency: A) ti_common.env sets do_main_cpsw0_qsgmii_phyinit to '0' and its value can only be updated automatically by main_cpsw0_qsgmii_phyinit. B) main_cpsw0_qsgmii_phyinit is defined in j721e.env and it can run only if 'do_main_cpsw0_qsgmii_phyinit' is already '1' which isn't possible unless the user manually assigns the value. Fix the aforementioned cyclic dependency by using board_late_init() to detect the QSGMII Daughtercard and set do_main_cpsw0_qsgmii_phyinit. Additionally, to address the issue of do_main_cpsw0_qsgmii_phyinit being 'undefined' for other platforms, replace: if test ${do_main_cpsw0_qsgmii_phyinit} -eq 1; with: if env exists do_main_cpsw0_qsgmii_phyinit; in ti_common.env. Fixes: 27cc5951c862 ("include: env: ti: add default for do_main_cpsw0_qsgmii_phyinit") Signed-off-by: Siddharth Vadapalli Reviewed-by: Anshul Dalal

include: env: ti: Use .env for environment variables

2025-09-08T14:44:33Z

Add omap common environment variables to .env. We retain the old-style C environment .h files to maintain compatibility with other omap devices that have not moved to using .env yet. Signed-off-by: Anurag Dutta

include: env: ti_common: remove bootm_size

2025-07-22T17:30:14Z

As the size of 64b ARM kernels, DTs, vendor firmware, and initial ram disks continues to grow, the 256MB size limit set aside for image processing by the bootm command has become too small for some K3 reference boards. For ARMv7 removing this limit could introduce issues so move the bootm_size variable to ti_armv7_keystone2.env and remove the limit for any board using a TI K3 SoC. Signed-off-by: Bryan Brattlof

include: configs: omap5: Add support for FDT overlay

2025-02-21T01:12:08Z

As AM57x uses overlays for display and camera interfaces, add support to load DT overlay files to MMC boot. Signed-off-by: Sinthu Raja Signed-off-by: Anurag Dutta

board: ti: am62x_evm: Add android bootflow

2024-10-02T19:33:53Z

Add Android bootflow support for AM62X SK EVM board with new android boot method. To build for AM62x for Android, we use the am62x_a53_android.config fragment when building A53 bootloaders: $ make am62x_evm_a53_defconfig $ make am62x_a53_android.config $ make Co-developed-by: Mattijs Korpershoek Signed-off-by: Mattijs Korpershoek Signed-off-by: Guillaume La Roque Reviewed-by: Mattijs Korpershoek Reviewed-by: Bryan Brattlof

include: env: ti_common: Remove findfdt from bootcmd_ti_mmc

2024-07-16T19:01:46Z

findfdt is used by bootcmd_ti_mmc by default which used to help populate the fdtfile. The users of findfdt from bootcmd_ti_mmc have migrated to ti_set_fdt_env for populating fdtfile; Hence, findfdt can be removed from bootcmd_ti_mmc having no-impact for any platform. Remove findfdt to not print out the warning that gets set after calling ti_set_fdt_env. viz. "echo WARN: fdtfile already set. Stop using findfdt in script" Signed-off-by: Dhruva Gole Signed-off-by: Manorit Chawdhry