Helios4: attempt to resurrect old board with most recent boot-loader

[igorpecovnik]

Description

Our automated builds are broken as reported. Solution is provided. https://forum.armbian.com/topic/49440-helios4-doesnt-boot-after-upgrading-to-linux-6671-linux-image-current-mvebu_2520-trunk343/#comment-212135

How Has This Been Tested?

Build but does not boot yet.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[iav]

Boot log

BootROM - 1.73

Booting from MMC

U-Boot SPL 2024.04-armbian-2024.04-S695f-Pfcf3-H9530-V68aa-Bb703-R448a (Feb 13 2025 - 00:26:16 +0000)
High speed PHY - Version: 2.0
Detected Device ID 6828
board SerDes lanes topology details:
 | Lane # | Speed |  Type       |
 --------------------------------
 |   0    |   6   | SATA0       |
 |   1    |   5   | USB3 HOST0  |
 |   2    |   6   | SATA1       |
 |   3    |   6   | SATA3       |
 |   4    |   6   | SATA2       |
 |   5    |   5   | USB3 HOST1  |
 --------------------------------
High speed PHY - Ended Successfully
mv_ddr: 14.0.0
DDR3 Training Sequence - Switching XBAR Window to FastPath Window
DDR Training Sequence - Start scrubbing
DDR3 Training Sequence - End scrubbing
mv_ddr: completed successfully
Trying to boot from MMC1


U-Boot 2024.04-armbian-2024.04-S695f-Pfcf3-H9530-V68aa-Bb703-R448a (Feb 13 2025 - 00:26:16 +0000)

SoC:   MV88F6828-A0 at 1600 MHz
DRAM:  2 GiB (800 MHz, 32-bit, ECC enabled)
Core:  30 devices, 20 uclasses, devicetree: separate
MMC:   mv_sdh: 0
Loading Environment from MMC... *** Warning - bad CRC, using default environment

Model: Helios4
Board: Helios4
Net:
Warning: ethernet@70000 (eth1) using random MAC address - 46:ba:85:51:80:03
eth1: ethernet@70000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot.scr
2996 bytes read in 10 ms (292 KiB/s)
## Executing script at 03000000
Boo 1 USB Device(s) found
scanning bus usb3@f8000 for devices... 1 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
scanning bus for devices...
Target spinup took 0 ms.
Target spinup took 0 ms.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
  Device 0: (0:0) Vendor: ATA Prod.: FUJITSU MHW2080B Rev: 0000
            Type: Hard Disk
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
No EFI system partition
Failed to persist EFI variables
No EFI system partition
Failed to persist EFI variables
  Device 1: (1:0) Vendor: ATA Prod.: Hitachi HTS54168 Rev: SB2O
            Type: Hard Disk
            Capacity: 76319.0 MB = 74.5 GB (156301488 x 512)
Target spinup took 0 ms.
Target spinup took 0 ms.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
timeout exit!

On my helios4 this PR not boots, but build from armbian main boots normal.

[igorpecovnik]

but build from armbian main boots normal.

Oh? Damn. I haven't boot Helios4 for years, I didn't even try to boot with a clean code as it was reported in forums that last nightly builds are broken and that u-boot needs some work. Here u-boot works, but then it seems ramdisk format, its size, compression method ... something is not right.

[igorpecovnik]

Could be related to this: #7805