We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
When using the ULink2 my ADuC7026 Microcontroller shows as "Unknown JTAG Device" in the ARM Target Driver Setup window. If I use an old ULink it shows up correctly and can be programmed, etc. What's wrong? The IDE detects the ULink2 correctly, it is version 3.53.
Have you tried with both ULINK2 jumper settings (as mentioned before) ?
Can you at least connect to the target ? Try to start the debug session with "Load Application at startup" disabled. If you can enter debug mode then check the value of REMAP register (address 0xFFFF0220 in Memory window). The value should be zero.
Check also the state of BM (Boot Mode) pin. It should be high at reset.
Hi Robert, I've tried both jumper positions, in the ARM position the ULink2 reads a garbled IDCODE, but in the 3,3V position it seems to detect the target correctly.
I usually get a lot of JTAG communication failures when I try to enter debug mode. Using the old ULink I can read the value of 0x06 from the REMAP register. With the ULink2 I think I once read a value of 0x11 from the REMAP register, which is interesting.
Next week I will have some custom hardware based around the ADuC7021. I'll play with it some more then.
Cheers, Mark
I believe that the problems could be caused by noise on the JTAG lines. The output drivers on ULINK2 are slightly different than on ULINK and this might explain the different behavior.
However we are not aware of such problems and we have tested ULINK2 (which we now use exclusively) on a lot of different targets. Maybe you can look at the JTAG waveforms with an oscilloscope to check if there is some ringing or other anomaly.
Hi, I have looked at TDO, TMS, TCK and TDI with a scope. To trigger some activity I changed the "Max JTAG Clock" to 100kHz each time. The most striking difference between the ULink and the ULink2 is that the frequencies are different. You can see the traces here:
www.analox.net/.../ULink.zip
You'll need to download it and unzip.
Thanks, Mark
The waveforms look OK (no problematic noise).
Can you also check nTRST and nRESET (on ULINK/ULINK2 and on chip - since it might be that they are not routed to the chip).
There's no noise on TRST and RESET. The levels on TRST looked a bit odd so I put a 100k pullup on that signal (there isn't one on the AD evaluation board) but it didn't help. Reset wasn't connected to the chip. It is connected now but that didn't help either!
You are sure that you are using the ULink2 with the AD Microconverter ADuC7026 evaluation board without problems?
Yes, I'm using ULINK2 with the Analog Device ADuC7026 Evaluation board (and other ADuC702x/703x boards) and never experienced any problems.
Can you send also the TRST waveform which you said looks a bit odd.
Hi, The graphs are now at: www.analox.net/.../TracesfromULinkandULink2.htm The graphs of the TRST do show some spikes on the ULink2 only. Cheers, Mark