Lpc2000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Walsh wrote:
> Bertrik Sikken wrote:
>>>>The weird thing is, getting ocdremote to recognise the cable is the
>>>>hard part, once that works it seems to run fine.
>>>>The trick I mentioned is to first tell ocdcommander that a raven cable
>>>>is connected, let it fail, then tell it to look for a wiggler. If I do
>>>>that, the wiggler is recognised fine, even at the highest speed.
>>>>
>>>Are you debugging from Windows or Linux with the wiggler?
>>>
>>
>>I am trying to debug from Windows (with cygwin).
>>
>>I also tried the gdb-arm-jtag package you mentioned earlier. I replaced
>>the pp.c file with an implementation that uses libieee1284 instead
>>of directly accessing /dev/parport0 and tried to get jtag-arm to
>>work under both windows and linux, but I'm getting no data back
>>yet.
>>
> I dragged out my old wiggler clone and tried the gdb-jtag-arm working. 
> It does connect to the ARM7TDMI cpu and identifies it as an ARM7TMDI. 
> But the gdb-remote won't work with the ARM7 processor.  No register are
> dumped. I tried with the jtag-arm tool and it comes back with all
> registers as 0xffffffff.
> 
> I'm sure it prolly has something to do with the length of the SCANCHAIN
> between an ARM9TDMI vs ARM7TDMI.  It was interesting to tinker with, but
> I went back to my other unit (BDI2000).

Hi Tom,

Thanks for going through the trouble of trying out your wiggler clone.

I think I'm making some progress with my (olimex) wiggler clone
and the gdb-arm-jtag sources. It appears I can at least get the
JTAG id code now. I get 4F1F0F0F for an LPC2148, which looks similar
to the 7F1F0F0F default code that I see in the ARM7TDMI-S docs from ARM.
Do you remember which idcode you got?

I needed to do two things to make gdb-arm-jtag work so far:
1) wait a bit after the device is reset before accessing JTAG
2) make sure that parallel port bits DATA4 and DATA7 are set

Regarding 2), I see that these pins are going somewhere in
the olimex wiggler clone, but I can't clearly see where
(could be the output enables or perhaps some kind of power pins)

All the best,
Bertrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDl1uOETD6mlrWxPURAuV1AJ9Sn4bVE4x3HTEBxJfLx3yrIYO+igCgm1Xz
dJY3PpzOkLPwuj4AnGWCcoc=
=mt+C
-----END PGP SIGNATURE-----