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

No device found for this id. Troubleshoot nRF Code 40414

bratvitaly

Hello,

I have a certificate attached, but in my personal account it gives an error when I enter the DK data.

Please tell me why the error occurs?

OS: macOS 10.13.6

Files: 

  • nrf9160dk_asset_tracker_nbiot_2020-10-30_5522ca2b.hex
  • mfwnrf9160122.zip

Parents
  • 0

    Hi,

    The device must be connected to nRF Cloud before you can add it to your account.

    On a nRF9160DK, LED 3 & 4 will blink together when the device is ready to be added.

    Also, the log from the device should say something like "Waiting for cloud association", although it might not be on the last line in the log.

    Was the device connected to nRF Cloud when you tried to add it to your account?

    Best regards,

    Didrik

  • 0 in reply to Didrik Rokhaug

    Hi,

    The device doesn't connect for some reason to nRF Cloud. Please add it to my account.

    Didrik Rokhaug said:
    On a nRF9160DK, LED 3 & 4 will blink together when the device is ready to be added.

    LED 3 & 4 doesn't blink.

    LED 1 & 2 blink together until I insert the SIM. After that, only LED 3 blinks.

    I haven't seen "Waiting for cloud association" yet.

    Didrik Rokhaug said:
    Was the device connected to nRF Cloud when you tried to add it to your account?

    No, it wasn't.

    Best regards,

    Vitaliy

  • 0 in reply to bratvitaly
    bratvitaly said:
    LED 1 & 2 blink together until I insert the SIM. After that, only LED 3 blinks.

     The SIM needs to be inserted for the application to work correctly.

    When only LED 3 blinks, that means that the device is searching for a network to connect to: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.4.0/nrf/applications/asset_tracker/README.html#user-interface

    What SIM card are you using?

    Are there LTE-M or NB-IoT coverage in your area (and where is that)?

    Has the SIM card been activated, and does it support your local LTE-M or NB-IoT network?

    If you are running the default application that came programmed on the chip, or an unmodified version of the asset_tracker, it will try to connect to LTE-M.

    If there is only NB-IoT coverage in our area, you might want to try the *_nbiot_* or *_nbiot_legacy_pco_* pre-compiled .hex files from our website: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF9160-DK/Download#infotabs

    If you do not use an application compiled with the "correct" network mode, you will have to wait 10 minutes before the network search times out and it tries the other mode.

    Finally, could you send me the log from the application?

    That way, I can see if the device finds any networks, but get rejected, or if it doesn't find any.

  • 0 in reply to Didrik Rokhaug

    Dear Didrik,

    Thanks for the info. 

    Didrik Rokhaug said:
    What SIM card are you using?

    I use iBasis, which is bundled with DK. Today I learned from an iBasis representative that their SIM does not support LTE-M and NB-IoT networks in my country.

    I'll try to find a SIM that supports IoT and try again with a connection to the nRF Cloud.

    Peripheral

	

	

Domain

	

	

Status

00 NRF_P0               Non-Secure

	

OK

01 NRF_CLOCK            Non-Secure

	

OK

02 NRF_RTC0             Non-Secure

	

OK

03 NRF_RTC1             Non-Secure

	

OK

04 NRF_NVMC             Non-Secure

	

OK

05 NRF_UARTE1           Non-Secure

	

OK

06 NRF_UARTE2           Secure

	

	

SKIP

07 NRF_TWIM2            Non-Secure

	

OK

08 NRF_SPIM3            Non-Secure

	

OK

09 NRF_TIMER0           Non-Secure

	

OK

10 NRF_TIMER1           Non-Secure

	

OK

11 NRF_TIMER2           Non-Secure

	

OK

12 NRF_SAADC            Non-Secure

	

OK

13 NRF_PWM0             Non-Secure

	

OK

14 NRF_PWM1             Non-Secure

	

OK

15 NRF_PWM2             Non-Secure

	

