ble uart example won't run when built from source

RE: ble uart example won't run when built from source

endnode — Mon, 01 Jan 2018 20:19:21 GMT

That's what I suggested, I believe it's even mentioned in tutorials or SDK release notes: pre-compiled HEX files are merged with Soft Device when applicable. So it's not some magic or mystical reason, it's simply because you flashed both app and SD so it worked.

RE: ble uart example won't run when built from source

Ray Wendt — Mon, 01 Jan 2018 18:43:58 GMT

I discovered that I have to flash the softdevice after I program the board with the hex file that I built, opposite from the way I had been doing it, and then the example works. For some reason the provided hex file does not require the softdevice to be flashed after the board is programmed, which was the source of my confusion.

RE: ble uart example won't run when built from source

endnode — Mon, 01 Jan 2018 11:48:44 GMT

Just to clarify why do I ask: there is no such bug indicate in nRF5 SDK v14.x bug list so I believe the examples shouldn't have any issue with iOS11 devices connecting (otherwise this thread will need attention from Nordic support team to reproduce and file the bug on their side). If this is true then again it indicates you just do something wrong on your side...

RE: ble uart example won't run when built from source

endnode — Mon, 01 Jan 2018 11:44:04 GMT

Hi Ray, even before doing step-by-step debugging (which is anyway very limited as you cannot run it during any time-restricted action such as BLE link) could you elaborate on how nRF5 SDK V14.2.0 pre-compiled HEX file(s) work on your PCA10056 nRF52840 PDK board? If these work but once you "touch" it (try to build yourself) then it looks like problem is in your build set-up. WOuld you agree?;)

RE: ble uart example won't run when built from source

Deepansh — Mon, 01 Jan 2018 10:38:20 GMT

Hi, Ray which IDE you are using and do step by step debugging and see after which line your code stuck or it works till the ends. if it works till the end without stucking then do it by making log statements as a comment