Hi scottfk,
Can you give me the version of u-boot on your board? Ideally the whole boot log would be nice.
Thanks!
Alex
Heya.
I started with the version in your post (fw_payload_jh7100_20211230/u-boot-2022.01-rc4-g0c08d33). That didn’t work, so I upgraded to fw_payload_jh7100_20220311/u-boot-2022.04-rc2. Still didn’t fix the issue, but I left it there.
I’ll reattach it to the serial rig and get you the boot log a bit later today.
/s
Boot log:
> bootloader version:211102-0b86f96
> ddr 0x00000000, 1M test
> ddr 0x00100000, 2M test
> DDR clk 2133M,Version: 211102-d086aee
> 0 crc flash: 7816e82f, crc ddr: 7816e82f
> crc check PASSED
>
> bootloader.
>
> OpenSBI v1.0
> ____ _____ ____ _____
> / __ \ / ____| _ \_ _|
> | | | |_ __ ___ _ __ | (___ | |_) || |
> | | | | '_ \ / _ \ '_ \ \___ \| _ < | |
> | |__| | |_) | __/ | | |____) | |_) || |_
> \____/| .__/ \___|_| |_|_____/|____/_____|
> | |
> |_|
>
> fdt_reset_driver_init: gpio-restart init failed, -1001
> Platform Name : StarFive VisionFive V1
> Platform Features : medeleg
> Platform HART Count : 2
> Platform IPI Device : aclint-mswi
> Platform Timer Device : aclint-mtimer @ 6250000Hz
> Platform Console Device : uart8250
> Platform HSM Device : ---
> Platform Reboot Device : ---
> Platform Shutdown Device : ---
> Firmware Base : 0x80000000
> Firmware Size : 300 KB
> Runtime SBI Version : 0.3
>
> Domain0 Name : root
> Domain0 Boot HART : 1
> Domain0 HARTs : 0*,1*
> Domain0 Region00 : 0x0000000002000000-0x000000000200ffff (I)
> Domain0 Region01 : 0x0000000080000000-0x000000008007ffff ()
> Domain0 Region02 : 0x0000000000000000-0xffffffffffffffff (R,W,X)
> Domain0 Next Address : 0x0000000080200000
> Domain0 Next Arg1 : 0x0000000082200000
> Domain0 Next Mode : S-mode
> Domain0 SysReset : yes
>
> Boot HART ID : 1
> Boot HART Domain : root
> Boot HART ISA : rv64imafdcsux
> Boot HART Features : scounteren,mcounteren
> Boot HART PMP Count : 16
> Boot HART PMP Granularity : 4096
> Boot HART PMP Address Bits: 36
> Boot HART MHPM Count : 2
> Boot HART MIDELEG : 0x0000000000000222
> Boot HART MEDELEG : 0x000000000000b109
>
>
> U-Boot 2022.04-rc2-VisionFive (Mar 07 2022 - 21:12:22 +0800)StarFive
>
> CPU: rv64imafdc
> Model: StarFive VisionFive V1
> DRAM: 8 GiB
> Core: 13 devices, 9 uclasses, devicetree: separate
> MMC: mmc@10000000: 0, mmc@10010000: 1
> Loading Environment from SPIFlash... cadence_spi spi@11860000: Can't get reset: -524
> SF: Detected gd25lq128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
> OK
> StarFive EEPROM format v1
>
> --------EEPROM INFO--------
> Vendor : StarFive Technology Co., Ltd.
> Product full SN: VF7100A1-2204-D008E000-0000009A
> data version: 0x1
> PCB revision: 0x1
> BOM revision: A
> Ethernet MAC address: 6c:cf:39:00:00:99
> --------EEPROM INFO--------
>
> In: serial@12440000
> Out: serial@12440000
> Err: serial@12440000
> Net: dwmac.10020000
> MMC CD is 0x1, force to True.
> MMC CD is 0x1, force to True.
> switch to partitions #0, OK
> mmc0 is current device
> MMC CD is 0x1, force to True.
> MMC CD is 0x1, force to True.
> Can't set block device
> Can't set block device
> Autoboot in 2 seconds
> 151552 bytes read in 52 ms (2.8 MiB/s)
> MMC CD is 0x1, force to True.
> Card did not respond to voltage select! : -110
> Disk mmc@10010000.blk not ready
> Welcome to GRUB!Hi there!
I just want to let you know that I’ve tried the nezha image (without changes) in a MangoPi board and it runs OK with HDMI. I haven’t made tests (I need an usb-c adapter for my keyboard), nonetheless it runs and when I connect to network I’ll reply here. 
Is that the failing bootlog? If yes, this is weird since at the end, we can see “Welcome to GRUB!”.
Hi zxnord,
Thanks for your feedback, that’s nice to know! I guess you have the 1GB of DDR3 version of the board otherwise you would have probably fallen into the same issue as the LicheeRV.
Thanks,
Alex
1 Like
Successful bootlog. I’ll need to reset variables to defaults to get failure. Coming soon…
Hello Alex:
I want to know how to build the preinstalled image, I want made a ubuntu distro for my intel edison board.
HI, I managed to burn the image, now I wonder what are the login credentials, as I’m asked about them> 
Thanks for the help!
login: ubuntu
password: ubuntu
Hi initd,
Sorry I missed your question: ubuntu-image is not (yet) the application we use to create such images, for now we use live-build.
Alex
Hi, I try the 22.04.1 image and the latest(6th Oct) image, but both are not bootable. The bootloader and DDR etc have been upgraded to the newest version. This is the boot log:
The boot log is here.
But when I try the Fedora image, it works well. The way is to use the boot parameters from the Fedora image, it works well even though there are errors. The boot log with parameters is here.
fdt_high=0xffffffffffffffff
initrd_high=0xffffffffffffffff
scriptaddr=0x88100000
script_offset_f=0x1fff000
script_size_f=0x1000
kernel_addr_r=0x80200000
kernel_comp_addr_r=0x90000000
kernel_comp_size=0x10000000
fdt_addr_r=0x88000000
ramdisk_addr_r=0x88300000
bootcmd_mmc0=devnum=0; run mmc_boot
Thanks.
On VisionFive board,
using Image: jammy-preinstalled-server-riscv64+visionfive.img,
Kernel: 5.17.0-1008-starfive
Attempting to install firefox
Output:
Package firefox is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Also tried procedure listed here:
https://linuxiac.com/install-firefox-from-deb-on-ubuntu-22-04-lts/
Still shows no valid target package. Any ideas?
There doesn’t seem to be any built-in method of starting a browser, that I can see. The link on the XFCE desktop doesn’t work.
looks like we’ll need to make sure the firefox snap gets built for this architecture, it is currently only created for amd64, arm64 and armhf …
1 Like
I seem to be having hardware compatibility issues with LicheeRV.
ubuntu can boot on my SanDisk 8GB SD card.
But it won’t boot on my EAGET 32G and DM 64G SD cards.
This is mentioned in the LicheeRV wiki: https://wiki.sipeed.com/hardware/zh/lichee/RV/flash.html
I’m not sure if it’s a brand or capacity issue with the SD card.
I logged SD info, please see: https://github.com/initdc/sd-info/tree/data/SD
Can others help to test it?
How’s VisionFive 2 going?
2 Likes
Hi everyone,
On linux when using the dd command on the preinstalled ubuntu image I get an invalid alternate GPT error with insufficient space (mSD 32GiB).
Command: xzcat ubuntu-22.04.1-preinstalled-server-riscv64+nezha.img.xz | sudo dd of=/dev/sdd bs=1M status=progress conv=fsync
Test on Nezha [output]:
[ 12.280139] <<-GTP-ERROR->> I2C Read: 0x8047, 1 bytes failed, errcode: -70! Process reset.
[ 12.440651] <<-GTP-ERROR->> GTP i2c test failed time 5.
[ 12.470622] I2C communication ERROR!
[ 12.470657] regulator-dummy: Underflow of regulator enable count
[ 12.486289] gt9xxnew_ts: probe of 2-0014 failed with error -1
[ 15.020955] ======== XRADIO WIFI OPEN ========
[ 15.030706] [XRADIO] Driver Label:XR_V02.16.84_P2P_HT40_01.31
[ 15.037456] [XRADIO] Allocated hw_priv @ 0000000095352fb0
[ 15.061631] sunxi-rfkill soc@3000000:rfkill@0: bus_index: 1
[ 15.087619] sunxi-rfkill soc@3000000:rfkill@0: wlan power on success
[ 15.510657] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 0Hz bm PP pm UP vdd 21 width 1 timing LEGACY(SDR12) dt B
[ 15.521761] [XRADIO] Detect SDIO card 1
[ 15.540719] sunxi-mmc 4021000.sdmmc: no vqmmc,Check if there is regulator
[ 15.560636] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[ 15.603906] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[ 15.633660] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing LEGACY(SDR12) dt B
[ 15.671858] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 400000Hz bm PP pm ON vdd 21 width 1 timing SD-HS(SDR25) dt B
[ 15.700694] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 50000000Hz bm PP pm ON vdd 21 width 1 timing SD-HS(SDR25) dt B
[ 15.720810] sunxi-mmc 4021000.sdmmc: sdc set ios:clk 50000000Hz bm PP pm ON vdd 21 width 4 timing SD-HS(SDR25) dt B
[ 15.751863] mmc1: new high speed SDIO card at address 0001
[ 15.771187] [SBUS] XRadio Device:sdio clk=50000000
[ 15.790719] [XRADIO] XRADIO_HW_REV 1.0 detected.
[ 15.961271] [XRADIO] xradio_update_dpllctrl: DPLL_CTRL Sync=0x00c00000.
[ 16.113561] [XRADIO] Bootloader complete
[ 16.270767] [XRADIO] Firmware completed.
[ 16.282098] [WSM] Firmware Label:XR_C09.08.52.64_DBG_02.100 2GHZ HT40 Jan 3 2020 13:14:37
[ 16.310702] [XRADIO] Firmware Startup Done.
[ 16.321093] [XRADIO_WRN] enable Multi-Rx!
[ 16.333125] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 16.390888] Error: Driver 'gt9xxnew_ts' is already registered, aborting...
[ 17.118430] ieee80211_do_open: vif_type=2, p2p=0, ch=3, addr=a0:ac:f8:86:57:31
[ 17.140739] [STA] !!!xradio_vif_setup: id=0, type=2, p2p=0, addr=a0:ac:f8:86:57:31
[ 17.179471] [AP_WRN] BSS_CHANGED_ASSOC but driver is unjoined.
Trying to connect to SWUpdate...
[ 35.680647] usb1-vbus: disabling
Edit:
Retry again and finnaly works (fix GPT with gdisk [p -> v -> w])
Hi,
Does anyone know what the timeline is for the Vision Five 2 image?
Thanks.
3 Likes
Would also love to know that. I’ve got my board ready to go, but I don’t want to go with another distro just to switch back in a short time.
1 Like