• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 73 subscribers
  • Views 2065 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 128513
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

Why is a HardFault exception occuring in sd_ble_gatts_hvx (SD 132 V5.1)

Kyle Krueger

After already having sent a few notifications with a custom BLE characteristic, I am getting a HardFault in the softdevice.

Initially I had added a log call to print the result of the command with NRF_LOG_FLUSH() called immediately afterwards. However, this log message was never printed.

So I booted up Ozone, and found in the Call Stack that the device is getting choked up on HardFault Exception within the call to sd_ble_gatts_hvx.

Anyone else having crashes like this within the softdevice on the new S132 V5.1 release?

Parents
  • 0

    Hi,

    I have not heard of any issues with the S132 V5.1 release.

    Do you only have this issue with S132 V5.1? You don't have this issue with S132 V5.0 ?

    Could you post some example code on what you are doing ?

    How does the Call Stack looks like when you get the HardFault?

Reply
  • 0

    Hi,

    I have not heard of any issues with the S132 V5.1 release.

    Do you only have this issue with S132 V5.1? You don't have this issue with S132 V5.0 ?

    Could you post some example code on what you are doing ?

    How does the Call Stack looks like when you get the HardFault?

Children
No Data
Related
Terms of service