• State Not Answered
  • Replies 2 replies
  • Subscribers 91 subscribers
  • Views 436 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 288092
Options

Problem programming 9160 using nRFConnect 3.11.0

Pema

Hi,

I am using a j-link EDU to program our devices. I use nRFConnect 3.11.0 and prorammer 2.3.3. My problem is that I don't get the j-link device up in the programmer tool so I can't select it (select device -> ends up in "connect a nRF SDK" or similar). Backing to nRFConnect 3.7.1 (programmer 1.4.11) the device comes up selectable and I can program my device without problem. I have seen similar problem with earlier versions (nRFConnect 3.9.0, https://devzone.nordicsemi.com/f/nordic-q-a/82234/no-matching-trait-found), so is there still something strange with it?

/Peter

  • 0

    Hi Peter,

    The bugs regarding this should be fixed as far as I am aware of, but it is possible that some bug went unnoticed or that this is related to something else.

    Please give some more information about your environment, such as OS and what version of nrfjprog and JLink you have installed (you can find this by running nrfjprog -v).

    The Programmer app will not detect a debugger if there is no JLink device connected, so make sure that the nRF9160 is connected and turned on.

    It would also be very helpful to get some logs from the Programmer app with verbose logging enabled. To get this, perform the following steps (make sure you are using the version of the Programmer app where you are seeing this issue, 2.3.3):

    1. Make sure the J-Link EDU is connected to your computer and to the nRF9160, and that the nRF9160 is turned on.
    2. In Programmer go to the 'About' tab and enable verbose logging
    3. Select 'Restart with verbose logging'
    4. After the app restarts click on 'open log file' at the bottom of the terminal.
    5. Either save the log file somewhere and upload it here with Insert -> Image/video/file, or copy the contents of the log file and go to Insert -> Code then paste the log there.

    Best regards,

    Marte

  • 0 in reply to Marte Myrvold

    Hi Marte,

    It seems it is a handling issue. The first time, I normally start the programmer and then attach the cables to the IC. With these versions (3.11.0/ programmer 2.3.3, the J-link does not appear in the device list for me. With these versions it seems you have to attach the IC first, then start the programmer. So it works with that changed procedure.

    /Peter

Related
Terms of service