Beware that this post is related to an SDK in maintenance mode
More Info: Consider nRF Connect SDK for new designs

What's wrong with my nrf52DK?

Hi, I'm currently working on a program for the NRF52DK using Keil's download tool.
So far, there has been no problem for me to write a code into NRF52DK by using Keil.
However, I recently purchased a new development kit, and despite trying multiple times with Keil, I'm unable to write the code onto the board.

I was able to write code onto the board using "nRF Connect for Desktop". However, it's inconvenient as I need to write the code every time I want to revise the code.

I'm wondering if there's a solution to this problem, as I'd prefer to use Keil's download tool. When I press "download" after revising the code, there are no error messages, and it seems like the code has been written successfully, but the changes made in the code are not reflected on the device.

If anyone has any clues on how to resolve this issue and is able to help me, I would really appreciate it.

  • Hi Sungcheol. 

    Could you give information about Keil version you are using ? Do you have any limit on the size of the application you can build with Keil (license limit). 

    Which Jlink version have you installed ? Could you try install the latest Jlink version ? 


    Can you try using nrfjprog.exe to read the flash after you program using Keil ? If you try to debug with Keil, would it work ? 

  • Really appreciate the swift response.

    The version of my Keil is 5.28.

    However, the thing is, since I have kept writing the same code from the same Keil so far, I doubt whether this situation came from Keil.

    The J-Link Commander that I have is V7.80c now.

    The thing is, it has worked very well so far. However, once I try with a new NRF52DK, I cannot write a code with Keil (same procedure).

    I think I forgot some setup for the DVK, but I don't know what that is.

  • Hi SungCheol, 

    Could you take a screenshot of your configuration in Keil ? 
    Here is mine: 

    When programming my log is slightly different from yours: 

    Could you try to select "Erase Full Chip" instead of Erase Sectors ? 

    It's strange that verify says OK but it not working. 
    Could you try to flash and then read the content of flash out using nrfjprog.exe --readcode file.hex ? 

    Also another test you can do is to do a nrfjprog --recover . And then use Keil to program (don't reset the chip in between). 
    I suspect that the new chip has new APPROTECT mechanism and it may cause an issue. 

  • Thank you very much.

    I still don't understand why, but.... it is working normally today.

    I didn't do anything special and it was just fixed.

    Once again, really appreciate your response and will let you know when I face another situation!!

Related