u-boot.git/board/adi, branch next

arm: sc5xx: Add fdt_addr_r, kernel_addr_r, and ramdisk_addr_r

2026-06-04T18:24:18Z

Add fdt_addr_r, kernel_addr_r, and ramdisk_addr_r to the SC5xx boards. These variables are currently unused in the environment but will be used in the future once support for booti commands is added to the SC5xx boards. Signed-off-by: Caleb Ethridge

arm: sc5xx: add missing boot env selectors

2026-06-04T18:24:18Z

Define the boot options for SC598 SOM EZ-LITE so the shared ADI boot environment includes the expected boot commands for this board. SC598 SOM EZ-LITE board environment utilizes the shared ADI boot environment, but it does not define any of the USE_* boot mode selectors. Without those selectors, the shared env does not generate the board boot commands such as `spiboot`. This leaves the default `bootcmd=run spiboot` without a matching environment command and breaks autoboot. Fixes: c9e893d6266d ("board: adi: Add support for SC598") Signed-off-by: Ozan Durgut Reviewed-by: Simon Glass

arm: sc5xx: Remove SC5XX_LOADADDR

2026-06-04T18:24:18Z

Remove the SC5XX_LOADADDR Kconfig option, replace its users with CONFIG_SYS_LOAD_ADDR, and update the ADI boot environment to use `loadaddr`. SC5XX_LOADADDR was an ADI-specific duplicate of standard U-Boot load address handling. U-Boot already uses CONFIG_SYS_LOAD_ADDR for the default load address and `loadaddr` for boot commands, so keeping separate SC5XX-specific names is redundant. Signed-off-by: Ozan Durgut Signed-off-by: Caleb Ethridge

mach-sc5xx: Update image load address

2026-06-04T18:24:18Z

Update the load address for the image in each environment to match the updated partitions in Linux. The partitions in Linux for the spi are named as follows: - u-boot-spl - u-boot - kernel - rootfs The kernel partition is at 0x100000 for sc59x family boards, and 0xd0000 for all other sc5xx boards. Signed-off-by: Caleb Ethridge

mach-sc5xx: sc573: Rename EZKIT board to EZLITE

2026-06-04T18:24:18Z

Rename the SC573 EZKIT board to EZLITE across the device tree, defconfig, board file, and related Kconfig/Makefile entries to match with release naming. EZKIT was used internally before the official product release. Signed-off-by: Caleb Ethridge Reviewed-by: Simon Glass

mach-sc5xx: Add USB boot command

2026-06-04T18:24:18Z

Add the USB boot command to the environments of the boards that support it. Signed-off-by: Caleb Ethridge

mach-sc5xx: Update boot commands

2026-06-04T18:24:18Z

Update the default boot commands to match the expected bootargs in Linux and new SPI partitioning scheme. Because the environment is no longer stored in the SPI flash, imagesize has been removed and replaced with a fixed length read to load from the SPI. Additionally the partitions of the mmc have been updated. The first partition holds the fitImage at /fitImage, and the second partition contains the rootfs. With this change, the imagefile environment variable has also been eliminated, the image in the first partition is expected to always be named fitImage. Signed-off-by: Caleb Ethridge

mach-sc5xx: Remove update commands from default environment

2026-06-04T18:24:17Z

Remove the update_spi family of commands from the U-Boot environment. These commands are not standard in U-Boot, and boot media programming has moved to Linux, so the commands can be safely removed. Additionally, this commit removes the adi_stage2_offset, adi_rfs_offset, imagefile, jffs2file, and init_ethernet variables that were consumed by the update commands as they are no longer needed. CONFIG_SC5XX_UBOOT_OFFSET and CONFIG_SC5XX_ROOTFS_OFFSET are also removed. Signed-off-by: Caleb Ethridge

board: adi: Fix exception when using standalone SoM

2026-04-22T20:22:33Z

Although less common, ADSP SoM boards can be operated standalone without a carrier board. The SoM can be powered over USB-C by moving the jumper on JP1. The board configuration needs to be heavily refactored to reduce the number of defconfigs and leverage the devicetree. The TI DP83867 support, which is dependent on that configuration, needs to be removed. Until then this change allows the same U-Boot binary to work correctly both with carrier boards and the standalone SoM. The carrier board initialization code in somcrr_ezkit.c and somcrr_ezlite.c calls gpio_hog_lookup_name() to find ethernet control GPIOs, but does not check if the lookup succeeds before using the returned pointers. When running on a standalone SoM without a carrier board, these GPIO hogs do not exist in the device tree. The gpio_hog_lookup_name() function returns -ENODEV and sets the pointer to NULL, but the code continues to call dm_gpio_set_value() with uninitialized pointers, causing a synchronous abort exception: "Synchronous Abort" handler, esr 0x96000004 elr: 00000000960326c4 lr : 0000000096038d5c (reloc) Signed-off-by: Philip Molloy Reviewed-by: Greg Malysa

arm: mach-sc5xx: Align header paths with SYS_SOC convention

2026-04-07T17:32:59Z

Define CONFIG_SYS_SOC in the mach-sc5xx Kconfig. Follow the standard U-Boot include path convention by moving the SC5xx SoC headers from arch/arm/include/asm/arch-adi/sc5xx/ to the conventional arch/arm/include/asm/arch-sc5xx/ location. Update includes from to across mach-sc5xx and board files. Signed-off-by: Philip Molloy