We have a new system inhouse that uses a LPC2148 and every few days
(it's really random), the system locks up and requires a hard reset. I
have a serial RX tied to UART0 getting packets of info.
I got it to fail on my debugger with much effort and noticed that the
code aborts to location 0x00000040. Is this the DAbt_Handler? I don't
have any code mapped to any of these handlers? Any good writeups on how
to figure out these types of errors/crashes? It's not a stack issue (I
don't think). The stack pointer (SP) is at the top of my stack when the
error occurs. I guess it could be trying to access over the top, I
suppose. Any ideas of causes to look at? Thanks.
Sutton
--
Sutton Mehaffey
Lookout Portable Security
4040 Royal Dr.
Kennesaw, GA 30144
770-514-7999, 800-207-6269
Fax: 770-514-1285
http://www.lookoutportablesecurity.com
s...@lookoutportablesecurity.com
LPC2148 - DAbt_Handler
Started by ●January 21, 2013
Reply by ●January 22, 20132013-01-22
Hello,
Search old messages here, look for data and program abort handler. I posted
complete data abort and program abort handler. I'm using it on LPC2148 and
it's helpfull, but it will give you only address and register contents so
you must have map file and/or full disasembly listing.
On Mon, Jan 21, 2013 at 11:59 PM, Sutton Mehaffey <
s...@lookoutportablesecurity.com> wrote:
> We have a new system inhouse that uses a LPC2148 and every few days
> (it's really random), the system locks up and requires a hard reset. I
> have a serial RX tied to UART0 getting packets of info.
>
> I got it to fail on my debugger with much effort and noticed that the
> code aborts to location 0x00000040. Is this the DAbt_Handler? I don't
> have any code mapped to any of these handlers? Any good writeups on how
> to figure out these types of errors/crashes? It's not a stack issue (I
> don't think). The stack pointer (SP) is at the top of my stack when the
> error occurs. I guess it could be trying to access over the top, I
> suppose. Any ideas of causes to look at? Thanks.
>
> Sutton
> --
> Sutton Mehaffey
> Lookout Portable Security
> 4040 Royal Dr.
> Kennesaw, GA 30144
> 770-514-7999, 800-207-6269
> Fax: 770-514-1285
> http://www.lookoutportablesecurity.com
> s...@lookoutportablesecurity.com
>
Search old messages here, look for data and program abort handler. I posted
complete data abort and program abort handler. I'm using it on LPC2148 and
it's helpfull, but it will give you only address and register contents so
you must have map file and/or full disasembly listing.
On Mon, Jan 21, 2013 at 11:59 PM, Sutton Mehaffey <
s...@lookoutportablesecurity.com> wrote:
> We have a new system inhouse that uses a LPC2148 and every few days
> (it's really random), the system locks up and requires a hard reset. I
> have a serial RX tied to UART0 getting packets of info.
>
> I got it to fail on my debugger with much effort and noticed that the
> code aborts to location 0x00000040. Is this the DAbt_Handler? I don't
> have any code mapped to any of these handlers? Any good writeups on how
> to figure out these types of errors/crashes? It's not a stack issue (I
> don't think). The stack pointer (SP) is at the top of my stack when the
> error occurs. I guess it could be trying to access over the top, I
> suppose. Any ideas of causes to look at? Thanks.
>
> Sutton
> --
> Sutton Mehaffey
> Lookout Portable Security
> 4040 Royal Dr.
> Kennesaw, GA 30144
> 770-514-7999, 800-207-6269
> Fax: 770-514-1285
> http://www.lookoutportablesecurity.com
> s...@lookoutportablesecurity.com
>
Reply by ●January 22, 20132013-01-22
2013/1/22 Sutton Mehaffey
> **
> I got it to fail on my debugger with much effort and noticed that the
> code aborts to location 0x00000040. Is this the DAbt_Handler? I don't
>
1a. Send the dissassembly of first 0x100 bytes of you flash code please
1b. Or send Startup file
2. Find out there is your Dabt Handler? see you startup file
For example this is my Dabt Handler
The stack pointer (SP) is at the top of my stack when the
>
error occurs. I guess it could be trying to access over the top, I
> suppose. Any ideas of causes to look at? Thanks.
>
3. If it is an data abort handler then your theory is not 100% right
because Data abort handler has it's own SP and this SP can be setted at the
end of SP
--
CMake build environment project
for micro-controllers (use
it or
addyou
favorite MCU )
> **
> I got it to fail on my debugger with much effort and noticed that the
> code aborts to location 0x00000040. Is this the DAbt_Handler? I don't
>
1a. Send the dissassembly of first 0x100 bytes of you flash code please
1b. Or send Startup file
2. Find out there is your Dabt Handler? see you startup file
For example this is my Dabt Handler
The stack pointer (SP) is at the top of my stack when the
>
error occurs. I guess it could be trying to access over the top, I
> suppose. Any ideas of causes to look at? Thanks.
>
3. If it is an data abort handler then your theory is not 100% right
because Data abort handler has it's own SP and this SP can be setted at the
end of SP
--
CMake build environment project
for micro-controllers (use
it or
addyou
favorite MCU )
