(11-23-2020, 03:22 PM)Bullet64 Wrote: Hi @sigmaris , i am testing your u-boot 2020.10. When i boot from PCIe NVMe SSD boot process stuck @ "Booting using the fdt blob at 0x1f0000".
I've seen a few similar reports of the kernel not booting with recent mainline U-Boot, not just this build. Are you loading the u-boot env from SPI? If so, you could try removing the "usb start" from the "preboot" env variable to avoid initialising USB, as I read that having USB initialised by U-Boot might be related with the kernel not booting.
(11-30-2020, 02:41 PM)Waryle Wrote: Hi @sigmaris , first thanks for your work!
But I have a problem here and I would use some help.
- I have a RockPro64 (I guess rev 2.3)
- a 32Gb Samsung SD Card class 10
- one 120Gb SSD
- two 4Tb HDD
The SSD and the two HDDs are connected using a Ziyituod SATA Card (with a Marvell 88SE9215 chip).
I can install Armbian on the SD card, then use armbian-config to put the system on the SSD while keeping the bootloader on the SD Card.
But I would like to not rely on the SD Card and thus, use SPI to boot directly on the SATA SSD.
- I have downloaded your flash_spi.img.gz (from your 2020.10 release)
- I've extracted the img and wrote it on the SD Card
- I inserted the card into the RockPro64 and booted, then waited for the white led to stop blinking (following your guide : https://github.com/sigmaris/u-boot/wiki/...oot-to-SPI )
- I took the SD Card back, wrote the latest release of Armbian on it
- Booted in Armbian and apt update/upgrade
- I used armbian-config with the "Boot from SPI - Install on SATA" option, installed the system on the SATA SSD
- I accepted for armbian-config to update the bootloader
But when I reboot without the SD Card, the system just won't boot. The RockPro is lighting up as well as the SATA card, but no white LED and no SSH available, even after letting it boot for 20 minutes.
I have tried multiple times with variations (trying to flash_spi.img AFTER installing the system, not accepting armbian-config to update the bootloader, etc...) but to no avail.
Did I miss something or do something wrong?
I'm not exactly sure, as I haven't tried armbian-config myself. Are you able to get logs of the boot process via the UART/serial console? Failing that, U-Boot does now have HDMI support and hopefully would display some messages on a connected HDMI display.
