Pre-built hex for ble_blinky works, however when i build it in segger studio and try flashing it using nrf programmer it doesnt work and occupies more memory

[Subbu_queter]

I was implementing custom services and characteristics(softdevice:s140, ble) on the nrf52840 dongle, however I couldn't get it to work, even though my code seemed correct.

Then I decided to locally build ble_blinky example using segger embedded studio and tried flashing the hex using nrf programmer, however

1. Application hex occupies more memory than that occupied by pre-build hex(that comes along with the sdk v17.1.0 for ble_blinky example)
2. It doesn't work at all.

The pre-build hex of the ble_blinky example works like magic

If anyone has resolved this issue, please help me out!

[Hung Bui]

Hi, 
If you are getting started with Nordic's chip, I would suggest you get started with a nRF52840 DK instead of a dongle. As Jorg mentioned, the dongle doesn't support flashing via SWD out of the box. Instead it support updating the firmware via USB with a bootloader. 
It's not possible to debug the dongle without using an external debugger.  

Please also be aware that for new product we suggest to use nRF Connect SDK and not the legacy nRF5 SDK.