MAX V "Jtag chain problem detected"

Did you find out what is causing this? I've been having similar JTAG related issues except I have 2 devices in my chain: Stratix IV GX and Max V. In the JTAG Chain Debugger, both devices show up normally most of the time, but, I get the message "Warning: Uncertain JTAG chain". Occasionally it will show an extra device in the chain as you describe. I don't see this on another module that is identical.

Since it was showing an extra device, I had assumed this was something on the clock line with extra clocks being detected somewhere so I started poking around. When I attached the scope probe (3.9pF / 10Mohm) on TCK it works consistently with no errors. The TCK signal looks very clean throughout the chain. All of the other JTAG signals are very clean as well. Anyone have any ideas? Are there any known issues with JTAG on either of these parts (MaxV/StratixIV)?

Thanks for the update. Glad to hear you got it working.

Mine is working reliably now as well. I added a 1nF capacitor between TCK and GND to slow down the edges. Even though it works, the signal looks like crap compared to what it was before. The clock now looks like a shark tooth rather than a perfect square wave. 1nF is probably too much and I'll probably try 10pF or 100pF.

With that said, I suspect it is the StratixIV causing my problems. Even when extra devices are shown the MaxV (last device in chain) almost always appears correct. The JTAG seems extremely sensitive to the TCK signal. As I said before, the signal integrity was almost perfect when looked at with the scope (only 3.9pF load). Further, I have a few identical modules and I don't see this issue on all of them. I'd be curious to know if anyone else has seen similar issues. The datasheet lists 180mV hysteresis for the TCK pin and I honestly can't see the ripple coming anywhere close to that at any point from what I see on the scope, however, it also works with the scope attached.

This has been solved for a while now, but, I thought I'd post an update on this issue in case it would help anyone out.

Upon further investigation, the issue was related to an impedance mismatch on the JTAG lines, TCK specifically. The USB blaster is designed with very fast rise times using low impedance 25ohm transmission lines. My board was designed with a 50ohm controlled impedance which caused a mismatch and related reflections at the JTAG connector. The positioning of the Stratix device and routing of the TCK line were such that the reflections caused a slight flattening of the TCK line right at the threshold which was causing "false" clock edges to be detected by the Stratix.

On the scope, the signals looked quite clean and only a very slight flattening could be observed (no ringing), however, it also worked reliably with the scope probe (10Mohm / 3.9pF) attached. I suspect, without the probe the flattening/ripple may have been more pronounced and enough to overcome the specified hysteresis. Also, had the TCK trace length been slightly longer or shorter the flattening would have been moved away from the threshold crossing and there would have been no issue. In the end, a 56pF capacitor was added to the TCK line which slowed the edge down enough so it wasn't an issue.