Hello all,
just re-installed the above and ran the post install script (install_package_and_dependencies.sh).
On reboot, the board is dead, power on (red light) nothing else.
I have not changed anything in the hardware/switches etc. I have also not ran any apt upgrades/full-upgrades.
This is getting tiresome.
Any ideas?
Regards
Aubrey
PS I hope an SPL and/or u-boot update is not necessary to accomodate the abovementioned release/Image.
You will need to look at what the console is showing. with 202302 this means you need a serial adaptor. That is the only way to see if this is a SBI/Uboot load failure, or a failure when the kernel boots.
[With no serial, use a clean full disk SD image and set the DIP switches to boot from SD, that /should/ ensure you get the correct SBI and UBoot. (but you need to wait while they update, without a serial to show progress you must give it a few mins even if nothing shows on the green led).]
Thanks for the advice, but too late, I have already formatted the SD card (again) and put a fresh (202302) image on the card.
I am surprised that nobody else has experienced the same or no?
Regards
Aubrey
I think you will find that most of us have, but we immediately move over to the serial console for any boot failure.
I originally updated u-boot at the end of December when I first purchased the board.
I hope I do not have to do this again…
As stated, I have re-imaged the SD card and rebooted again, everything is working again.
I am NOT going to run this - “install_package_and_dependencies.sh” again however.
Why has nobody the posted what they see in the serial console when they encountered such a situation like myself?
Aubrey
If you use the minimal SDcard.img from the github releases then you need to run install_package_and_dependencies.sh to get all the desktop stuff. This is why this step is only documented in the ‘Minimal Image’ section of the guide.
If you are using the pre-configured Google / Baidu drive images (SD or eMMC) you do not need to run the installer. The image already has these updates and a working lightdm/xfce install; attempting to ‘upgrade’ the pre-configured development images it will generally break the GUI.
EDIT: I was wrong about the google/baidu images, they still need the installer to be run. Apologies if this has mislead anyone.
I am not near the machine (board) now, but I recall the preconfigured Google SD image (202302) had no Firefox or Libreoffice.
How does one react to this situation?
Regards
Aubrey
@Stromkiller You can download it, as explained in the release notes.
wget https://github.com/starfive-tech/Debian/releases/download/v0.7.0-engineering-release/install_package_and_dependencies.sh
chmod +x install_package_and_dependencies.sh
sudo ./install_package_and_dependencies.sh
https://rvspace.org/en/project/VisionFive2_Debian_Wiki_202302_Release
That is exactly what I DO NOT WANT to do. Please read the start of this topic.
Aubrey
You should never have bought an Earlybird. You are always complaining about things that are quite normal at this stage. So please stop annoying us with your bad purchase.
I agree with @SunWukong. It is a very new architecture (which is still undergoing major changes, just speed read the RISC-V Profiles, which was ratified 18 hours ago.) in a new SoC on a new board with a lot of software that is being worked on right now. My advise to you @Stromkiller if you are frustrated by this, is to shelf the board until mainline kernel support is finished and fully upstreamed, and by then you will probably be able to install official Debian, official Ubuntu, official …
This board exists to put a very reasonably priced RISC-V platform into the hands of those who will help make that happen. And those who wish to optimise performance of applications under RISC-V.
I am not complaining about anything, I want this board to fly just as much as anyone else.
@sunwukong I find your comments inappropriate and unhelpful.
Aubrey
Yes, you are correct on that. Apologies for the bad advice. You will still need to run the install script for the extra utilities. …which is not ideal, but is how it is.
Engineering Release.
… the clue is the lack of either the words ‘production’ or ‘distro’ in there. Starfive are not going to waste time building upgrade-ability or easy installers into this. They will deliver code to upstream repos and leave it up to the real distro builder to do that later.
I thought they were quite appropriate. so another thing we can disagree on.
Hello Stromkiller,
I experienced something like you I wasn’t seeing anything on the hdmi display at all, just the red LED. Afterwards, I wiped sdcard and dd’ed the newest engineering image, booted it up, installed the mtd-utils, fetched the newer spl/payload, flashcp’ed spl/payload, “shutdown -h now”, and finally powered it up. It behaved correctly afterwards.
You did mention all these steps being tiresome. We are EARLY-BIRD EDITION PRE-ALPHA TESTERS. Call me masochist, but I enjoy having hands on this hardware to try stuff. Sure I made mistakes, but isn’t all this fun to try? Isn’t it why you got this board? It’s true I do have some expectations from the board and they are well on their way being met.
I’m already rooting for a VF3 with more cores, more pcie lanes, more RAM, more powerful GPU LOL 
Go Starfive GO!!!
In general, if you want help, perhaps you should change your attitude.
In the end the VisionFive 2 doesn’t care what you want or don’t want to do. As far as I know, there is only one procedure to get the patched software packages.
It doesn’t work for you? So far it seems nobody else encountered your situation, so there is no reason for us to post the output of the serial console.
You want a working image? Consider falling back to an older image with the software included, or try 202303.
The Debian images of Starfive are too tiresome for you?
Perhaps consider installing one of the other images/procedures you can find in the forums.
Hello LivingLinux, I did encounter something similar to Stromkiller. I also encounter errors when I attempted to flash the new spl/payload from the older 69 image on the sdcard. Oddly enough, after booting from the newer engineering image, the flashing of the newer spl/payload with flashcp worked successfully from there. I don’t get the inconsistency, but I did welcome the newer spl/payload on the sbc itself. All I’m saying, I understand Stromkiller’s comments. The experience might not be perfect and painless when attempting the exact steps described on the forum and documentation, but with a little finagling here and there, it’s possible to get it to the expected behaviour with corrective steps. We just need to be patient and take those corrective steps and share with the rest of the community when we succeed and when we fail. It makes for a stronger vf2 community in the long-run.
I’ll agree with others, when we are here expressing ourselves with feelings, It’s ok. Please try to encourage others rather than criticizing others. I apologize if any of what I’ve stated offended anybody, but please keep in mind it’s all in the lens of constructive criticisms to make the VF2 and subsequent VF SBC’s stronger and more enjoyable to use.
Finally, LivingLinux I enjoy your videos. They helped me to progress in my VF2 user experience. You’re awesome and a superhero in my books.
All’s well that end well.
Doubtless, we all want to see this board perform reliably and well, despite the initial teething problems.
Regards
Aubrey
@omac777
You state “fetched the newer spl/payload”
Is that a “must” with 202302, as I have not updated the firmware since I purchased the board
in early January?
I cannot find the changelog for the newer firmware.
Regards
Aubrey