• State Verified Answer
  • Replies 12 replies
  • Subscribers 63 subscribers
  • Views 5914 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 119167
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Found a trouble with read back protect

jasonbu

using nrfjprog --rbp all and got a success

and using nrfjprog --readuicr got unavaible

but if using j-flash and read whole chip, it's able to be readback...

it only happens in

N52832

QFAAB0

1636CQ

tried 5 chips and all got this trouble... quite confuzed

Parents
  • 0

    Hi, this is really strange. Could you paste output from command line where you do readback protection? Note that it's effective from next chip reset not before, so even after this you can still dump the memory. Could you then reset the board (ideally power off/on), connect with J-Flash and dump some known area, e.g. beginning of address space from offset 0x00000000 where MBR and SoftDevice are? Can you then paste such screenshot? I haven't faced any issue with setting UICR.APPROTECT to PALL on nRF52, chips seems to be locked and debugger doesn't work (neither possibility to issue SWD commands and read memory).

Reply
  • 0

    Hi, this is really strange. Could you paste output from command line where you do readback protection? Note that it's effective from next chip reset not before, so even after this you can still dump the memory. Could you then reset the board (ideally power off/on), connect with J-Flash and dump some known area, e.g. beginning of address space from offset 0x00000000 where MBR and SoftDevice are? Can you then paste such screenshot? I haven't faced any issue with setting UICR.APPROTECT to PALL on nRF52, chips seems to be locked and debugger doesn't work (neither possibility to issue SWD commands and read memory).

Children
No Data
Related