You mentioned only a red light is on. Did you wait about 5 minutes? You should see some flashing green after a while.
You should also notice some ethernet port light blinking with activity and solid on after a while.
Do you see anything like that? Please be more patient with the board.
The default when you bought had recovery bin from Dec22 installed already on the board.
I never uploaded the dec22 recovery bin to the board.
The first image file was v2.5.0 I believe.
Then you could have upgraded to v2.6.0. for the two firmware files NOT RECOVERY BIN.
Then you could have upgraded to v2.8.0 for the two firmware files. These came out 3 weeks ago, but I just installed it yesterday. No issues.
You keep on saying the only image that works for you is the original image file. Ok. At least you have one that boots up.
Once booted up, log into it, download the latest firmware v.2.8.0 directly on that sdcard.
Then run the flashcp for both of them.
Then shutdown -h now
Power down. Take out that sdcard. Now get another sdcard and wipefs --all /dev/NEWSDCARD, then dd the full image 69 on it, or try the experimental debian sid image. Take your pick. They both work. The archlinux, gentoo image are available as well, but I haven’t spent time with them. I also heard there are opensuse tumbleweed, deepin, and openeuler images available as well.
FYI I booted off a debian 69 minimal image to do the firmware upgrade from v2.5.0 to v.2.6.0.
I then started using the experimental debian sid image and apt-get install mtd-utils, then upgraded to v2.8.0 and shutdown and continued using the experimental debian sid without issues.
cwt say to avoid using uboot-upgraded/uboot-update because it fiddles with the fdt files. No matter. Don’t be scared. At the very worst you can always uart and upload the recovery binary and re-update the firmware files again. My only advice is continue playing with the board until you get it right. Be patient with yourself and keep on asking questions.
When running any commands, be patient. Let the commands settled down, give them time to do their task.
For the initial bootup, wait 5 minutes before logging in via ssh.
After entering your password for ssh, wait 5-10 seconds and you’ll eventually see the bash prompt show up.
When you are using a slow sdcard, everything is slow. That’s my situation and understand it perfectly well.
Once you start debootstrapping to an nvme and chroot /mnt the nvme, things go a bit faster in my case 6x faster.
It doesn’t boot from the nvme, but that’s ok. It’s still early days.
This is not a user board. This is definitely a developer board because it’s early days for riscv tv-boxes, pi4 like sbc’s and such. pi4’s have a desktop gui. vf2 is still working out the bugs for desktop gui and such. vf2 is still working out how to make it easy to boot off of emmc and nvme. Please be patient. Other images will come that will be easier to use, but in the mean time be aware this is more for developers trying to get their feet wet to improve the riscv ecosystem. Cheers.