Forum Discussion
Hi
What happens if you power cycle the board after you get the JTAG chain problem notification? Can you scan the JTAG chain successfully?
- NIJGNAS1 month ago
New Contributor
Hi SteveK_Arrow,
I tested that. After the JTAG chain problem occurred, I power-cycled the board and tried scanning again.
Result: no change. JTAG Auto Detect still fails after the power cycle on both:
- embedded JTAG, and
- external USB-Blaster II via J10.
The JTAG Chain Debugger continues to show the same behavior (unknown devices, chain problem) as before. 'jtagconfig --debug' shows the same.
Thanks.
- SteveK_Arrow1 month ago
New Contributor
Hi NIJGNAS
Is the QSPI device flashed with content? What are the MSEL DIP switch SW2[1:4] settings? Are they set to configure using JTAG or Avalon streaming interface x8?
Thanks
- NIJGNAS1 month ago
New Contributor
Hi,
Yes, the QSPI is flashed with content.
- With SW8.2 = ON (FPGA removed from the JTAG chain), I was able to Program and Verify the factory recovery image AVSTX8.pof into the QSPI successfully. In this mode, the JTAG chain shows only the MAX10 (10M50DAF256) and the QSPI_2Gb device (see attached JTAG chain screenshot).
- If I try to program without removing the FPGA from the chain (SW8.2 = OFF), the programming fails with:
Error(209062): Flash Loader IP not loaded on device 2
Error(209012): Operation failed
- After successfully programming the QSPI (with SW8.2 = ON), switching SW8.2 back to OFF still does not restore JTAG. Quartus Programmer Auto Detect continues to fail (same behavior on both embedded JTAG and external USB-Blaster II).
Regarding MSEL DIP SW2[1:4]:
- Only when I initially ran the Nios V Hello flow, SW2[1:4] was [OFF:OFF:OFF:OFF] (JTAG).
- Since then, SW2[1:4] has been kept at [ON:OFF:OFF:OFF] (AVST x8) and has not been changed.
Thanks.