Skip to Content
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.5
edited by Mengting Qiu
on 2025/07/29 14:00
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,16 +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 ====
325 +==== 4.1.2.5 Certificate Management for -NB/-NS Models ====
326 326  
327 327  
328 328  The -NB/-NS modules (BC660K) do not support clearing certificates via AT commands or firmware updates.
329 329  
330 +To effectively remove existing certificates or test certificate upload functionality, users may overwrite them with dummy data.
331 +
332 +
330 330  To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps:
331 331  
332 -1. Overwrite Certificates:
335 +**Scenario A:** Clearing Existing Certificates
333 333  
334 -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).
335 335  Example:
336 336  
337 337  AT+CACERT=123456}
... ... @@ -341,7 +341,21 @@
341 341  AT+CLIKEY=123456}
342 342  
343 343  
349 +**Scenario B:** Testing Certificate Upload Functionality
344 344  
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 +2. Upload Valid Certificates (Optional):
360 +
361 +After overwriting, users may proceed to upload new valid certificates if needed.
362 +
363 +
345 345  == 4.2  For -CB /-CS model ==
346 346  
347 347  === 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===