This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

nRF52 DK segger (PCA10036) not giving option to lock the application code

I am using nRF51822 (PTR5518A) with SDK v12 and s130 softdevice. To dump the code I am using nRF52 DK segger (PCA10036). With that I am able to dump the code but there is no option to lock it. I don't have any other segger board to dump the code. Is there any way to enable code locking facility in nRF52 DK segger board ? Or can I enable it through code?

Parents
  • This looks like misunderstanding. Every nRF5x chip you can "lock" against read-back and debugger access. This is what most of the people do once they are done with development and go to production. The only way to bypass it is either hack it (there unfortunately is vulnerability on nRF51 which allows some tricks) or erase the chip completely which will "unlock" it.

    Then you say you have PCA10036 but you don't have other SEGGER board. Why would you need it? "Lock" in nrfjprog or nRFgo Studio is of course linked to the nRF5x target chip not to SEGGER J-Link OB fw (that is kind of locked by itself, you can only bootload it and update with other FW image from SEGGER or Nordic...)

  • (2/2)

    • Now you talk about some "check box" but where is it? I suppose some SW. Can you be more precise about where it is, what is says, maybe add some screenshot? Why you assume it has anything to do with SEGGER J-Link FW/chip on PCA10036? This one means if after all SWD programming the SW should also lock target through specific UICR register (they have different name on nRF51 and nRF52 but purpose is the same: enable read-back protection and disable SWD debugger.
Reply
  • (2/2)

    • Now you talk about some "check box" but where is it? I suppose some SW. Can you be more precise about where it is, what is says, maybe add some screenshot? Why you assume it has anything to do with SEGGER J-Link FW/chip on PCA10036? This one means if after all SWD programming the SW should also lock target through specific UICR register (they have different name on nRF51 and nRF52 but purpose is the same: enable read-back protection and disable SWD debugger.
Children
No Data
Related