Thanks for your help. Unfortunatly there are few progress. I change in the global dts of the board the state of all the i2c descriptor from disable to okay and the device i2c-0 to 3 appear in linux, unfortunatly i2cdetect does'nt see the device on address 68 i2c@1c000 { compatible = "amlogic,meson-axg-i2c"; status = "disabled"; reg = <0x00 0x1c000 0x00 0x20>; interrupts = <0x00 0x27 0x01>; #address-cells = <0x01>; #size-cells = <0x00>; clocks = <0x02 0x18>; phandle = <0x12d>; }; I try a lot of tracks with the overlay but nothing change. And it's very difficult to debug and understand what is missing dtoverlay is not available nothing in syslog during boot and quite frankly I have'nt experience in dts design. the only information is the schematic of the board which describe pin3(40pins connector) =GPIOX_17 and pin5 =GPIOX_18 of the processor. inside the processor the route between the ports and the software is a mystery for me (mux adress of register ...) and how to link all that in the dtbo. Thanks if you can give me some direction ?

OK, I'm getting somewhere, I think -- with your help. I went ahead and flashed the image, which took fine: TIM-1.0 mv_ddr-devel-g4a3dc09 DDR4 16b 1GB 1CS WTMI-devel-18.12.1-a3e1c67 WTMI: system early-init SVC REV: 5, CPU VDD voltage: 1.213V Setting clocks: CPU 1200 MHz, DDR 750 MHz CZ.NIC's Armada 3720 Secure Firmware 14f39dd (Feb 24 2026 19:59:06) Running on ESPRESSObin Ultra NOTICE: Booting Trusted Firmware NOTICE: BL1: v2.14.0(release):1d5aa93 NOTICE: BL1: Built : 19:59:08, Feb 24 2026 NOTICE: BL1: Booting BL2 NOTICE: BL2: v2.14.0(release):1d5aa93 NOTICE: BL2: Built : 19:59:11, Feb 24 2026 NOTICE: BL1: Booting BL31 NOTICE: BL31: v2.14.0(release):1d5aa93 NOTICE: BL31: Built : 19:59:12, Feb 24 2026 U-Boot 2026.01-g127a42c7257a (Feb 24 2026 - 19:57:59 +0000) DRAM: 1 GiB Core: 59 devices, 27 uclasses, devicetree: separate WDT: Not starting watchdog@8300 Comphy chip #0: Comphy-0: USB3_HOST0 5 Gbps Comphy-1: PEX0 5 Gbps Comphy-2: SATA0 6 Gbps Target spinup took 0 ms. AHCI 0001.0300 32 slots 1 ports 6 Gbps 0x1 impl SATA mode flags: ncq led only pmp fbss pio slum part sxs PCIe: Link up MMC: mmc@d8000: 0 Loading Environment from SPIFlash... SF: Detected mx25u3235f with page size 256 Bytes, erase size 4 KiB, total 4 MiB OK Model: Globalscale Marvell ESPRESSOBin Ultra Board MMC Device 1 not found Net: eth0: ethernet@30000 [PRIME] Hit any key to stop autoboot: 0 My attempt to target the drive for boot was using scsi via so: => scsi scan scanning bus for devices... Device 0: (0:0) Vendor: ATA Prod.: ORICO Rev: Y090 Type: Hard Disk Capacity: 976762.3 MB = 953.8 GB (2000409265 x 512) => setenv scsi_fdt_name "/boot/dtb/marvell/armada-3720-espressobin-ultra.dtb" => setenv scsiboot "scsi dev 0; ext4load scsi 0:1 $kernel_addr_r $image_name;ext4load scsi 0:1 $fdt_addr_r $scsi_fdt_name;setenv bootargs $console root=/dev/sda1 rw rootwait net.ifn" => scsi info Device 0: (0:0) Vendor: ATA Prod.: ORICO Rev: Y090 Type: Hard Disk Capacity: 976762.3 MB = 953.8 GB (2000409265 x 512) => run scsiboot Device 0: (0:0) Vendor: ATA Prod.: ORICO Rev: Y090 Type: Hard Disk Capacity: 976762.3 MB = 953.8 GB (2000409265 x 512) ... is now current device 36991488 bytes read in 580 ms (60.8 MiB/s) 13472 bytes read in 6 ms (2.1 MiB/s) ## Flattened Device Tree blob at 06f00000 Booting using the fdt blob at 0x6f00000 Working FDT set to 6f00000 Using Device Tree in place at 0000000006f00000, end 0000000006f0649f Working FDT set to 6f00000 Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.12.68-current-mvebu64 (build@armbian) (aarch64-linux-gnu-gcc (Ubuntu 13.3.0-6ubuntu2~24.04) 13.3.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #5 SMP PREE6 [ 0.000000] KASLR enabled Trying again to load from the SATA M/B-key drive, via SCSI, perhaps I'm confusing myself or the SATA is not properly initializing? It looks as if we get pretty far -- if i leave the USB drive plugged in.. but i'm assuming that is taking /dev/sda1, which is why we're not finding a rootfs... but i'm obviously missing how to engage and/or reference the SATA drive, then? [ 3.098515] usb-storage 1-1.1:1.0: USB Mass Storage device detected [ 3.105468] scsi host0: usb-storage 1-1.1:1.0 [ 4.132658] scsi 0:0:0:0: Direct-Access Generic- SD/MMC 1.00 PQ: 0 ANSI: 0 CCS [ 4.484329] sd 0:0:0:0: [sda] 3907584 512-byte logical blocks: (2.00 GB/1.86 GiB) [ 4.492568] sd 0:0:0:0: [sda] Write Protect is off [ 4.498058] sd 0:0:0:0: [sda] No Caching mode page found [ 4.503387] sd 0:0:0:0: [sda] Assuming drive cache: write through [ 4.532225] sda: sda1 [ 4.535092] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 4.549528] FAT-fs (sda1): IO charset iso8859-1 not found [ 4.564748] FAT-fs (sda1): IO charset iso8859-1 not found [ 4.572867] List of all partitions: [ 4.576509] 0100 48000 ram0 [ 4.576522] (driver?) [ 4.582715] 1f00 3968 mtdblock0 [ 4.582724] (driver?) [ 4.589256] 1f01 64 mtdblock1 [ 4.589262] (driver?) [ 4.595906] 1f02 64 mtdblock2 [ 4.595912] (driver?) [ 4.602444] b300 7636800 mmcblk0 [ 4.602450] driver: mmcblk [ 4.609231] b301 7635776 mmcblk0p1 89708921-01 [ 4.609238] [ 4.616022] b308 4096 mmcblk0boot0 [ 4.616027] (driver?) [ 4.622811] b310 4096 mmcblk0boot1 [ 4.622817] (driver?) [ 4.629596] 0800 1953792 sda [ 4.629602] driver: sd [ 4.635695] 0801 1953761 sda1 169d3094-01 [ 4.635701] [ 4.642048] No filesystem could mount root, tried: [ 4.642051] ext3 [ 4.646922] ext4 [ 4.648837] ext2 [ 4.650757] vfat [ 4.652672] xfs [ 4.654592] [ 4.657900] Kernel panic - not syncing: VFS: Unable to mount root fs on "/dev/sda1" or unknown-block(8,1)

