• State Not Answered
  • Replies 1 reply
  • Subscribers 68 subscribers
  • Views 36 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 333814
Options

"lte_lc: Could not send AT command, error" with nRF9160 SIAA B1 on Custom Board Using SDK v2.5.0 and Modem v1.3.5

ksksue

I am using a custom board with the nRF9160 SIAA B1.
I encounter an error where AT commands cannot be sent. How can I resolve this issue?
modem version 1.3.5
SDK version 2.5.0,

When I run the aws_iot sample code, I get the following error messages:

*** Booting nRF Connect SDK v2.5.0 ***e: Fatal error! Rebooting the device.
[00:00:00.253,601] <inf> aws_iot_sample: The AWS IoT sample started, version: v1.0.0
[00:00:00.253,631] <inf> aws_iot_sample: Bringing network interface up and connecting to the network
[00:00:00.483,367] <inf> nrf_modem_lib_trace: Trace thread ready
[00:00:00.490,661] <inf> nrf_modem_lib_trace: Trace level override: 2
[00:00:00.501,312] <err> lte_lc: Could not send AT command, error: 65536
[00:00:00.501,342] <err> lte_lc: Could not set system mode, error: -14
[00:00:00.501,373] <err> lte_connectivity: lte_lc_init, error: -14
[00:00:00.501,373] <err> aws_iot_sample: conn_mgr_all_if_up, error: -14
*** Booting nRF Connect SDK v2.5.0 ***e: Fatal error! Rebooting the device.

Our product only requires LTE connectivity, so we switched from nRF9160 SICA B1 to SIAA B1.
This error did not occur on SICA or the DK board, but on the SIAA-based custom board, the AT command error appears.

Additionally, I found that using modem version 1.3.2 with SDK version 2.0.2, the aws_iot sample works correctly, and LTE connectivity is established without the error on the SIAA board.

When I use the samples/cellular/at_client sample code, the AT commands seem to work correctly:

*** Booting nRF Connect SDK v2.5.0 ***
The AT host sample started
Ready
> AT+CFUN?
+CFUN: 0
OK
> AT+CFUN=1
OK
> AT+CFUN?
+CFUN: 1
OK
> AT+CFUN=4
OK
> AT+CFUN?
+CFUN: 4
OK
> AT%SHORTSWVER
%SHORTSWVER: nrf9160_1.3.5
OK

Parents
  • 0

    I made a small modification to the aws_iot sample to comment out sections that caused AT command errors with lte_lc and prevented repeated reboots.
    Additionally, I set CONFIG_AT_HOST_LIBRARY=y to enable AT command responses.
    However, when I tested it, the AT command errors still appeared as shown below:

    *** Booting nRF Connect SDK v2.5.0 ***
[00:00:00.253,417] <inf> aws_iot_sample: The AWS IoT sample started, version: v1.0.0
[00:00:00.253,448] <inf> aws_iot_sample: Bringing network interface up and connecting to the network
> AT
[00:00:07.959,197] <err> at_host: Error while processing AT command: -1
AT> AT
[00:00:16.997,100] <err> at_host: Error while processing AT command: -1
AT

    I also tested the aws_iot sample using modem version 1.3.6 with SDK version 2.5.3 on the SIAA board,
    but the results were the same as with modem version 1.3.5 and SDK version 2.5.0.
Reply
  • 0

    I made a small modification to the aws_iot sample to comment out sections that caused AT command errors with lte_lc and prevented repeated reboots.
    Additionally, I set CONFIG_AT_HOST_LIBRARY=y to enable AT command responses.
    However, when I tested it, the AT command errors still appeared as shown below:

    *** Booting nRF Connect SDK v2.5.0 ***
[00:00:00.253,417] <inf> aws_iot_sample: The AWS IoT sample started, version: v1.0.0
[00:00:00.253,448] <inf> aws_iot_sample: Bringing network interface up and connecting to the network
> AT
[00:00:07.959,197] <err> at_host: Error while processing AT command: -1
AT> AT
[00:00:16.997,100] <err> at_host: Error while processing AT command: -1
AT

    I also tested the aws_iot sample using modem version 1.3.6 with SDK version 2.5.3 on the SIAA board,
    but the results were the same as with modem version 1.3.5 and SDK version 2.5.0.
Children
No Data
Related