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.

MSP432E401Y: Hard Fault Address = 0xbebebebe

Part Number: MSP432E401Y

Hi Charles,

I have the problem that although our system is working functionally fine, at some point of time a system exception will occur during load tests. I know, the exception show does not need to be related to where the system has come to crash as other functions may have overwritten memory, I know you have well-written problem solving guides. But given all that, we have done a lot of debugging, code review, heap monitoring, added traps in the those parts of the code which may potentially create complex situations, ... Nothing, all fine.

Below a screenshot of the ROV:

There are not memory overruns within the tasks, the only red one is just closing and in the moment a task exits/deletes, ROV always shows PeakSize = TaskSize. There are no overruns in mailboxes (the overrun itself would not harm but it could show that something is going wrong with a task execution), no Semaphores pending unexpectedly.

There is plenty of heap memory, the only strange thing is the orphan heap with ID 12 which requested 0 bytes and it shown in overrun state. But as the system clock counter is low, this does not seem to be related to the exception to me.

All Hwi interrups result despatched and - not visible here - also on Swi/clock side there is nothing pending.

NDK is fine as well in terms of memory and working sockets.

What caught my attention is the decoded exception message:
Hard Fault: FORCED: BUSFAULT: PRECISERR.Data Access Error. Address = 0xbebebebe

Does 0xbebebebe indicate any specific address or event?

As the task sll shows status "preempted" but it is not waiting for anything (nothing shown pending on the right column), does this mean it has been the last task running before the system entered the exitSpin?

Do you have any other suggestion where to look at or what may cause the exception?

Regards
Peter