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 48.1
edited by Bei Jinggeng
on 2025/07/16 14:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Bei
Content
... ... @@ -322,31 +322,6 @@
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 Certificate Management for -NB/-NS Models ====
326 -
327 -
328 -The -NB/-NS modules (BC660K) do not support clearing certificates via AT commands or firmware updates.
329 -
330 -To effectively remove existing certificates or test certificate upload functionality, users may overwrite them with dummy data.
331 -
332 -To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps:
333 -
334 -1. Overwrite Certificates:
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 -Example:
338 -
339 -AT+CACERT=123456}
340 -
341 -AT+CLICERT=123456}
342 -
343 -AT+CLIKEY=123456}
344 -
345 -2. Upload Valid Certificates (Optional):
346 -
347 -After overwriting, users may proceed to upload new valid certificates if needed.
348 -
349 -
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 ===