Hi i have done a few boxes with armbian installed, some boxes wifi do not work but that is to be expected.But i got a amlogic box now that is giving me intrm error,It seems i can boot armbian and it loads up but after the loading it just get stuck at intrims.This has somethnig to do with the boot process from sd card.When i boot it form usb stick it works fine but the same setup from sd card gives me that error. I suspect the second part to boot the os is controlled by the box,I need to have first boot all the time What can i do to modify the sd card.

@KV1 I'm happy I'm able to help. I got a lot of help originally from @Pali and by the time we sorted out that the bootloader was the problem it seems that people have largely given up on these devices. It is a shame because they are actually quite good routers (except the wifi). You are actually the first person with an Ultra to reach out. OK, that's looking good. It means the bootloader image works for you and you should be safe to flash it if you want. The messages you posted above are indeed kernel output. To be clear, you don't have to have a more recent kernel to get the device to boot, but DVFS (frequency scaling) may not work without the patch to enable 1.2Ghz clock speed. If you run a kernel without that patch, everything will still work it will just run at full speed all the time which isn't very energy efficient. You are now at the stage where you have to consider how Armbian configures and packages the kernel for this device and ensure that your U-Boot configuration is using a supported boot flow. For example, U-Boot can support loading the kernel as an UEFI image directly (EFISTUB) among many other variations. The messages you posted above suggest that the device tree that is getting loaded may be incorrect/old and I would probably start by examining that. I don't know much about Armbian, but @Igor may also be able to point you in the right direction. Feel free to post your u-boot configuration here too as that could provide some insight into the boot process being used.

Thanks @bschnei! Yes, using the prebuilt image from your release worked -- the base mmc installation boots fine. And i do have the Espressobin-Ultra model. I still end up stuck in the Armbian (from SATA) build at: [ 1.580359] PM: genpd: Disabling unused power domains [ 1.585946] Waiting for root device /dev/sda1... [ 1.606664] usb 1-1: New USB device found, idVendor=1a40, idProduct=0101, bcdDevice= 1.11 [ 1.614861] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 1.621998] usb 1-1: Product: USB 2.0 Hub [ 1.626711] hub 1-1:1.0: USB hub found [ 1.630668] hub 1-1:1.0: 4 ports detected [ 11.622348] platform d0070000.pcie: deferred probe pending: platform: wait for supplier /soc/internal-regs@d0000000/phy@18300/phy@1 [ 11.634188] platform d00e0000.sata: deferred probe pending: platform: wait for supplier /soc/internal-regs@d0000000/phy@18300/phy@2 [ 11.645998] platform d0058000.usb: deferred probe pending: platform: wait for supplier /soc/internal-regs@d0000000/phy@18300/phy@0 However, putting it together, i'm guessing this is back to your mention of needing 6.15 or later kernel. Which Debian/Armbian hasn't folded in yet? I'll have to look into whether i can fork the Armbian, back-port the kernel patch. The fact that my build environment ended up with the initial issue makes me wonder if that's going to run into similar issues though. Either way, really appreciate all the work you've done in this space, and the help you're providing!