Lpc2000

We are developing on a Ashling EVBA7 with a LPC2106 using the IAR 
EWARM 4.11A. We are using nesting interrupts. We have some code 
which seems to run fine on 1 of the EVBA7 boards but branches to 
0x7FFFE254 on the other 2 as soon as interrupts are enabled. They 
are all using the 14.745MHz xtals and the code is setting up and 
using I2C, Timer0 and Timer1. We are setting the PLL to run at 
58.98MHz and the VPB is set to 1 to run the VPB at the same speed as 
the processor. The same problem occurs whether we run the code in 
flash or RAM.

I have tried everything a can think of to track down the cause but 
so far no luck.

This is NOT being caused by an exception. All of the exceptions 
except IRQ point back to itself in the startup code.

Does anyone know what may be causing this to happen.

Thanks
Rick

0x7FFFE254? Thats appears to be an address in the bootblock section.

Just out of curiosity, what's your current MEMMAP configuration?

--- In lpc2000@yahoogroups.com, "helicopterproject2003" 
<helicopterproject2003@y...> wrote:
> We are developing on a Ashling EVBA7 with a LPC2106 using the IAR 
> EWARM 4.11A. We are using nesting interrupts. We have some code 
> which seems to run fine on 1 of the EVBA7 boards but branches to 
> 0x7FFFE254 on the other 2 as soon as interrupts are enabled. They 
> are all using the 14.745MHz xtals and the code is setting up and 
> using I2C, Timer0 and Timer1. We are setting the PLL to run at 
> 58.98MHz and the VPB is set to 1 to run the VPB at the same speed 
as 

> the processor. The same problem occurs whether we run the code in 
> flash or RAM.
> 
> I have tried everything a can think of to track down the cause but 
> so far no luck.
> 
> This is NOT being caused by an exception. All of the exceptions 
> except IRQ point back to itself in the startup code.
> 
> Does anyone know what may be causing this to happen.
> 
> Thanks
> Rick

> This is NOT being caused by an exception. All of the exceptions 
> except IRQ point back to itself in the startup code.

what happens when you make IRQ point to itself? If this locks the 
LPC at IRQ vector then you have something wrong in your interrupt 
driver code.

--- In lpc2000@yahoogroups.com, "helicopterproject2003" 
<helicopterproject2003@y...> wrote:
> We are developing on a Ashling EVBA7 with a LPC2106 using the IAR 
> EWARM 4.11A. We are using nesting interrupts. We have some code 
> which seems to run fine on 1 of the EVBA7 boards but branches to 
> 0x7FFFE254 on the other 2 as soon as interrupts are enabled. They 
> are all using the 14.745MHz xtals and the code is setting up and 
> using I2C, Timer0 and Timer1. We are setting the PLL to run at 
> 58.98MHz and the VPB is set to 1 to run the VPB at the same speed 
as 

> the processor. The same problem occurs whether we run the code in 
> flash or RAM.
> 
> I have tried everything a can think of to track down the cause but 
> so far no luck.
> 
> This is NOT being caused by an exception. All of the exceptions 
> except IRQ point back to itself in the startup code.
> 
> Does anyone know what may be causing this to happen.
> 
> Thanks
> Rick

When flashing MEMMAP=2, when loading to RAM MEMMAP=1 along with the 
changes to the .xcl files that specify the flash and RAM addresses.

--- In lpc2000@yahoogroups.com, "Leighton Rowe" <leightonsrowe@y...> 
wrote:
> 0x7FFFE254? Thats appears to be an address in the bootblock 
section.
> 
> Just out of curiosity, what's your current MEMMAP configuration?
> 
> --- In lpc2000@yahoogroups.com, "helicopterproject2003" 
> <helicopterproject2003@y...> wrote:
> > We are developing on a Ashling EVBA7 with a LPC2106 using the 
IAR 
> > EWARM 4.11A. We are using nesting interrupts. We have some code 
> > which seems to run fine on 1 of the EVBA7 boards but branches to 
> > 0x7FFFE254 on the other 2 as soon as interrupts are enabled. 
They 
> > are all using the 14.745MHz xtals and the code is setting up and 
> > using I2C, Timer0 and Timer1. We are setting the PLL to run at 
> > 58.98MHz and the VPB is set to 1 to run the VPB at the same 
speed 
> as 
> > the processor. The same problem occurs whether we run the code 
in 
> > flash or RAM.
> > 
> > I have tried everything a can think of to track down the cause 
but 

> > so far no luck.
> > 
> > This is NOT being caused by an exception. All of the exceptions 
> > except IRQ point back to itself in the startup code.
> > 
> > Does anyone know what may be causing this to happen.
> > 
> > Thanks
> > Rick

> When flashing MEMMAP=2, when loading to RAM MEMMAP=1 along with 
the 
> changes to the .xcl files that specify the flash and RAM addresses.
> 
Hmm...it appears your vectors are mapped to RAM if your code's 
running from flash, or mapped to flash if you're running code from 
RAM. I haven't seen this done before.

(According to pg.42 of the 2106 UM for the Sys. control block)
MEMMAP = 1 (when in User Flash Mode)
MEMMAP = 2 (when in User Ram Mode) 

Try switching your MEMMAP assignments and see what happens.