⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
星期四,2017-05-04 45
#1
dhirajp15
Offline
Last seen:2 years 1 month ago
加入:2016-06-08 15:26
Production Debug Output

Hi Dialog ,
我们正在向s production , and have enabled PRODUCTION_DEBUG_OUTPUT to know if any hardfault occurs . On a hardfault I am getting the following dump on Uart channel:
<\n>--- HF STATUS<\r><\n>r0 =0x200097dc<\r><\n>r1 =0x20004988<\r><\n>r2 =0xffffffff<\r><\n>r3 =0x31534f50<\r><\n>r12=0x0000001c<\r><\n>lr =0x2000472b<\r><\n>pc =0x35343332<\r><\n>psr=0x80000019<\r><\n><\n>--- NMI STATUS<\r><\n>r0 =0x00000008<\r><\n>r1 =0x50003300<\r><\n>r2 =0x00000000<\r><\n>r3 =0x00000000<\r><\n>r12=0x0000001c<\r><\n>lr =0x00028143<\r><\n>pc =0x2000065a<\r><\n>psr=0x21000003<\r><\n><\0><9><2>
Is there a user manual to interpret this data and figure out the type of hardfault occured?
Thanks,

Regards,
Dhiraj

Device:
DA14583
Thu, 2017-05-04 16:20
MT_dialog
Offline
Last seen:2 months 2 weeks ago
Staff
加入:2015-06-08 11:34
Hi dhirajp15,

Hi dhirajp15,

There is no indication that will notify you about the type of the hardfault that occurs, hardfaults occur due to NULL pointer invocation, access an unaligned address, etc. You can only check the PC counter in the hardfault ISR and check the line in your source code that caused the ARM to go in hardfault. There is a tutorial in the Tutorial section in the documents Tab, check the Training 8:Debugging methods_v1.0.

Thanks MT_dialog

Accepted answer