at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

RE: at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

Oguzhan Turk — Thu, 27 Jul 2023 08:07:36 GMT

I found the problem. The problem was using SDK as 2.1.3 but modem firmware as 2023-03-02_8f26142b which has changelog "Updated to nRF Connect SDK 2.3.0". On Nordic firmware, there is some kind of backward compatibility issue. I downgraded firmware to 2022-09-15_7a358cb7 which has changelog "Updated to nRF Connect SDK 2.1.0" and problem solved.

RE: at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

Didrik Rokhaug — Tue, 18 Jul 2023 09:12:23 GMT

[quote user="Oguzhan Turk"]I executed AT%XMODEMTRACE=1,2 and it returned OK and then I executed AT+CFUN=4. It stucked again and didn't produce any extra output for tracing.[/quote]

Was CONFIG_NRF_MODEM_LIB_TRACE enabled?

Also, the modem trace is outputted on a separate COM port, it will not add more output from the application itself.

[quote user="Oguzhan Turk"]I also tried your mosh_mtrace.hex but it didn't work on my dev board. Instead of proper mosh outputs it put non-human readable characters to the screen like that:[/quote]

What baudrate did you use?

The .hex file works as expected on my DK.

The shell interface is sent on one COM port, with a baudrate of 115200. The modem trace is sent on a different COM port, with baudrate 1000000, but it is not human readable anyway. Instead, you should use the Cellular Monitor in nRF Connect for Desktop to receive the trace and save it to disk. Then you can send me the .mtrace file.

(note that the COM port will probably be different in your case. The Cellular Monitor should be able to select the correct one automatically)

RE: at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

Oguzhan Turk — Fri, 14 Jul 2023 13:44:59 GMT

By the way, I'm using development kit www.nordicsemi.com/.../nRF9160-DK

RE: at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

Oguzhan Turk — Fri, 14 Jul 2023 13:09:52 GMT

I executed AT%XMODEMTRACE=1,2 and it returned OK and then I executed AT+CFUN=4. It stucked again and didn't produce any extra output for tracing.

I also tried your mosh_mtrace.hex but it didn't work on my dev board. Instead of proper mosh outputs it put non-human readable characters to the screen like that:

�!�B�,X�,P(<B^/��; ,A8$��8B��"��(R��; ��,X�(�`��P/(R��BbB�(PA �"((�<(!�(��N
XA�R(�k��hB(̬k��jB��8��
N�(�A8�J(,�N�K
XA8Bb
��
��,�3�
HAx�
-A!
B�$-��H@Aj@9Ȓ
B�
.�X�R-� JA8B� #��!# P ��(P ah��P��h,�@��N�,��N�R
�n
�@��n��A��{��k�-(��
�R̨BH�Ax��R(�HB�R-
XKD��F�D�aHB�#B��;�
Cc$�� X��C �� x+P��X�@N��ǀB5��H4PB ��H��B X$�ȃ ��CBSȣ��
�Jh@( �`8�
`ddtdpX��@ !-0ZC
A��I�Zc�R)� �BA��2�(�@A��c��A�bB�`(�B@XAh��@P�BP��B)�#��@A�
�c)��sc(�AP�
Q�
��J�B�(��X�� b�c��(��tlr�� P��Q�P(��P(�BA�c�2�sc(3��$�!��X�0�0D��E \�D�B`A0�A��T��8��(��(HB��@��((�`<<C��@� B�#�#Xx� ��؁� ��(P@ �B
$��*
�`� @`�db � �$ �a�`��'��P�:N!N�N��
�� L��H��@��L��L�H��H��B�RB��@��B��(��L�H��!��Hp@4�
�� H�H��H��$�
N��
��偦��@�@��&��F��&��H�@��!��PT 1��B��N��

��9��#��@�@��(��
��N��H�@��
�J��8��0 H�)��@��
H��
��@��L��1��!��#"��J�N��"�2D��4��L�H��Z�@��Q
�8@��
�� J�N��R��#�A��r<@��
��$��@��
��8��(�� B�F��$��H��'�� J��@��dp��X��L��R��(a�0��(��B��@!��Y��PA��)��
��A��A��A�i"�@��`��FP��P��a"��d��Ά ��@�N��H��%@�@��P�H��H��R��@�@�!��P��p/RA�ZA{�AA�A(�A
��a��΀&Pa�P�� P��i"&'�� Za�F�΀�d��>c��a��a��`Xa�Ra��V�D��V��A��X�X��(�J�0�:X@*(��*(1� ��@f�!!�9��XB�ġ0�X�9! ��#

�
B<88�H�� >::P�:*ġ6�*��"P""�"` �d��

RE: at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

Didrik Rokhaug — Fri, 14 Jul 2023 11:32:01 GMT

Hi Oguzhan Turk,

I am not able to reproduce this.

Could you take a modem trace, so we can see if the problem is on the modem side?

I've attached a version of the modem shell, built for the nRF9160 DK, with modem tracing enabled.

Before you send the AT+CFUN=4 command, please send AT%XMODEMTRACE=1,2 to ensure that the modem has tracing enabled.

devzone.nordicsemi.com/.../mosh_5F00_mtrace.hex

Best regards,

Didrik

RE: at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

Achim Kraus — Fri, 14 Jul 2023 10:14:53 GMT

Uups, sorry I missed to read your ticket precisely.

I'm not common with that " at_cmd_mode", so I don't know what happens there.

RE: at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

Oguzhan Turk — Fri, 14 Jul 2023 09:50:44 GMT

Achim Kraus It always stuck and doesn't come back even after 60s. Are there any solution or workaround etc?

RE: at_cmd_mode AT+CFUN=4 problem on modem_shell firmware

Achim Kraus — Thu, 13 Jul 2023 11:43:08 GMT

If you search this forum, you will find some tickets, which discus what happens.

The modem tries to "release the network registration", but in many cases, this ends up in a timeout, which is about 60s.