Skip to Content
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.8
edited by Mengting Qiu
on 2025/07/29 14:13
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,31 +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 -1. Overwrite Certificates:
335 -
336 -Use the standard AT commands (AT+CACERT, AT+CLICERT, AT+CLIKEY) to write non-certificate data (e.g., random strings like 123456).
337 -Example:
338 -
339 -AT+CACERT=123456}
340 -
341 -AT+CLICERT=123456}
342 -
343 -AT+CLIKEY=123456}
344 -
345 -2. Upload Valid Certificates (Optional):
346 -
347 -After overwriting, users may proceed to upload new valid certificates if needed.
348 -
349 -
350 350  == 4.2  For -CB /-CS model ==
351 351  
352 352  === 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===
... ... @@ -362,6 +362,8 @@
362 362  
363 363  Methods to Update Firmware:
364 364  
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 +
365 365  * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
366 366  
367 367  === 4.2.2 Configure certificate ===
... ... @@ -427,7 +427,7 @@
427 427  
428 428  After successful execution, as shown in the following figure.
429 429  
430 -[[image:image-20250306134213-1.png]]
407 +[[image:image-20240528174502-15.png]]
431 431  
432 432  Display (% style="color:blue" %)**"Successfully configured CA certificate."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
433 433  
... ... @@ -550,15 +550,9 @@
550 550  Display(% style="color:blue" %)** "Successfully configured client private key."**(%%) If the configuration is successful, otherwise it is considered configuration failure.
551 551  
552 552  
553 -==== 4.2.2.4 Re-upgrade the firmware ====
530 +==== 4.2.2.4 For -CB /-CS model Certificate setting error/change certificate ====
554 554  
555 555  
556 -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]].
557 -
558 -
559 -==== 4.2.2.5 For -CB /-CS model Certificate setting error/change certificate ====
560 -
561 -
562 562  (% data-sider-select-id="7c5a8abc-e707-467b-ac02-db0a89098320" %)When you set the wrong certificate or you need to re-set another certificate.
563 563  Please use the following three commands：
564 564