nRF9160-DK unable to connect to LTE-M network in Tokyo

[calexr]

I followed the tutorial here:

https://devzone.nordicsemi.com/tutorials/b/getting-started/posts/getting-started-with-nrf9160-dk?CommentId=98ebb127-8333-4fca-8409-53845d1e1401

in getting my nRF9160-DK setup, no problem. I was unable to connect to the nRF Cloud so I installed the AT Client to debug as many others have on this forum. I have tried multiple locations outdoors and have been unable to see any towers. The iBasis eSim should work and there should be LTE-M coverage. I am in central Tokyo.

Here is the output from AT Client:

***** Booting Zephyr OS v1.13.99-ncs2 *****

Secure Boot: configure flash

Secure Boot: SPU: set region 0 as Secure

Secure Boot: SPU: set region 1 as Secure

Secure Boot: SPU: set region 2 as Secure

Secure Boot: SPU: set region 3 as Secure

Secure Boot: SPU: set region 4 as Secure

Secure Boot: SPU: set region 5 as Secure

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: "352656100038853"

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

204080813512661

OK

+CEREG: 2,"FFFE","FFFFFFFF",7

AT+COPS=?

+COPS: 

OK

AT+COPS?

+COPS: 2

OK

What should I try next? Thank you!

[Håkon Alseth]

Hi,

mfw-m1_nrf9160_0.6.6-46.prealpha

 There is an update available for the modem, which you can find on this page: https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF9160-DK/Download#infotabs

The modem dfu tool can be installed via python pip:

pip install nrf9160_mdm_dfu-0.10.0+dev-py3-none-any.whl

 

Then run the modem update function in the folder you have the new modem firmware:

cd path\to\modem\firmware && nrf9160_mdm_dfu --update

 

Could you check if the connection issues still remain after the modem update?

 

Kind regards,

Håkon

[calexr]

Thanks for the response.

I updated the firmware and regretfully no improvement.

[calexr]

I don't think the problem is with the eSIM: I can't see any towers on band 3.

I think LTE-M only functions on band 1 and band 8 in Japan. Can you confirm?

NTT Docomo does operate on band 3, but it is for high speed LTE and I am not sure, but I am thinking it does not support LTE-M.

I tested another LTE-M device and confirmed I can see NTT Docomo, KDDI and SoftBank towers from the location I am currently testing (on B1/B8). 

[calexr]

Hi Håkon,

After a fair amount of research I'm pretty sure in order to use the nrf9160 in Japan it needs to support B1 / B8. 

I can also confirm KDDI only allows approved devices on their network.

Do you have any idea when TELEC approval for B1 / B8 will come through? (summer, next year, etc.)

Thanks!

[Håkon Alseth]

Hi,

 

According to our certification page, the approval for bands 1 and 8 is ongoing:

https://www.nordicsemi.com/Products/Low-power-Cellular-IoT/nRF9160-Certifications

I cannot say when this will be finished, or when a modem released with these bands enabled will be available, as I do not have these timelines available.

If you contact your regional sales manager, he should be able to provide more details on this matter. If you do not have the details for your RSM, please send me a direct message and i'll provide you the details.

Kind regards,

Håkon

[calexr]

I happened to have a business trip to Thailand and so tested the device there. I can confirm the device and sim work properly. So, this confirms my thought that the problem is with certification. I have contacted the sales rep here but haven't received a response yet. 

[calexr]

Hi Yusuke,

I was able to get in touch with a Nordic representative in Japan. We should be able to connect to the LTE network by summer if not a bit earlier. I will post here again once I have tested and verified.

[Håkon Alseth]

Hi calexr,

 

That is great news! Thanks for keeping this thread updated and helping others find this information!

Cheers,

Håkon

[calexr]

Good news! The nRF9160 is now able to connect in Japan (tested in Tokyo).  If you have a board purchased before March / April you will need to update modem firmware which you can find here:

https://www.nordicsemi.com/Software-and-Tools/Development-Kits/nRF9160-DK/Download#infotabs

I tested on 0.7.0-15.alpha. You can see that more bands have been activated (likely due to certification). Happy hacking! 

[Yusuke]

Thanks a lot for giving this info!