Yahoo Groups archive

Lpc2000

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

Thread

LPC210x and Rowley CW

LPC210x and Rowley CW

2004-02-04 by Milos Prokic

Hi everyone,

I\u2019ve been developing stuff with LPC for some time now\u2026

Initially I\u2019ve been playing with Ashling software tools, then I build my own board and used Philips ISP to download code\u2026 but now that the code complexity and size is increasing I purchased the Macraigor Wiggler and started evaluating CW for ARM. Since everything so far was done in GCC, I\u2019m expecting no complications in moving the project to CW.

However, I\u2019m having some issues with flash downloads. Wiggler seems to detect something on the JTAG (0x4F1F0F0F).. and when I try downloading a hex or binary file it looks like it\u2019s erasing and then downloading but the memory content stays the same \u2013 whatever was in flash before didn\u2019t get erased, not to mention overwritten.

If anyone knows what\u2019s the trick to get the LPC210x to work with CW/Wiggler I would be very grateful.

Thank you in advance,

m.

RE: [lpc2000] LPC210x and Rowley CW

2004-06-04 by Paul Curtis

Milos,
 
One of the problems we've seen is that parallel port cables are just too
long going to the Wiggler.  What you can do is just reduce the JTAG
frequency in the target interface (i.e. increase the frequency divider I
think) and see if that works for you.  Alternatively, try a shorter or
higher quality parallel cable.

--
Paul Curtis, Rowley Associates Ltd http://www.rowley.co.uk
<http://www.rowley.co.uk/> 
CrossWorks for MSP430, ARM, and (soon) Atmel AVR processors 
Show quoted textHide quoted text
	-----Original Message-----
	From: Milos Prokic [mailto:milos.prokic@...] 
	Sent: 04 February 2004 18:47
	To: lpc2000@yahoogroups.com
	Subject: [lpc2000] LPC210x and Rowley CW
	
	

	Hi everyone,

	I've been developing stuff with LPC for some time now... 

	Initially I've been playing with Ashling software tools, then I
build my own board and used Philips ISP to download code... but now that
the code complexity and size is increasing I purchased the Macraigor
Wiggler and started evaluating CW for ARM. Since everything so far was
done in GCC, I'm expecting no complications in moving the project to CW.


	However, I'm having some issues with flash downloads. Wiggler
seems to detect something on the JTAG (0x4F1F0F0F).. and when I try
downloading a hex or binary file it looks like it's erasing and then
downloading but the memory content stays the same - whatever was in
flash before didn't get erased, not to mention overwritten.

	If anyone knows what's the trick to get the LPC210x to work with
CW/Wiggler I would be very grateful.

	Thank you in advance,

	m.

Re: LPC210x and Rowley CW

2004-06-04 by leon_heller

--- In lpc2000@yahoogroups.com, "Milos Prokic" <milos.prokic@m...> 
wrote:
> Hi everyone,
> 
> I've been developing stuff with LPC for some time now. 
> 
> Initially I've been playing with Ashling software tools, then I 
build my own
> board and used Philips ISP to download code. but now that the code
> complexity and size is increasing I purchased the Macraigor Wiggler 
and
> started evaluating CW for ARM. Since everything so far was done in 
GCC, I'm
> expecting no complications in moving the project to CW. 
> 
> However, I'm having some issues with flash downloads. Wiggler seems 
to
> detect something on the JTAG (0x4F1F0F0F).. and when I try 
downloading a hex
> or binary file it looks like it's erasing and then downloading but 
the
> memory content stays the same - whatever was in flash before didn't 
get
> erased, not to mention overwritten.
> 
> If anyone knows what's the trick to get the LPC210x to work with 
CW/Wiggler
> I would be very grateful.

Have a look at my Wiggler interface:

http://www.geocities.com/leon_heller/lpc2104.html

If yours is connected differently, that might be the problem. Those 
connections work with both a real Wiggler and my own version, with 
the Rowley software and the Macraigor utility.

Leon

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.