NRF52 SDK12 hardfault if secure bootloader present

RE: NRF52 SDK12 hardfault if secure bootloader present

Mariano — Tue, 15 Aug 2017 12:07:16 GMT

Yes! I was using the rtc module to implement a timeout at the bootloader. I had to uninit it before start the app. Thanks so much guys, "Estaba orinando fuera del tarro"

RE: NRF52 SDK12 hardfault if secure bootloader present

Hung Bui — Mon, 14 Aug 2017 11:50:56 GMT

@Mariano: I agree with RK. If you don't implement the handler of the interrupt it will end up there. FPU_IRQHandler() happens to be the last in the list. The value of the register would help telling which IRQ was triggered. I suspect in a peripheral was used without proper configuration. And if the bootloader use the same peripheral (UART for example) you may run into trouble if it's not re-configured properly in the application.

RE: NRF52 SDK12 hardfault if secure bootloader present

RK — Sun, 13 Aug 2017 00:14:38 GMT

Are you sure it is the FPU IRQ handler? All your handlers are at the same address, they are just aliases for each other, the FPU one just happens to be shown last in the disassembly. What are the actual registers at this point, that will tell you the actual exception/irq which has been taken.

RE: NRF52 SDK12 hardfault if secure bootloader present

Mariano — Sat, 12 Aug 2017 23:32:39 GMT

@Hung Bui, see my update please! Also, making a more detailed debugging I could saw the UART event handler still working, but the freertos's tasks are dead. Again, erasing the bootloader all works ok.

RE: NRF52 SDK12 hardfault if secure bootloader present

Hung Bui — Thu, 10 Aug 2017 12:12:41 GMT

Hi Mariano,

From what you described, doesn't seems that it's a hardfault. For some reason the FPU interrupt was enabled and you don't have a FPU interrupt handler to handle it. Is it correct ? You can test by implementing the FPU_IRQHandler() in your main.c and clear the event.

If it's correct there must be something wrong with the bootloader that it enable the FPU interrupt.

RE: NRF52 SDK12 hardfault if secure bootloader present

Mariano — Wed, 09 Aug 2017 12:28:38 GMT

Hi, i'm running s132 softdevice + freertos. I'm using FDU (I'm setting Use Single Precision in keil). I got the hardfault when I'm debugging the app after download it through DFU. Also the system crash but not reboot.

I know how to debug with keil, but I can't find the cause.

["If I erase the bootloader (no need of downdload the app again) all works fine" is pretty strange. If you flashed the bootloader and erase it, the app shouldn't start. I'm not sure what's wrong here.] Me neither, I'will try with other app, but i'm follow the guides and examples to setup the secure bootloader and all seems to work fine.

Any other suggestion in the meantime?

RE: NRF52 SDK12 hardfault if secure bootloader present

Hung Bui — Wed, 09 Aug 2017 11:54:17 GMT

Does your app use FPU ? Could you check in debug mode what exactly cause the problem? You may want to follow the debugging guide here.

This: "If I erase the bootloader (no need of downdload the app again) all works fine" is pretty strange. If you flashed the bootloader and erase it, the app shouldn't start. I'm not sure what's wrong here.

Can you reproduce the issue with our SDK's example as the application ?

I assume you download your app to the flash using OTA DFU , not using SWD interface to flash ?