nRF Connect Programmer v2.3.3 fails to detect nRF5340dk board

Hi to All Colleagues:

New to Nordic and its development platform. Finished installing required tools using nRF Connect for Desktop v3.10.0. Attempting to use nRF Connect Programmer v2.3.3 to download the Heart Rate Monitor (HRM) demo application as recommended on  "Running a first test", but the Programmer tool fails to detect the connected nRF5340dk board. No device is shown under "Select Device". Below some additional information:

nrfjprog -v
nrfjprog version: 10.15.4 external
JLinkARM.dll version: 7.62a

Attempted erasing the device after reading some recommendations on the forum by issuing a "nrfjprog --recover". It didn't correct the situation, only erased the demo application that came preloaded with the DK. We can connect to the J-Link onboard debugger using Segger Embedded Studio.

We have two DKs, both experience the same problem. Second one is set aside w/o modifications for reference.

Any advice you can give us to continue our development journey will be greatly appreciated. Please let us know if more information is required from us to determine the cause of the problem.

Thanks in advance, best regards

Parents
  • Hi Claudio,

    Do you have a spare board of the same type to check if the results that you are getting are the same for both boards?
    Can you connect to the device from VS Code? Can device be found in the list of connected devices in VS Code?

    issuing a "nrfjprog --recover"

    Based on nrfjprog documentation, the correct way to recover would be to first recover the network core and then the application core:
    nrfjprog --recover --coprocessor CP_NETWORK     
    nrfjprog --recover

    Best regards,
    Dejan

  • Hi Dejan,

    Here are our answers:

    1. Yes, we have a second dk board, and when exercised we get the same results.

    2. We have VS Code installed, but not familiar with it. We can connect to the device using Segger Embedded Studio.

    3. We followed the recommended sequence of commands, didn't correct the situation.

    C:\Users\***>nrfjprog --recover --coprocessor CP_NETWORK
    Recovering device. This operation might take 30s.
    Writing image to disable ap protect.
    Erasing user code and UICR flash areas.

    C:\Users\***>nrfjprog --recover
    Recovering device. This operation might take 30s.
    Writing image to disable ap protect.
    Erasing user code and UICR flash areas.

    Best regards,

    Claudio

Reply
  • Hi Dejan,

    Here are our answers:

    1. Yes, we have a second dk board, and when exercised we get the same results.

    2. We have VS Code installed, but not familiar with it. We can connect to the device using Segger Embedded Studio.

    3. We followed the recommended sequence of commands, didn't correct the situation.

    C:\Users\***>nrfjprog --recover --coprocessor CP_NETWORK
    Recovering device. This operation might take 30s.
    Writing image to disable ap protect.
    Erasing user code and UICR flash areas.

    C:\Users\***>nrfjprog --recover
    Recovering device. This operation might take 30s.
    Writing image to disable ap protect.
    Erasing user code and UICR flash areas.

    Best regards,

    Claudio

Children
No Data
Related