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

Summary

Details

Page properties
Content
... ... @@ -329,11 +329,14 @@
329 329  
330 330  To effectively remove existing certificates or test certificate upload functionality, users may overwrite them with dummy data.
331 331  
332 +
332 332  To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps:
333 333  
334 -1. Overwrite Certificates:
335 +**Scenario A:** Clearing Existing Certificates
335 335  
336 -Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456).
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"]]**
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).
337 337  Example:
338 338  
339 339  AT+CACERT=123456}
... ... @@ -342,11 +342,19 @@
342 342  
343 343  AT+CLIKEY=123456}
344 344  
345 -2. Upload Valid Certificates (Optional):
346 346  
347 -After overwriting, users may proceed to upload new valid certificates if needed.
349 +**Scenario B:** Testing Certificate Upload Functionality
348 348  
351 +If users want to test whether certificate writing works (without having valid certificates yet):
349 349  
353 +~1. Follow the same steps as above.
354 +
355 +2. Check for success responses after each command:
356 +
357 +
358 +3. Later, when you have real certificates, overwrite the dummy data with actual certificates.
359 +
360 +
350 350  == 4.2  For -CB /-CS model ==
351 351  
352 352  === 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===