ST67W611M1 (mission firmware 2.0.106, T01 and T02): BLE link security on the host, factory reset, and OTA status
Hello,
We are using the ST67W611M1 with an STM32H573 host, X-CUBE-ST67W61 1.3.0 and mission firmware 2.0.106 (AT 1.0.0). We started on T01 and have now moved to T02. The BLE and firmware-update observations below were made on T01; please say where T02 behaves differently.
BLE security
1. Encrypted-only characteristics. How can a GATT server characteristic be made to require an encrypted, authenticated link? `AT+BLEGATTSCHARCRE` accepts permission 1 (READ) and 2 (WRITE), but answers ERROR to 17 (READ | READ_AUTHEN) and 34 (WRITE | WRITE_AUTHEN). Is support for the encryption and authentication permission bits planned?
2. Link security level on the host. After `AT+BLESECSTART=<conn>,3` on a bonded reconnect, the module answers OK but sends no further event. Is there an event or a query that tells the host the current security level of a connection (for example a "security changed" event)? If not, is one planned?
3. How many bonds does the mission firmware keep, and what happens when a new device pairs at the limit?
4. Is the security level set with `AT+BLESECPARAM` enforced by the module on every connection, or is it only a default for `AT+BLESECSTART`?
Factory reset
5. Which command removes stored Wi-Fi credentials and BLE bonds from the module (and TLS files under T01)? Does `AT+RESTORE` (sent by the driver for `W61_RESET_MODE_RESTORE`) erase them from flash?
Module firmware update (AT+OTASTART / OTASEND / OTAFIN)
6. When the transferred image fails its SHA-256 check, the module logs `[OTA] check SHA256 NOT Correct` after `AT+OTAFIN` and does not reboot. But `AT+OTAFIN` has already answered OK, so `W6X_FWU_Finish` waits 30 s for a reboot and then fails. Could `AT+OTAFIN` return ERROR in this case, and the driver handle it?
7. When the module does not switch to the new image and boots the previous one, `W6X_FWU_Finish` returns OK. Is there a way for the host to learn that a rollback happened, for example an event at boot or a query for the active firmware partition, other than comparing version strings?
8. How is the anti-rollback version used for mission firmware images? What version do 2.0.97 and 2.0.106 carry, and can it be raised in production (by an AT command, or only with `--efuse` at the factory)?
9. The host driver refuses a module whose architecture does not match its build (`W6X_Init`: "SDK T01 variant is required"). Does the module itself refuse a T01 image sent over `AT+OTASTART` while it runs T02, and the reverse, or must the host check the image before sending it?
Thank you.
