• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 62 subscribers
  • Views 946 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 129570
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

Bootloader SDK14.x

Sensorion

I have recompiled the secure boot loader, s132 and it works great on the dev board but not on my board. The difference in boards is minimal with the exception of the fact we don't use a LF XTAL, but instead use the internal RC.

it is the exact same boot loader image being loaded to both, one advertises and the other does not. Note that this is not the debug boot loader either but the release version.

This has been an on going problem and I am lost as to what the heck is going on.

  • 0

    On both units, my board and the dev board (10040) the boot loader runs to a call to (void)sd_app_evt_wait(); at line 147 of nrf_dfu.c. The dev board works fine, mine stops responding. If I run the boards via the debugger, both boards work fine.

  • 0

    one characteristic is that the advertising LED does not turn on when run in normal mode, but it does turn on while in debug mode.

  • 0

    Source of error was improperly selected LF Clock source in new SKDConfig.h file format. I am still lost as to why it worked while in the debugger. Note I am using Keil, also note that I had changed the sdkconfig.h file in the soft device clock area correctly before this error occurred, the setting in question was in the drivers section I believe not the SD area. Both areas must be changed.

Related