Not possible to write a device certificate with at AT%CMNG=0,16842753,1

RE: Not possible to write a device certificate with at AT%CMNG=0,16842753,1

MB — Thu, 27 Mar 2025 16:12:44 GMT

I used the at_client as suggested, that worked.

RE: Not possible to write a device certificate with at AT%CMNG=0,16842753,1

Hakon — Fri, 14 Mar 2025 07:35:51 GMT

Just using the normal AT command interface.

RE: Not possible to write a device certificate with at AT%CMNG=0,16842753,1

MB — Thu, 20 Feb 2025 15:27:13 GMT

Without CONFIG_AT_SHELL?

RE: Not possible to write a device certificate with at AT%CMNG=0,16842753,1

Hakon — Thu, 20 Feb 2025 14:56:24 GMT

Have you tried writing the cert directly with at+cmng? Does that also fail?

RE: Not possible to write a device certificate with at AT%CMNG=0,16842753,1

MB — Thu, 20 Feb 2025 12:55:03 GMT

[quote userid="73166" url="~/f/nordic-q-a/119144/not-possible-to-write-a-device-certificate-with-at-at-cmng-0-16842753-1/523882"]Are you using the nrf9160 DK as a UART-USB CDC ACM bridge to your custom board?[/quote]

yes

RE: Not possible to write a device certificate with at AT%CMNG=0,16842753,1

Hakon — Thu, 20 Feb 2025 12:22:02 GMT

Hello,

Available ports:
1: /dev/ttyACM0 nRF9160-DK
Opening port /dev/ttyACM0 as generic device...

-> at AT+CGMR
<- mosh:~$ at AT+CGMR
<- mfw_nrf91x1_2.0.2
<- OK

saw this in the log. Are you using the nrf9160 DK as a UART-USB CDC ACM bridge to your custom board? If not, why do you run MFW on nRF9160 DK?