• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 62 subscribers
  • Views 6025 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 112305
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

sd_softdevice_enable hardfault

Fabien Comte

Hello,

sd_softdevice_enable falls in hardfault. I have no 32.768 KHz crystal but is set lfclk with NRF_CLOCK_LFCLKSRC_SYNTH_250_PPM.

I'm running my application on a custom board with a nRF52, S132 SD 2.0.0 alpha 7, jling debug over nRF52 DK.

What can i check please ?

Parents
  • 0

    .. but you're calling it from an interrupt handler? Check the actual value of the IRQ priority you are running at when you call sd_softdevice_enable(), remembering that the IRQ available priority values are different on the nRF52 than the nRF51. You should be able to see that in one of the status registers.

    If that doesn't give you the answer, then you look at the stack and figure out exactly where you came from.

Reply
  • 0

    .. but you're calling it from an interrupt handler? Check the actual value of the IRQ priority you are running at when you call sd_softdevice_enable(), remembering that the IRQ available priority values are different on the nRF52 than the nRF51. You should be able to see that in one of the status registers.

    If that doesn't give you the answer, then you look at the stack and figure out exactly where you came from.

Children
No Data
Related