VisionFive2 Software v3.9.3 Release

VisionFive 2 （English Forum)
,
1

More details about v3.9.3：

New Features

A summary of the main new features are as follows.

  • Support JH7110 SDK v5.9.3;
  • Support VisionFive2 v1.2A & 1.3B SBC;
  • Support Linux Kernel 5.15.0 and 6.1.31;
  • Support libcamera/libcamera-apps;
    • Add necessary V4L2 controls for ISP;
    • Add FRAME_SYNC event to the SC sub-device;
  • Add EtherCAT master applications;
  • Bug fix:
    • OMX: fix yuv channel alignment issues in some resolution;
    • ISP: fix some hardcode on search path and ss0/ss1 output resolutions;
    • ISP compatible issue between std_isp_ctl and libcamera;
    • Libcamera: fix some libcamera-vid and libcamera-still issues;
    • Update DC8200 logic to boost desktop performance upto 4k30fps;
    • Camera image cannot be output to MIPI LCD via v4l2test command;
4 Likes
2

With this version nothing boots anymore, not even the own Debian images 202310 and 202311.

Here is the log:

U-Boot 2021.10 (Nov 29 2023 - 14:51:40 +0800), Build: jenkins-github_visionfive2-20

CPU:   rv64imacu_zba_zbb
Model: StarFive VisionFive V2
DRAM:  4 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
OK
StarFive EEPROM format v2

--------EEPROM INFO--------
Vendor : StarFive Technology Co., Ltd.
Product full SN: VF7110B1-2310-D004E000-00001493
data version: 0x2
PCB revision: 0xb2
BOM revision: A
Ethernet MAC0 address: 6c:cf:39:00:50:18
Ethernet MAC1 address: 6c:cf:39:00:50:19
--------EEPROM INFO--------

In:    serial
Out:   serial
Err:   serial
Model: StarFive VisionFive V2
Net:   eth0: ethernet@16030000, eth1: ethernet@16040000
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1 is current device
Try booting from MMC1 ...
Can't set block device
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
## Error: "boot2" not defined
Card did not respond to voltage select! : -110
starfive_pcie pcie@2B000000: Port link up.
starfive_pcie pcie@2B000000: Starfive PCIe bus probed.
PCI: Failed autoconfig bar 10
starfive_pcie pcie@2C000000: Port link down.
starfive_pcie pcie@2C000000: Starfive PCIe bus probed.
PCI: Failed autoconfig bar 10

Device 0: unknown device

Device 0: unknown device
Tring booting distro ...
switch to partitions #0, OK
mmc1 is current device
Try booting from MMC1 ...
Can't set block device
## Warning: defaulting to text format
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
Can't set block device
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
fatwrite - write file into a dos filesystem

Usage:
fatwrite <interface> <dev[:part]> <addr> <filename> [<bytes> [<offset>]]
    - write file 'filename' from the address 'addr' in RAM
      to 'dev' on 'interface'
Retrieving file: /extlinux/extlinux.conf
Can't set block device
Error reading config file
Card did not respond to voltage select! : -110

Device 0: unknown device

Device 0: unknown device
StarFive #

I started with v2.10.4, this version could still boot other OS on the SD card.

Then I updated to v3.8.2, which now could only boot from the own Debian image because of a changed “optimized” boot order by SaminGuo, see Specific image does not boot after SPL and U-Boot update to v3.8.2 · Issue #87 · starfive-tech/VisionFive2 · GitHub.

Last update was from v3.8.2 to v3.9.3 which now can’t boot anything at all.

On the monitor I can see only a white boot screen.

IMG_20240109_142640
IMG_20240109_1426403264×1836 936 KB

How can I now update to v5.10.3?

By the way how are you supposed to boot from sdcard.img (800 MB), I never go this one to boot.

1 Like
3

Try this image for updating to latest software →

https://github.com/starfive-tech/VisionFive2/releases/download/JH7110_VF2_515_v5.10.3/sdcard.img

Look at the jumper settings in the VF2 user guide →

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjAoMfT-tCDAxWqgf0HHarNBIkQFnoECA8QAQ&url=https%3A%2F%2Fdoc-en.rvspace.org%2FVisionFive2%2FPDF%2FVisionFive2_QSG.pdf&usg=AOvVaw2Fxcm7qCojKFGh8O2xUjbE&opi=89978449

4

maybe this can help you
VisionFive 2 SDK Quick Start Guide (rvspace.org)

1 Like
5

As you’ve got a working serial port, there’s this method:

1 Like
6

Thanks to rvalles I could update to the latest version via UART. Saved me from opening up the case again to change the dip switch to SD.

U-Boot 2021.10 (Dec 27 2023 - 19:53:40 +0800), Build: jenkins-github_visionfive2-21

riscv64-buildroot-linux-gnu-gcc.br_real (Buildroot JH7110_VF2_515_v5.10.3) 12.2.0
GNU ld (GNU Binutils) 2.39

But I still can’t boot into the Debian image. Can anybody confirm/verify that v5.10.3 boots the latest Debian (2311) so I can rule out bad SD cards?

7

Download starfive-jh7110-202311-SD-minimal-desktop.img.bz2 and burn into sdcard.
StarFiveTech

8

I finally figured out what was wrong, I messed around with the U-Boot environment variables trying to make it boot to another distro. I already reset the environment variables several times but I forgot to save them.

Thanks to this post I can now boot again.

env default -a -f
saveenv
reset
2 Likes