nrf9160 sms send Response +CMS ERROR: 300

RE: nrf9160 sms send Response +CMS ERROR: 300

Didrik Rokhaug — Wed, 11 Nov 2020 10:14:13 GMT

This is the procedure I use when I take a modem trace:

1. Flash the at_client sample.

2. Send AT%XMODEMTRACE=1,2 followed by AT+CFUN=0 (you should get "OK" back from the modem for both the commands.

3. Set CONFIG_BSD_LIBRARY_TRACE_ENABLED=y in the prj.conf file of my project. If I am using SES, re-open the project.

4. Build and flash my project.

5. Start capturing the trace, then reset the device. Let the trace run until the situation I want to study has been captured.

If everything is working as it should, the size of the trace should increase rapidly. The trace should be at least several kilobytes, and often a megabyte or more.

RE: nrf9160 sms send Response +CMS ERROR: 300

copen — Wed, 11 Nov 2020 03:21:56 GMT

At present, follow the at routine to capture the trace of the module, open the macro definition CONFIG_BSD_LIBRARY_TRACE_ENABLED, send AT%XMODEMTRACE=1,2 and AT+CFUN=0, and then press the reset button to restart, use nrf connection V3.60 to capture the trace collector, but there is no change in the data inside, all are 2b in size

RE: nrf9160 sms send Response +CMS ERROR: 300

copen — Wed, 11 Nov 2020 03:18:34 GMT

RE: nrf9160 sms send Response +CMS ERROR: 300

Didrik Rokhaug — Tue, 10 Nov 2020 14:09:00 GMT

Hi,

+CMS error 300 is "ME failure".

Could you take a modem trace so we can see what happens on the modem side?

Best regards,

Didrik