• State Not Answered
  • Replies 5 replies
  • Subscribers 89 subscribers
  • Views 1516 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281435
Options

Nrf Connect Programmer write function

Gueston

Hi,

I discovered that when I use the 'write' button in the nrf connect programmer, that it completely overwrites the whole program (similar to erase&write). Before I didnt notice this and it worked with only overwriting the memory region which was in the file memory layout.

I only use the command line programmer and there it works fine but another developer in our team needs to use this tool. Did something change in a new version?

I use V2.0.1

  • 0

    Hello Gaston,

    Could you provide me the log from the nRF Connect Programmer?

    Best regards,

    Elfving

  • 0 in reply to Elfving

    Hi, see below:

    2021-12-17T13:08:08.429Z INFO Update files regions according to Application core
2021-12-17T13:08:08.431Z INFO Parse memory regions for file
2021-12-17T13:08:20.973Z INFO Parsing HEX file:  C:\Users\gholl\OneDrive\Desktop\nrf52832_xxaa.hex
2021-12-17T13:08:20.974Z INFO File was last modified at  16-12-2021 14:16:26
2021-12-17T13:08:21.021Z INFO Update files regions according to Application core
2021-12-17T13:08:21.021Z INFO Parse memory regions for file
2021-12-17T13:08:24.571Z INFO Does not need to be reloaded:  C:\Users\gholl\OneDrive\Desktop\nrf52832_xxaa.hex
2021-12-17T13:08:24.571Z INFO Writing procedure starts for Application core
2021-12-17T13:08:24.612Z INFO Writing HEX to Application core
2021-12-17T13:08:25.063Z INFO Uploading image through JLink: 0%
2021-12-17T13:08:27.994Z INFO Uploading image through JLink: 100%
2021-12-17T13:08:28.169Z INFO Writing HEX to Application core completed
2021-12-17T13:08:28.169Z INFO Writing procedure ends for Application core
2021-12-17T13:08:28.170Z INFO Resetting device
2021-12-17T13:08:28.755Z INFO Resetting device completed
2021-12-17T13:08:28.758Z INFO Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
2021-12-17T13:08:28.758Z INFO JLink OB firmware version J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 17 2020 14:43:00
2021-12-17T13:08:28.764Z DEBUG Sending usage data...
2021-12-17T13:08:28.764Z DEBUG Category: pc-nrfconnect-programmer
2021-12-17T13:08:28.764Z DEBUG Action: Open jlink device
2021-12-17T13:08:28.764Z DEBUG Label: J-Link OB-SAM3U128-V2-NordicSemi compiled Mar 17 2020 14:43:00
2021-12-17T13:08:28.768Z DEBUG Usage data has been sent
2021-12-17T13:08:28.768Z INFO Device family NRF52
2021-12-17T13:08:28.768Z DEBUG Sending usage data...
2021-12-17T13:08:28.768Z DEBUG Category: pc-nrfconnect-programmer
2021-12-17T13:08:28.768Z DEBUG Action: Open jlink device
2021-12-17T13:08:28.768Z DEBUG Label: NRF52
2021-12-17T13:08:28.769Z DEBUG Usage data has been sent
2021-12-17T13:08:28.769Z INFO Device version NRF52832_xxAA_REV2
2021-12-17T13:08:28.770Z DEBUG Sending usage data...
2021-12-17T13:08:28.770Z DEBUG Category: pc-nrfconnect-programmer
2021-12-17T13:08:28.770Z DEBUG Action: Open jlink device
2021-12-17T13:08:28.770Z DEBUG Label: NRF52832_xxAA_REV2
2021-12-17T13:08:28.771Z DEBUG Usage data has been sent
2021-12-17T13:08:28.771Z INFO Board version PCA10040
2021-12-17T13:08:28.771Z DEBUG Sending usage data...
2021-12-17T13:08:28.771Z DEBUG Category: pc-nrfconnect-programmer
2021-12-17T13:08:28.771Z DEBUG Action: Open jlink device
2021-12-17T13:08:28.771Z DEBUG Label: PCA10040
2021-12-17T13:08:28.772Z DEBUG Usage data has been sent
2021-12-17T13:08:28.772Z INFO Loading readback protection status for Application core
2021-12-17T13:08:29.313Z INFO Readback protection status: NRFDL_PROTECTION_STATUS_NONE
2021-12-17T13:08:29.881Z INFO Device is loaded and ready for further operation
2021-12-17T13:08:29.883Z INFO Reading memory for Application core
2021-12-17T13:08:37.520Z INFO Reading memory for Application core completed
2021-12-17T13:08:37.522Z INFO Parse memory regions for Application core

  • 0 in reply to Gueston

    Hey again Gaston,

    This isn't by design. We are looking into it, but things might take a bit longer than usual due to the holidays.

    I'll get back to you.

    Best regards,

    Elfving

  • 0 in reply to Elfving

    Hello again! Sorry about the wait.

    Would you mind expanding a bit on your co-workers use case for the Programmer application?

    Best regards,

    Elfving

  • 0

    It seems I was mistaken; it has sadly been made this way now by design. The option of not recovering the device was supported before, but the situation now is that our new devices are app protected by default, they will need to be recovered anyway before writing. If the use case you have is important enough for you we will consider changing it back.

    Best regards,

    Elfving

Related