https://devzone.nordicsemi.com/f/nordic-q-a/16138/unable-to-flash-code-on-nrf1822-chip-using-stlink-debugger-by-keil-idehi i am working on nRF51822 chip, trying to flash code using keil IDE through STLink debugger. which i have attached image . while flashing the code it is showing Flash is finished on the keil console and also STLink LED is blinking during flash. buten-USTelligent Community 13Mon, 05 Sep 2016 09:18:28 GMThttps://devzone.nordicsemi.com/thread/61556?ContentTypeID=1Mon, 05 Sep 2016 09:18:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:4135e83a-b97d-40a9-8026-1211de6ccbdbPawelrutka<p>OpenOCD &amp; StLink works great with this devel kit you have. When developing on Nrf51822 I found arm gcc and eclipse toolset more convinient to use.</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/61557?ContentTypeID=1Thu, 01 Sep 2016 23:39:39 GMT137ad170-7792-4731-bb38-c0d22fbe4515:aefd4519-fc48-4619-a303-838d8a063c20Roger Clark<p>The only time I have seen this sort of thing happen, is when the programmer does not correctly identify the nRF51822 device and just treats it as Cortex-M0</p> <p>When this happens, the generic erase command for Cortex-M0 does not seem to erase the flash</p> <p>I had the same issue when developing nRF51822 specific target code for the BlackMagic probe</p> <p>In this case the BlackMagic probe looks at the hardware ID of the nRF51822 but could not determine the device type and hence used Cortex-M0 as its target device.</p> <p>I had to add a load of extra ID codes to the BlackMagic sourcecode and reflash the programmer with those additional ID codes</p> <p>I think OpenOCD may support flashing of nRF51822 via STLInk and I know their ID codes are up to date, so you could try that</p> <p>Or if you have any STM32F103C boards kicking around you could flash the Blackmagic probe firmware onto one of them.</p><div style="clear:both;"></div>