I have just connected a ULINK2 to my development board and i get communications error.
The device is a ADuC7026 (ARM7TDMI core)... A few Questions??
The uVision3 options for the debugger gives 2. ARM Debugger & ARM7 Debugger Which Should I use??
If I select the ARM7 one i get an error message, "Missing jarm.dll" If I selet the ARM it gets further but there is JTAG Communication Failure against the TDO line
Second question...should the TDO line on the chip goto the TDO on the ULINK or should there be crossover with TDI->TDO and TDO->TDI
use ULINK ARM Debugger only
If I selet the ARM it gets further but there is JTAG Communication Failure against the TDO line
what do you mean by "failure against TDO line?"
In general if target JTAG setting is not proper then it will display JTAG communication failure
TDI of MCU to be connected to TDI line of ULINK2. for better understanding you can refer to ULINK2 user guide under Help
There is nothing wrong with my target board because using another Jtag device i can communicate with an FPGA which is chained after the MCU so data is going through the MCU ok.
The problem must be in the ULINK2 or the uvision3 setup.
When I select ULINK ARM DEBUGGER and go to settings page I get "JTAG Communications failure" below the JTAG Device Chain side.
On the left under the "ULINK USB-JTAG Adapter" there is nothing no serial number, no ULINK Version etc
So it would seem that the uVision is not talking to the ULINK BOX
yes you are correct if nothing is shown under adapter you can suspect ULINK only.
if ULINK connector is connected in reverse direction the latches inside the ULINK will go bad.
replace the particular latch and you can use it again.
Thanks...
I I connect the ULINK to PC only then all the data under the Adapter section is displayed.
when i connect ULINK to PC and Target then nothing is displayed under Adapter section and I get Comms failure message.
To me that would now suggest that the target setup is wrong.
I am using 10k pullups instead of the 100k suggested in user guide, would that cause a problem??
I connect the ULINK to PC only then all the data under the Adapter section is displayed.
if that is the case it is very clear that you are connecting ULINK JTAG connector in reverse direction to your Target board. If you had done this many times your ULINK will work no more.
what I can suggest you is connect the ULINK JTAG connector in right direction and check once again(take the help of user guide for connector direction details).
still you are having problem you can either change the ULINK or get the concerned latches in ULINK changed.
Here I am not suspecting your target board because you said that using the same JTAG you have communicated with FPGA.
Thanks
PLease advise which chips are the latches.
When I use the Altera usb adapter and its software ( the altera device sits first on the chain) it returns an ID for the Altera chip but for the ADuC7026 chip it just lists it as UNKNOWN DEVICE.
The idcode returned for the ADuC7026 using the Altera adapter is 0x3F0F0F0F which seems ok from what i have read.
Data verify for the Altera chip is ok so that pass through is ok for the micro. So clearly the Target is working OK but the ULINK2 is not, latches look ok as well.
Has anybody got any waveforms for the jtag signals so I can check them.