Skip to Content
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.15
edited by Mengting Qiu
on 2025/07/29 14:24
Change comment: There is no comment for this version
To version 49.11
edited by Mengting Qiu
on 2025/07/29 14:16
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -329,14 +329,17 @@
329 329  
330 330  To effectively remove existing certificates or test certificate upload functionality, users may overwrite them with dummy data.
331 331  
332 -
333 333  To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps:
334 334  
335 335  **Scenario A:** Clearing Existing Certificates
336 336  
337 -1.Flash the certificate-provisioning firmware: **[[Set up TLS certificate - Dropbox>>https://www.dropbox.com/scl/fo/1ykfsesmr3702tj3kp663/AOOyH1GiVEOGR41gASuiDk0?rlkey=1q7a1b5yvjgt87d16w8tt0cum&st=vdy765ut&dl=0||data-sider-select-id="830d1b64-cb24-48b3-91e4-49da5c3f0783"]]**
336 +If users want to remove old certificates:
338 338  
339 -2. Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456).
338 +~1. Connect to the module via serial/USB and open a terminal (e.g., PuTTY, Tera Term).
339 +
340 +
341 +
342 +Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456).
340 340  Example:
341 341  
342 342  AT+CACERT=123456}
... ... @@ -345,17 +345,6 @@
345 345  
346 346  AT+CLIKEY=123456}
347 347  
348 -
349 -**Scenario B:** Testing Certificate Upload Functionality
350 -
351 -If users want to test whether certificate writing works (without having valid certificates yet):
352 -
353 -~1. Follow the same steps as above.
354 -
355 -2. Check for success responses after each command:
356 -
357 -
358 -
359 359  2. Upload Valid Certificates (Optional):
360 360  
361 361  After overwriting, users may proceed to upload new valid certificates if needed.