SIMPLELINK-MSP432-SDK: HWI fault in SimpleLink SD driver code.

Hi,

I sent it to a concerned engineer. We will get back to you ASAP. Please bear with us.

Thanks,

PM

Hi Michael,

I have tracked the heap memory, but that didn't seem to be the issue.  (See Image Below.)

However, further troubleshooting has found that there was an NVM write occurring that seemed to be the cause of the failure.  By commenting out the NVM write and reads I was able prevent the error from occurring running some 200 iterations of the read write cycle on the SD card without issue. 

But I am still troubled. 

After 2 days of adding everything else back with the exception of those NVM writes (they store adaptive settings for our instrument.)  The functionality continued without incident for over 1000 cycles. So I added the NVM writes and reads back with the intention of troubleshooting the failure.  My issue is that now I am unable to reproduce the failures.  I'm still attempting different combinations of scenarios to see if I can identify why this failure occurred in the first place. 

We have at least 4 documented occurrences of  this failure occurring in field testing units over the past year.  It seems to me that it is something that occurs when there is a confluence of more than one factor, but what those factors are, I'm unable to isolate at the moment.  I am not confident in my assumption that the NVM write is directly responsible for the error (I will continue to verify that the code is behaving) or if by removing the NVM writes I simply inadvertently altered either a memory location or a persistent failure. 

So I have two main questions in my attempt to troubleshoot this further.

1) Do you know of a mechanism in which an NVM write could cause a failure such that when the SD driver attempts to mount the file system an error occurs but not prior to this, (multiple UART communications and memory writes occur to store the data from the instrument write.)
2) Where or how might I get an Idea of what elements are stored in what parts of memory such that a busfault as thrown in my original question can be diagnosed.  I tried looking at previous forum threads but suggestions there don't seem to be applicable (ie I can't find a file hw_memmap.h etc.)

I apologize if either of these have an obvious answer, I was dropped on this issue due to a change in manpower and embedded is not my primary area of expertise.

Cheers,
GE

Hi,

It's good to hear that you've narrowed down the issue you were seeing to the NVM accesses. 

It's not so good to hear that adding the NVM accesses back in doesn't result in the issue reproducing itself again. This makes me think that the root cause of the issue doesn't have to do with the NVM accesses. 

For these NVM accesses, are you using the NVS driver? Also, are you using the internal flash, an external flash device, or something else as your NVM?

I suspect that when you reintroduced your NVM code, the compiled output changed to the point where the failure might not occur in the same way as before. With the sort of bus fault you are getting, it is possible in the new binary the same error case is occurring, but the address read is a legal address within the memory map of the device. This executable memory map can be seen within the MSP_EXP432P401R_TIRTOS.cmd linker file, and within section 1.4 of the TRM: ti.com/lit/slau356

One thing you could do is look at the PC and LR of your error case, and see if you can identify what functions may be causing the bus fault directly. If you look at your project's debug folder with the .out, there should also be a .map file. This file will map every compiled object to a memory address. When you combine this with looking at the raw assembly code, you should be able to track down what instruction in which function causing the abort. From there, you can look at the register values to see how your MSP432 got into its bus fault state.

You can load your old .out binary if you still have it manually through the debugger. See this E2E post for pointers: https://e2e.ti.com/support/legacy_forums/embedded/tirtos/f/355/t/557599?how-to-re-establish-debug-connection-after-hibernate-reset

Once your old binary is loaded, you can look through the memory browser and assembly code to try to trace back what went wrong. If you cannot reproduce the error with your new binary, then that is probably the most straightforward method to debug your issue.

Regards,

Michael