This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF52 SDK12 hardfault if secure bootloader present

Hi! For a custom board, I have my app working ok. So I wanted to add the dfu secure bootloader to my project. I Had no problem to do that, both app and bootloader start ok and I could download the software package ok.

BUT: near to a minute after de app start, it crash. In debug I get: FPU_IRQHandler, inside of "Default Handler" at "arm_startup_nrf52" [UPDATED]: See the picture below.

If I erase the bootloader (no need of downdload the app again) all works fine [UPDATED]: I tried it again, and I was wrong.

I'm suspecting a memory issue, maybe in ram? But I had no succed in found a solution.

image description Help please!!!

Parents
  • @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.

Reply
  • @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.

Children
Related