Lpc2000

Yes - I have the debug jumper installed, the bsl and jrst jumpers are
open.  I tried the other board - same response.  I think I got a bum
wiggler.

Karim

-----Original Message-----
From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com]On Behalf
Of Dan Beadle
Sent: Wednesday, November 23, 2005 7:24 PM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board


Are you sure that the jumpers are installed to enable JTAG?  

 

The JTAG port is pretty rugged - so unlikely that you fried it.

 

The ports are pull up to the 3.3V on the jtag port - so not likely that
you would do any damage.  I would try the other board, check the jumpers
first (there is a jumper that tells the chip to use JTAG, otherwise it
is ignored)

 

Dan

 

 

  _____  

From: lpc2000@yahoogroups.com [mailto:lpc2000@yahoogroups.com] On Behalf
Of Karim Virani
Sent: Wednesday, November 23, 2005 5:21 PM
To: lpc2000@yahoogroups.com
Subject: RE: [lpc2000] Problems with olimex (wiggler) jtag and olimex
lpc2129 proto board

 

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 

 

*	 Visit your group "lpc2000
<http://groups.yahoo.com/group/lpc2000> " on the web.
	  
*	 To unsubscribe from this group, send an email to:
	 lpc2000-unsubscribe@yahoogroups.com
<mailto:lpc2000-unsubscribe@yahoogroups.com?subject=Unsubscribe> 
	  
*	 Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service <http://docs.yahoo.com/info/terms/> . 

 

  _____  



[Non-text portions of this message have been removed]




 
Yahoo! Groups Links



 





[Non-text portions of this message have been removed]