Lpc2000

And the real beauty of the LPC series is you can put a long jump at the data abort vector (or any other vector) - jump back to "main" (or where ever) and put up a little helpful message on your LCD display (or what ever) saying "Memory Error please contact your supplier." :-)



Owen

Subject: Re: 


--- In lpc2000@yahoogroups.com, Robert Adsett <subscriptions@a...> wrote:

>> At 03:23 PM 3/6/05 +0000, david_z_lawson wrote:
>  
>
>>> >I'm new to ARM / embedded / Philips. I've got some code that I've been
>>> >stepping through and one instruction is causing a data abort, I think,
>>> >since execution goes to 0x00000010 (the data abort vector). But core
>>> >interrupts are disabled. I guess that a data abort is not really an
>>> >interrupt. But what could cause this to happen?
>>> >
>>> >on the MCB2130 / LPC2138:
>>> >
>>> >r0 =    0x00000000
>>> >r1 =    0x4000f6f4
>>> >cpsr =  0x800000df
>>> >pc =    0x400000b4
>>> >
>>> >strcc   r0, [r1], #4    <<<< causes 'data abort', goes to 0x00000010
>>    
>>
>> 
>> Doesn't the 2138 only have 32K RAM?  R1 is well above that point. 
>  
>
You are 

>> trying to access an area to no memory.
>> 
>> 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
>  
>


You're right. I just tried defining 32k memory size in my linker file
and it works fine now. I thought that I read somewhere that this
processor had 64k of ram. I just looked it up and is says 32k.

David






__________