Skip to Content
Last modified by Mengting Qiu on 2025/07/29 15:24
From version 49.16
edited by Mengting Qiu
on 2025/07/29 14:25
Change comment: There is no comment for this version
To version 46.1
edited by Mengting Qiu
on 2025/05/20 15:51
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
... ... @@ -322,41 +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 -
333 -To effectively "clear" existing certificates, users may overwrite them with arbitrary data by following these steps:
334 -
335 -**Scenario A:** Clearing Existing Certificates
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).
340 -Example:
341 -
342 -AT+CACERT=123456}
343 -
344 -AT+CLICERT=123456}
345 -
346 -AT+CLIKEY=123456}
347 -
348 -
349 -**Scenario B:** Testing Certificate Upload Functionality
350 -
351 -If users want to test whether certificate writing works (without having valid certificates yet):
352 -
353 -~1. Follow the same steps as above.
354 -
355 -2. Check for success responses after each command:
356 -
357 -
358 -3. Later, when you have real certificates, overwrite the dummy data with actual certificates.
359 -
360 360  == 4.2  For -CB /-CS model ==
361 361  
362 362  === 4.2.1 Upgrade the firmware to configure TLS firmware to set the certificate ===
... ... @@ -372,6 +372,8 @@
372 372  
373 373  Methods to Update Firmware:
374 374  
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 +
375 375  * Update through UART TTL interface : **[[Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART_Access_for_NB_ST_BC660K-GL/#H4.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]]**.
376 376  
377 377  === 4.2.2 Configure certificate ===