Yahoo Groups archive

Lpc2000

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

Thread

Problem with LPC2106

Problem with LPC2106

2004-03-02 by moostieuk

I have the olimex LPC-P1 board & I'm evaluating the crossworks system.

I placed a breakpoint on the first code of line in my main procedure 
and the debugger stopped at this point, the debugger is working and 
allows me to step/watch/etc.  

If I let the software break at this instruction and don't do 
anything, after a while the view switches to assembler and it appears 
to have jumped off to an exception vector, for example data abort, 
without me actually doing anything.

I can't get their uart example working properly either, I modified 
the cpu frequency so that it is correct.  If I single step through 
the uart initialisation (assuming I make it all the way through 
without it not jumping to an exception handler) and then run, I get 
all the "hello worlds" on the serial port.  However, if I just run 
the code without single stepping the initialisation then I get random 
sequences of "H" "L" and "."....

So, I decided to try gdb, I downloaded the 2 packages for windows 
from the mcgraigor site.  When I run the "ocdlibremote -c ARM7 -d 
WIGGLER -a 1 -s 8" I can get gdb to connect but it doesn't work and 
usually results in gdb stopping.  If I try any speed other than 8 I 
can't get it to work.

Anybody got any ideas about what's going on here?  I really don't 
know what to do - other than trying another pc.

Thanks.

Re: [lpc2000] Problem with LPC2106

2004-03-03 by Robert Adsett

At 11:15 PM 3/2/04 +0000, you wrote:
>So, I decided to try gdb, I downloaded the 2 packages for windows
>from the mcgraigor site.  When I run the "ocdlibremote -c ARM7 -d
>WIGGLER -a 1 -s 8" I can get gdb to connect but it doesn't work and
>usually results in gdb stopping.  If I try any speed other than 8 I
>can't get it to work.

One thing with the wiggler make sure of the mode your parallel port is 
in.  The Mcgraigor stuff at least prefers EPP.

Also that combination won't let you set breakpoints in flash.

Robert

" 'Freedom' has no meaning of itself.  There are always restrictions,
be they legal, genetic, or physical.  If you don't believe me, try to
chew a radio signal. "

                         Kelvin Throop, III

Re: Problem with LPC2106

2004-03-03 by moostieuk

Looks like it was the parallel port cable I was using....(The 
byteblaster cable that was supplied with a nios devkit)  Switched to 
a belkin cable and it appears to work now without problem.




--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> 
wrote:
> At 11:15 PM 3/2/04 +0000, you wrote:
> >So, I decided to try gdb, I downloaded the 2 packages for windows
> >from the mcgraigor site.  When I run the "ocdlibremote -c ARM7 -d
> >WIGGLER -a 1 -s 8" I can get gdb to connect but it doesn't work and
> >usually results in gdb stopping.  If I try any speed other than 8 I
> >can't get it to work.
> 
> One thing with the wiggler make sure of the mode your parallel port 
is 
> in.  The Mcgraigor stuff at least prefers EPP.
> 
> Also that combination won't let you set breakpoints in flash.
> 
> Robert
> 
> " 'Freedom' has no meaning of itself.  There are always 
restrictions,
> be they legal, genetic, or physical.  If you don't believe me, try 
to
Show quoted textHide quoted text
> chew a radio signal. "
> 
>                          Kelvin Throop, III

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.