Skip to Content
Last modified by Mengting Qiu on 2025/06/17 09:18
From version 57.1
edited by Edwin Chen
on 2025/02/12 14:59
Change comment: There is no comment for this version
To version 39.1
edited by Mengting Qiu
on 2025/01/21 09:38
Change comment: Uploaded new attachment "image-20250121093834-4.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.ting
Content
... ... @@ -64,19 +64,16 @@
64 64  == 3.1 Required Components ==
65 65  
66 66  
67 -* See FAQ 4.4 for how to update LA66 with the [[OTA Dongle Firmware>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/AFhmjtEOaipfBAFrpMCoWrI/LoRaWAN%20End%20Node/LA66%20LoRaWAN%20module/Firmware/OTA_Firmware?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]].
67 +* Hardware: [[LA66 USB>>doc:Main.User Manual for LoRaWAN End Nodes.LA66 USB LoRaWAN Adapter User Manual.WebHome]] with [[OTA_firmware>>https://www.dropbox.com/sh/4qnjreg1esxu16i/AADbRjW_tuBP3IIkmf11nSoma?dl=0]] installed.
68 +
68 68  * Software: [[OTA_Tool>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&dl=0]]. Only support Windows now
69 69  
70 70  [[image:image-20230513120722-2.png||height="409" width="866"]]
71 71  
72 72  
73 -== 3.2 OTA Update Firmware via Mobile Phone + LA66 ==
74 +== 3.2 OTA Update Firmware ==
74 74  
75 75  
76 -
77 -== 3.3 OTA Update Firmware via PC ==
78 -
79 -
80 80  (% class="wikigeneratedid" %)
81 81  (% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Firmware (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/SSvOqvBrwGg>>https://youtu.be/SSvOqvBrwGg]]**
82 82  
... ... @@ -84,7 +84,7 @@
84 84  === (% style="color:blue" %)**Step1:**(%%) Plug LA66 USB to PC and run OTA_Tool. ===
85 85  
86 86  
87 -[[image:image-20250121091115-1.png]]
84 +[[image:image-20231212171036-1.png]]
88 88  
89 89  
90 90  === (% style="color:blue" %)**Step2:**(%%) Set up OTA Tool ===
... ... @@ -92,7 +92,7 @@
92 92  
93 93  * (% style="color:blue" %)**DevEUI**(%%): Input DevEUI of your sensor
94 94  
95 -* (% style="color:blue" %)**Password**(%%): Passord of your sensor**(Last eight bytes/** **Last 16 characters of APPSKEY)**
92 +* (% style="color:blue" %)**Password**(%%): Passord of your sensor**(Last eight bytes of APPSKEY)**
96 96  
97 97  * (% style="color:blue" %)**Port**(%%): Com port of LA66 USB
98 98  
... ... @@ -100,23 +100,20 @@
100 100  
101 101  * (% style="color:blue" %)**Upload_File**(%%): The firmware to be upload to the sensor. make sure the firmware is with surfix _without_bootloader. For example: LHT65N_EU868_v1.5_without_bootloader.
102 102  
103 -* (% style="color:blue" %)**DEUI_File**(%%): If customer has lots of sensors. He can also import the Dev EUI files and use droplist to choose the sensor to update. (If you did not ask us for a uniform update file, then you do not need to use this field, please ignore it.) Format is as below:
100 +* (% style="color:blue" %)**DEUI_File**(%%): If customer has lots of sensors. He can also import the Dev EUI files and use droplist to choose the sensor to update. Format is as below:
104 104  
105 105  [[image:image-20230114174640-3.png||height="130" width="1169"]]
106 106  
107 107  
108 -=== (% style="color:blue" %)**Step3:**(%%) After re-plugging the LA66 USB, click "Start" in the OTA tool. ===
105 +=== (% style="color:blue" %)**Step3:**(%%) Press Start in OTA Tool and then Press Reset button to restart LA66 USB ===
109 109  
110 110  
111 -Upon re-plugging, the LA66 USB will reboot and broadcast the update process using the Dev EUI and passcode
108 +After press reset button, LA66 USB will restart and broadcast update process with the Dev EUI and Password.
112 112  
113 113  
114 114  === (% style="color:blue" %)**Step4:** (%%)Press reset button on the end node, or re-activate the end node. ===
115 115  
116 -When the OTA Tool displays “**LA66 is scanning for sensor Dev EUI ‘(% style="color:blue" %)DevEUI(%%)’. Please reset the sensor for connection and update**”, press and hold the ACT button on the terminal node for 5 seconds to perform a terminal node reset so that the OTA Tool can connect successfully.
117 117  
118 -[[image:image-20250121093705-3.png]]
119 -
120 120  In every reboot/ reactivate, the end node will check if there is update request. If end node gets the update request from LA66. End node will check if the Dev EUI and Password match. If match, End node will establish connection with LA66 USB for OTA update.
121 121  
122 122  
... ... @@ -125,29 +125,34 @@
125 125  
126 126  Below shows the update successul result.
127 127  
128 -[[image:image-20250121093834-4.png]]
122 +[[image:image-20231212171543-2.png||height="575" width="753"]]
129 129  
130 130  
131 -= 4. FAQ =
125 +== 3.3 OTA Update Configure ==
132 132  
133 -== 4.1 OTA_Tool supports two upgrade methods for -LB products. ==
134 134  
128 +(% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Configure (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/5XedoNVkbQQ>>https://youtu.be/5XedoNVkbQQ]]**
135 135  
136 -(% style="color:red" %)**Note: The premise of using OTA_Tool is that all your devices have bootloaders.**
130 +OTA Update Configure is good for batch update configure in same type of sensors.
137 137  
138 -(% style="color:red" %)**1. **(%%)Only devices with bootloader can perform OTA upgrades(OTA upgrade method).
139 139  
140 -(% style="color:red" %)**2.**(%%) This is because the boot loader's address is (% style="color:blue" %)**0x08000000**(%%), the general functional firmware's address is (% style="color:blue" %)**0x0800D000**(%%), and burning the firmware through OTA_Tool will only write content to the address (% style="color:blue" %)**0x0800D000**(%%). So whether you use the OTA_Tool's OTA upgrade method or the UART upgrade method, you can only use it to download firmware without a bootloader, otherwise you will incorrectly place the bootloader at address (% style="color:blue" %)**0x08000000**(%%).
133 += 4. FAQ =
141 141  
142 -* For OTA_Tool, you can choose to use the (% style="color:blue" %)**OTA upgrade method**(%%), refer to the above upgrade steps in this user manual.
135 +== 4.1 Can i use other devices to connect to PC if i don't have LA66 USB? ==
143 143  
144 -[[image:image-20250122104151-4.png||height="318" width="673"]]
145 145  
146 -* Of course, if you have a USB-TTL adapter, you can also choose to use the [[UART upgrade method>>https://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H3.2UpdateFirmware28Assumethedevicealreadyhaveabootloader29]] via OTA_Tool.
138 +If user doesn't have LA66 USB Adapter, they can still use other Dragino Device to connect to PC for OTA update.
147 147  
148 -[[image:image-20250122104131-3.png||height="330" width="674"]]
140 +(% style="color:blue" %)**Steps:**
149 149  
142 +* Find the suitable mode which base on LA66 chip ( All LoRaWAN model with LB or LS suffix , such as SN50v3-LB)
150 150  
144 +* Update the LA66 USB OTA firmware to the device.
145 +
146 +* Connect the device to PC via UART interface.
147 +
148 +* Make sure power off or update the firmware back to original firmware , because the LA66 USB OTA fimware is not low power consumption firmware. it will consume the battery very fast.
149 +
151 151  == 4.2 Where to find OTA Password? ==
152 152  
153 153  
... ... @@ -168,26 +168,8 @@
168 168  2. OTA update require a reset or reactivate action. If the crash firmware doesn't have them work, user need to manuall push the physic reset button on the PCB or power off/on device.
169 169  
170 170  
171 -== 4.4 How to update the LA66 OTA Dongle V1.1 via mobile phone? ==
170 +== 4.4 Will OTA update effect the Local LoRaWAN Network. ==
172 172  
173 -
174 -[[image:image-20250122113225-5.png||height="259" width="615"]]
175 -
176 -* If you have never downloaded LA66 OTA DongleV1.0 to your LA66, you can directly upgrade the LA66 OTA DongleV1.1 program from your phone using the following method.
177 -
178 -[[bootlooder>>url:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/LoRa_OTA_Bootloader_v1.4.bin?rev=1.1]] and [[OTA_firmware>>url:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/LA66%20OTA%20DONGLE%20v1.1.bin?rev=1.1]].
179 -
180 -Tool Download: [[Download link form Dropbox.>>https://www.dropbox.com/scl/fo/gyscmfn1s03oz3n8rif8w/AJW7JoMQsQ56dtlls2SNf9c?rlkey=3q2cxwriyzh26vuairx01yebc&st=be5jv92w&dl=0]] 
181 -
182 -Operation instructions: [[Reference for operating procedures.>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1.3.3LA66upgrade]]
183 -
184 -* If you have burned LA66 OTA DONGLE V1.0 for your LA66 according to previously existing instructions. Then you need to re-burn your LA66 boot loader first: [[LA66 USB LoRaWAN Adapter User Manual - DRAGINO>>url:https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LA66%20USB%20LoRaWAN%20Adapter%20User%20Manual/#H1.10.2Updatemethod:A0ForLA66withoutbootloader]]
185 -
186 - Please refer to FAQ 4.7 for detailed reasons.
187 -
188 -
189 -== 4.5 Will OTA update effect the Local LoRaWAN Network. ==
190 -
191 191  User can configure the OTA_Frequency.txt file to change the Update frequency point so it won't conflict with the general LoRa Frequency. See below for the file as reference and explain. The OTA update also use a none-use SF (SF=5) which won't conflict with the current use SF.
192 192  
193 193  (% class="mark" %)#Define the OTA frequency use for OTA.
... ... @@ -213,31 +213,6 @@
213 213  RU864;869.3;869.5,869.7
214 214  
215 215  
216 -== 4.6 The old version LA66 is different from the new version LA66. Can OTA_Tool be used for both versions? ==
217 -
218 -
219 -The most obvious hardware difference between LA66 V1 and LA66v2 when burning is the presence of a "RESET "button, and the RESET operation is only for LA66 without a boot loader, you can refer to this link to learn how to upgrade LA66 without a boot loader：[[LA66 USB LoRaWAN Adapter User Manual - DRAGINO>>url:https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LA66%20USB%20LoRaWAN%20Adapter%20User%20Manual/#H1.10.2Updatemethod:A0ForLA66withoutbootloader]]
220 -
221 -[[image:image-20250122134752-6.png||height="288" width="543"]]
222 -
223 -In summary, as long as your LA66 has a boot loader, either LA66 V1 or LA66 V2 can use OTA_Tool.
224 -
225 -
226 -== 4.7 Why can't LA66 burn its own working firmware after it is used for OTA upgrade of -LB products? ==
227 -
228 -
229 -We are sorry for the inadequacy of LA66 for OTA updates in the past.
230 -
231 -* In the past, the download address of LA66 OTA DONGLE V1.0 was (% style="color:blue" %)**0x08000000**(%%), and the address of the bootloader that existed by default when the LA66 was shipped was also (% style="color:blue" %)**0x08000000**(%%).
232 -
233 -Therefore, when you burn OTA_Firmwar v1.0 (LA66 OTA DONGLE v1.0) for the LA66 in order to use the LA66‘s ability to perform OTA upgrades for -LB products, the LA66’s bootloader is overridden.
234 -
235 -So if you need to switch back to the LA66's working firmware, you'll need to refer to this [[link>>https://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LA66%20USB%20LoRaWAN%20Adapter%20User%20Manual/#H1.10.2Updatemethod:A0ForLA66withoutbootloader]] for instructions to burn firmware with a bootloader for the LA66.
236 -
237 -[[image:image-20250122113225-5.png||height="336" width="798"]]
238 -
239 -* For the new version of LA66 OTA DONGLE V1.1, we have changed the supported download address to (% style="color:blue" %)**0x0800D000**(%%) the same as other working firmware addresses, so you can simply use OTA_Tool to burn LA66 OTA DONGLE V1.1 and LA66 working firmware for LA66.
240 -
241 241  = 5. OTA Tool Known Bug: =
242 242  
243 243  
image-20250122101944-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -34.2 KB
Content
image-20250122103630-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -47.0 KB
Content
image-20250122104131-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -21.7 KB
Content
image-20250122104151-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -23.3 KB
Content
image-20250122113225-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -27.0 KB
Content
image-20250122134752-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -3.3 MB
Content