u-boot.git/board, branch v2025.10

Merge tag 'u-boot-stm32-20250930' of https://source.denx.de/u-boot/custodians/u-boot-stm

2025-09-30T16:47:19Z

CI: https://source.denx.de/u-boot/custodians/u-boot-stm/-/pipelines/27776 - stm32mp1: Fix env_get_location() - stm32mp2: Update register used by BL31 for boot parameter

board: mpfs_icicle: fix pointer assignment in board_fdt_blob_setup()

2025-09-30T16:10:08Z

Correct the assignment in board_fdt_blob_setup() to use *fdtp instead of fdtp, ensuring the caller receives the correct FDT address. This resolves an issue where the device tree pointer was not properly set due to assigning to the local parameter rather than the dereferenced pointer. Fixes: 7c16ebba1ed ("board: mpfs_icicle: implement board_fdt_blob_setup()/board_fit_config_name_match()") Signed-off-by: Jamie Gibbons Reviewed-by: Conor Dooley

Revert "board: st: stm32mp1: Clean env_get_location()"

2025-09-30T14:44:26Z

This reverts commit d37641c61ba212241c38e3fd22f0335fc0bebc96. Restore support for environment storage in EXT4 filesystem on eMMC boot. The previous cleanup incorrectly removed this fallback option which is needed for boards that store their environment in an EXT4 partition. This configuration is OS-specific rather than board-dependent and should remain as it is configurable via menuconfig. Even if it is not described in ST defconfigs people may have enabled it in their defconfig. Signed-off-by: Kory Maincent Reviewed-by: Patrice Chotard

board: rzg2l: Check the DTB pointer passed by the TF-A.

2025-09-25T21:18:34Z

On the RZG2L platform, the advised TF-A (https://github.com/renesas-rz/rzg_trusted-firmware-a/tree/v2.5/rzg2l) does not pass any DTB blob to U-Boot. On the other hand, the RZG2L part of U-Boot expects a DTB to be passed. It means that if one flashes the latest TF-A as well as the mainline U-Boot, it will crash trying to dereference the NULL DTB pointer before outputing anything. Check if the DTB pointer is NULL before trying to use it. Signed-off-by: Mathieu Othacehe Reviewed-by: Marek Vasut

board: phytec: common: Fix missing newline in error message

2025-09-24T13:50:13Z

The error message in phytec_get_product_name() was missing a newline, causing log output to be concatenated with subsequent messages. Add the newline to improve readability. Signed-off-by: Wadim Egorov

board: phytec: phycore_am6xx: Update scriptaddr

2025-09-24T13:50:13Z

After switching our boards to standard boot, we observed that the kernel hangs when booting with the "script" boot method over the network. The original scriptaddr value was copied from ti_common.env and remained unused for some time. On phycore-am62x and phycore-am62ax, however, this address conflicts with the current location where ATF is loaded (CONFIG_K3_ATF_LOAD_ADDR). Move scriptaddr to 0x89100000, directly after fdtoverlay_addr_r. The phycore-am64x is not affected by this issue, but we update it as well to keep all phycore-am6xx boards consistent. Signed-off-by: Wadim Egorov Reviewed-by: Anshul Dalal

MAINTAINERS: Update Luka Perkov's roles

2025-09-23T18:37:40Z

Per a private email, drop Luka Perkov from MAINTAINERS entries. Reviewed-by: Tony Dinh Signed-off-by: Tom Rini

board: phytec: phycore-imx93: Fix i.MX93 voltage modes

2025-09-21T12:09:13Z

Fix support for i.MX93 voltage modes on phyCORE-i.MX93 SoM boards. First of all, Kconfig option CONFIG_IMX9_LOW_DRIVE_MODE is gone since commit c9efcad23741 ("imx93_evk: Remove CONFIG_IMX9_LOW_DRIVE_MODE and ld defconfig") and was replaced by runtime detection mechanism. Thus lets use is_voltage_mode() instead of Kconfig to detect CPU type and select proper voltage mode. Secondly, 1400MHz ND mode (Nominal Drive) requiring 0.85V BUCK voltage was not supported with current power_init_board() PMIC settings. Add check also for this CPU type and set BUCK voltage accordingly. Last but not least, add printf() printouts about PMIC voltage mode to the console. This makes it more apparent and verbose about voltage mode in use. Also our internal tests depend on this printout to catch issues with i.MX93 CPU types and set PMIC voltage modes. Signed-off-by: Primoz Fiser

imx8ulp_evk: Fix ELE FW version print bug

2025-09-21T12:08:26Z

According to latest ELE Get FW version API, the FW version word is defined as below. The patch version only has 4 bits and minor version has 12 bits. However, the codes use 8 bits for patch version and minor version. Add the patch to fix the issue. ELE firmware version [31] - When set indicates a dirty build. [30] - Reserved [29:28] - Hotfix version. [27] - When set, indicate that ELE FW is authenticated and operational. [26:25] - Reserved [24] - When set, indicate that an alternative FW is running. [23:16] - Indicate the major version. This byte is checked against the version set in the fuses to determine if the FW execution can be authorized [15:4] - Indicate the minor version. [3:0] - Indicate the patch version. Signed-off-by: Ye Li Reviewed-by: Peng Fan

board: dhelectronics: Use isascii() before isprint() in dh_read_eeprom_id_page()

2025-09-17T15:06:37Z

The isprint() checks printability across all 256 characters, some of the upper 128 characters are printable and produce artifacts on UART. Call isascii() first to only consider the bottom 7bit ASCII characters as printable, and then check their printability using isprint(). This fixes a rare misprint in case the ID page content is uninitialized or corrupted. Signed-off-by: Marek Vasut Reviewed-by: Christoph Niedermaier