Cannot Flash 5340DK

Hello, I have two nRF35340 DK. One of them can be flash successfully, another one always encounter this issue:

WARNING: Specifying runner options for multiple domains is experimental.
If problems are experienced, please specify a single domain using '--domain <domain>'
-- west flash: using runner nrfjprog
-- runners.nrfjprog: reset after flashing requested
-- runners.nrfjprog: Flashing file: C:\Users\Gary\Desktop\peripheral_uart\53\merged_CPUNET.hex
[error] [ Client] - Encountered error -220: Command enable_coprocessor executed for 10005 milliseconds with result -220
Failed to enable coprocessor with unknown error.
[error] [ Worker] - 10 second timeout elapsed, no time left to wait for debug port to power up.
ERROR: Operation failed due to timeout. Check the log messages for more details.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 64: nrfjprog --program 'C:\Users\Gary\Desktop\peripheral_uart\53\merged_CPUNET.hex' --sectorerase --verify -f NRF53 --coprocessor CP_NETWORK --snr 1050041747

I have tried

nrfjprog --recover -f NRF53 --coprocessor CP_APPLICATION --snr 1050041747

nrfjprog --recover -f NRF53 --coprocessor CP_NETWORK --snr 1050041747

nrfjprog -f NRF53 --recover --snr 1050041747 

All of them cannot work

But nrfjprog --ids can get the right result!

Parents
  • Hi,

    Are both the nRF5340DK new out of box, or have you used them previously?

    If they are not new you should check if the solder bridge for current measurement(SB40) have been cut, if it is cut you need a jumper on P22.

    The SWD interface may also have been disconencted from the onboard debugger, check if tSB54(SWDIO) and SB55(SWDCLK) have been cut.

     

    Best regards,

    Bendik

Reply
  • Hi,

    Are both the nRF5340DK new out of box, or have you used them previously?

    If they are not new you should check if the solder bridge for current measurement(SB40) have been cut, if it is cut you need a jumper on P22.

    The SWD interface may also have been disconencted from the onboard debugger, check if tSB54(SWDIO) and SB55(SWDCLK) have been cut.

     

    Best regards,

    Bendik

Children
  • Thank you so much for your reply!

    Yes, it is brand new, so that I'm sure the SB40 SB54 SB55 are connected. I have anther new board and it can be flashed successfully.

    I have tried to use the NRF programmer but still cannot, below is the error information:

    Error: Failed with exit code 1. Failed to device info one or more devices: * 1050041747: [jlink] Unable to fetch device-info, code: Generic. Message: Operation device-info failed, [jlink] Unable to fetch device-info.
    21:28:51.076	Reading readback protection status for Application core
    21:28:51.076	Reading readback protection status for Application core 0%
    21:28:51.206	Failed "reading readback protection status for application core". Error: code: 9, description: Nrfjlink, message: Batch task protection-get failed, [jlink] INVALID_OPERATION
    21:28:51.381	Error: Failed with exit code 1. One or more batch tasks failed: - [jlink] INVALID_OPERATION, code: Nrfjlink. Message: Batch task protection-get failed, [jlink] INVALID_OPERATION.

    Again I try to use the NCS to flash, the error shows:

    WARNING: Specifying runner options for multiple domains is experimental.
    If problems are experienced, please specify a single domain using '--domain <domain>'
    -- west flash: using runner nrfjprog
    -- runners.nrfjprog: mass erase requested
    -- runners.nrfjprog: reset after flashing requested
    -- runners.nrfjprog: Flashing file: C:\Users\Gary\Desktop\peripheral_uart\53\merged_CPUNET.hex
    [error] [ Client] - Encountered error -220: Command enable_coprocessor executed for 10010 milliseconds with result -220
    Failed to enable coprocessor with unknown error.
    [error] [ Worker] - 10 second timeout elapsed, no time left to wait for debug port to power up.
    ERROR: Operation failed due to timeout. Check the log messages for more details.
    NOTE: For additional output, try running again with logging enabled (--log).
    NOTE: Any generated log error messages will be displayed.
    FATAL ERROR: command exited with status 64: nrfjprog --program 'C:\Users\Gary\Desktop\peripheral_uart\53\merged_CPUNET.hex' --chiperase --verify -f NRF53 --coprocessor CP_NETWORK --snr 1050041747

    I hope you could help me to figure out the problems:Grinning

  • Can you measure the VDD_nRF' voltage on this pin:

    It should be 3V.

    Can you try is to supply the nRF5340 using the second USB connector in addition to the debugger USB connector. To do this you need to switch the power source to USB using switch SW9.

Related