HardFault Handler triggered in isodepMapFsdLength

[CurtisHx]

I'm using SDK nRF5_SDK_15.0.0_a53641a, and I was able to trigger the hard fault handler from within the Nordic NFC library.  Nothing was running.  The microcontroller was asleep when the NFCT interrupt fired.

Here's the call stack:

Here's the Disassembly of where it crashed:

Unfortunately, I disconnected the debugger and reset the device before I was able to grab the CPU registers.  I'm not quite sure what I did to cause this, either.  I was "abusing" the NFC by doing lots and lots of reads with an Android phone.  If I manage to crash it again, I'll be sure to get more information.

[bjorn-spockeli]

Hi Curtis, 

Thanks for letting us know. 

I cant find any open issues related to HardFaults caused by isodepMapFsdLength() function on wakeup in our internal bug reports.

Its hard to say what the cause of the HardFault is without knowing which params that were passed to function or the steps to reproduce the issue( other than doing lots of reads) .  I will forward your findings to the developers and see what they have to say about it.

If you manage to reproduce the issue then let us know. 

Best regards

Bjørn 

 

 

[CurtisHx]

I have not been able to make it happen again (and I was doing a LOT of NFC activity).  It did happen when the NFC interrogator was physically distant from the nRF52 NFC antenna.  There coupling was not good. 

[bjorn-spockeli]

Thanks for the additional information. I have not heard anything from the developers yet, but I will pass on the information regarding the distance between the interrogator and the nRF52 NFC antenna.

Bjørn