Lpc2000

>     Hi,
>
>  I have a Agilent E5900B emulation probe that I've been trying to get
>  working on a LPC2134 with ADS.  It works fine on my AT91 dev board,
>  but I cant get it to work in ADS with the LPC2134.  Note that this
>  probe is ARM7TDMI not -S.  I seem to have some success (RESET, STOP,
>  RUN, and STEP, and poll register etc..) using the telnet interface
>  when I disconnect the RTCK pin.  But either way I get alot of Data
>  Aborts in ADS.

I also had some problems (with a Jeeni). It seems to work sometimes or up
to a certain moment and then strange errors pop up.

Meanwhile I am developing my own JTAG probe - using RTCK I get to about 2
MHz on the jtag clock (14.7 MHz crystal).
There are indeed some differences between the TDMI and the -S version that
may render your TDMI debugger unusable. The TDMI has a third public jtag
chain and (as far as I remember) supports both INTEST and EXTEST.

A wiggler may do OK for you but I don't like the use of the printer port
(apart from not being available on my laptop). Therefor I decided to go
for a debuggerpod that is connected via Ethernet, using the RDI protocol
which makes it suitable for a wider range of debugger software.
Software is not yet finished, I keep running into small problems from time
to time ...

If the Agilent uses RID, try using another debugger (e.g. gdb). I found
that I could do some debugging with the Jeeni via the RealView debugger
but was not able to do anything with GDB. It may be the other way around
for you.

Regards,

    Rob