Forum Discussion
Altera_Forum
Honored Contributor
12 years agoThis is not an undocumented feature. There is something wrong with your hardware.
When you use the JTAG debugger, probe the JTAG pins. When you press the check IDCODE, the debugger will generate JTAG transitions on TCK and TMS to reset the JTAG TAP, which defaults to loading the IDCODE JTAG instruction. TCK and TMS will then be toggled to move the TAP into the Shift-DR state and the IDCODE should be output on TDO. See the attached scope trace. If you don't see valid logic levels on these three signals, then you may have an issue. To test TDI, use the other tab of the debugger and move the TAP to the Shift-DR state, and enter a 32-bit value, eg., 0xAAAAAAAA. Then shift that into the TAP. The response will be the JTAG ID code, but TDI will be toggled. Cheers, Dave