Related
Recommended

Getting Started with nRF9160 DK

Akash Patel

2020-08-04: The content of this guide is now covered in the documentation on Infocenter. For the most up-to-date Getting started guide with nRF9160 DK please follow this link. 

2020-03-09: Updated tutorial to support nRF Connect SDK (NCS) v1.2.0 (Screenshots may not be updated with the latest version number but the text is)

2019-07-31: Updated tutorial to support nRF Connect SDK (NCS) v1.0.0

2019-05-21: Updated tutorial to cover the changes in the nRF Connect SDK

Parents Comment Children
  • in reply to iBasis Tech Support

    AT+CFUN?
    ***** Booting Zephyr OS v1.13.99-ncs2 *****
    Secure Boot: configure flash
    Secure Boot: SPU: set region 6 as Secure
    Secure Boot: SPU: set region 7 as Secure
    Secure Boot: SPU: set Flash region 8 as Non-Secure
    Secure Boot: SPU: set Flash region 9 as Non-Secure
    Secure Boot: SPU: set Flash region 10 as Non-Secure
    Secure Boot: SPU: set Flash region 11 as Non-Secure
    Secure Boot: SPU: set Flash region 12 as Non-Secure
    Secure Boot: SPU: set Flash region 13 as Non-Secure
    Secure Boot: SPU: set Flash region 14 as Non-Secure
    Secure Boot: SPU: set Flash region 15 as Non-Secure
    Secure Boot: SPU: set Flash region 16 as Non-Secure
    Secure Boot: SPU: set Flash region 17 as Non-Secure
    Secure Boot: SPU: set Flash region 18 as Non-Secure
    Secure Boot: SPU: set Flash region 19 as Non-Secure
    Secure Boot: SPU: set Flash region 20 as Non-Secure
    Secure Boot: SPU: set Flash region 21 as Non-Secure
    Secure Boot: SPU: set Flash region 22 as Non-Secure
    Secure Boot: SPU: set Flash region 23 as Non-Secure
    Secure Boot: SPU: set Flash region 24 as Non-Secure
    Secure Boot: SPU: set Flash region 25 as Non-Secure
    Secure Boot: SPU: set Flash region 26 as Non-Secure
    Secure Boot: SPU: set Flash region 27 as Non-Secure
    Secure Boot: SPU: set Flash region 28 as Non-Secure
    Secure Boot: SPU: set Flash region 29 as Non-Secure
    Secure Boot: SPU: set Flash region 30 as Non-Secure
    Secure Boot: SPU: set Flash region 31 as Non-Secure
    Secure Boot: configure SRAM
    Secure Boot: SPU: set SRAM region 0 as Secure
    Secure Boot: SPU: set SRAM region 1 as Secure
    Secure Boot: SPU: set SRAM region 2 as Secure
    Secure Boot: SPU: set SRAM region 3 as Secure
    Secure Boot: SPU: set SRAM region 4 as Secure
    Secure Boot: SPU: set SRAM region 5 as Secure
    Secure Boot: SPU: set SRAM region 6 as Secure
    Secure Boot: SPU: set SRAM region 7 as Secure
    Secure Boot: SPU: set SRAM region 8 as Non-Secure
    Secure Boot: SPU: set SRAM region 9 as Non-Secure
    Secure Boot: SPU: set SRAM region 10 as Non-Secure
    Secure Boot: SPU: set SRAM region 11 as Non-Secure
    Secure Boot: SPU: set SRAM region 12 as Non-Secure
    Secure Boot: SPU: set SRAM region 13 as Non-Secure
    Secure Boot: SPU: set SRAM region 14 as Non-Secure
    Secure Boot: SPU: set SRAM region 15 as Non-Secure
    Secure Boot: SPU: set SRAM region 16 as Non-Secure
    Secure Boot: SPU: set SRAM region 17 as Non-Secure
    Secure Boot: SPU: set SRAM region 18 as Non-Secure
    Secure Boot: SPU: set SRAM region 19 as Non-Secure
    Secure Boot: SPU: set SRAM region 20 as Non-Secure
    Secure Boot: SPU: set SRAM region 21 as Non-Secure
    Secure Boot: SPU: set SRAM region 22 as Non-Secure
    Secure Boot: SPU: set SRAM region 23 as Non-Secure
    Secure Boot: SPU: set SRAM region 24 as Non-Secure
    Secure Boot: SPU: set SRAM region 25 as Non-Secure
    Secure Boot: SPU: set SRAM region 26 as Non-Secure
    Secure Boot: SPU: set SRAM region 27 as Non-Secure
    Secure Boot: SPU: set SRAM region 28 as Non-Secure
    Secure Boot: SPU: set SRAM region 29 as Non-Secure
    Secure Boot: SPU: set SRAM region 30 as Non-Secure
    Secure Boot: SPU: set SRAM region 31 as Non-Secure
    Secure Boot: configure peripherals
    Secure Boot: MSP_NS 200265f0
    Secure Boot: prepare to jump to Non-Secure image
    ***** Booting Zephyr OS v1.13.99-ncs2 *****
    The AT host sample started
    AT+CFUN?
    +CFUN: 4
    OK
    AT+CFUN=1
    OK
    AT+CFUN?
    +CFUN: 1
    OK
    AT+CGSN=1
    +CGSN: "352656100047839"
    OK
    AT+CGMI
    Nordic Semiconductor ASA
    OK
    AT+CGMM
    nRF9120
    OK
    AT+CGMR
    mfw-m1_nrf9160_0.6.6-46.prealpha
    OK
    AT+CEMODE?
    +CEMODE: 2
    OK
    AT%XCBAND=?
    %XCBAND: (3,4,13,20)
    OK
    AT+CMEE?
    +CMEE: 0
    OK
    AT+CMEE=1
    OK
    AT+CNEC?
    +CNEC: 0
    OK
    AT+CNEC=24
    OK
    AT+CGEREP?
    +CGEREP: 0,0
    OK
    AT+CGDCONT?
    OK
    AT+CGACT?
    OK
    AT+CGEREP=1
    OK
    AT+CIND=1,1,1
    OK
    AT+CEREG=2
    OK
    AT+CEREG?
    +CEREG: 2,4,"FFFE","FFFFFFFF",7
    OK
    AT%CESQ=1
    OK
    AT+CESQ
    +CESQ: 99,99,255,255,255,255
    OK
    AT%XSIM=1
    OK
    AT%XSIM?
    %XSIM: 1
    OK
    AT+CPIN?
    +CPIN: READY
    OK
    AT+CPINR="SIM PIN"
    +CPINR: "SIM PIN",3
    OK
    AT+CIMI
    204080813514015
    OK
    +CEREG: 2,"FFFE","FFFFFFFF",7

  • in reply to iBasis Tech Support

    According to the Nordic FAE I've corresponded with the %XCBAND: (3,4,13,20) response is suspect - he expected to see channel 12.

    Board build is 0.8.2

  • in reply to robmilne

    Hi Robmilne,  You will need to have band 17 opened since we have tested Telus and Bell over band 17.  Please work with Nordic Tech Support.  Kind Regards,

  • in reply to iBasis Tech Support

    Update - I tried with an older 0.7.0 build board (M4 based?) and was able to connect to Bell's network.  Bands 1-5,8,12-14,17-20,24-28.66 are listed in "LTE Link Monitor".  Definitely something not quite right with 0.8.2.

  • in reply to robmilne

    Hi , I'm also trying to connect to Bell's network using the nrf9160-dk. Do you still have the 0.7.0 firmware files? Did you had to do something else than setting the APN? Thanks!