-About TTL adapter. No. I’m not using such a thing.
-About the power supply. I’m using the 5 V 6 A purchased with the board on allnet China website.
-The microSD is a 32 GB Sandisk. (flashed with Raspberry Pi imager).
-I purchased a 16 GB eMMC, a reader and the wifi dongle in the same order. The eMMC is now installed on the board and formatted to ext4.
Last night I’ve tried some heavy websites and some desktop configurations to test the overall performance with htop, then i noticed that my board is the 4 GB RAM version. Tried again to check this with “cat /proc/meminfo”,which gave me the same result.
I recommend to check this to anyone who have ordered the 8 GB RAM model.
I’m writing down again this lines with Firefox and the Vision Five 2.
Hello.
I’m trying to connect to a 1680x1050 @60Hz DVI monitor through a DVI-HDMI cable which works perfectly on a Raspberry Pi.
I’ve tried to add the mode with cvt first, then xrandr (–newmode --addmode), but without success when selected.
I keep trying other ways. ¿Can someone give me a clue?.
One of the “Known Issues / Limitation” currently listed in the pdf is “Auto-selection of 4GB/8GB ddr in uboot”, which I interpreted as the software failing somehow to differentiate between 4 and 8 GiB of RAM. Probably best to confirm the part number of 2/4/8GB LPDDR4 chip on the board, and lookup what the hardware really is, at least until the software issue is resolved.
“cat /proc/meminfo” - Using software to check what hardware is there only works correctly when the software is working.
Release jammy-server-visionfive2_20221219 · initdc/rootfs-tools
i tried this image but unfortunately it seems to be missing some functionality (device tree/kernel module?) for display… after setting up kde it get the following when trying to startx (other things seems to run well)
open /dev/fb0: No such file or directory
Hello,
my experience is, boot with SDK shows 8 GB RAM and boot with Debian it shows 4 GB.
I buyed a 8GB board.
Best regards
Damian
Hi,
the -v55 image works on my VisionFive2. Unfortunately, I’m stuck with updating uboot/firmware. There was no procfs, thus I added proc to /etc/fstab. I installed mtd-tools like suggested in the QSG-PDF.
Yet no MTD devices are available, the kernel doesn’t spit out anything usable during booting neither (dmesg | cat mtd).
I really don’t want to setup a tftp environment.
How do I get MTD to start, so I can update the firmware and use the -v69 debian image?
Lost a few hours yesterday only to find out that you are serious about the firmware update. V69 doesn’t boot without the update. I tried switching GPT to MBR on the SDCard and several other things …
Any help here would be appreciated.
Thank you,
Best regards
Dirk
Post Scriptum: The description in the QSG is lacking details on how to boot into tftp at all. Setting to boot switches to UART?
Both ways described do not work to update the firmware.
I had the same case
And wouldnt setup tftp: but finaly did it.
As suggested by @dtometzki i could have compile uboot by myself but wasn’t confident
Then i decided to setup tftp
→ macos (sierra) it is already installed in cli
→ for linux, seems to be one apt install
→ for both you place files in right folder and it should just works
But definitly àll commands in VF2 side were executed through UART.
I have an alternative way if you don’t want to update firmware by tftp.
- flash sdcard.img into tf card;
- power on and login system(user/password: root/starfive);
- transfer the latest uboot/spl files into board by USB or Ethernet;
- flashcp command to update;
- re-insert the debian tf card and reboot;
Thank you for your replies. A little fiddling worked:
- Windows → PumpKIN TFTP-Server. Make sure that you enable it in the firewall for public and local networks as Windows will see the ethernet connection as public (lost some time there).
- Connect USB-2-Serial. Connection setting for Terminal 8N1, 115200bps. Open COM-port in Putty, for example.
- Set your ethernet adress to 192.168.120.99 in Windows, no gateway, netmask 255.255.255.0
- When booting VisionFive2, make sure to press any key during the 3 seconds countdown which will stop the booting process and makes you reside in the firmware environment.
- Now the commands work like shown in the QSG.
Thank you for the headsup!Feels a bit like bleeding edge. 
So I was able to get my VisionFive 2 board working using the sdcard.img on the TF card and using the USB serial cable. I then was able to manually configure the eth1 network interface and get an ssh session going.
At least I know the board is working and that’s something.
What I don’t quite get is what is this sdcard.img file? It’s a Linux image of some sort but appears to be only a minimal set of things without any way to add more packages.
Does anyone have any tips on how to get the Debian image to boot? When I try it on the TF card I get nothing. Either the image is bad or I’m preparing it wrong.
Also, I’d really like to run from an NVMe device instead of the TF device. Has anyone been able to master that? If so, what’s the secret?
Thanks!
Image69 should work as is.
Nvme not yet supported for booting OS, only for storage.
did you try this debian image ?
https://drive.google.com/drive/folders/1xTdKqBMGLqI_MslVfeZaHrCDiklDJ3J4
Again, my pet rant… an image with no NVME boot capability or indeed, an image/firmware release that does not support NVME booting is a non-starter for me.
I downloaded the “69” image and flashed it to the TF card. When I try to boot I see only this on the USB serial console:
BOOT fail,Error is 0xffffffff
Hello @jwh20
Please check your boot switches. you have to set QSPI flash to boot.
Second do you have updated your u-boot and SPL ? Is required for Image “69” ?
I tried all 4 switch positions and get the same error. As far as u-boot and SPL, I’m unclear on how to accomplish that. Is there are procedure? I saw a couple of mentions but it seemed that you had to know how to do it in order to do it.
If I’m correct, you can boot the minimal image v69 with the original firmware.
As you have the serial console working, you can copy the files to the VF2 and use flashcp (instead of tftp).
See the link “Updating SPL and U-Boot” inside the post below to update.
I think that is the best and easiest way
Whats is the difference between the sdcard.img and the Debian (69) image?
Is the sdcard.img a kickstarter/rescue image?