• State Not Answered
  • Replies 9 replies
  • Subscribers 91 subscribers
  • Views 2940 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 286542
Options

nRF Progammer v2.3.3

Learner

Hello,

While programming my board with a merged.hex I sometimes see some differences at the end of the Programmer log.

Sometimes the log ends like this,

2022-03-25T14:05:24.026Z DEBUG Usage data has been sent
2022-03-25T14:05:24.026Z INFO Loading readback protection status for Application core
2022-03-25T14:05:24.662Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_ALL
2022-03-25T14:05:24.671Z INFO Parse memory regions for Application core
2022-03-25T14:05:24.675Z INFO Device is loaded and ready for further operation

and other times it ends like this,

2022-03-25T13:49:15.964Z DEBUG Usage data has been sent
2022-03-25T13:49:15.964Z INFO Loading readback protection status for Application core
2022-03-25T13:49:16.725Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE

The programming of the target board looks as if it succeeded but I am concerned something else went wrong e.g. the SoC protection is not enabled.

Which of the two programming sessions have completed successfully?

Does it mean I need to reprogram the boards when I get NRFDL_PROTECTION_STATUS_NONE?

Can someone please explain what is going on here? 

Thank you.

Kind regards

Mohamed

  • 0 in reply to Simonr

    Hi Simon,

    I have had an instance today, where I was programming one of my boards, where I saw the message

    2022-04-12T15:32:19.336Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE

    when using a version of the nRF52833 that should have protection. 

    This is the information written of the actual casing of the chip:

    N52833
    QDAAB0
    2118AB

    I thought the B0 SoC version has the protection. Please explain what is going on here.

    The Programmer log is inserted below.

    Fullscreen 2022-04-12T15_30_51.689Z-log.txt Download 
    2022-04-12T15:30:52.026Z INFO Application data folder: C:\Users\mohamed.belaroussi\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2022-04-12T15:30:52.198Z DEBUG App pc-nrfconnect-programmer v2.3.3 official
