Community
cancel
Showing results for 
Search instead for 
Did you mean: 
JWrig25
Beginner
401 Views

New error when programming device: "Unable to scan device chain. On-board programming hardware is disabled."

I have been trying to get the Avalon-MM design programmed on my Stratix V GX FPGA Development Kit. I finally got it to compile on an old version of Quartus since the newer versions are not compatible with the design. I have tried to then program my board with the design but I run into the error above. I have been able to program the board successfully in the past and have no idea why it stopped working now. I made sure all the DIP switches are in the correct factory default positions but that did not fix the issue. I am on my second FPGA board since the first one stopped working like my second just stopped and also gave me the same error. Everything suggested to me to fix it requires that I can program with the board in Quartus or can connect to the BTS or BUP which I cannot do. The BTS gives me the error: "Connecting to the target... java.lang.Exception: No USB Blaster detected. Please check connections and restart the program". When I try to program on Quartus, it will recognize the USB_Blaster II but gives me the error "Unable to scan device chain. On-board programming hardware is disabled". Please help, I have had nothing but problems with these FPGA boards, with Quartus not programming, designs specific to my FPGA not compiling, other issues and now this.

0 Kudos
23 Replies
JWrig25
Beginner
166 Views

FYI: I used Quartus 14.0 to compile the Avalon design, and the 2nd FPGA I have been using would program even though when I turn it on it doesn't load the factory default settings like trying to connect to the BUP, but was always still able to program the board with Quartus up until now, recently I had been inserting the FPGA into a PCIe slot on a Linux CPU host but since the Hard IP isn't configured, no communications have been made to the board that way so I don't believe that is the issue.

JohnT_Intel
Employee
166 Views

Hi,

I think the embedded USB-Blaster is damage. I would recommend you to use the external USB-Blaster.

JWrig25
Beginner
166 Views

Hi, the Stratix V GX FPGA Development Kit does not come with an external USB-Blaster device. Would I need to buy one and from where?

Thanks

JohnT_Intel
Employee
166 Views

JWrig25
Beginner
166 Views

Hi, I will look into this option but I was wondering if there were any other potential solutions before I commit to buying the external USB-Blaster II.

JohnT_Intel
Employee
166 Views

Hi,

 

Usually if this happen, it is detecting something is connected to the 10-pin header of the JTAG pin. You can try to clean the 10-pin header if is is able to resolved the issue. If not then the only method is to use external USB-Blaster.

JWrig25
Beginner
166 Views

Hi,

 

I purchased the external USB-Blaster II device but unfortunately it did not solve the problem. I used Quartus 14.0 to try and program the FPGA using the new part but the error still pops up saying that Quartus can't find the device programming hardware. I have tried running the jtagconfig --debug command, and both the external USB-Blaster and the direct internal USB-Blaster get the same output being "Unable to read device chain". The external USB-Blaster says "JTAG chain broken" and the internal USB-Blaster says "Hardware Disabled". I am not sure what to do now. I will try to use Quartus 18.1, the first version I was programming with and see if that works but I have my doubts. Any help would be appreciated.

JohnT_Intel
Employee
166 Views

Hi,

 

May I know if you have other boards to test out? Are you able to see that the board is power up successfully?

JWrig25
Beginner
166 Views

Hi,

I do have one other Stratix V GX FPGA Development Kit, that was the original device I was using until the board got corrupted via programming by Quartus Prime, and that one also since then became unprogrammable. That is when I moved to my current second board which now also doesn't work. I do believe the boards power up correctly with the Config Done LED lighting up, but they power up into a different "programmed state" than the original factory default state.

JohnT_Intel
Employee
166 Views

Hi,

 

May i know what configuration mode are you using on your board? If you are using AS mode then can you change the MSEL to other setting and try to reprogram the FPGA?

JWrig25
Beginner
166 Views

I am not sure what config mode is being used, I know that when the board turns on, it will load the current image and light up the config done LED. How do I find the config mode I am using?

JohnT_Intel
Employee
166 Views

Hi,

 

If you look into SW4 shown in Figure 4 inhttps://www.intel.com/content/dam/www/programmable/us/en/pdfs/literature/ug/ug_svgx_fpga_dev_kit.pdf then you can check what is the setting is set to.

JWrig25
Beginner
166 Views

SW4 is in the factory default setup, so all the switches are in the On(0) position except for MSEL3 which is in the OFF(1) position. What should I change it to?

JohnT_Intel
Employee
166 Views

Hi,

 

Could you change MSEL4 and MSEL1 to 1 and MSEL3 to 0?

JWrig25
Beginner
166 Views

Hi,

 

I will try that and see if that works, I pry won't be able to get to that until tomorrow but I will let you know the results, thanks again for all your help.

JohnT_Intel
Employee
166 Views

Hi,

 

Sure. I will wait for your update.

JWrig25
Beginner
166 Views

Hi,

 

I switched SW4 to have MSEL1 at 1, MSEL4 at 1, and MSEL3 at 0, and tried to program with the external USB-Blaster II device connected to my FPGA. Unfortunately, the programming failed immediately, the auto detect feature also throws an error, and by moving the switches the Error LED (D16) lights up. Any other ideas?

JohnT_Intel
Employee
166 Views

Hi,

 

It looks like the board has been damaged. I am not able to think of other way to fixed the issue.

JWrig25
Beginner
166 Views

Thank you for your help, I will keep trying to fix it.

JohnT_Intel
Employee
32 Views

Hi,

 

I might suspect that the U14 device which is the Max II device is corrupted. The other method is to remove this device so that it does not interfere with your JTAG Chain

Reply