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

Migration from SDK 11 alpha to 11 final, advertising problem

Hello,

This morning i did migration of my code from SDK 11 alpha 2 to 11 final on nRF52 and i have a big problem.

Nor bootloader or application do advertising. Am I alone ?

(i possibly not checked bootloader in 11 alpha but it worked with SDK 9 on nRF51)

What can I do as test ?

Parents
  • I found.

    Very strange but HF Crystal don't start with 11 final.

    If i use NRF_CLOCK_LF_SRC_SYNTH in place of NRF_CLOCK_LF_SRC_RC, it works !!!

    Question does NRF_CLOCK_LF_SRC_SYNTH need parameters (PPM ?)

  • I usually use C++ and if you turn warnings up you get a useful warning about uninitialised struct members and I turned on the equivalent for C too, not that I remember what it is. It's a bit annoying sometimes but can be rather useful. I would think however that field is ignored totally in the RC case. I don't really understand where your problem likely lies, the bootloader isn't special, it's just another BLE service which runs out of a different piece of flash, if BLE works in general on that device with the S132 softdevice, there's no particular reason the bootloader wouldn't.

    You could try sticking a breakpoint in the softdevice fault handler, see if it's going there (as opposed to the usual error handler) although I'd think you'd notice.

Reply
  • I usually use C++ and if you turn warnings up you get a useful warning about uninitialised struct members and I turned on the equivalent for C too, not that I remember what it is. It's a bit annoying sometimes but can be rather useful. I would think however that field is ignored totally in the RC case. I don't really understand where your problem likely lies, the bootloader isn't special, it's just another BLE service which runs out of a different piece of flash, if BLE works in general on that device with the S132 softdevice, there's no particular reason the bootloader wouldn't.

    You could try sticking a breakpoint in the softdevice fault handler, see if it's going there (as opposed to the usual error handler) although I'd think you'd notice.

Children
No Data
Related