I’m new to the VisionFive 2 as well as embedded devices though I have quite a bit of experience with computer programming. I’m just now learning how to build a Linux kernel and a bootable image. I don’t know anything about U-Boot or firmware downloads or a Linux boot sequence for an embedded device.
I have a VisionFive 2 1.2A board that boots from a 64 GB SD card fine when I use the 202310 Debian OS downloaded from the StarFive drive.
I have been working with this device for several weeks now with my experience captured in the following article, Setting Up a New VisionFive 2 RISC-V SBC.
I’m now experimenting with building an image for the VisionFive 2 and the image is not booting from the 32 GB SD card the way that the official build image does.
The last line is “mipi_09p: disabling” and the boot seems to hang at that point.
I’m pulling the source code from the StarFive VisionFive2 Git repository and following the procedure as outlined in the README.md file. I’m using a processor count of 10 in the following as I have an Intel i5 with 12 processors according to Linux.
make -j10
make buildroot_rootfs -j10
make img
I’ve been wrestling with a number of problems before finally getting to the point where an sdcard.img file was created without seeing any errors.
My worst problem appears to have been the result of a copy paste error when installing the necessary packages for cross compiling the source with Ubuntu on an x86 PC using Windows Subsystem for Linux under Microsoft Windows 10. However there was also the error when I did not have Git LFS installed. I have addressed both of these errors and am now able to do what appears to be a complete image build from the source.
I found a post in this forums from someone having a similar problem, Boot Stuck at mipi_0p9 disabling, but did not see any kind of answer or resolution.
From some posts, it appears that some people have had a problem with firmware that needed to be upgraded however in the boot text displayed on my HDMI 1920x1080 monitor, it appears there is a firmware download being done. There are a number of messages of “[ecrnx] firmware downloading” followed by a percentage that counts up to 100%. The last few lines of this say:
[ecrns] firmware downloading 100%
random: crng init done
random 7 urandom warning(s) missed due to ratelimiting
dl-fw ack fail, magic: 165
firmware download successfully!
What other information can I provide that will be able to help someone point me in the right direction to resolve this?