Changes for page Dragino -NB/-CB device connection to AWS platform instructions
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.3
edited by Mengting Qiu
on 2025/07/29 13:58
on 2025/07/29 13:58
Change comment:
There is no comment for this version
To version 49.9
edited by Mengting Qiu
on 2025/07/29 14:15
on 2025/07/29 14:15
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -322,18 +322,36 @@ 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 OverwritingCertificateson -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 + 330 330 To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps: 331 331 332 - 1. OverwriteCertificates:334 +**Scenario A:** Clearing Existing Certificates 333 333 336 +If users want to remove old certificates: 334 334 335 335 336 336 340 + 341 +Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456). 342 +Example: 343 + 344 +AT+CACERT=123456} 345 + 346 +AT+CLICERT=123456} 347 + 348 +AT+CLIKEY=123456} 349 + 350 +2. Upload Valid Certificates (Optional): 351 + 352 +After overwriting, users may proceed to upload new valid certificates if needed. 353 + 354 + 337 337 == 4.2 For -CB /-CS model == 338 338 339 339 === 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===