• State Not Answered
  • Replies 5 replies
  • Subscribers 75 subscribers
  • Views 648 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 249786
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

nRF9160 DK refuses to connect

Caycee

I activated the iBasis SIM (Rochester, NY), but LED's 1 and 2 don't blink. LED5 is mostly on solid with a 1-second slight off-pulse.

AT commands from nRF Connect just timeout, so basically it's just not working.  

  • 0

    Hi,

    Can you describe the steps that you have performed on this DK?

    Did you flash the modem firmware?

    Which link did you follow to connect the DK to nrfcloud?

    We can better assist you if you can provide more details.

  • 0 in reply to Guojun Wang

    I don't remember following any links other than running nRF Connect.

    It seems to me something auto-updated the first time I ran it but I don't remember any specifics--it's been a while.

    I just ran the programmer and hit 'Read' and got the following:

    09:26:25.600
    Application data folder: C:\Users\kcrippe\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
    09:26:25.810
    Using nrfjprog library 10.8.0, pc-nrfjprog-js 1.7.2
    09:26:54.798
    Using nrfjprog to communicate with target
    09:26:55.530
    Using J-Link Software version 6.70
    09:26:56.963
    Segger serial: 960030047
    09:26:56.964
    Segger speed: 2000 kHz
    09:26:56.964
    Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
    09:26:56.969
    Core probed: 960030047.
    09:26:56.970
    Core RAM: 256KiB.
    09:26:56.970
    Core ROM: 1024KiB in pages of 4KiB.
    09:26:57.266
    Model: NRF9160_xxAA_REV1.
    09:26:58.065
    Core0: Reading device non-volatile memory. This may take a few seconds.
    09:26:58.256
    Core0: UICR has been read. Click read button to read full non-volatile memory.
    09:28:22.981
    Using nrfjprog to communicate with target
    09:28:23.704
    Using J-Link Software version 6.70
    09:28:24.890
    Segger serial: 960030047
    09:28:24.890
    Segger speed: 2000 kHz
    09:28:24.890
    Segger version: J-Link OB-K22-NordicSemi compiled Jan 21 2020 17:33:01
    09:28:24.896
    Core probed: 960030047.
    09:28:24.896
    Core RAM: 256KiB.
    09:28:24.896
    Core ROM: 1024KiB in pages of 4KiB.
    09:28:25.202
    Model: NRF9160_xxAA_REV1.
    09:28:25.860
    Core0: Reading device non-volatile memory. This may take a few seconds.
    09:28:35.170
    Core0: Non-volatile memory has been read. 3 non-empty memory blocks identified
  • 0 in reply to Caycee

    Hi, 

    This only shows that the programmer have access to the chip and has read out chip specific information.

    I think it may have done some update for the programmer itself.

    It shall not update anything for the chip.

    Can you follow this link and make sure you have flashed both the nrf91 application hex file and the nrf91 modem firmware? https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_nc_programmer%2FUG%2Fnrf_connect_programmer%2Fncp_introduction.html

    Which example did you run with?

    And can you start from scratch and provide a list of steps that you have performed, if it still fails?

    Thanks!

  • 0

    Ok, got it working.  Flashed the modem FW and the application and now it connects and responds to AT commands.

    Perhaps whoever had this before me had messed it up somehow, as I was initially expecting it to work out-of-the-box. 

Related
Terms of service