2022-04-12T15:30:52.198Z DEBUG App path: C:\Users\mohamed.belaroussi\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2022-04-12T15:30:52.198Z DEBUG nRFConnect 3.10.0, required by the app is (^3.10.0)
2022-04-12T15:30:52.198Z DEBUG nRFConnect path: C:\Users\mohamed.belaroussi\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-04-12T15:30:52.199Z DEBUG HomeDir: C:\Users\mohamed.belaroussi
2022-04-12T15:30:52.199Z DEBUG TmpDir: C:\Users\MOHAME~1.BEL\AppData\Local\Temp
2022-04-12T15:30:54.038Z DEBUG iface: Ethernet
2022-04-12T15:30:54.039Z DEBUG IP4: 
2022-04-12T15:30:54.039Z DEBUG IP6: 
2022-04-12T15:30:54.039Z DEBUG MAC: f8:b4:6a:bb:ce:96
2022-04-12T15:30:54.040Z DEBUG Client Id: 80e630351047be5f595583a5a071094126272e61
2022-04-12T15:30:54.041Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-04-12T15:31:36.815Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-04-12T15:31:36.816Z INFO JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20
2022-04-12T15:31:36.816Z DEBUG Sending usage data...
2022-04-12T15:31:36.816Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:31:36.816Z DEBUG Action: Open jlink OB version
2022-04-12T15:31:36.816Z DEBUG Label: J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20
2022-04-12T15:31:36.818Z DEBUG Usage data has been sent
2022-04-12T15:31:36.818Z INFO Device family NRF52
2022-04-12T15:31:36.818Z DEBUG Sending usage data...
2022-04-12T15:31:36.818Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:31:36.818Z DEBUG Action: Open jlink device family
2022-04-12T15:31:36.818Z DEBUG Label: NRF52
2022-04-12T15:31:36.819Z DEBUG Usage data has been sent
2022-04-12T15:31:36.819Z INFO Device version NRF52833_xxAA_REV1
2022-04-12T15:31:36.819Z DEBUG Sending usage data...
2022-04-12T15:31:36.820Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:31:36.820Z DEBUG Action: Open jlink device version
2022-04-12T15:31:36.820Z DEBUG Label: NRF52833_xxAA_REV1
2022-04-12T15:31:36.821Z DEBUG Usage data has been sent
2022-04-12T15:31:36.821Z INFO Board version PCA10100
2022-04-12T15:31:36.821Z DEBUG Sending usage data...
2022-04-12T15:31:36.822Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:31:36.822Z DEBUG Action: Open jlink device board version
2022-04-12T15:31:36.822Z DEBUG Label: PCA10100
2022-04-12T15:31:36.822Z DEBUG Usage data has been sent
2022-04-12T15:31:36.823Z INFO Loading readback protection status for Application core
2022-04-12T15:31:36.823Z DEBUG Sending usage data...
2022-04-12T15:31:36.823Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:31:36.823Z DEBUG Action: Open device
2022-04-12T15:31:36.823Z DEBUG Label: jlink
2022-04-12T15:31:36.824Z DEBUG Usage data has been sent
2022-04-12T15:31:38.331Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2022-04-12T15:31:39.853Z INFO Parse memory regions for Application core
2022-04-12T15:31:39.865Z INFO Device is loaded and ready for further operation
2022-04-12T15:32:01.735Z INFO Parsing HEX file:  C:\Sandbox\HomeBeacon_dev_v131+location\build_nrf52833dk_nrf52833_release\zephyr\merged.hex
2022-04-12T15:32:01.748Z INFO File was last modified at  05/04/2022, 17:21:44
2022-04-12T15:32:01.843Z INFO Update files regions according to Application core
2022-04-12T15:32:01.843Z INFO Parse memory regions for file
2022-04-12T15:32:06.447Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core
2022-04-12T15:32:11.635Z INFO Recovering NRFDL_DEVICE_CORE_APPLICATION core completed
2022-04-12T15:32:11.639Z INFO Device recovery completed
2022-04-12T15:32:11.640Z INFO Writing procedure starts for NRFDL_DEVICE_CORE_APPLICATION core
2022-04-12T15:32:11.744Z INFO Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core
2022-04-12T15:32:13.011Z INFO Uploading image through JLink: 0%
2022-04-12T15:32:16.205Z INFO Uploading image through JLink: 100%
2022-04-12T15:32:16.382Z INFO Writing HEX to NRFDL_DEVICE_CORE_APPLICATION core completed
2022-04-12T15:32:16.382Z INFO Writing procedure ends for NRFDL_DEVICE_CORE_APPLICATION core
2022-04-12T15:32:16.385Z INFO Resetting device
2022-04-12T15:32:17.892Z INFO Resetting device completed
2022-04-12T15:32:17.894Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2022-04-12T15:32:17.895Z INFO JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20
2022-04-12T15:32:17.895Z DEBUG Sending usage data...
2022-04-12T15:32:17.895Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:32:17.895Z DEBUG Action: Open jlink OB version
2022-04-12T15:32:17.895Z DEBUG Label: J-Link OB-SAM3U128-V2-NordicSemi compiled Feb  2 2021 16:47:20
2022-04-12T15:32:17.896Z DEBUG Usage data has been sent
2022-04-12T15:32:17.896Z INFO Device family NRF52
2022-04-12T15:32:17.897Z DEBUG Sending usage data...
2022-04-12T15:32:17.897Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:32:17.897Z DEBUG Action: Open jlink device family
2022-04-12T15:32:17.897Z DEBUG Label: NRF52
2022-04-12T15:32:17.898Z DEBUG Usage data has been sent
2022-04-12T15:32:17.898Z INFO Device version NRF52833_xxAA_REV1
2022-04-12T15:32:17.898Z DEBUG Sending usage data...
2022-04-12T15:32:17.898Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:32:17.898Z DEBUG Action: Open jlink device version
2022-04-12T15:32:17.898Z DEBUG Label: NRF52833_xxAA_REV1
2022-04-12T15:32:17.899Z DEBUG Usage data has been sent
2022-04-12T15:32:17.899Z INFO Board version PCA10100
2022-04-12T15:32:17.899Z DEBUG Sending usage data...
2022-04-12T15:32:17.900Z DEBUG Category: pc-nrfconnect-programmer
2022-04-12T15:32:17.900Z DEBUG Action: Open jlink device board version
2022-04-12T15:32:17.900Z DEBUG Label: PCA10100
2022-04-12T15:32:17.900Z DEBUG Usage data has been sent
2022-04-12T15:32:17.900Z INFO Loading readback protection status for Application core
2022-04-12T15:32:19.336Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE

    Thank you.

    Kind regards

    Mohamed

  • 0

    Hi

    Sorry about the late reply, the Easter vacation period has left us with quite the backlog that we're now going through. 

    Have you perhaps disabled readback protection with the APPROTECT register in your application?

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hi Simon,

    I only disable the readback protection when I am developing and building a debug version of the code. However, as far as I can remember, the merged.hex file I was using was from a release build as shown in the Programmer log below.

    2022-04-12T15:32:01.735Z INFO Parsing HEX file: C:\Sandbox\HomeBeacon_dev_v131+location\build_nrf52833dk_nrf52833_release\zephyr\merged.hex

    It could be that I had a debug version running on my board and I was updating it to a release version. If this was the case, would it explain the behaviour I have reported?

    Thank you.

    Kind regards
    Mohamed

  • 0

    Hi Mohamed

    The PROTECTION_STATUS_NONE should mean that the readback protection is disabled (not protected). Please double check whether you are able to get this not protected message with a board where you have enabled readback protection in the application, I don't think that should be possible.

    If you do, please open the console in nRF Connect for Desktop by pressing ctrl+Shift+I and take a screenshot so we can take a look, and we'll investigate.

    Best regards,

    Simon

Related
Terms of service