Mixed bag today:
- Good: #OpenBSD :openbsd: boots without issue on the #VisionFive2 without even mucking with u-boot (there are commits from at least 2 OpenBSD devs working with this board, they figured out where to store the EFI loader so the onboard OpenSBI finds it)
- Good: the latest -current snapshot tries to attach several drivers!
- Not great: the sd driver complains that it can't get a clock frequency to talk to the card and so *doesn't* attach. Booting in verbose mode indicates there are other failures attachments (also successful attachments for less exciting items).
- Hope: I only had time to try a couple dtb versions today, and I tried the latest. But the last commit to the jh7110 files was July, so it was probably last tested with an older version. So maybe backing up to a July or earlier version will work
- More encouraging news: the changes to the sd card driver basically consist of the driver just saying yes to a new manufacturer string, so if I can get this working under OpenBSD without the clock issue, there's a decent chance #FreeBSD support is a similarly straightforward change to an existing driver.
If I can get sd storage working, I could try cross-building a #NanoBSD :freebsd: (https://docs.freebsd.org/en/articles/nanobsd/) image for local (over serial) work...
#openbsd #visionfive2 #freebsd #nanobsd
Okay, short instructions on booting #FreeBSD on a #VisionFive2 #riscv board, maybe I'll put these somewhere more stable later:
- Grab a copy of https://github.com/robn/freebsd-vf2
- edit mkvf2img.sh to mention an actually-existing snapshot; I used alpha 2
- optionally, edit it use grab a newer dtb for the board. 2.5.0 probably still works, but I took a gamble on 3.1.5 and it worked for me.
- run mkvf2img.sh on a FreeBSD system. If you know how to replace those uses of mdconfig and mkimg (which appear FreeBSD-specific) you could probably get it to run elsewhere, but I don't know how
- burn vf2.img to an sd card
- set your board to boot from flash/SPI. On my board (v1.3B) there's already a working u-boot installation there; on earlier boards it's possible you'll have to follow StarFive's directions to flash u-boot if you haven't already (not sure, I only have a recent 1.3B). This is the main thing missing from the instructions in that repo (I'll make a PR at some point), was which u-boot was in use (common instructions work with images that stick a copy of u-boot on the sd card)
- Now follow the instructions from the readme, using a USB TTL cable, *except* change the first command to ```fatload mmc 1:1 0x48000000 dtb/starfive/starfive_visionfive2.dtb``` (there was a PR that changed where the DTB went). All later commands work as advertised.
+ (they're not kidding about loading of root.img.uzip taking a while)
Useful tips:
- Along the way you'll see *a lot* of one particular error message. Clearly something isn't quite right, but don't panic if you see the one error a few hundred times
- If you get dumped at a ```dd>``` prompt you probably mistyped something at the OK prompt (or accidentally hit enter, in which case it tries to boot without a root filesystem)
Arch Linux image for the #VisionFive2 release "cwt15".
Since "cwt14" was built with Arch standardized "by the book," "cwt15" is merely an update to accommodate the new kernel (with u-boot and spl) from #StarFive.
Link to the release: https://github.com/cwt/Arch-VF2-Image/releases/tag/cwt15
The build script for Arch Linux Image for #VisionFive2 release cwt14 is complete.
The new image differs from my previous images as it is now based on the latest Arch RISC-V rootfs, and the btrfs subvolumes are created according to the Arch Wiki guidelines.
The kernel, StarFive’s soft_3rdpart, and the GPU driver are built and installed as packages.
The image can be downloaded directly from the GitHub release page at https://github.com/cwt/Arch-VF2-Image/releases
I just create a kernel package for Arch Linux for the board #VisionFive2 here: https://github.com/cwt/pkgbuild-linux-cwt-starfive-visionfive2/releases/tag/cwt13-3.0.4-1
It should work on your image too @thefossguy
I just uploaded my new image (cwt13) for #VisionFive2
https://forum.rvspace.org/t/arch-linux-image-for-visionfive-2/1459
I'm building #VisionFive2 upstream kernel from https://github.com/starfive-tech/linux/tree/JH7110_VisionFive2_upstream
Wish me some luck ;-)
Watch "RISC-V Business: Testing "the world's leading RISC-V SBC"" on YouTube
https://youtu.be/aFze0XVhHZA
I have uploaded a new image and kernel files for the #VisionFive2 to https://forum.rvspace.org/t/arch-linux-image-for-visionfive-2/1459. I hope this will resolve the ethernet issue. I am still waiting for the delivery of the revision B board.
@veer66 @semiauto @DrRider รอ #VisionFive2 revision B ที่จะมาส่งประมาณต้นเดือนหน้า อยากจะ make -j8 ใจจะขาด
cwt6 image สำหรับบอร์ด #VisionFive2 มาละครับ https://forum.rvspace.org/t/arch-linux-image-for-visionfive-2/1459
Build kernel บน #VisionFive2 ทีเดียว 3 ตัว พร้อมๆ กัน อาห์ นอนได้ละ พรุ่งนี้เช้าคงเสร็จพร้อมกันหมด
ทดลอง optimize เวลา build อะไรต่างๆ บน #VisionFive2 เลยได้รู้ว่า cargo ใส่ config แบบนี้ได้ แล้วก็เลยมาตั้งให้ optimize บน x86_64 ได้ด้วย (แต่ native ยังใช้กับ RISC-V ไม่ได้)
Finally, my single board RISC-V computer VisionFive 2 from StarFive is on its way to me.
I’m excited to run open source software on an open hardware platform. First Ubuntu, but hopefully soon Haiku OS!
#riscv #haikuos #opensource #starfive #visionfive2
Watch "#VisionFive2 RISC-V SBC - A Raspberry Pi Killer?" on YouTube
https://youtu.be/ZSRvTZyS0KI