Yahoo Groups archive

Lpc2000

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

Message

Re: [lpc2100] GCC-3.4 2003-12-17 snapshot

2003-12-19 by Pablo Bleyer Kocik

Hello!

At 10:49 19-12-2003, you wrote:
>OK, wow have I messed up.  They say as you get old, the mind is the
>second thing to go.  Yesterday when I finally stated my conclusion
>that the gcc-3.4 snapshot was working OK, well, err, I was wrong.
>Between the mail list activity, meetings, and other work, I had
>removed the snapshot and I was actually compiling and testing the code
>with the GNUpro distribution that has always worked for me.
>
>This morning I reloaded the gcc-3.4 snapshot and recompiled from
>scratch.  Using an older version of Insight, I could not get the code
>to run on either my eval board or in the simulator.  In the simulator,
>I could single-step (asm level) it seems for as long as I wanted.  But
>anything greater than that (C lang step) would cause the simulator to
>start executing code where there was no code.  I could not get even
>that far with Insight and a JTAG connection to my eval board (running
>in RAM on an EB40A).  The code jumps into never-never land during the
>port initialization routine well before interrupts are enabled.
>
>I'll try to spend some more time on the problem in an attempt to
>isolate it.  Sorry for the repeated erroneous reports.

  Did you try the 3.3.2 release?

  I just updated it to use the fixed build scripts. I rebuilt Newlib to 
pick up the interwork libs.

  BTW, I was reading my yesterday reply to your email. It shows up there:

---8<---
ISRs do not return with the bx instruction. ISRs restore the CPSR
saved in the link register (r14). This will preserve the mode the processor
was in before the interrupt.
--->8---

  This is obviously not correct. There is part of a sentence missing here. 
It should say "ISRs restore the CPSR and then the return address saved in 
the link register".

  Please keep me updated with your tribulations ;^)

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.