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

Summary

Details

Page properties
Content
... ... @@ -322,17 +322,21 @@
322 322  After completing the certificate configuration, Burn the [[bootloader>>https://www.dropbox.com/sh/u0uzvvnn58yrie4/AAAvvF_KRveNgmDejzp23ziLa/NB-IoT/Bootloader?dl=0&subfolder_nav_tracking=1]] firmware first, then re-burn the original working [[firmware>>https://www.dropbox.com/sh/u0uzvvnn58yrie4/AACREHllkTe0rATD4ZOqddyga/NB-IoT?dl=0]].
323 323  
324 324  
325 -==== 4.1.2.5 Overwriting Certificates on -NB/-NS Models Certificate Management for -NB/-NS Models ====
325 +==== 4.1.2.5 Certificate Management for -NB/-NS Models ====
326 326  
327 327  
328 -
329 329  The -NB/-NS modules (BC660K) do not support clearing certificates via AT commands or firmware updates.
330 330  
330 +To effectively remove existing certificates or test certificate upload functionality, users may overwrite them with dummy data.
331 +
332 +
331 331  To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps:
332 332  
333 -1. Overwrite Certificates:
335 +**Scenario A:** Clearing Existing Certificates
334 334  
335 -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).
336 336  Example:
337 337  
338 338  AT+CACERT=123456}
... ... @@ -341,6 +341,17 @@
341 341  
342 342  AT+CLIKEY=123456}
343 343  
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 +
344 344  2. Upload Valid Certificates (Optional):
345 345  
346 346  After overwriting, users may proceed to upload new valid certificates if needed.