Looks like the server doesn’t allow access to the directories?
Comes out at 403 forbidden
Nice, seems to work perfectly fine
Doesn’t work for me. Wrote the image to an SD, switched boot mode to SDIO and rebooted. Serial shows boot stopping with “unkown command sysboot”.
Then I tried to flash the irradium firmware and switched to QSPL mode. Same result.
1 Like
mara
June 2, 2024, 8:03pm
30
thanks,
I’ll check on my board the image should be loaded into SDIO 0 1
2 Likes
I double checked, it is on SD and also booted the original debian image from another SD and that worked.
1 Like
mara
June 3, 2024, 5:26pm
32
everything loads fine
U-Boot SPL 2024.04-jh7110 (Jun 01 2024 - 07:38:36 +0300)
DDR version: dc2e84f0.
Trying to boot from MMC2
OpenSBI v1.4
____ _____ ____ _____
/ __ \ / ____| _ \_ _|
| | | |_ __ ___ _ __ | (___ | |_) || |
| | | | '_ \ / _ \ '_ \ \___ \| _ < | |
| |__| | |_) | __/ | | |____) | |_) || |_
\____/| .__/ \___|_| |_|_____/|____/_____|
| |
|_|
Platform Name : StarFive VisionFive 2 v1.3B
Platform Features : medeleg
Platform HART Count : 5
Platform IPI Device : aclint-mswi
Platform Timer Device : aclint-mtimer @ 4000000Hz
Platform Console Device : uart8250
Platform HSM Device : ---
Platform PMU Device : ---
Platform Reboot Device : gpio-restart
Platform Shutdown Device : ---
Platform Suspend Device : ---
Platform CPPC Device : ---
Firmware Base : 0x40000000
Firmware Size : 363 KB
Firmware RW Offset : 0x40000
Firmware RW Size : 107 KB
Firmware Heap Offset : 0x50000
Firmware Heap Size : 43 KB (total), 2 KB (reserved), 9 KB (used), 31 KB (free)
Firmware Scratch Size : 4096 B (total), 328 B (used), 3768 B (free)
Runtime SBI Version : 2.0
Domain0 Name : root
Domain0 Boot HART : 3
Domain0 HARTs : 0*,1*,2*,3*,4*
Domain0 Region00 : 0x0000000010000000-0x0000000010000fff M: (I,R,W) S/U: (R,W)
Domain0 Region01 : 0x0000000002000000-0x000000000200ffff M: (I,R,W) S/U: ()
Domain0 Region02 : 0x0000000040040000-0x000000004005ffff M: (R,W) S/U: ()
Domain0 Region03 : 0x0000000040000000-0x000000004003ffff M: (R,X) S/U: ()
Domain0 Region04 : 0x000000000c000000-0x000000000fffffff M: (I,R,W) S/U: (R,W)
Domain0 Region05 : 0x0000000000000000-0xffffffffffffffff M: () S/U: (R,W,X)
Domain0 Next Address : 0x0000000040200000
Domain0 Next Arg1 : 0x0000000040400000
Domain0 Next Mode : S-mode
Domain0 SysReset : yes
Domain0 SysSuspend : yes
Boot HART ID : 3
Boot HART Domain : root
Boot HART Priv Version : v1.11
Boot HART Base ISA : rv64imafdcbx
Boot HART ISA Extensions : zihpm
Boot HART PMP Count : 8
Boot HART PMP Granularity : 12 bits
Boot HART PMP Address Bits: 34
Boot HART MHPM Info : 2 (0x00000018)
Boot HART MIDELEG : 0x0000000000000222
Boot HART MEDELEG : 0x000000000000b109
U-Boot 2024.04-jh7110 (Jun 01 2024 - 07:38:36 +0300)
CPU: rv64imafdc_zba_zbb
Model: StarFive VisionFive 2 v1.3B
DRAM: 4 GiB
Core: 135 devices, 26 uclasses, devicetree: board
WDT: Not starting watchdog@13070000
MMC: mmc@16010000: 0, mmc@16020000: 1
Loading Environment from SPIFlash... SF: Detected gd25lq128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
StarFive EEPROM format v2
--------EEPROM INFO--------
Vendor : StarFive Technology Co., Ltd.
Product full SN: VF7110B1-2310-D004E000-00001219
data version: 0x2
PCB revision: 0xb2
BOM revision: A
Ethernet MAC0 address: 6c:cf:39:00:26:e3
Ethernet MAC1 address: 6c:cf:39:00:26:e4
--------EEPROM INFO--------
starfive_7110_pcie pcie@2b000000: Starfive PCIe bus probed.
starfive_7110_pcie pcie@2c000000: Starfive PCIe bus probed.
In: serial@10000000
Out: serial@10000000
Err: serial@10000000
Net: eth0: ethernet@16030000, eth1: ethernet@16040000
starting USB...
Bus xhci_pci: Register 5000420 NbrPorts 5
Starting the controller
USB XHCI 1.00
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Working FDT set to ff72e9b0
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
** File not found /boot.bmp **
** Booting bootflow 'mmc@16020000.bootdev.part_3' with script
Boot script loaded from mmc 1:3
155 bytes read in 2 ms (75.2 KiB/s)
41931 bytes read in 8 ms (5 MiB/s)
24173912 bytes read in 764 ms (30.2 MiB/s)
Working FDT set to 46000000
Failed to load '/dtb/starfive/overlay/starfive-fixup.scr'
4862806 bytes read in 207 ms (22.4 MiB/s)
## Loading init Ramdisk from Legacy Image at 46100000 ...
Image Name: uInitrd
Image Type: RISC-V Linux RAMDisk Image (gzip compressed)
Data Size: 4862742 Bytes = 4.6 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 46000000
Booting using the fdt blob at 0x46000000
Working FDT set to 46000000
Loading Ramdisk to fe27c000, end fe71f316 ... OK
Loading Device Tree to 00000000fe209000, end 00000000fe27bfff ... OK
Working FDT set to fe209000
Starting kernel ...
CCACHE: DataError @ 0x00000000.080227F8
CCACHE: DataFail @ 0x00000000.080227F4
debugfs: Directory '16008000.dma-controller' with parent 'dmaengine' already present!
designware-i2s 100e0000.i2s: probe with driver designware-i2s failed with error -110
designware-i2s 120b0000.i2s: probe with driver designware-i2s failed with error -110
designware-i2s 120c0000.i2s: probe with driver designware-i2s failed with error -110
cdns-csi2rx 19800000.csi: probe with driver cdns-csi2rx failed with error -22
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
Invalid ELF header magic: != ELF
1 Like
Normally it should boot once you put maras firmware on it. I had similar issues with the default firmware which seems to expect very specific layout and boot information that the irradium image doesn’t seem to have
1 Like
But I did exactly that and it complained with the sysboot error I provided earlier. And, I’m in some matrix chat group where other guys encountered the same issue. I should have recorded the serial output but I forgot. I’ll try it again perhaps on the weekend and report back with the logs.
1 Like
That’d be great, I think you can also try to reset the boot environment in openSBI (interrupt bootup in openSBI prompt) since if I recall correctly it sometimes forgets the boot order setting it should have when updating the firmware for the first time.
Should do the trick maybe
1 Like
thanks for that hint, I’ll try that if it fails again!
btw: does irradium use the new opensource rogue driver and mesa or still the binary blob?
1 Like
mara
June 4, 2024, 3:33pm
37
The latest available version from patchwork is used
2 Likes
Sorry for the late replay, didn’t make it earlier. So I now removed my NVME and switched to SDIO boot via the switches. Then booted a fresh debian SD to make sure that things work. That was successful. Then I flashed a new SD with irradium and tried to boot. First boot failed again. Then I resetted the environment, just as it was said some answers above. This time it worked better and it tried to boot the kernel at least but then errors where thrown and it rebooted automatically. That reboot then got stuck again. Here is the log of all three boot attempts, including the environment reset:
vf2_irradium_boot.txt (29.1 KB)
After that, the debian SD won’t boot anymore. Again resetting the environment and rebooting then works again.
mara
June 15, 2024, 5:49pm
39
According to the log, it loaded irradium, the first reboot is to update the partitions, the second before logging in, a swap file is created, this takes time (depends on the speed of the SD card)
2 Likes
Finally got it to boot!
Thank you for your help!
1 Like