The hex file that comes with the official website can be programmed, but the hex file generated by SES cannot be programmed.

[caijh]

The blinky example from the official website can be programmed, but after opening the code and compiling with SES to generate the hex file, it cannot be programmed. An MBR file was added additionally. I didn't changed any content. I also used 17.1 and 15 sdk, but i didn't work. 

I also noticed that the hex file generated by SES is a few KB smaller than the hex file that comes with the official website.

 When I program the chip, nRF Connect displays a successful program message, but the light goes from red to suddenly turning off.

[tesc]

Hi,

Working with the nRF52 Dongle is a bit more complicated than working with a DK, since the Dongle does not have a programmer (interface MCU). This means you must either build the apps for doing DFU, or connect with a programmer to the Dongle for programming it directly.

From what I can tell from the picture, you have connected it to a programmer. I can see SWCLK and SWDIO labels. However, they are not connected? If you have programmed the Dongle using a programmer, and not put the DFU bootloader on it, then the only way to program it would currently be to use a programmer. (DFU would not be available at this point.) So: What method of programming are you performing? Further, if you are programming using the SWD interface (using a programmer), then nrfjprog might in some instances work better than using the nRF Connect for Desktop programmer app, especially if a bootloader is involved.

I also noticed that the hex file generated by SES is a few KB smaller than the hex file that comes with the official website.

Application size depends on the compiler, including optimization level and advances in compiler technology. It is therefore not unusual that builds differ in size, and especially if you compare a build done today with a build done several years ago.

When I program the chip, nRF Connect displays a successful program message, but the light goes from red to suddenly turning off.

The app might not start if for instance you miss one or more of the software components needed on the device. (Depending on the app, you might need all of MBR, Bootloader, SoftDevice and application.) It might also be that the bootloader settings page doesn't match the current application. This might happen for instance if you do have the DFU bootloader, but the app was programmed using a programmer, and the bootloader settings page was not also written to reflect the application.

Regards,
Terje