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

Can't get modem to turn off for certificate update AT+FUN=4

ERIK

I'm trying to provision a DK to talk to an Azure IoT Hub and have a CA Cert, Private Key, and Public Key to use with them.  I'm having trouble getting authentication of the TLS sockets working (-95 error) when using the nrf inbuilt key write functions, so thought I'd try programming the certificates in via the nRF LTE Link Monitor Certificate Manager.

I'm trying to follow these instructions: https://devzone.nordicsemi.com/nordic/cellular-iot-guides/b/getting-started-cellular/posts/nrf-cloud-certificate-update

I have loaded the AT Client with the 3072 byte buffer, and have removed the SIM, but I can't seem to get the modem to stay off with AT+CFUN=4.  I send AT+CFUN=4, and then read with AT+CFUN? and it always goes back to AT+CFUN=1.

In the example below, I send AT+CFUN=4.  Then I check with AT+CFUN?, but an extra AT command gets sent: AT+CFUN=1!!!

2020-01-01T03:02:37.179Z INFO Application data folder: C:\Users\eriks\AppData\Roaming\nrfconnect\pc-nrfconnect-linkmonitor
2020-01-01T03:02:37.468Z DEBUG App pc-nrfconnect-linkmonitor v1.1.1 official
2020-01-01T03:02:37.469Z DEBUG App path: C:\Users\eriks\.nrfconnect-apps\node_modules\pc-nrfconnect-linkmonitor
2020-01-01T03:02:37.469Z DEBUG nRFConnect 3.3.0 is supported by the app (^3.2.0)
2020-01-01T03:02:37.469Z DEBUG nRFConnect path: C:\Users\eriks\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-01-01T03:02:37.469Z DEBUG HomeDir: C:\Users\eriks
2020-01-01T03:02:37.469Z DEBUG TmpDir: C:\Users\eriks\AppData\Local\Temp
2020-01-01T03:02:44.660Z INFO Modem port is opened
2020-01-01T03:02:44.669Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-01-01T03:02:44.704Z DEBUG modem << +CFUN: 0\x0D\x0A
2020-01-01T03:02:44.707Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:00.186Z DEBUG modem >> AT+CFUN=4\x0D\x0A
2020-01-01T03:03:00.200Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:10.798Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-01-01T03:03:10.812Z DEBUG modem << +CFUN: 4\x0D\x0A
2020-01-01T03:03:10.826Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:10.830Z DEBUG modem >> AT+CFUN=1\x0D\x0A
2020-01-01T03:03:10.879Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:26.892Z DEBUG modem >> AT+CFUN?\x0D\x0A
2020-01-01T03:03:26.899Z DEBUG modem << +CFUN: 1\x0D\x0A
2020-01-01T03:03:26.915Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:26.918Z DEBUG modem >> AT+CGSN=1\x0D\x0A
2020-01-01T03:03:26.925Z DEBUG modem << +CGSN: "352656100158156"\x0D\x0A
2020-01-01T03:03:26.925Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:26.928Z DEBUG modem >> AT+CGMI\x0D\x0A
2020-01-01T03:03:26.933Z DEBUG modem << Nordic Semiconductor ASA\x0D\x0A
2020-01-01T03:03:26.935Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:26.942Z DEBUG modem >> AT+CGMM\x0D\x0A
2020-01-01T03:03:26.947Z DEBUG modem << nRF9160-SICA\x0D\x0A
2020-01-01T03:03:26.948Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:26.951Z DEBUG modem >> AT+CGMR\x0D\x0A
2020-01-01T03:03:26.958Z DEBUG modem << mfw_nrf9160_1.1.0\x0D\x0A
2020-01-01T03:03:26.959Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:26.960Z INFO Nordic Semiconductor ASA nRF9160-SICA [mfw_nrf9160_1.1.0] SerNr: 352656100158156
2020-01-01T03:03:26.962Z DEBUG modem >> AT+CEMODE?\x0D\x0A
2020-01-01T03:03:26.967Z DEBUG modem << +CEMODE: 2\x0D\x0A
2020-01-01T03:03:26.968Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:26.976Z DEBUG modem >> AT%XCBAND=?\x0D\x0A
2020-01-01T03:03:26.985Z DEBUG modem << %XCBAND: (1,2,3,4,5,8,12,13,14,17,18,19,20,25,26,28,66)\x0D\x0A
2020-01-01T03:03:26.987Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:26.997Z DEBUG modem >> AT+CMEE?\x0D\x0A
2020-01-01T03:03:27.003Z DEBUG modem << +CMEE: 0\x0D\x0A
2020-01-01T03:03:27.005Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.008Z DEBUG modem >> AT+CMEE=1\x0D\x0A
2020-01-01T03:03:27.013Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.016Z DEBUG modem >> AT+CNEC?\x0D\x0A
2020-01-01T03:03:27.022Z DEBUG modem << +CNEC: 0\x0D\x0A
2020-01-01T03:03:27.026Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.029Z DEBUG modem >> AT+CNEC=24\x0D\x0A
2020-01-01T03:03:27.034Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.041Z DEBUG modem >> AT+CGEREP?\x0D\x0A
2020-01-01T03:03:27.047Z DEBUG modem << +CGEREP: 0,0\x0D\x0A
2020-01-01T03:03:27.048Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.052Z DEBUG modem >> AT+CGDCONT?\x0D\x0A
2020-01-01T03:03:27.056Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.059Z DEBUG modem >> AT+CGACT?\x0D\x0A
2020-01-01T03:03:27.063Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.066Z DEBUG modem >> AT+CGEREP=1\x0D\x0A
2020-01-01T03:03:27.074Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.076Z DEBUG modem >> AT+CIND=1,1,1\x0D\x0A
2020-01-01T03:03:27.081Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.083Z DEBUG modem >> AT+CEREG=2\x0D\x0A
2020-01-01T03:03:27.087Z DEBUG modem << OK\x0D
2020-01-01T03:03:27.089Z DEBUG modem >> AT+CEREG?\x0D\x0A
2020-01-01T03:03:27.096Z DEBUG modem << +CEREG: 2,90,"FFFE","FFFFFFFF",7\x0D\x0A
2020-01-01T03:03:27.097Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.110Z DEBUG modem >> AT%CESQ=1\x0D\x0A
2020-01-01T03:03:27.115Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.119Z DEBUG modem >> AT+CESQ\x0D\x0A
2020-01-01T03:03:27.126Z DEBUG modem << +CESQ: 99,99,255,255,255,255\x0D\x0A
2020-01-01T03:03:27.127Z DEBUG modem << OK\x0D
2020-01-01T03:03:27.136Z DEBUG modem >> AT%XSIM=1\x0D\x0A
2020-01-01T03:03:27.143Z DEBUG modem << OK\x0D\x0A
2020-01-01T03:03:27.146Z DEBUG modem >> AT%XSIM?\x0D\x0A
2020-01-01T03:03:27.152Z DEBUG modem << %XSIM: 0\x0D\x0A
2020-01-01T03:03:27.153Z DEBUG modem << OK\x0D

Can I program the certificates in this state?  Am I doing something wrong?  Should I just set it to 4 and then never check it, assuming it is in the right state?

Thanks,

Erik

Related
Terms of service