Forum Discussion
Hi Gan,
Normally the issue involve TCK frequency that need to be lower than 24MHz(please try different frequency). But I think you have try it?
We do not have any other issue with USB blaster i/ii last year, except for expired license and we have provided a patch for that.
https://www.intel.com/content/www/us/en/support/programmable/articles/000086243.html -if you want to have a look(can be use for other quartus version)
How are you sure that this issue is cause by the USB blaster ii? I can't say the reason of this issue is due to USB Blaster ii itself.
It can also be quartus or other issue.
Have you try with different USB Blaster ii?
Can you confirm this; you can program but cannot configure or cannot program at all?
Is there any error messages?
Regards,
Aiman
- HuaHongGan3 years ago
New Contributor
Hi Aiman,
Sorry for late reply. Here is all the test, I did
- I had used 5 USB Blaster II and they all act the same. After programmed, the nCE was kept at 0 and CONF_DONE at 1 which is incorrect. However, I change to USB Blaster I and it just work perfectly fine.
- I used one of the USB Blaster II and set it to 6M, 16M and 24M for the JtagClock. It does not work. This is the cmd I use to change the clock "jtagconfig --setparam 1 JtagClock 16M"
For your last question,
Yes, I am able to program it but the problem is the USB Blaster II seems to latch my device up/down and require a hard power recycle to make my device work again. I don't think this is normal. According to the the data sheet, once the programming is done the device should refreshed and run with the new code but not recycling the power.
Can you check on your end? Take a Cyclone 3 and program AS POF with USB Blaster II. See if it happens on your side.
Thanks
Gan