• State Not Answered
  • Replies 12 replies
  • Subscribers 68 subscribers
  • Views 2730 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 237104
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

NRF_SDH_CLOCK_LF_SRC Changes Break app and DFU in 15.3 (from 15.2)

dmacpro91

I've finally worked around some funky bugs that only appeared after updating to 15.3. In my app, I had to change my clock source to RC or SYNTH to make it work (was hanging on enabling the softdevice). My XTAL setting worked fine in 15.2. When I got to working with DFU, I had some issues and tried everything mentioned on here (mergehex to fix the UICR/MBR bug, fixing the Makefile, etc.), but still couldn't get the DFUTarg device to appear. Loaded the debug version of the DFU module and stepped through it to find it failed to execute past the command to start the softdevice. It dawned on that this was probably the same issue that prevented my app from executing. After changing the clock source, everything worked as expected.

Now my question: What changed that makes the XTAL clock setting work fine in 15.2, but not 15.3? I'm using the DVK-BL652-SA device from Laird. Is there any issue using the SYNTH clock setting if power consumption isn't really a concern?

Parents
  • 0

    Hi

    I'm curious if you could either explain the UICR/MBR bug a bit more or link to another post about it? I'm having a very similar issue as you, where I have the debug version of the secure bootloader (SDK v15.3.0) running as well as my own app. If I flash my nRF52832 with a hex file containing the combined app, bootloader debug build, bootloader settings, and softdevice hex files I also find that execution seems to stop when the bootloader passes control over to the softdevice.

    I tried your solution and that didn't seem to fix it unfortunately, I'm looking for anything that I can try. The weird thing is that if I do the exact same thing but use the hex file for the release configuration of the debug bootloader everything works fine.

Reply
  • 0

    Hi

    I'm curious if you could either explain the UICR/MBR bug a bit more or link to another post about it? I'm having a very similar issue as you, where I have the debug version of the secure bootloader (SDK v15.3.0) running as well as my own app. If I flash my nRF52832 with a hex file containing the combined app, bootloader debug build, bootloader settings, and softdevice hex files I also find that execution seems to stop when the bootloader passes control over to the softdevice.

    I tried your solution and that didn't seem to fix it unfortunately, I'm looking for anything that I can try. The weird thing is that if I do the exact same thing but use the hex file for the release configuration of the debug bootloader everything works fine.

Children
Related