Immediate HardFault on custom nRF52832 board

RE: Immediate HardFault on custom nRF52832 board

Hung Bui — Wed, 23 Mar 2016 12:06:31 GMT

Hi Lucas,

Yes it's the anomaly 73 as in this document: infocenter.nordicsemi.com/.../nRF52832_Engineering_B_Errata_v1.1.pdf

We called them PAN (Product Anomaly Notification) earlier.

RE: Immediate HardFault on custom nRF52832 board

Lucas Magasweran — Wed, 23 Mar 2016 01:54:41 GMT

Hi @hungbui, I am not sure what a PAN fix is. The release notes mention that to use the latest SoftDevices on Engineering A and B nRF52 chips you must implement the workaround for anomaly 73 (TIMER: Event lost, see infocenter.nordicsemi.com/.../errata.html ).

RE: Immediate HardFault on custom nRF52832 board

Hung Bui — Tue, 22 Mar 2016 13:13:17 GMT

Hi Lucas,

Good to know it worked now, and please be noted that if you want to use PCA10040 v0.9 with S132 v2.0.0 production you would to apply a PAN fix. Please refer to the release note.

RE: Immediate HardFault on custom nRF52832 board

Lucas Magasweran — Mon, 21 Mar 2016 22:56:28 GMT

Thank you @HungBui ! SoC revision was my issue. I updated my board to a Engineering C SoC and ported my project to the latest nRF5 SDK v11.0.0. I did an nrfjprog --eraseall to remove the previous SoftDevice and now blinky works with debug support.

RE: Immediate HardFault on custom nRF52832 board

Hung Bui — Thu, 17 Mar 2016 12:34:31 GMT

Hi Lucas,

The QAAAC is the Engineering A chip, which is very early version and has lots of errata with it. Maybe some of the workaround is not applied when you test with newer SDK. Could you try to test with SDK v0.9.0 here ? Also you mentioned that you had a working BLE application before on your custom board, would you be able to debug with that application ? I mean to get to main loop ?