blinky and nRFConnect SDK

[Bret Foreman]

I can build the blinky demo with the nRFConnect SDK and I can flash my PCA10040 DK board from the VS Code tool. But the blinky app does not start - no flashing LEDs.

I know the GUI hex file loader does not work with the PCA10040 (app never starts) so I guess the SDK loader might not work either. I can use the command line loader if I know where the appropriate Zephyr hex file is located in the directory tree of the application. Where does it end up when I do a build and what is it called?

[Priyanka]

Hi Bret,

Do you mean to say that even after you successfully flash the blinky sample onto your DK, there is no visible output observed?

Which SDK version are you using? And what is your DK revision?

Have you tried programming via command line? 

If you are looking for the hex file, it will be the zephyr.hex file inside the zephyr folder inside the build folder.

Best Regards,

Priyanka

[Bret Foreman]

I'm using SDK version 17.1.0. And yes, the command line loader works fine. This is a known bug with the SDK and version 3.0.0 of the PCA10040 DK board. The GUI exe loader doesn't work with the version of Segger on that board. But the command line does.
But back to my question: Where do I find the exe file created by nRF Connect so I can use the command line loader? What is the specific path and file name?

[Priyanka]

Hi Bret,

I am a bit confused. You mentioned the v17.1.0, So that means you are using the nRF5 SDK? 

But the sample you tried was from nRF Connect SDK. You had mentioned this in the query.

Both are different. nRF5 SDK was our old SDK. It's still available but we are gradually moving to nRF Connect SDK which is Zephyr RTOS based.

-Priyanka