Yahoo Groups archive

Lpc2000

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

Message

Re: Crossworks and Ram debug

2004-07-13 by hodgejackiehank

> 
> Are you sure that you need to re-compile the loader? The default 
> loader uses the ARM's debug comms channel to communicate with the 
> debugger and the debug comms channel has nothing to do with the 
> serial port. If it is an issue of signal usage, then I can't see that 
> the RAM loader would be any better as it uses the same JTAG signals 
> used by the debug comms channel loader.
> 
> Jon Elliott

Uh hu. As you may have seen on earlier posts, I started out with web7
days kit. I have now 'upgraded' to Olimex, but still have thier wriggler.

Now, early on in the show I saw the comms channel loader, and I knew
that the bootloader used the serial port, so I kind off assumed that
the comm loader option was for use together with the serial port.....I
attached a serial leaded to com1 and it started to work. I still had
some difficulty but found that the target board did not have the 3v3
connected and it was running througth the protection diodes. I also
noted that the ground pins on the wriggler side were not connected to
gnd, gns was only connected on the // port side, but I assumed that
previously it had been getting 0V via the serial.

Of course it had, but I had not realised that was the **only** reason
I was getting more results by connecting the serial cable :-o

I have been working away assuming that the Flash debug option was
using the serial port to mod the code!

BTW, Be wary of saving a few dollars with web 7 days.....they really
are rock bottom quality wise!

The Olimex stuff works fine, and well built, allthougth the V.regs
could do with a bit more heatsinking, I would reccomend using a
regulated supply @ about 7V.

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.