Page 1 of 1
Not able to write Mqtt cert in v3.2.0.0 ESP32-WROOM-32
Posted: Fri Jun 14, 2024 12:24 pm
by chiragteksun
Using ESP32 Flash Download Tool Download v3.2.0.0 ESP32-WROOM-32-AT-V3.2.0.0.zip in ESP 32 wroom 32,
After when give AT+SYSFLASH? then we are able to see only two 2 partition not able to see Mqtt client server partition,in 0x37000 address we are try to write the Mqtt cert but we are not able to write it,
But when Download v2.1.0.0 ESP32-WROOM-32-AT-V2.1.0.0.zip and give AT+SYSFLASH? at that time we are able to see all partition and we are able to write the Mqtt cert.
so in new version how we can write the Mqtt cert?
Re: Not able to write Mqtt cert in v3.2.0.0 ESP32-WROOM-32
Posted: Fri Jun 28, 2024 8:07 am
by esp-at
Hello!
You can refer to Breaking changes of v3.2.0.0.
https://github.com/espressif/esp-at/rel ... g/v3.2.0.0
In short, you can use AT+SYSMFG command to operate PKI items.
https://docs.espressif.com/projects/esp ... cmd-sysmfg
Re: Not able to write Mqtt cert in v3.2.0.0 ESP32-WROOM-32
Posted: Tue Jul 02, 2024 12:03 pm
by chiragteksun
Ok thank you for your response,
using AT+SYSMFG i am trying to write client.cert,i used Arduino serial port for write the data,
using AT+SYSMFG=2,"client_cert","client_cert.0",8,1164 i write the data, after write data when i read data using AT+SYSMFG=1,"client_cert","client_cert.0",I read below data in one line,
so how i can add the new line when we used serial terminal?
+SYSMFG:"client_cert","client_cert.0",8,1164,\"-----BEGIN CERTIFICATE-----\n" \ "MIIDLTCCAhWgAwIBAgIJAN6LrsW0Qt2FMA0GC........
Re: Not able to write Mqtt cert in v3.2.0.0 ESP32-WROOM-32
Posted: Tue Aug 06, 2024 8:24 am
by esp-at
In the standard certificate format, there is always a line break (one character, i.e., ASCII code 0a) following `-----BEGIN CERTIFICATE-----`.
However, from your description, it seems that instead of a line break, there is `\n` (two characters, i.e., ASCII codes 5c, 6e) after `-----BEGIN CERTIFICATE-----`. This appears to be due to the absence of a line break in the written certificate.
You might need to check the certificate format again to ensure it is written correctly.