OSSC Pro: Failed Firmware Update

[JAMIEvx]

@marqs Just flashed 0.77 via the USB Blaster using the .jic file and the OSSC Pro would not boot. It appears to have successfully flashed according to the log in Quartus Programmer.

[marqs]

I see. After going back to 0.76, could you export profile 0 to SD card and share it with settings.bin? I can try importing those and see if I could replicate the issue (very unlikely, though).

[JAMIEvx]

@marqs Here you go

[BoldFusion]

@JAMIEvx So I have to use a USB Blaster to get my OSSC Pro working again? Which one did you use? I’ve never used one before.

[Morpheus_79]

@BoldFusion As I’ve written here:

OSSC Pro: Failed Firmware Update

… there are some problems with the very cheap ones. But for just a one-off usage it’s understandable, that no one wants to spend around $300 for an original Altera/Intel Blaster or even $70 for a Terasic one.

I would recommend buying an ultra-cheap Blaster for 5-9 bucks… like this one:

https://www.amazon.com/dp/B07F5H5LPZ

… and using it under Linux (since with its original firmware it has its problems under Windows).

OR using this custom firmware with it:

https://github.com/dougg3/CH55x-USB-Blaster

… like it’s described here:

Fixing a knockoff Altera USB Blaster that never worked

… and using it under Windows (or Linux)!

Alternatively you can buy the little more expensive WaveShare Blaster:

https://www.amazon.com/dp/B08CV3L6LF/

… and using it only under Windows (since it has its problems under Linux).

[JAMIEvx]

@BoldFusion I did end up shelling out the cash for the Terasic USB Blaster that was mentioned on the wiki.

Thanks @Morpheus_79 for the info on other blasters though!

[marqs]

@JAMIEvx Tried importing the linked profile+settings pair as default but could not replicate the lockup. I regenerated bitstream with different seed which slightly changes timings within FPGA (.jic here). During development I’ve occasionally managed to generate a bitstream that similarly does not boot, but so far I’ve thought that it’d due to a tool bug and would behave identically on every board.

[JAMIEvx]

@marqs That appears to have worked!

[marqs]

@BoldFusion sending it back to VGP for re-flashing is also an option. Then we could also try to analyze why a few boards don’t boot with the firmware to prevent similar occurences in future.

[BoldFusion]

I did finally get a Waveshare USB Blaster V2 and was able to successfully reflash firmware 0.70 so my OSSC Pro is working again at least. But now when I try flashing 0.77 I get an error saying “Can’t erase or program protected sectors in the EPCS/EPCQ device”.  Also when I click on “Auto-Detect” in the JTAG programmer, it lists two devices: 5CEBA5 and 5CEFA5. I’m not what these are but 5CEFA5 worked the first time. Now both are giving me the same message. I’m not a computer programmer so all this language is foreign to me, but I am happy that my OSSC Pro is at least working again. I’ll try updating to 0.76 via SD card later.

[Morpheus_79]

@BoldFusion
According to these FAQs:

https://www.macnica.co.jp/en/business/semiconductor/support/faqs/intel/124561/

… go in Quartus Prime to “Tools” -> “Options” and select this option under “Programmer”:

[BoldFusion]

@Morpheus_79 Thanks, I must of missed that option. I’ve now successfully flashed 0.77 using the updated file @marqs posted. Now I can finally use my legacy AV board.

[Morpheus_79]

I forgot…

According to @marqs :

To program flash, a combined FPGA image must be first generated and converted into JTAG indirect Configuration file (.jic). Open conversion tool (“File->Convert Programming Files”) in Quartus, click “Open Conversion Setup Data”, select “ossc_pro.cof” and press Generate. Then open Programmer and ensure that “Initiate configuration after programming” and “Unprotect EPCS/EPCQ devices selected for Erase/Program operation” are checked in Tools->Options. Then clear file list, add generated file (output_files/ossc_pro.jic) and press Start after which flash is programmed. Installed/updated firmware is activated when programming finishes (or after power-cycling the board in case of a fresh flash chip).

… both of these checkboxes should be ticked:

[Author]

Posts