Looks like that the firmware of my board has an old hash which does not support -v but when I connect the USB stick with the image on it to my Linux laptop, mount the file system, edit the boot.scr with hexedit, and overwrite the 2 occurences of -v with 2 spaces, then save, unmount, plug the USB stick into the board and boot, it errors:
I succeeded with the firmware update, editing the -v out of the hash calls of boot.scr by overwriting each -v with 2 spaces using hexedit. To get a valid boot.scr again I followed the instructions of
Hello,
First of all thanks for all your hard work.
I’m trying to upgrade my board firmware with u-boot-2021-07-r1.bin but I found the script (u-boot-2021-07-r1.scr) is trying to get the old firmware file name (u-boot-2020-07-r7.bin) into it.
Also I found the links into README.txt are outlated.
Oh, ok.
Now I see, when I search for firmware (into the search box) this post is the first one I get. Then the correct one is Libre Computer Board Firmware Update Images, right?
Thanks!
Hi! I tested this new spiflash. It boots and ran the flasing process but ends with and error, unfortunately I didn’t take a picture. Now if I press a key during the boot process I get a prompt (uboot prompt?) Then I think the flashing process worked, also I don´t see the LOST menu anymore. One more thing, when it boots from emmc, after the grub menu the monitor remains black, like it hasn’t video signal.
I am probably in the same boat you were - however I fear that I corrupted the SPI flash while trying to update the old u-boot-2021-07-r1 to the version as of 3rd of November by removing the -v options in the .scr file.
I am able to get into the debian grub menu as well as starting a boot.scr script utilising boot.py - but I am not able to flash a new SPI image or boot an operating system with HDMI output as of now (however I only ran limited tests until now).
Did you have any success booting an OS that can be somehow accessed (preferrably via HDMI output but also possible via SSH session)?
Hi @skyfall !! yes, I think we are at the same place. I’m still have a working OS because it was already working into an emmc, and I’m not using HDMI, just accessing via SSH.
I’m also not sure how I’ll be able to flash a new SPI image.
I’m able to access the emmc card using the boot.py utility.
I think you may try using a USB-TTL usb adapter to connect to the board console and you should be able to write a the OS login prompt.
I installed the u-boot-2021-07-r1 back when it was new and had the SBC running since then until last month without any issues.
On November 3rd I then tried to update the SPI to the newest version in order to reuse or resell the SBC.
However, I did not yet have time to test reflashing - would it be possible to use mtdutils or similar provided I could “manually boot” a debian/ubuntu image using boot.py?
As @sserantes pointed out, serial access and/or SSH should be possible - I haven’t yet tried that.
I’ll try to take some time in the next two weeks and report back.