• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 40 subscribers
  • Views 184 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/CC3220SF: exception

Asaf Tvito
Genius 4010 points
Part Number: CC3220SF
Other Parts Discussed in Thread: SYSBIOS

Tool/software: Code Composer Studio

Hi,

how can i know the reasone for:

[Cortex_M4_0] ti.sysbios.family.arm.m3.Hwi: line 1178: E_hardFault: FORCED
ti.sysbios.family.arm.m3.Hwi: line 1259: E_busFault: IMPRECISERR: Delayed Bus Fault, exact addr unknown, address: e000ed38
Exception occurred in background thread at PC = 0x01014004.
Core 0: Exception occurred in ThreadType_Task.
Task name: {unknown-instance-name}, handle: 0x200060b8.
Task stack base: 0x20006120.
Task stack size: 0x800.
R0 = 0x00010001 R8 = 0x0104de9c
R1 = 0x00000002 R9 = 0x00000000
R2 = 0x01018479 R10 = 0x00000000
R3 = 0x05000010 R11 = 0x2003d59c
R4 = 0x00000000 R12 = 0x17680200
R5 = 0x00000001 SP(R13) = 0x20006810
R6 = 0x20006840 LR(R14) = 0x010303f5
R7 = 0x2003c2c3 PC(R15) = 0x01014004
PSR = 0x21000000
ICSR = 0x04423803
MMFSR = 0x00
BFSR = 0x04
UFSR = 0x0000
HFSR = 0x40000000
DFSR = 0x00000001
MMAR = 0xe000ed34
BFAR = 0xe000ed38
AFSR = 0x00000000
Terminating execution...

  • 0
    TI__Mastermind 40965 points

    Hi,

    As the IMPRECISERR indicates, the register data saved is not from precisely when the exception occurred. Thus, examining the register data will likely be fruitless in debugging the root cause of the issue.

    Instead, you should take a look at the running state of the device when your hard fault occurs. If you are using TIRTOS, I suggest you use the ROV classic tool built into CCS to check the status of the thread stacks and heaps. Some instructions can be found here:

    https://e2e.ti.com/support/wireless-connectivity/wifi/f/968/p/733294/2707429#2707429

    Please take a look at your RTOS state and ensure that you are not running into one of those memory corruption states - in my experience the most likely cause of an IMPRECEISERR hard fault is due to memory management issues.

    Regards,

    Michael