Greetings! I'm looking for a bit of advice.
After numerous attempts, I am unable to get my Star64 board to boot. I'm attempting to run Armbian, including the build by balbes150 ( https://forum.pine64.org/showthread.php?tid=18344) and the build on the Armbian website.
I've read about setting the Component S1804 switches to boot from SD card, which I've tried. I also wrote an image to an eMMC module and tried booting from that (changing the S1804 switches accordingly).
I have a 3amp power supply purchased from Pine.
I'm using the serial console on pins 6, 8 and 10. The only message I ever see is this:
Code: BOOT fail,Error is 0xffffffff
08-18-2023, 08:24 AM
(This post was last modified: 08-18-2023, 08:36 AM by balbes150.)
return the switch to the factory state (flash 0,0) and show the log of the entire UART log from the power-on moment when starting any image from the specified theme (download, unpack and burn to the SD card, do not change anything after recording, connect to Star64 and turn on the power).
Please note, there is no bootloader (u-boot) in my images and they work exclusively in startup mode with built-in u-boot (factory state of the device). If you want to test the launch from an SD card, use Fishwaldo images, they have a built-in u-boot and they can work in both switch position options (SD and flashe).
(08-18-2023, 08:24 AM)balbes150 Wrote: return the switch to the factory state (flash 0,0) and show the log of the entire UART log from the power-on moment when starting any image from the specified theme (download, unpack and burn to the SD card, do not change anything after recording, connect to Star64 and turn on the power).
Please note, there is no bootloader (u-boot) in my images and they work exclusively in startup mode with built-in u-boot (factory state of the device). If you want to test the launch from an SD card, use Fishwaldo images, they have a built-in u-boot and they can work in both switch position options (SD and flashe).
Thanks for the assistance! Returning the switch to factory state got some much more interesting results, however it is still not booting successfully. It occurs to me that this may be because I likely did not successfully update the bootloader according to your post on the Armbian boards. But before I attempt that again, I'll post the UART log:
Code: U-Boot SPL 2021.10 (Jan 19 2023 - 04:09:41 +0800)
DDR version: dc2e84f0.
Trying to boot from SPI
OpenSBI v1.2
____ _____ ____ _____
/ __ \ / ____| _ \_ _|
| | | |_ __ ___ _ __ | (___ | |_) || |
| | | | '_ \ / _ \ '_ \ \___ \| _ < | |
| |__| | |_) | __/ | | |____) | |_) || |_
\____/| .__/ \___|_| |_|_____/|____/_____|
| |
|_|
Platform Name : StarFive VisionFive V2
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 : jh7110-hsm
Platform PMU Device : ---
Platform Reboot Device : pm-reset
Platform Shutdown Device : pm-reset
Firmware Base : 0x40000000
Firmware Size : 288 KB
Runtime SBI Version : 1.0
Domain0 Name : root
Domain0 Boot HART : 1
Domain0 HARTs : 0*,1*,2*,3*,4*
Domain0 Region00 : 0x0000000002000000-0x000000000200ffff (I)
Domain0 Region01 : 0x0000000040000000-0x000000004007ffff ()
Domain0 Region02 : 0x0000000000000000-0xffffffffffffffff (R,W,X)
Domain0 Next Address : 0x0000000040200000
Domain0 Next Arg1 : 0x0000000042200000
Domain0 Next Mode : S-mode
Domain0 SysReset : yes
Boot HART ID : 1
Boot HART Domain : root
Boot HART Priv Version : v1.11
Boot HART Base ISA : rv64imafdcbx
Boot HART ISA Extensions : none
Boot HART PMP Count : 8
Boot HART PMP Granularity : 4096
Boot HART PMP Address Bits: 34
Boot HART MHPM Count : 2
Boot HART MIDELEG : 0x0000000000000222
Boot HART MEDELEG : 0x000000000000b109
U-Boot 2021.10 (Jan 19 2023 - 04:09:41 +0800), Build: jenkins-github_visionfive2-6
CPU: rv64imacu
Model: StarFive VisionFive V2
DRAM: 8 GiB
MMC: sdio0@16010000: 0, sdio1@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 : PINE64
Product full SN: STAR64V1-2310-D008E000-00000021
data version: 0x2
PCB revision: 0xc1
BOM revision: A
Ethernet MAC0 address: 6c:cf:39:00:75:99
Ethernet MAC1 address: 6c:cf:39:00:75:9a
--------EEPROM INFO--------
In: serial@10000000
Out: serial@10000000
Err: serial@10000000
Model: StarFive VisionFive V2
Net: eth0: ethernet@16030000, eth1: ethernet@16040000
switch to partitions #0, OK
mmc1 is current device
found device 1
bootmode flash device 1
** Invalid partition 3 **
Couldn't find partition mmc 1:3
Can't set block device
** Invalid partition 3 **
Couldn't find partition mmc 1:3
Can't set block device
Hit any key to stop autoboot: 0
** Invalid partition 3 **
Couldn't find partition mmc 1:3
Can't set block device
Importing environment from mmc1 ...
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
** Invalid partition 2 **
Couldn't find partition mmc 1:2
Can't set block device
## Warning: defaulting to text format
## Error: "boot2" not defined
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /boot/extlinux/extlinux.conf
Retrieving file: /boot/extlinux/extlinux.conf
332 bytes read in 6 ms (53.7 KiB/s)
1: Armbian
Retrieving file: /boot/uInitrd
24114630 bytes read in 1012 ms (22.7 MiB/s)
Retrieving file: /boot/Image
8085097 bytes read in 342 ms (22.5 MiB/s)
append: root=UUID=309ddfae-1d04-4ad9-83ea-12a45bfa3520 console=ttyS0,115200n8 console=tty0 earlycon=sbi rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 splash plymouth.ignore-serial-consoles
Retrieving file: /boot/dtb/starfive/jh7110-pine64-star64.dtb
48314 bytes read in 13 ms (3.5 MiB/s)
kernel_comp_addr_r or kernel_comp_size is not provided!
SCRIPT FAILED: continuing...
Card did not respond to voltage select! : -110
No EFI system partition
ethernet@16030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@16040000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@16030000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED: -110ethernet@16040000 Waiting for PHY auto negotiation to complete......... TIMEOUT !
phy_startup() failed: -110FAILED:
Yes, you haven't updated the loader. Now you have the correct state of the switch to start the update. Download the update file, write it to the SD card, insert it into Star64 and turn on the power. Wait for the update to finish (about 1-2 minutes) and turn off Star64. You can burn the ArmbianTV image to the same SD card and now it will work. I recommend using the LEGACY version, all the hardware works in it. The CURRENT and EDGE versions are test versions with a new kernel, some of the hardware is not working in them yet. If you need a working browser, I recommend using Alt Linux images, they have a full-fledged browser.
(08-19-2023, 12:33 AM)balbes150 Wrote: Yes, you haven't updated the loader. Now you have the correct state of the switch to start the update. Download the update file, write it to the SD card, insert it into Star64 and turn on the power. Wait for the update to finish (about 1-2 minutes) and turn off Star64. You can burn the ArmbianTV image to the same SD card and now it will work. I recommend using the LEGACY version, all the hardware works in it. The CURRENT and EDGE versions are test versions with a new kernel, some of the hardware is not working in them yet. If you need a working browser, I recommend using Alt Linux images, they have a full-fledged browser.
Thank you once again. I just got Sid Legacy - XFCE booted (though I'm still only using the serial console for now). WiFi is working and all is well thus far.
I've seen a few other places mention that doing an apt update is not advisable. Is that the case for your current build?
My final question would be, is there anything I can do to help test?
(08-19-2023, 09:50 AM)jdoolin Wrote: I've seen a few other places mention that doing an apt update is not advisable. Is that the case for your current build?
My final question would be, is there anything I can do to help test?
you can safely update the system, a different principle of using packages (deb) is used here, this is a standard system from network repositories and it can be updated, install any packages from network repositories without restrictions.
|
