• State Verified Answer
  • Replies 12 replies
  • Subscribers 86 subscribers
  • Views 1097 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 350579
Options

Issue with programming multiple nRF52840 boards – J-Link DLL error after first programming in Programmer v4.6.2

Tomasz Chudy

Hello,

I am experiencing a recurring issue when programming multiple nRF52840 boards using the nRF Programmer.

  • Problem description:
    When programming the first board, everything works fine.
    However, when I try to program the second and subsequent boards, after performing Reset and Erase & Write, I always get the following error:

13:04:07.646 Failed "loading core information for application core". Error: code: 1, description: Generic, message: Batch task core-info failed, Device error: Failed to read from memory address 0x10000130: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code = -1) 13:04:07.663 Error: Failed with exit code 1. One or more batch tasks failed: * 801050888: Device error: Failed to read from memory address 0x10000130: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code = -1)

If I press reset and run Erase & Write again, the programming works successfully.
Then on the next board, the same error appears again, and I need to repeat the reset/erase cycle.

  • Additional information:
    This issue only started appearing with the current version of the software.
    In the previous version of nRF Programmer, I did not have this problem.

Could you please help me understand what is causing this error and how to fix it?

Thank you in advance.

Parents
  • 0

    Hello, 

    Thank you for your patience while waiting for us to respond. 

    Could you please let me know which version of the nRF Programmer which was the last version without this issue? 

    Also, please let me know what your programming setup is: 

    • Are you working with an nRF52840 DK as the programmer? If yes: what is the board version? 
    • Are you using another device as a programmer? I.e. a dedicated J-Link programmer.

    Best regards,

    Maria 

  • 0 in reply to Maria Gilje

    Hello,

    I am programming my own custom board based on the nRF52840.
    I always use nRF Connect for Desktop v5.2.0 (Programmer v4.6.2) on Windows 11. On Programmer v4.6.0 I did not have this issue.

    I am using J-Link v8.18. I also tried with J-Link v8.64, but the error is still the same.

    Here is the error and when it appears (after programming the first board, when trying the next one):

    12:08:21.843 Recovering Application core completed
    12:08:21.845 Loading core information for Application core
    12:08:21.845 Loading core information for Application core 0%
    12:08:21.845 Update files regions according to Application core
    12:08:21.845 Parse memory regions for file
    12:08:21.886 Failed "loading core information for application core". Error: code: 1, description: Generic, message: Batch task core-info failed, Device error: Failed to read from memory address 0x10000130: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1)
    12:08:21.904 Error: Failed with exit code 1. One or more batch tasks failed: * 801050888: Device error: Failed to read from memory address 0x10000130: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1) (Generic) Message: Batch task core-info failed, Device error: Failed to read from memory address 0x10000130: Failed to write DebugPort register 0x08: Unknown Error in J-Link DLL (error code =-1).


  • 0 in reply to Tomasz Chudy

    Hi Tomasz, 

    Thank you for testing this. And I'm also glad that using the command line to program proved to be an improvement to your workflow.

    I'll notify the team that there may be an issue with the Programmer v4.6.2. If they are not able to reproduce this, they may want logs of the issue with the "Verbose Logging" enabled to properly diagnose what is happening. I appreciate if you could share those whenever convenient for you. 

    Best regards,

    Maria

  • 0 in reply to Maria Gilje

    Hi Maria,

    This is the log with "Verbose Logging" enabled and showing this error.

    Best regards
    Tomasz

  • 0 in reply to Tomasz Chudy

    Thank you! 

    Could you also let me know what the Auto-read memory switch is set to? 

  • 0 in reply to Maria Gilje

    Hi Maria,

    Auto read memory is off.

    Best regards
    Tomasz

  • +1 in reply to Tomasz Chudy

    Hi Tomasz, 

    Thanks!

    The issue is related to a known issue with nrfutil device v2.12.3 (from v2.12.0-v2.12.3) which was fixed in v2.12.5: 

    (from nrfutil device changelog)

    As you can see this is an issue when using nrfutil device batch-execute, which is why you don't see it when using your batch script. 

    The developers for the Programmer application are aware of this now. You can expect this issue to be fixed when the Programmer application is updated to use nrfutil device version >= v2.12.5. I'm not able to share a timeline for this update. Your Regional Sales Manager may be able to provide some more information for you if you're interested. 

    In the mean time I hope that the command line programming is working well for you. As a side note, you don't have to stay with nrfutil device v2.12.3 when using the command line. You could update to the latest version, or the specified version for the nRF Connect SDK version you are working with. See the Required tools table in Requirements reference and change the version to your SDK version under the header. 

    Tthank you for reporting this and for providing the needed information for us to find out the source for the issue in Programmer. 

    Best regards,

    Maria

Reply
  • +1 in reply to Tomasz Chudy

    Hi Tomasz, 

    Thanks!

    The issue is related to a known issue with nrfutil device v2.12.3 (from v2.12.0-v2.12.3) which was fixed in v2.12.5: 

    (from nrfutil device changelog)

    As you can see this is an issue when using nrfutil device batch-execute, which is why you don't see it when using your batch script. 

    The developers for the Programmer application are aware of this now. You can expect this issue to be fixed when the Programmer application is updated to use nrfutil device version >= v2.12.5. I'm not able to share a timeline for this update. Your Regional Sales Manager may be able to provide some more information for you if you're interested. 

    In the mean time I hope that the command line programming is working well for you. As a side note, you don't have to stay with nrfutil device v2.12.3 when using the command line. You could update to the latest version, or the specified version for the nRF Connect SDK version you are working with. See the Required tools table in Requirements reference and change the version to your SDK version under the header. 

    Tthank you for reporting this and for providing the needed information for us to find out the source for the issue in Programmer. 

    Best regards,

    Maria

Children
Related
Terms of service