OK

16 NRF_PWM3             Non-Secure

	

OK

17 NRF_WDT              Non-Secure

	

OK

18 NRF_IPC              Non-Secure

	

OK

19 NRF_VMC              Non-Secure

	

OK

20 NRF_FPU              Non-Secure

	

OK

21 NRF_EGU1             Non-Secure

	

OK

22 NRF_EGU2             Non-Secure

	

OK

23 NRF_DPPIC            Non-Secure

	

OK

24 NRF_GPIOTE1          Non-Secure

	

OK

25 NRF_REGULATORS       Non-Secure

	

OK

SPM: NS image at 0x1c200

SPM: NS MSP at 0x2002f080

SPM: NS reset vector at 0x252f1

SPM: prepare to jump to Non-Secure image.

*** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***

[00:00:00.198,394] 

[0m<dbg> nrf9160_gps.setup: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577

[0m

[00:00:00.207,336] 

[0m<dbg> nrf9160_gps.setup: COEX0 set: AT%XCOEX0=1,1,1570,1580

[0m

[00:00:00.215,118] 

[0m<inf> asset_tracker: Asset tracker started

[0m

[00:00:00.228,515] 

[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656106120358

[0m

[00:00:00.237,823] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656106120358/shadow

[0m

[00:00:00.249,572] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656106120358/shadow/get/accepted

[0m

[00:00:00.261,138] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656106120358/shadow/get/rejected

[0m

[00:00:00.273,773] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656106120358/shadow/update/delta

[0m

[00:00:00.286,773] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656106120358/shadow/update

[0m

[00:00:00.298,706] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656106120358/shadow/get

[0m

[00:00:00.311,004] 

[0m<inf> asset_tracker: Connecting to LTE network. 

[0m

[00:00:00.317,779] 

[0m<inf> asset_tracker: This may take several minutes.

[0m

[00:00:00.332,702] 

[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0

[0m

+CEREG: 2,"4B0B","0022D7D4",9,0,0,"11100000","11100000"

[00:01:10.463,775] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2

[0m

+CEREG: 4,"4B0B","0022D7D4",9,0,15,"11100000","11100000"

[00:01:11.118,682] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4

[0m

+CEREG: 2,"4B56","0021D1D4",9,0,15,"11100000","11100000"

[00:01:12.713,409] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2

[0m

[00:10:00.380,432] 

[0m<inf> lte_lc: Network connection attempt timed out

[0m

+CEREG: 0,"4B56","0021D1D4",9,0,15,"11100000","11100000"

[00:10:00.395,935] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 0

[0m

[00:10:00.404,327] 

[0m<inf> lte_lc: Using fallback network mode

[0m

[00:10:00.410,491] 

[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0

[0m

+CEREG: 2,"FFFE","FFFFFFFF",7,0,15,"11100000","11100000"

[00:10:28.682,739] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2

[0m

[00:20:00.459,259] 

[0m<inf> lte_lc: Network connection attempt timed out

[0m

[00:20:00.466,247] 

[1;31m<err> asset_tracker: LTE link could not be established.

[0m

*** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***

[00:00:00.004,974] 

[0m<inf> mcuboot: Starting bootloader

[0m

[00:00:00.011,322] 

[0m<inf> mcuboot: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3

[0m

[00:00:00.021,392] 

[0m<inf> mcuboot: Boot source: none

[0m

[00:00:00.026,885] 

[0m<inf> mcuboot: Swap type: none

[0m

[00:00:00.359,741] 

[0m<inf> mcuboot: Bootloader chainload address offset: 0x10000

[0m

[00:00:00.367,492] 

[0m<inf> mcuboot: Jumping to the first image slot

[0m

*** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***

Flash regions

	

	

Domain

	

	

Permissions

00 02 0x00000 0x18000 

	

Secure

	

	

rwxl

03 31 0x18000 0x100000 

	

Non-Secure

	

rwxl

Non-secure callable region 0 placed in flash region 2 with size 32.

SRAM region

	

	

Domain

	

	

Permissions

00 07 0x00000 0x10000 

	

Secure

	

	

rwxl

08 31 0x10000 0x40000 

	

Non-Secure

	

rwxl

Peripheral

	

	

Domain

	

	

Status

00 NRF_P0               Non-Secure

	

OK

01 NRF_CLOCK            Non-Secure

	

OK

02 NRF_RTC0             Non-Secure

	

OK

03 NRF_RTC1             Non-Secure

	

OK

04 NRF_NVMC             Non-Secure

	

OK

05 NRF_UARTE1           Non-Secure

	

OK

06 NRF_UARTE2           Secure

	

	

SKIP

07 NRF_TWIM2            Non-Secure

	

OK

08 NRF_SPIM3            Non-Secure

	

OK

09 NRF_TIMER0           Non-Secure

	

OK

10 NRF_TIMER1           Non-Secure

	

OK

11 NRF_TIMER2           Non-Secure

	

OK

12 NRF_SAADC            Non-Secure

	

OK

13 NRF_PWM0             Non-Secure

	

OK

14 NRF_PWM1             Non-Secure

	

OK

15 NRF_PWM2             Non-Secure

	

OK

16 NRF_PWM3             Non-Secure

	

OK

17 NRF_WDT              Non-Secure

	

OK

18 NRF_IPC              Non-Secure

	

OK

19 NRF_VMC              Non-Secure

	

OK

20 NRF_FPU              Non-Secure

	

OK

21 NRF_EGU1             Non-Secure

	

OK

22 NRF_EGU2             Non-Secure

	

OK

23 NRF_DPPIC            Non-Secure

	

OK

24 NRF_GPIOTE1          Non-Secure

	

OK

25 NRF_REGULATORS       Non-Secure

	

OK

SPM: NS image at 0x1c200

SPM: NS MSP at 0x2002f080

SPM: NS reset vector at 0x252f1

SPM: prepare to jump to Non-Secure image.

*** Booting Zephyr OS build v2.1.99-ncs1-1145-g13dc96f83bab  ***

[00:00:00.198,272] 

[0m<dbg> nrf9160_gps.setup: MAGPIO set: AT%XMAGPIO=1,0,0,1,1,1574,1577

[0m

[00:00:00.207,214] 

[0m<dbg> nrf9160_gps.setup: COEX0 set: AT%XCOEX0=1,1,1570,1580

[0m

[00:00:00.214,965] 

[0m<inf> asset_tracker: Asset tracker started

[0m

[00:00:00.228,363] 

[0m<dbg> nrf_cloud_transport.nct_client_id_get: client_id = nrf-352656106120358

[0m

[00:00:00.237,640] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_base_topic: $aws/things/nrf-352656106120358/shadow

[0m

[00:00:00.249,389] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: accepted_topic: nrf-352656106120358/shadow/get/accepted

[0m

[00:00:00.260,986] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: rejected_topic: $aws/things/nrf-352656106120358/shadow/get/rejected

[0m

[00:00:00.273,620] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_delta_topic: $aws/things/nrf-352656106120358/shadow/update/delta

[0m

[00:00:00.286,590] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: update_topic: $aws/things/nrf-352656106120358/shadow/update

[0m

[00:00:00.298,522] 

[0m<dbg> nrf_cloud_transport.nct_topics_populate: shadow_get_topic: $aws/things/nrf-352656106120358/shadow/get

[0m

[00:00:00.310,821] 

[0m<inf> asset_tracker: Connecting to LTE network. 

[0m

[00:00:00.317,626] 

[0m<inf> asset_tracker: This may take several minutes.

[0m

[00:00:00.332,550] 

[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=0,1,1,0

[0m

+CEREG: 2,"E7F1","0BD2EBF8",9,0,0,"11100000","11100000"

[00:01:14.270,721] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2

[0m

+CEREG: 4,"E7F1","0BD2EBF8",9,0,15,"11100000","11100000"

[00:01:14.682,495] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4

[0m

+CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"

[00:01:14.970,672] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4

[0m

+CEREG: 2,"2352","0BCC89CC",9,0,15,"11100000","11100000"

[00:01:25.109,313] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2

[0m

+CEREG: 4,"2352","0BCC89CC",9,0,15,"11100000","11100000"

[00:01:26.010,131] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4

[0m

+CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"

[00:01:26.680,725] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4

[0m

+CEREG: 2,"4B0B","0022D7D4",9,0,15,"11100000","11100000"

[00:01:38.141,784] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2

[0m

+CEREG: 4,"4B0B","0022D7D4",9,0,15,"11100000","11100000"

[00:01:38.796,417] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4

[0m

+CEREG: 4,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"

[00:01:39.241,760] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4

[0m

+CEREG: 4,"E7F1","0BD2EBF8",9,0,15,"11100000","11100000"

[00:02:15.711,273] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 4

[0m

+CEREG: 2,"4B56","0021D1D4",9,0,15,"11100000","11100000"

[00:04:47.587,738] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2

[0m

+CEREG: 2,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"

[00:05:02.387,329] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 2

[0m

[00:10:00.380,279] 

[0m<inf> lte_lc: Network connection attempt timed out

[0m

+CEREG: 0,"FFFE","FFFFFFFF",9,0,15,"11100000","11100000"

[00:10:00.402,343] 

[0m<dbg> lte_lc.parse_nw_reg_status: Network registration status: 0

[0m

[00:10:00.410,766] 

[0m<inf> lte_lc: Using fallback network mode

[0m

[00:10:00.416,931] 

[0m<dbg> lte_lc.w_lte_lc_connect: Network mode: AT%XSYSTEMMODE=1,0,1,0

[0m

  • 0 in reply to bratvitaly

    First, when adding log files, could you use 'Insert->Image/video/file':

    Otherwise, the posts gets quite long, which makes it hard to navigate the ticket.

    I have also edited your replies by putting the logs in a 'code' section, to shorten the posts.

    The log shows that you find a network:

    +CEREG: 2,"4B0B","0022D7D4",9,0,0,"11100000","11100000"

    But get rejected, with cause 15:

    +CEREG: 4,"4B0B","0022D7D4",9,0,15,"11100000","11100000"

    Cause 15 is:

    Cause #15 – No suitable cells in tracking area This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area or location area in the same PLMN or an equivalent PLMN.

    In other words, it does not look like your new operator has NB-IoT coverage in your area, or your subscription does not cover your area (e.g. if you are roaming).

    The log shows the device trying some other tracking areas, but it always get the same reject cause.

Reply
  • 0 in reply to bratvitaly

    First, when adding log files, could you use 'Insert->Image/video/file':

    Otherwise, the posts gets quite long, which makes it hard to navigate the ticket.

    I have also edited your replies by putting the logs in a 'code' section, to shorten the posts.

    The log shows that you find a network:

    +CEREG: 2,"4B0B","0022D7D4",9,0,0,"11100000","11100000"

    But get rejected, with cause 15:

    +CEREG: 4,"4B0B","0022D7D4",9,0,15,"11100000","11100000"

    Cause 15 is:

    Cause #15 – No suitable cells in tracking area This EMM cause is sent to the UE if it requests service, or if the network initiates a detach request, in a tracking area where the UE, by subscription, is not allowed to operate, but when it should find another allowed tracking area or location area in the same PLMN or an equivalent PLMN.

    In other words, it does not look like your new operator has NB-IoT coverage in your area, or your subscription does not cover your area (e.g. if you are roaming).

    The log shows the device trying some other tracking areas, but it always get the same reject cause.

Children
Related
Terms of service