Yahoo Groups archive

Lpc2000

Index last updated: 2026-04-28 23:31 UTC

Message

RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex lpc2129 proto board

2005-11-24 by Karim Virani

Yes - I went back to the original modern laptop and it works with Rowley!  Must've had something off on the parallel port on the older system (though I can use it for other bidirectional, non ecp applications).  Still can't use the newer system with IAR or OCDCommander - it doesn't even recognize the wiggler.  At least I know the jtag hardware works.

So Rowley works like a dream - I can connect via the wiggler, I can download and I can set hardware breakpoints and debug from flash in it.  Goes back to the old price problem for hobbyists.  Maybe they'll sell me an academic licence.  The other problem is that there are many fewer examples.  There's no complete set of header files and examples for the olimex 2129 proto board like there are in IAR.

And is most of the example and free code out there implemented for the gnuarm chain?  I'm entirely new to microconrollers.  Perhaps I should go with Jim Lynch's environment and not worry about flash debugging for now.  I'm under the impression that OCDLibRemote in cygwin doesn't have the same problems that OCDCommander running natively in Windows has.  Is that right?

Thanks,

Karim

-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Michael Johnson
Sent: Thursday, November 24, 2005 12:59 AM
To: lpc2000@yahoogroups.com
Subject: Re: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


Hi Karim,

Do you have another computer you can try? It could be that your PC 
parallel port isn't working.

Regards
Michael

>Since Crossworks is supposed to be bulletproof with wigglers, so I
>downloaded a trial copy. It won't connect to the target - I get the
>message "Cannot identify target. Check JTAG Connections and that the
>target is powered" Same message as when there's nothing connected to the
>parallel port.
>
>Is it more likely that my olimex-jtag is DOA or it's the jtag port on
>the 2129 board? If the olimex-jtag adapter is fried, can it endanger the
>board - I have a 2nd board I can try, but don't want to risk frying it. 
>
>Karim
>
>-----Original Message-----
>From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
>Of Joel Winarske
>Sent: Tuesday, November 22, 2005 11:50 AM
>To: lpc2000@yahoogroups.com
>Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
>lpc2129 proto board
>
>
>  
>
>>I understand that the wiggler will only let you debug in RAM, and in
>>    
>>
>IAR
>  
>
>>linker options I do have the RAM xcl file selected.  In debugger
>>    
>>
>options
>  
>
>>I don't have any startup macro file defined - I'm not sure what I
>>    
>>
>should
>  
>
>>be using.  I did enable hardware reset like you recommended, but that
>>didn't work either.
>>    
>>
>
>Your IAR debug macro file must have the following in order to debug from
>RAM:
>
>execUserPreload()
>{
>    __writeMemory32(0x00000002, 0xE01FC040, "Memory"); // MEMMAP = 2;
>}
>
>
>Joel
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>
>  
>




 
Yahoo! Groups Links

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.