Attachments (0)
Nordic Case Info
  • Case ID: 341013
Options

Board cannot be found using J-Link Commander V8.12f

Johan123

Hey there!

I am currently trying to upload a .hex file onto the board to flash it using the nRF connect programmer. But while flashing i get this error:

11:10:10.496
Failed "reading readback protection status for application core". Error: code: 1, description: Generic, message: Batch task protection-get failed, [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(XXXXXXXXX))' was found
11:10:10.673
Error: Failed with exit code 1. One or more batch tasks failed: - [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(XXXXXXXXX))' was found, code: Generic. Message: Batch task protection-get failed, [Probe] Emulator error: No emulator with connection info 'Usb(JLinkSerialNumber(XXXXXXXXX))' was found.
So i tried opening the J-Link Commander V8.12f for arm64, and the device cannot be found;
I think it has something to do with the drivers of J-link or nRF Command Line Tools. I am having the same issues trying to connect a STM board, with driver issues. Does anyone know how i get the right drivers?
I forgot to add; Im using the nRF9160 DK, so its a simple usb to microusb connection, i used different cables.
What i do am able to is to drag and drop .hex files onto the board using the windows explorer, but id like to debug aswell.
Your Sincerely,
John
Parents
  • 0

    Hi,

     

    The firmware running on the SEGGER ODB (on board debugger) can contain an older version, which requires the use of SEGGER's legacy usb driver. Could you check this box during jlink installation and see if it runs as expected afterwards?

     

    Kind regards,

    Håkon

  • 0 in reply to Håkon Alseth

    Hi Hakon,

    I already tried it, this does not work. the device is recognizable by nRF connect.

    What does seem off is that it uses 3 different COM ports to communicate with the device.

  • +1 in reply to Johan123

    Hi,

     

    This is because the USB CDC drivers are enumerated correctly, and the serial number of the device itself is then reported back to the PC via that specific usb descriptor.

    So i tried opening the J-Link Commander V8.12f for arm64, and the device cannot be found;

    This seems to require different handling unfortunately:

    https://kb.segger.com/J-Link_on_Windows_ARM

     

    Do you have a x86 device available which you can run the above sequence on?

     

    Kind regards,

    Håkon

  • 0 in reply to Håkon Alseth

    I followed these steps and it worked! thank you!

Reply Children
Terms of service