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 52.4
edited by Mengting Qiu
on 2025/07/29 15:23
on 2025/07/29 15:23
Change comment:
There is no comment for this version
To version 49.8
edited by Mengting Qiu
on 2025/07/29 14:13
on 2025/07/29 14:13
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -322,21 +322,18 @@ 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 C learCertificatesby Overwriting(For -NB/-NS Modules)====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, users may overwrite them with dummy data. 330 +To effectively remove existing certificates or test certificate upload functionality, users may overwrite them with dummy data. 331 331 332 - 333 333 To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps: 334 334 335 - **Scenario A:** Clearing ExistingCertificates334 +1. Overwrite Certificates: 336 336 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 +Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456). 340 340 Example: 341 341 342 342 AT+CACERT=123456} ... ... @@ -345,15 +345,11 @@ 345 345 346 346 AT+CLIKEY=123456} 347 347 345 +2. Upload Valid Certificates (Optional): 348 348 347 +After overwriting, users may proceed to upload new valid certificates if needed. 349 349 350 -2. Check for success responses after each command:[[image:1753772253801-330.png||height="495" width="620"]] 351 351 352 -* If you get "Failure", retry or check module connectivity. 353 - 354 -3. Later, when you have real certificates, overwrite the dummy data with actual certificates. 355 - 356 - 357 357 == 4.2 For -CB /-CS model == 358 358 359 359 === 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===
- 1753772253801-330.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -88.7 KB - Content