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 44.1
edited by Mengting Qiu
on 2025/03/06 13:42
Change comment: Uploaded new attachment "image-20250306134213-1.png", version {1}

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
... ... @@ -322,11 +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 For certificate coverage of the -NB/-NS model ====
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 -
329 -
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 ===
... ... @@ -342,6 +342,8 @@
342 342  
343 343  Methods to Update Firmware:
344 344  
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 +
345 345  * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
346 346  
347 347  === 4.2.2 Configure certificate ===
... ... @@ -407,7 +407,7 @@
407 407  
408 408  After successful execution, as shown in the following figure.
409 409  
410 -[[image:image-20250306134213-1.png]]
407 +[[image:image-20240528174502-15.png]]
411 411  
412 412  Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
413 413  
... ... @@ -530,15 +530,9 @@
530 530  Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
531 531  
532 532  
533 -==== 4.2.2.4 Re-upgrade the firmware ====
530 +==== 4.2.2.4 For -CB /-CS model Certificate setting error/change certificate ====
534 534  
535 535  
536 -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]].
537 -
538 -
539 -==== 4.2.2.5 For -CB /-CS model Certificate setting error/change certificate ====
540 -
541 -
542 542  (% data-sider-select-id="7c5a8abc-e707-467b-ac02-db0a89098320" %)When you set the wrong certificate or you need to re-set another certificate.
543 543  Please use the following three commands:
544 544