AT firmware not saving bonding information persistent

[javier.reyes]

Related Information:

• ESP-AT FW v4.0.0 release

• ESP32-C6-Mini-1U (ESP32-C6 DevKitM-1)

AT Commands sequence used:

Code: Select all

ATE0
AT+BLEINIT=2
AT+BLEADVPARAM=50,50,0,0,7,0,,
AT+BLEADVDATA="020106030302A00A09736D6172745F6D6174"
AT+BLESPPCFG=1,1,7,1,5
AT+BLESECPARAM=13,0,16,3,3,1
AT+BLESETKEY=654321
AT+BLEADVSTART
/* When remote mobile device (running LightBlue App) connects */
AT+BLEENC=0,3
/* Pairing process is started in mobile device, passkey correctly entered, pairing completed and confirmed */
AT+BLEENCDEV?
/* Response shows a new entry with MAC address of remote device (Resolvable Private Address) */

/* After a while, device is either reseted, restarted, power cycle */
ATE0
AT+BLEINIT=2
AT+BLEADVPARAM=50,50,0,0,7,0,,
AT+BLEADVDATA="020106030302A00A09736D6172745F6D6174"
AT+BLESPPCFG=1,1,7,1,5
AT+BLESECPARAM=13,0,16,3,3,1
AT+BLESETKEY=654321
AT+BLEADVSTART
AT+BLEENCDEV?
/* At this point, the previous entry for bonding data is lost, bonding data is completely empty */

Q1: Is the bonding information not stored persistent by default in ESP-AT FW v4.0.0 release? If so, why is this not mentioned in the documentation, as it is shown in other sections (like the WebServer section)?

Q2: When researching about the FW Stack used in ESP-AT, one finds that the BLE Stack might be either BlueDroid or NimBLE. Which one of these is being used in v4.0.0 release?

Q3: What I assume from the file sdkconfig present in the folder where the v4.0.0 binary files are, is that for NimBLE is the setting CONFIG_NIMBLE_NVS_PERSIST not enabled. If Q2 answer is NimBLE, would it be necessary to enable this setting and rebuild the AT firmware in oder to have functional pairing process? (BLE Pairing that is not persistent is absolutely useless).

Thanks in advance for any reply/feedback on this

Kind regards