BLE app uart example not running after flashing

[Julian]

Hi,

I am running the BLE app uart example, using Segger Embedded Studio in Windows.

I've found that that after build and run procedure, the firmware doesn't run, as there are no advertisement and no LED blinking on the PCA10056.

However, as soon as I enter debug mode in the IDE, the firmware starts running and stays running until I power cycled the board. 

This happens to both central and peripheral uart example.

Other examples (e.g. BLE blinky) work fine.

Help appreciated.

Edit: I'm using SDK15

Thanks.

[Joakim Jakobsen]

Hi!

That is strange. I have no problem running the UART examples in the SDK.

Have you made any modifications to the code?
We have a precompiled hex file (where the softdevice and application hex files have been merged).
Located in sdk_folder/examples/ble_peripheral/ble_app_uart/hex
Maybe you could try to flash that to your DK and see if that works?

Best regards,
Joakim.

 

[Julian]

Hi Joakim,

Here's an update on what I've tried so far.

1. Flashing the precompiled hex file has no problems. The firmware runs immediately.

2. Building the example out of the box using SES and then flashing that fails to run the firmware.

3. Building using the makefile provided has no problems.

So I'm suspecting something with the SES build procedure.

[Joakim Jakobsen]

You might be correct. However, I haven't seen any trouble building the example in SES.

Which version of SES do you have?
Which build configuration are you using?
Are you using SES to download the application and softdevice to your board?
Are you sure the softdevice is being flashed to the device?
Have you tried flashing the softdevice and the .hex file output by SES using nrfjprog/nRF Connect - Programmer app?

I haven't been able to find any issues with the ble_app_uart example.

Cheers.

 

 

[Julian]

Hi Joakim,

I'm using SES release 3.40.

Build configuration is Release.

I'm using the SES  build and run command, which performs the flashing of the softdevice and the actual firmware to the chip.

I have tried manually flashing the softdevice using make flash_softdevice, and then make flash the .hex output by SES(not makefile), using nrfjprog. This doesn't work, as in the firmware doesn't run.

So my workaround right now is using SES to write code, and then using make to build and flash.

Thanks for your support on this.

[Joakim Jakobsen]

Hi!

I am not able to reproduce this.
I've tried the release configuration and flashing from SES, using nrfjprog, nRF Connect - Programmer and there is no issue.

Maybe you could try downgrade to SES v.3.34.

As you can see from the SDK v.15.0.0 release notes, SES v.3.34 is the tested and supported version.

We have seen some issues with the combination of SES v.3.40 and SDK v.15.0.0.

Best regards,
Joakim.

[Julian]

Hi Joakim,

I have downgraded to SES v3.34b and the problem disappears. I have also found some explanation and an alternative solution to the issue in this link