nRF9160 DK testing

RE: nRF9160 DK testing

iBasis Tech Support — Mon, 04 Mar 2019 22:26:02 GMT

Hi Hoang,

We apologize for the inconvenience. Can you please provide us with the ICCID's for your esims? We would like to check from our end why you are having trouble connecting.

Kind Regards,

iBasis Tech Support

RE: nRF9160 DK testing

Øyvind — Mon, 04 Mar 2019 10:13:30 GMT

I am not able to see the attached images, they are too small.

[quote user=""]

LED3 and LED4 are OFF

Is it correct for SecureBoot?

[/quote]

Yes, this is correct for the SecureBoot application.

-Oeyvind

RE: nRF9160 DK testing

Hoang — Sat, 02 Mar 2019 09:52:32 GMT

Hi Øyvind,

I tried again step by step to understand more about nrf9160 DK

nRF9160: Secure Boot

Connect nRF9160 DK , turn on and SW5 to nRF91: Build and Run

Preparing target for download
Executing script TargetInterface.resetAndStop()
Reset: Halt core after reset via DEMCR.VC_CORERESET.
Reset: Reset device via AIRCR.SYSRESETREQ.
Downloading ‘zephyr.elf’ to J-Link
Programming 13.3 KB of addresses 00000000 — 0000353f
Programming 0.1 KB of addresses 00003540 — 000035f3
J-Link: Flash download: Bank 0 @ 0x00000000: Skipped. Contents already match
Download successful

Run: nRF Connect v2.6.2 - LTE Link Monitor , Select device

2019-03-02T09:46:15.689Z DEBUG modem << Secure Boot: configure peripherals\x0D\x0A
2019-03-02T09:46:15.710Z DEBUG modem << Secure Boot: MSP_NS ffffffff\x0D\x0A
2019-03-02T09:46:15.730Z DEBUG modem << Secure Boot: prepare to jump to Non-Secure image\x0D\x0A
2019-03-02T09:46:15.750Z DEBUG modem << ***** Booting Zephyr OS v1.13.99-ncs2 *****\x0D\x0A
2019-03-02T09:46:15.771Z DEBUG modem << Secure Boot: configure flash\x0D\x0A
2019-03-02T09:46:15.794Z DEBUG modem << Secure Boot: SPU: set region 0 as Secure\x0D\x0A
2019-03-02T09:46:15.815Z DEBUG modem << Secure Boot: SPU: set region 1 as Secure\x0D\x0A
2019-03-02T09:46:15.835Z DEBUG modem << Secure Boot: SPU: set region 2 as Secure\x0D\x0A
2019-03-02T09:46:15.857Z DEBUG modem << Secure Boot: SPU: set region 3 as Secure\x0D\x0A
2019-03-02T09:46:15.876Z DEBUG modem << Secure Boot: SPU: set region 4 as Secure\x0D\x0A
2019-03-02T09:46:15.897Z DEBUG modem << Secure Boot: SPU: set region 5 as Secure\x0D\x0A
2019-03-02T09:46:15.918Z DEBUG modem << Secure Boot: SPU: set region 6 as Secure\x0D\x0A
2019-03-02T09:46:15.939Z DEBUG modem << Secure Boot: SPU: set region 7 as Secure\x0D\x0A
2019-03-02T09:46:15.960Z DEBUG modem << Secure Boot: SPU: set Flash region 8 as Non-Secure\x0D\x0A
2019-03-02T09:46:15.980Z DEBUG modem << Secure Boot: SPU: set Flash region 9 as Non-Secure\x0D\x0A
2019-03-02T09:46:15.999Z DEBUG modem << Secure Boot: SPU: set Flash region 10 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.019Z DEBUG modem << Secure Boot: SPU: set Flash region 11 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.039Z DEBUG modem << Secure Boot: SPU: set Flash region 12 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.060Z DEBUG modem << Secure Boot: SPU: set Flash region 13 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.079Z DEBUG modem << Secure Boot: SPU: set Flash region 14 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.099Z DEBUG modem << Secure Boot: SPU: set Flash region 15 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.119Z DEBUG modem << Secure Boot: SPU: set Flash region 16 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.138Z DEBUG modem << Secure Boot: SPU: set Flash region 17 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.159Z DEBUG modem << Secure Boot: SPU: set Flash region 18 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.179Z DEBUG modem << Secure Boot: SPU: set Flash region 19 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.201Z DEBUG modem << Secure Boot: SPU: set Flash region 20 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.224Z DEBUG modem << Secure Boot: SPU: set Flash region 21 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.248Z DEBUG modem << Secure Boot: SPU: set Flash region 22 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.270Z DEBUG modem << Secure Boot: SPU: set Flash region 23 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.292Z DEBUG modem << Secure Boot: SPU: set Flash region 24 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.314Z DEBUG modem << Secure Boot: SPU: set Flash region 25 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.334Z DEBUG modem << Secure Boot: SPU: set Flash region 26 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.353Z DEBUG modem << Secure Boot: SPU: set Flash region 27 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.374Z DEBUG modem << Secure Boot: SPU: set Flash region 28 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.393Z DEBUG modem << Secure Boot: SPU: set Flash region 29 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.413Z DEBUG modem << Secure Boot: SPU: set Flash region 30 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.435Z DEBUG modem << Secure Boot: SPU: set Flash region 31 as Non-Secure\x0D\x0A
2019-03-02T09:46:16.454Z DEBUG modem << Secure Boot: configure SRAM\x0D\x0A
2019-03-02T09:46:16.474Z DEBUG modem << Secure Boot: SPU: set SRAM region 0 as Secure\x0D\x0A
2019-03-02T09:46:16.496Z DEBUG modem << Secure Boot: SPU: set SRAM region 1 as Secure\x0D\x0A

