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 Michael Johnson

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
>
>
>
> 
>
>
>  
>

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.