SDK v12.3 code not successfully flashing onto custom NRF51822 board with Segger Embedded Studio' Build and Run command

[thoric_fish]

Hi we are trying to program code using the SDK v12.3 library onto a custom NRF51822 board using SES. The custom code contains Bluetooth routines, GPIO routines, and TWI routines.

We are unable to get any of the custom code running using SES' Build and Run command. However, we are successfully able to get the code flashed and running when we use SES' Build and Debug command. 

We also tested the example code from Vidar from this post. His example project works when we use both Build and Run or Build and Debug in SES. We tested Vidar's code on both the NRF51 DK and the custom NRF51822 board, so we can confirm that BLE can be successfully programmed onto both boards. https://devzone.nordicsemi.com/f/nordic-q-a/54507/section-init-will-not-fit-in-region-unplaced_sections-and-region-unplaced_sections-overflowed-by-76048-bytes

Here is a screenshot showing our main.c and our main() custom code. 

It seems like the first function call, the UART call, in main() does not even get executed when we use SES' Build and Run command. The custom NRF51822 board is connected via COM11 and we are listening to any UART output with the Arduino monitor. We also checked the baud rate and it is correct.

But after we click Build and Run in SES, we wait and nothing comes through the UART from the custom NRF51822 board. 

We verify that the custom code does get successfully executed and works when we use SES' Build and Debug command. Attached below is the output when we run Build and Debug.

Does anyone have any suggestions?

[Jimmy Wong]

HI,

you can use my example (https://github.com/jimmywong2003/SES-Project-For-NRF51).  It works on the SES with SDK 12.3.

[thoric_fish]

Hi Jimmy, 

Thank you for your reply and the example. We have verified that when we use other people's SES example code for SDK v12.3 we can successfully program our custom NRF51822 board using either SES 'build and debug' or 'build and run'. For example, using Vidar's example code, we are able to do Bluetooth advertising and connection with the custom board. https://devzone.nordicsemi.com/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-a4769ae267a347178f60b8c69cd9edf1/nRF5_5F00_SDK_5F00_12.3.0_5F00_SES_5F00_51_5F00_example.zip

Our custom code has Bluetooth advertising, but also includes GPIO routines and TWI routines for interfacing with sensors. But when we add our own custom code to Vidar's existing SES project, we can no longer successfully flash the custom board using 'build and run' command. 

When we use 'build and run' to program the custom board, nothing happens on the custom board - there is no Bluetooth advertising or UART output. When we use 'build and debug' we can do Bluetooth advertising and UART output form the custom board. So basically, when we are trying to program and run our custom code on the custom board, we can only successfully do so using 'build and debug' in SES. 

This is strange behavior and we do not know why it is occurring. 

[Jimmy Wong]

Hi ,

I think you need to enable the debug mode and step by step for figure out the problem.

For example, you can check on the Program counter (PC) when the problem is stuck (without ble advertising).

if you use the same source code and run with gcc compiler, do you see the same problem?

[thoric_fish]

Hi Jimmy,

I am not sure if there is a misunderstanding. We do not run into any problem with the code execution when using debug mode. When we use 'build and run' mode to flash the custom NRF51822 board, there is no code execution happening on the board anymore. As in, the custom board is not getting successfully programmed. Or the custom board cannot run any code flashed using 'build and run' mode. 

[Jimmy Wong]

HI,

Then, I prefer you to check on the hardware first.  For example, you can use the nrfjprog to check whether the target board can be detected or not.

Also, check on the external 32MHz crystal / 32KHz crystal (if have) to have signal during power up or not.

It seems that it is not related to the SES.

You 

https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/optimizing-power-on-nrf52-designs