AWR1642BOOST: debug error

user5153216

Part Number: AWR1642BOOST
Other Parts Discussed in Thread: SYSBIOS, AWR1642

hello，

the debugging error as followes：

Exception occurred in ThreadType_Task.
Task handle: 0x8000178.
Task stack base: 0x80001c8.
Task stack size: 0x800.
R0 = 0x08006000 R8 = 0x00000004
R1 = 0x08000040 R9 = 0x00000000
R2 = 0x0800003c R10 = 0x08009d3c
R3 = 0x00000000 R11 = 0xffffffff
R4 = 0x00000000 R12 = 0xa0000000
R5 = 0x08009d18 SP(R13) = 0x07fffff8
R6 = 0x08000068 LR(R14) = 0x000083e4
R7 = 0x00000000 PC(R15) = 0x0000fea4
PSR = 0x200c019f
DFSR = 0x0000080d IFSR = 0x00000000
DFAR = 0x07ffffe0 IFAR = 0x00000000
ti.sysbios.family.arm.exc.Exception: line 205: E_dataAbort: pc = 0x0000fea4, lr = 0x000083e4.
xdc.runtime.Error.raise: terminating execution

Thanks！

over 6 years ago

0 user5153216 over 6 years ago

Intellectual 990 points

case Exception_Type_DataAbort:
Error_raise(0, Exception_E_dataAbort, pc, excStack[2]);
break;

0 user5153216 over 6 years ago in reply to user5153216

Intellectual 990 points

What caused this error?

0 Cesar over 6 years ago in reply to user5153216

TI__Guru*** 138439 points

Hi

Please use the Task handle value to identify which task has produced this exception.

Please also search the forums for TI RTOS debug information that would help you debug this issue.

Thank you
Cesar

0 user5153216 over 6 years ago in reply to Cesar

Intellectual 990 points

Your answer is not clear, there is no help！

0 user5153216 over 6 years ago

Intellectual 990 points

case Exception_Type_DataAbort:
Error_raise(0, Exception_E_dataAbort, pc, excStack[2]);
break;

0 Cesar over 6 years ago in reply to user5153216

TI__Guru*** 138439 points

Hi,

Since the AWR1642 has two processing cores (C647x and ARM), the first debug step is to identify if the exception happens on the C647x core or the ARM core.

In the log above, you can see that the exception comes from "ti.sysbios.family.arm.exc.Exception", which means that the exception is generated by ARM core.

Second debug step is to identify the instruction that generates the exception by looking-up in disassembly window the PC address to see where the code is.

In the log, "pc = 0x0000fea4". Please identify what instruction this corresponds to.

Third debug step is to analyze the DFSR and IFSR to understand what type of fault generated the exception. Please search the ARM R4F documentation from ARM website

infocenter.arm.com/.../index.jsp

Fourth debug step, analyze the DFAR to understand which data address caused the fault if it was because of data access , which seems the case here. Please search the ARM R4F documentation from ARM website

infocenter.arm.com/.../index.jsp

Thank you
Cesar

Sensors

Sensors forum

AWR1642BOOST: debug error