January 30, 2017 at 4:57 AM #11025FnnrqwinParticipant
I’m attempting to update from 0.73 to 0.75 using a Sandisk 2GB MicroSD card. I’ve followed the Wiki’s instructions, and am using Win32DiskImager, which I’ve used in the past with no problems. Anyway, I have a pre-built system, so I’m not sure why it would give me this error. I’ve tried updating to 0.74 instead to see if it was a problem with the .bin, but they doesn’t work either.January 30, 2017 at 5:25 PM #11026HarrumphParticipant
Have you formatted to FAT32 first?
Have you checked the card is properly inserted in the OSSC?
Are you getting any error message?January 30, 2017 at 6:07 PM #11027marqsParticipant
Formatting beforehand does not make difference as Win32DiskImager overwrites partition table. “Invalid image” message on character LCD means that first 4 bytes read raw from a detected SD card do not match the firmware image. Usually that means that there’s been an error writing the image to card, but in theory it could be caused by a hardware issue too. I’d first test writing the image via another computer before considering other options (jtag update / return).January 31, 2017 at 4:07 AM #11038awe444Participant
I also encountered “Invalid Image” under the exact same conditions the original post had (same SD card brand, same firmware version, WinDisk32Imager, etc.) Tried re-flashing the FW image onto the card multiple times and still got the error. Finally I just tried selecting the “Fw. update” menu option over and over again without touching anything, and after about 7 or 8 failed attempts it finally accepted the image and completed the update successfully.
Looking at the OSSC’s source code (/software/sys_controller/ossc/firmware.c) I see there’s a variable FW_UPDATE_RETRIES which is set to 3. Was the value of 3 chosen because failed reads were anticipated? If so, could setting it to a higher value make the updates proceed with a higher success rate?January 31, 2017 at 5:16 AM #11039MythicParticipant
^ Was exactly how I got mine to work. I just kept hitting update then it worked.January 31, 2017 at 11:39 PM #11047marqsParticipant
FW_UPDATE_RETRIES only controls how many retries update procedure is given if verification fails (e.g. some bits are not correctly written to flash) – increasing it does not help on card detection. Problems in detection are most likely caused by Altera’s less-than-stellar SD card controller which was replaced with a more compatible one in fw 0.74.February 12, 2017 at 2:00 AM #11150FnnrqwinParticipant
I could have sworn I had responded to this, but just constantly retrying eventually worked. Thank you!February 12, 2017 at 10:58 PM #11181awe444Participant
Updating from 0.75 to 0.76 worked on the first attempt without any problems at all. So either I was very lucky this time, or the updated SD card controller (from 0.74) has indeed fixed the issue encountered previously when updating from 0.73 to 0.75.March 1, 2018 at 10:29 PM #19742RetrorunnerParticipant
I am not able to install the new test image from borti:
because of the “invalid image” message. I tried several times to trigger the update. Tried different micro-sdcards same result. When using older images (also on bortis page ossc_0.79-bl_test.bin) it works on the first attempt. Any idea why its not working with the image: ossc_0.80beta-bl_test.bin ?
edit: wiped the micro sd card, formated with 32fat, used win32disk imager and same result.
edit: ok something wrong with the image after/when downloading
- You must be logged in to reply to this topic.