Hardfault on sd_softdevice_disable

[Matthieu Tardivon]

Hi,

I am trying to run several applications sequentially on the nRF51822. I have another microcontroller controlling the nRF51822 by SPI. I init the stack, the services, advertise and my first application works well. Then the microcontroller tells the nRF51822 to disable the stack and I get an Hardfault before asking to init it again and to init then my new services for my second application. How could disabling the soft device cause an hard fault ?

[Bastiaan]

Don't bother answering this thread, it can be deleted. The error comes from somewhere else. Keil uVision debugger step by step is a bit +")%#@?!!! (not to say the whole software) and made me believe the problem was due to disabling the stack. Sorry for wasting the time of people who read my question.

[Guest]

Don't bother answering this thread, it can be deleted. The error comes from somewhere else. Keil uVision debugger step by step is a bit +")%#@?!!! (not to say the whole software) and made me believe the problem was due to disabling the stack. Sorry for wasting the time of people who read my question.

[Ole Morten]

Good! I couldn't quite imagine any way that a call to the sd_softdevice_disable() should cause a HardFault, so I did suspect something else being the real problem.

For future reference, if you end up in the HardFault handler, that ususally means that you have triggered the MPU in some way, by writing to a protected peripheral, protected RAM or protected flash.

To clear things up, I'll mark this answer as accepted.

[psyuk]

I had this issue. Turns out I'd erased/reprogrammed the softdevice.

Worth noting as I can't see this mentioned anywhere as a possible cause of a hard fault on sd_softdevice_enable()