This is in reference with https://devzone.nordicsemi.com/f/nordic-q-a/44413/issue-while-debugging-ble_app_uart-program-on-nrf52832-in-iar-ide-version-8-20-1
I could run the program on BC-832 using changes suggested in the post. I had enhanced the program by referring (https://github.com/NordicPlayground/nrf52-ble-image-transfer-demo) to transfer large files.
Now, due to space constraints we had to shift to the smaller sized module named BMD-350 (manufactured by Rigado)
I had to change the Clock settings from NRF_CLOCK_LF_SRC_SYNTH to NRF_CLOCK_LF_SRC_RC with following other changes to get away with soft device initialization error at run time.
#define NRF_SDH_CLOCK_LF_SRC NRF_CLOCK_LF_SRC_RC
#define NRF_SDH_CLOCK_LF_RC_CTIV 16
#define NRF_SDH_CLOCK_LF_RC_TEMP_CTIV 4
#define NRF_SDH_CLOCK_LF_ACCURACY 0
With these changes, my program does not halt anywhere. but I can not discover my module on any of the BLE software (I tried custom one, NRF Connect, and BLE sniffer software)
I am still concerned about the clock setting that may cause this issue, or if there is anything specific to this module (BMD-350) that i am missing to configure; causing failure in BLE advertising.
Details about setup.
- controller : nRF52832 (512KB flash) on RIGADO module BMD-350
- Debugger : Segger Jlink Plus in 6 pin SWD mode.
- IDE : IAR workbench v 8.20.1
- SDK version : nRF5_SDK_15.2.0_9412b96
- Test program : nRF5_SDK_15.2.0_9412b96\examples\ble_peripheral\ble_app_uart
https://github.com/NordicPlayground/nrf52-ble-image-transfer-demo/tree/feature_upgrade_to_sdk15
Additional Note : Does, working of Soft device may get affected by the way we program it on the controller ?
I had to program softdevice using nRF Studio tool. When tried with other tools like IAR, Segger J-Flash; I did not get success in discovering device. ( On Fanstel as well )