LED3 and LED4 are OFF

Is it correct for SecureBoot?

RE: nRF9160 DK testing

Øyvind — Fri, 01 Mar 2019 14:11:31 GMT

Hei Hoang!
Bare hyggelig! :)

[quote user="hng"]I think, the problems came from the iBasic eSIM. I will try to look for GPS/LTE SIM card. and test again[/quote]

If you do get any more issues, please paste the output of the LTE Link Monitor here, and we can have a look at the AT responses.

God helg!

Best regards,
Oeyvind

RE: nRF9160 DK testing

Hoang — Fri, 01 Mar 2019 12:53:36 GMT

Hi Øyvind,

I changed to another TALE-SIM of Telia, and programmed SecureBoot and At_Client, and I got respond. I think, the problems came from the iBasic eSIM. I will try to look for GPS/LTE SIM card. and test again

Tusen hjertelig takk for hjelpen

hng

RE: nRF9160 DK testing

Øyvind — Fri, 01 Mar 2019 11:42:31 GMT

Each SIM can be used freely on any device, but since its tied to an account on nrfcloud to prepay for more data, you have to go through this portal to expand the data package on your SIM. When the SIM reaches the 10 MB limit, nrfcloud.com should provide a notice about this where you can buy more data.

Contact your local telecom company if you want another subscription

Kind regards,
Øyvind

RE: nRF9160 DK testing

Hoang — Fri, 01 Mar 2019 10:31:09 GMT

Hi Øyvind,

Can we have more SIM card for testing?

Regards,

hng

RE: nRF9160 DK testing

Hoang — Fri, 01 Mar 2019 09:58:37 GMT

I bought 3 nRF9160 DK kits, so I have 3 SIMs here. Each SIM can go for only 1 KIT?

eSIM just has 10MB free, I had used all of this, how can I buy more?

Thanks,

Regards

RE: nRF9160 DK testing

Øyvind — Thu, 28 Feb 2019 14:41:45 GMT

Ok, was the SIM registered to the same development kit?

Try to load the AT_client application again, and then start LTE Link Monitor. The monitor should output some information that can point us in the right direction. Please attach the output in a .txt file.

What do you get if you Build and Debug?

-Øyvind

RE: nRF9160 DK testing

Hoang — Thu, 28 Feb 2019 14:07:06 GMT

Hi @Øyvind,

I am trying to follow this userguide:

http://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/applications/asset_tracker/README.html

Step1.

nRF9160: Secure Boot

Connect nRF9160 DK , turn on and SW5 to nRF91: Build and Run

Then LED3 is blinking.

I tried to:

1. SW2 to NC

2. SW1 toggle

LED3 OFF and LED4 ON (not blinking)

Step2: Build Asset Tracker

Build and Run:

LED3 and LED4 OFF

Step3. Test on

Step4. Test on nrfcloud:

wait for along time, LED3 and LED4 were OFF

.......!!!

Whats wrong? I did something wrong?

Thanks,

Regards

hng

RE: nRF9160 DK testing

Hoang — Thu, 28 Feb 2019 13:19:39 GMT

the SIM card registered by another engineer.

Load the Asset Tracker application you mean; Build and Run. I did

Regards

Hng

RE: nRF9160 DK testing

Øyvind — Thu, 28 Feb 2019 13:02:21 GMT

Hello,

I can't see anything wrong with your description, everything looks correct so far.

Did you load the Asset Tracker application, and then try to register the SIM card?

Best regards,
Øyvind