Hello,
After upgrading helios4 I encountered this problem after rebooting:
U-Boot SPL 2019.04-armbian (Jul 03 2024 - 12:20:37 +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: mv_ddr-armada-18.09.2
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 2019.04-armbian (Jul 03 2024 - 12:20:37 +0000)
SoC: MV88F6828-A0 at 1600 MHz
DRAM: 2 GiB (800 MHz, 32-bit, ECC enabled)
MMC: mv_sdh: 0
Loading Environment from EXT4... ** File not found /boot/boot.env **
** Unable to read "/boot/boot.env" from mmc0:1 **
Model: Helios4
Board: Helios4
SCSI: MVEBU SATA INIT
Target spinup took 0 ms.
SATA link 1 timeout.
AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
flags: 64bit ncq led only pmp fbss pio slum part sxs
Net:
Warning: ethernet@70000 (eth1) using random MAC address - e2:6d:a3:83:7f:e1
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/boot.scr
2996 bytes read in 381 ms (6.8 KiB/s)
## Executing script at 03000000
Boot script loaded from mmc
158 bytes read in 369 ms (0 Bytes/s)
28834 bytes read in 691 ms (40 KiB/s)
11165487 bytes read in 2303 ms (4.6 MiB/s)
8551104 bytes read in 1847 ms (4.4 MiB/s)
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
SCRIPT FAILED: continuing...
starting USB...
USB0: MVEBU XHCI INIT controller @ 0xf10f4000
Register 2000120 NbrPorts 2
Starting the controller
USB XHCI 1.00
USB1: MVEBU XHCI INIT controller @ 0xf10fc000
Register 2000120 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning bus 1 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Device 0: device type unknown
... is now current device
I guess the most important part is this:
Wrong Ramdisk Image Format
Ramdisk image is corrupt or invalid
SCRIPT FAILED: continuing...
This happened when linux-image was upgraded from 24.11.0-trunk.403 to 25.2.0-trunk.316 (25.2.0-trunk.343 doesn't work either). To get it working again I unpacked previous kernel and I'm back to 24.11.0-trunk.403. I noticed that this topic
has similar problem. I still got some ideas about how to debug this but I before that I wanted to ask if anyone has encountered this on this board? Did the initrd changed format during upgrade and I have to upgrade uboot (I noticed that FORCE_UBOOT_UPDATE is set to null so I guess installing linux-u-boot-helios4-current_25.2.0-trunk.316_armhf.deb doesn't dd bootloader onto sdcard.
Thanks in advance!
