• State Verified Answer
  • Locked Locked
  • Replies 2 replies
  • Subscribers 88 subscribers
  • Views 563 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281158
Options
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

52840 F version prgram

William.wei

hi support team,

i have one customer have F version QIAA 840, and now i found that some problem with this version when burning hex file.

when burning application, softdevice is lost(when using keil);  And for ses, hex file lost after reset;

is there some instructions for this version chip?  like readback protection?

Regards,

William.

Parents
  • +1

    Hi William,

    The nRF52840 F version has the improved AP protection scheme. So to use that, you need both a recent MDK and recent versions of tools. SDK 17.1.0 includes this, but if using an older SDK, the customer needs to either migrate to SDK 17.1.0, or backport the new MDK (8.40.2 or later) to his old SDK.

    The hex file is not actually lost on reset, but if the firmware does not actively disable APPROTECT, it will be enabled again after reset. And then the only way to regain debugger access is to do a recover operation, which deletes the firmware. The solution is to ensure that the firmware you write disable APPROTECT, which will be the case when using a new MDK.

    Note that as it is the application that must enable debugging (disable APPROTECT), the SoftDevice can never do this. So you must actually program the application before the SoftDevice in this case, or alternatively together as a merged hex file (though that is not relevant from Keil).

    You can point to the official documentation in IN-141.

    Einar

Reply
  • +1

    Hi William,

    The nRF52840 F version has the improved AP protection scheme. So to use that, you need both a recent MDK and recent versions of tools. SDK 17.1.0 includes this, but if using an older SDK, the customer needs to either migrate to SDK 17.1.0, or backport the new MDK (8.40.2 or later) to his old SDK.

    The hex file is not actually lost on reset, but if the firmware does not actively disable APPROTECT, it will be enabled again after reset. And then the only way to regain debugger access is to do a recover operation, which deletes the firmware. The solution is to ensure that the firmware you write disable APPROTECT, which will be the case when using a new MDK.

    Note that as it is the application that must enable debugging (disable APPROTECT), the SoftDevice can never do this. So you must actually program the application before the SoftDevice in this case, or alternatively together as a merged hex file (though that is not relevant from Keil).

    You can point to the official documentation in IN-141.

    Einar

Children
Related