Lpc2000

Bertrik Sikken wrote:

>-----BEGIN PGP SIGNED MESSAGE-----
>Hash: SHA1
>
>Tom Walsh wrote:
>  
>
>>Bertrik Sikken wrote:
>>
>>    
>>
>>>>My interface works at full speed, perhaps I have a better PCB design. I
>>>>wasn't very impressed by the layout on the genuine Wiggler I have, and
>>>>        
>>>>
>>mine
>>    
>>
>>>>is faster than that.
>>>>  
>>>>
>>>>        
>>>>
>>>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).

TomW


-- 
Tom Walsh - WN3L - Embedded Systems Consultant
http://openhardware.net, http://cyberiansoftware.com
"Windows? No thanks, I have work to do..."
----------------------------------------------------