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

Summary

Details

Page properties
Content
... ... @@ -322,11 +322,30 @@
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 For certificate coverage of the -NB/-NS model ====
325 +==== 4.1.2.5 Overwriting Certificates on -NB/-NS Models Certificate Management for -NB/-NS Models ====
326 326  
327 -For the -NB/-NS models, there is no AT command available to clear configured certificates. Therefore, if users do not wish to use the pre-configured certificates, they only need to follow the instructions above and use the AT+CACERT, AT+CLICERT, and AT+CLIKEY commands to assign custom meaningless characters to the device. This will overwrite the original certificates.
328 328  
329 329  
329 +The -NB/-NS modules (BC660K) do not support clearing certificates via AT commands or firmware updates.
330 +
331 +To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps:
332 +
333 +1. Overwrite Certificates:
334 +
335 +Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456).
336 +Example:
337 +
338 +AT+CACERT=123456}
339 +
340 +AT+CLICERT=123456}
341 +
342 +AT+CLIKEY=123456}
343 +
344 +2. Upload Valid Certificates (Optional):
345 +
346 +After overwriting, users may proceed to upload new valid certificates if needed.
347 +
348 +
330 330  == 4.2  For -CB /-CS model ==
331 331  
332 332  === 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===