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

nRF52832 Internal Oscillator Softdevice Enable Hanging

I'm using the nRF52832 chip without an external crystal. I configured it to use the internal RC with:

nrf_clock_lf_cfg_t clock_lf_cfg;
clock_lf_cfg.source = NRF_CLOCK_LF_SRC_RC;
clock_lf_cfg.rc_ctiv = 16;
clock_lf_cfg.rc_temp_ctiv = 2;
clock_lf_cfg.xtal_accuracy = 0;

// Initialize SoftDevice.
SOFTDEVICE_HANDLER_APPSH_INIT(&clock_lf_cfg, true);

However, the device seems to be hanging upon enabling the SoftDevice. When going through with a debugger, it just jumps to address 0 continuously. I have the Monitor Mode debugging set up based on the blog post, so I wouldn't think that would be the issue.

Am I doing something wrong in configuring the Softdevice to use the Internal RC?

Parents
  • Great that you found the solution. This is a known and old bug from IARs side, where IAR will jump directly to the application's reset handler when starting debugging, instead of running the softdevice's reset handler. The line is therefore needed to force the debugger to know that the interrupt vectors are located in the SoftDevice. The line is added by default in all the IAR BLE examples in the SDK.

Reply
  • Great that you found the solution. This is a known and old bug from IARs side, where IAR will jump directly to the application's reset handler when starting debugging, instead of running the softdevice's reset handler. The line is therefore needed to force the debugger to know that the interrupt vectors are located in the SoftDevice. The line is added by default in all the IAR BLE examples in the SDK.

Children
No Data
Related