p.26 it is written:
Note:
This method only supports versions equal to or later than VF2_v2.5.0
Can I follow the procedure from image55 (which from it’s name seems to be a 2.3.0 ?)
OR this note apply only to u-boot&SPL v2.5.0 ?
p.26 it is written:
Note:
This method only supports versions equal to or later than VF2_v2.5.0
Can I follow the procedure from image55 (which from it’s name seems to be a 2.3.0 ?)
OR this note apply only to u-boot&SPL v2.5.0 ?
Here’s a magnet link to Image-69 if anyone wants to download without going through the Google Drive.
magnet:?xt=urn:btih:ddefc7df6e3f7a708930183fc8c384a57eb8c331&dn=Image-69&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A6969%2Fannounce
For future release, could the .torrent file be put into github, or just on the low bandwidth site directly?
As expected, image55 (v2.3.0) was not able to mount mtd devices then switched to the other solution (flashing through TFTP server).
As expected too, using image69 without updated u-boot & SPL failed booting and forced the boot to u-boot. From here the tftp procedure worked fine for updating u-boot and SPL
→ Reboot : debian booted directly.
Thx
I have a gigabit uplink that I’ll leave running on that, though it’ll take a while to get inertia. It’s estimating 44 hours, so my Gbit uplink in the states should help.
My download via your magnet link should be finished in 30 minutes, and I’ll let the machine running until the next image.
Hello, i build u-boot and opensbi and then installed the the mtd utilities via apt and the update wasnt a problem without tftp.
Are you saying that it is possible to use flashcp, even with the original SPL and U-Boot on the SBC itself?
If yes, is it possible for you to make this image available?
Or did I misunderstand your message?
Google Drive downloaded well over an hour then failed (~3 GB of >5GB).
Tried multiple times with same result.
Is there a ftp/wget site to dowload? Smaller image?
Smaller image is available in google drive inside image69 folder
Serving it now, in the US, from a GBit (fiber) uplink.
Hello LivingLinux,
you could install on the board the apt install mtd-utils and then you can use mtd. Do you see any output from cat /proc/mtd on your board ? Perhaps you need first update your kernel.
???
Ah, Ah! Sorry. Did not note that the checksums were against the uncompressed image.
AOK now!
I am looking forward to receiving a Vision5 2 board when it is ready and safe for you to ship.
The root partition of the minimal image has only 1.5 GB and only 5 MB of free space.
I had to resize it - in my case to 10 GB - in order to be able to install new packages with apt get.
Suggest to make it a bit bigger.
Thank you!
Actually no, it’s completely standard to ship a tight image. You are supposed to resize it. This keeps the distributed image small and besides, everyone will have a different size they want it resized to.
Hmmm… resize2fs does not seem to do this. How to resize please?
vvv===vvv
root@starfive:~# /sbin/resize2fs /dev/mmcblk1p3 20G
resize2fs 1.46.5 (30-Dec-2021)
The containing partition (or device) is only 404987 (4k) blocks.
You requested a new size of 5242880 blocks.
root@starfive:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
mtdblock0 31:0 0 128K 0 disk
mtdblock1 31:1 0 3M 0 disk
mtdblock2 31:2 0 1M 0 disk
mmcblk1 179:0 0 29.7G 0 disk
├─mmcblk1p1 179:1 0 16M 0 part
├─mmcblk1p2 179:2 0 100M 0 part /boot
└─mmcblk1p3 179:3 0 1.5G 0 part /
root@starfive:~#
^^^===^^^
You need to resize the partition first. I just used fdisk /dev/mmcblk1
and deleted 3 and created it again. After that the resize2fs
command works. Note, you do not need to reboot at any point.
Works great. Thanks!!
Now to get HDMI working…
Wouldn’t it be simpler to have some firmware loader SD card image?
I don’t really want to buy a uart dongle just to install the firmware.