Skip to Content
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.9
edited by Mengting Qiu
on 2025/07/29 14:15
Change comment: There is no comment for this version
To version 38.1
edited by Mengting Qiu
on 2025/03/06 11:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Dragino -NB/-CB device connection to AWS platform instructions
1 +Dragino NB device connection to AWS platform instructions
Content
... ... @@ -193,7 +193,7 @@
193 193  
194 194  After successful execution, as shown in the following figure.
195 195  
196 -[[image:image-20250306113849-2.png||height="742" width="456"]]
196 +[[image:image-20240528174502-15.png]]
197 197  
198 198  Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
199 199  
... ... @@ -322,36 +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 -**Scenario A:** Clearing Existing Certificates
335 -
336 -If users want to remove old certificates:
337 -
338 -
339 -
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 -
355 355  == 4.2  For -CB /-CS model ==
356 356  
357 357  === 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===
... ... @@ -367,6 +367,8 @@
367 367  
368 368  Methods to Update Firmware:
369 369  
340 +* (Recommended way) OTA firmware update via BLE: [[**Instruction**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE_Firmware_Update_NB_Sensors_BC660K-GL/]].
341 +
370 370  * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
371 371  
372 372  === 4.2.2 Configure certificate ===
... ... @@ -374,7 +374,7 @@
374 374  
375 375  After upgrade the firmware, the serial port displays as follows：
376 376  
377 -[[image:image-20250306114107-2.png||height="371" width="744"]]
349 +[[image:image-20240528174330-13.png||height="286" width="568"]]
378 378  
379 379  
380 380  ==== 4.2.2.1 Configure CA certificate ====
... ... @@ -432,7 +432,7 @@
432 432  
433 433  After successful execution, as shown in the following figure.
434 434  
435 -[[image:image-20250306134213-1.png]]
407 +[[image:image-20240528174502-15.png]]
436 436  
437 437  Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
438 438  
... ... @@ -555,15 +555,9 @@
555 555  Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
556 556  
557 557  
558 -==== 4.2.2.4 Re-upgrade the firmware ====
530 +==== 4.2.2.4 For -CB /-CS model Certificate setting error/change certificate ====
559 559  
560 560  
561 -After completing the certificate configuration, Burn the [[bootloader>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AE23WqlQ8CKU4cuy-sP1JkM/Utility/NB-IoT%20Bootloader?rlkey=ojjcsw927eaow01dgooldq3nu&e=1&subfolder_nav_tracking=1&dl=0]] firmware first, then re-burn the original working [[firmware>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/ANd2flSqspRRXl-ksF6gUqk/LTE-M?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]].
562 -
563 -
564 -==== 4.2.2.5 For -CB /-CS model Certificate setting error/change certificate ====
565 -
566 -
567 567  (% data-sider-select-id="7c5a8abc-e707-467b-ac02-db0a89098320" %)When you set the wrong certificate or you need to re-set another certificate.
568 568  Please use the following three commands：
569 569  
... ... @@ -651,3 +651,4 @@
651 651  [[image:image-20240528175133-19.png||height="563" width="1022"]]
652 652  
653 653  [[image:image-20240528175154-20.png||height="752" width="1042"]]
620 +
image-20250306113801-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -65.1 KB
Content
image-20250306113849-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -65.9 KB
Content
image-20250306114107-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -33.7 KB
Content
image-20250306134213-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -67.1 KB
Content