OSSC Pro: Failed Firmware Update
- This topic has 22 replies, 7 voices, and was last updated November 6, 2024 at 11:24 PM by .
- You must be logged in to reply to this topic.
NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Discussion and support › OSSC Pro: Failed Firmware Update
@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.
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 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.
@BoldFusion As I’ve written here:
… 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:
… 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).
@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!
@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.
Cookie | Duration | Description |
---|---|---|
_gat | 1 minute | This cookie is installed by Google Universal Analytics to restrain request rate and thus limit the collection of data on high traffic sites. |
Cookie | Duration | Description |
---|---|---|
__gads | 1 year 24 days | The __gads cookie, set by Google, is stored under DoubleClick domain and tracks the number of times users see an advert, measures the success of the campaign and calculates its revenue. This cookie can only be read from the domain they are set on and will not track any data while browsing through other sites. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
Cookie | Duration | Description |
---|---|---|
IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
Cookie | Duration | Description |
---|---|---|
ct_checked_emails | session | No description |
ct_has_scrolled | session | No description |
ct_mouse_moved | session | No description |
ct_screen_info | session | No description |
wordpress_apbct_antibot | session | No description |
wp_woocommerce_session_9cc3598a6315be16da4f85bb374cf6a5 | 2 days | No description |