NewHome › Forums › OSSC, OSSC Pro and DExx-vd isl › OSSC – Discussion and support › Troubleshooting JTAG Programmer
AetherSmith.Well, based on some suggestions from some Shmups forum posts, I decided not to worry too much about getting one of the official Altera USB blasters, and just got one of the much-cheaper clones off Amazon. Only problem is now I can’t get it working to update my firmware…
With the Altera drivers installed for the blaster, my computer bluescreens if I open the Quartus programmer with it connected, though detects it alright if I wait to connect it until the program has started up. However, if I then connect and switch on the OSSC, open the .jic file as described in the instructions, and finally hit Start, the programmer runs for a few minutes before failing with the error “Can’t access JTAG chain”.
Has anyone else encountered anything like this in trying to update their firmware via JTAG, or should I just chalk it up to the programmer being cheap junk?
Are you using the properly signed drivers that come with Quartus or the drivers that the programmer provides?
I think I got the official Altera drivers installed properly; I followed the instructions on the wiki and I don’t see anything wrong in the device manager. Anything look off to you?
Not sure if it’s related, but my computer would bluescreen whenever I connected my clone to usb after installing the drivers included with Quartus Lite 16.1. I was able to go into safe mode, connect the device, and delete the driver to stop the blue screen.
The driver available here worked fine both with the old programmer as well as the programmer included in Quartus 16.1: http://www.firebrandx.com/nespalette.html
Huh, well what do you know, that did the trick! Not sure if the driver is any different between your link and the one that comes with the current version of Quartus, but the Quartus 13 programmer that came with the download was much more stable and responsive in use. Maybe the blaster I got just really doesn’t like Quartus 16.
| 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 |
