Skip to Content
Last modified by Mengting Qiu on 2025/06/17 09:18
From version 70.5
edited by Mengting Qiu
on 2025/02/14 17:25
Change comment: There is no comment for this version
To version 38.1
edited by Mengting Qiu
on 2025/01/21 09:37
Change comment: Uploaded new attachment "image-20250121093705-3.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -63,136 +63,18 @@
63 63  
64 64  == 3.1 Required Components ==
65 65  
66 -* 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]].
66 +
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 +
67 67  * Software: [[OTA_Tool>>https://www.dropbox.com/scl/fo/9kqeqf6wmet10o9hgxuwa/h?rlkey=4ikrg6kg5v0yjxwhp0i37wrv7&dl=0]]. Only support Windows now
68 68  
69 69  [[image:image-20230513120722-2.png||height="409" width="866"]]
70 70  
71 71  
72 -== 3.2 OTA Update Firmware via Mobile Phone + LA66 ==
74 +== 3.2 OTA Update Firmware ==
73 73  
74 -=== 3.2.1 LB series ===
75 75  
76 -* Upgrade of external tools: LA66 USB
77 -[[image:image-20250214161740-1.png]][[image:image-20250214161758-2.png]]
78 -* Before using LA66 as a firmware burning tool for -LB products, you need to burn OTA_firmware for LA66 first.
79 -* 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.
80 -* Click to get [[bootlooder and OTA_firmware.>>https://www.dropbox.com/scl/fo/ztlw35a9xbkomu71u31im/ALF3WtzilGPi-2nOdtQw1Z4/Utility/Sensor%20Manager%20Utility/OTA_Firmware?dl=0&rlkey=ojjcsw927eaow01dgooldq3nu&subfolder_nav_tracking=1]]
81 -* The firmware burning method refers to the LA66 upgrade below.[[Click to redirect.>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1.3.3LA66upgrade]]
82 -
83 -The LA66 USB connects to the phone via the USB-Type c adapter.
84 -
85 -[[image:image-20250214161844-3.png]]
86 -
87 -
88 -After the connection is successful, the phone will pop up a prompt box, check it and click to confirm.
89 -
90 -(% style="color:red" %)**Note:**(%%)**Some models of cell phones require the OTG function of the cell phone system to be enabled manually in order to recognize the external device correctly.**
91 -
92 -[[image:image-20250214161907-4.png]]
93 -
94 -
95 -(% class="wikigeneratedid" id="H-1" %)
96 -Then, the Device Tool will automatically jump to the main interface of the tool.
97 -
98 98  (% class="wikigeneratedid" %)
99 -In the upper left corner of the main interface of the software, click (% _mstmutation="1" style="color:blue" %)**"Upgrade Device"**(%%) and select the LB type.
100 -
101 -(% class="wikigeneratedid" %)
102 -Follow the steps in order:
103 -
104 -(% class="wikigeneratedid" %)
105 -① Enter the DUIEI,
106 -
107 -(% class="wikigeneratedid" %)
108 -② Enter the PIN (**the PIN is the last 8 bytes of APPSKEY**),
109 -
110 -(% class="wikigeneratedid" %)
111 -③ Select the LoRa frequency to match the original frequency of the node,
112 -
113 -(% class="wikigeneratedid" %)
114 -④ Choose the upgrade file,(% style="color:red" %)**(The firmware upgrade file format only supports .bin files)**
115 -
116 -(% class="wikigeneratedid" %)
117 -⑤ After pressing the device's reset button, click start.
118 -
119 -(% class="wikigeneratedid" %)
120 -(% style="color:red" %)**Note:**
121 -
122 -(% class="wikigeneratedid" %)
123 -**~1. (If you are unable to access the upgrade for an extended period of time, you can perform the device reset step again.)**
124 -
125 -(% class="wikigeneratedid" %)
126 -**2. (If the user does not want to open the case, he/she can press and hold the ACT key for 5s until the device flashes green; this action is equivalent to pressing the reset button.)**
127 -
128 -[[image:image-20250214161928-5.png]]
129 -
130 -
131 -(% class="wikigeneratedid" id="H-2" %)
132 -When the upgrade is complete, it will prompt:"**update successfully**".
133 -
134 -[[image:image-20250214161941-6.png]]
135 -
136 -
137 -==== 3.1.3.3 LA66 upgrade ====
138 -
139 -The LA66 USB connects to the phone via the USB-Type C adapter.
140 -
141 -[[image:image-20250214161955-7.png]]
142 -
143 -
144 -After the connection is successful, the phone will pop up a prompt box, check it, and click to "OK".
145 -
146 -(% style="color:red" %)**Note:**(%%)**Some mobile phone models need to manually enable the OTG function to properly identify external devices.**
147 -
148 -[[image:image-20250214162012-8.png]]
149 -
150 -
151 -(% class="wikigeneratedid" id="H-1" %)
152 -Then, the Device Tool will automatically jump to the main interface of the tool.
153 -
154 -(% class="wikigeneratedid" %)
155 -In the upper left corner of the main interface of the software, click (% _mstmutation="1" style="color:blue" %)**"Upgrade Device"**(%%) and select the "(% _mstmutation="1" style="color:blue" %)**LaA66"**(%%) type.
156 -
157 -(% class="wikigeneratedid" %)
158 -Follow the steps in order:
159 -
160 -(% class="wikigeneratedid" %)
161 -① Click "SELECT UPGRADE FILE" to choose the firmware to upgrade.
162 -
163 -(% class="wikigeneratedid" %)
164 -② Click "START".
165 -
166 -(% class="wikigeneratedid" %)
167 -③ Press the reset key on the LA66 device.
168 -
169 -(% class="wikigeneratedid" %)
170 -[[image:image-20250214162029-9.png]]
171 -
172 -(% class="wikigeneratedid" %)
173 -(% style="color:red" %)**Note:**
174 -
175 -(% class="wikigeneratedid" %)
176 -**~1. In order to ensure that the LA66 USB works properly, make sure that there is a corresponding bootloader before updating the firmware.**
177 -
178 -(% class="wikigeneratedid" %)
179 -**2. If you don't have a bootloader, you need to use the "[[Tremo Programmer>>https://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H3.1.3Howtouploadbootloadertodevice3F]]" software to download it. Click to get **[[bootlooder>>url:https://wiki.dragino.com/xwiki/bin/download/Main/BLE%20Bluetooth%20Remote%20Configure/WebHome/LoRa_OTA_Bootloader_v1.4.bin?rev=1.1]].
180 -
181 -(% class="wikigeneratedid" %)
182 -**3. For LA66 USB LoRaWAN Adapter v1.2, the design of the reset button has been eliminated on the hardware. **
183 -
184 -[[image:image-20250214162156-13.png]]
185 -
186 -
187 -When the upgrade is complete, it will prompt:"**update successfully**".
188 -
189 -[[image:image-20250214162110-12.png]]
190 -
191 -
192 -== 3.3 OTA Update Firmware via PC ==
193 -
194 -
195 -(% class="wikigeneratedid" %)
196 196  (% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Firmware (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/SSvOqvBrwGg>>https://youtu.be/SSvOqvBrwGg]]**
197 197  
198 198  
... ... @@ -199,7 +199,7 @@
199 199  === (% style="color:blue" %)**Step1:**(%%) Plug LA66 USB to PC and run OTA_Tool. ===
200 200  
201 201  
202 -[[image:image-20250121091115-1.png]]
84 +[[image:image-20231212171036-1.png]]
203 203  
204 204  
205 205  === (% style="color:blue" %)**Step2:**(%%) Set up OTA Tool ===
... ... @@ -207,7 +207,7 @@
207 207  
208 208  * (% style="color:blue" %)**DevEUI**(%%): Input DevEUI of your sensor
209 209  
210 -* (% 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)**
211 211  
212 212  * (% style="color:blue" %)**Port**(%%): Com port of LA66 USB
213 213  
... ... @@ -215,23 +215,20 @@
215 215  
216 216  * (% 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.
217 217  
218 -* (% 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:
219 219  
220 220  [[image:image-20230114174640-3.png||height="130" width="1169"]]
221 221  
222 222  
223 -=== (% 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 ===
224 224  
225 225  
226 -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.
227 227  
228 228  
229 229  === (% style="color:blue" %)**Step4:** (%%)Press reset button on the end node, or re-activate the end node. ===
230 230  
231 -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.
232 232  
233 -[[image:image-20250121093705-3.png]]
234 -
235 235  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.
236 236  
237 237  
... ... @@ -240,29 +240,34 @@
240 240  
241 241  Below shows the update successul result.
242 242  
243 -[[image:image-20250121093834-4.png]]
122 +[[image:image-20231212171543-2.png||height="575" width="753"]]
244 244  
245 245  
246 -= 4. FAQ =
125 +== 3.3 OTA Update Configure ==
247 247  
248 -== 4.1 OTA_Tool supports two upgrade methods for -LB products. ==
249 249  
128 +(% class="mark text-uppercase" %)**Video Instruction:**(%%) ~-~- OTA Upgrade Configure (via LoRa) of LoRaWAN Sensors**: [[https:~~/~~/youtu.be/5XedoNVkbQQ>>https://youtu.be/5XedoNVkbQQ]]**
250 250  
251 -(% 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.
252 252  
253 -(% style="color:red" %)**1. **(%%)Only devices with bootloader can perform OTA upgrades(OTA upgrade method).
254 254  
255 -(% 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 =
256 256  
257 -* 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? ==
258 258  
259 -[[image:image-20250122104151-4.png||height="318" width="673"]]
260 260  
261 -* 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.
262 262  
263 -[[image:image-20250122104131-3.png||height="330" width="674"]]
140 +(% style="color:blue" %)**Steps:**
264 264  
142 +* Find the suitable mode which base on LA66 chip ( All LoRaWAN model with LB or LS suffix , such as SN50v3-LB)
265 265  
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 +
266 266  == 4.2 Where to find OTA Password? ==
267 267  
268 268  
... ... @@ -283,26 +283,8 @@
283 283  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.
284 284  
285 285  
286 -== 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. ==
287 287  
288 -
289 -[[image:image-20250122113225-5.png||height="259" width="615"]]
290 -
291 -* 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.
292 -
293 -[[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]].
294 -
295 -Tool Download: [[Download link form Dropbox.>>https://www.dropbox.com/scl/fo/gyscmfn1s03oz3n8rif8w/AJW7JoMQsQ56dtlls2SNf9c?rlkey=3q2cxwriyzh26vuairx01yebc&st=be5jv92w&dl=0]] 
296 -
297 -Operation instructions: [[Reference for operating procedures.>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1.3.3LA66upgrade]]
298 -
299 -* 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]]
300 -
301 - Please refer to FAQ 4.7 for detailed reasons.
302 -
303 -
304 -== 4.5 Will OTA update effect the Local LoRaWAN Network. ==
305 -
306 306  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.
307 307  
308 308  (% class="mark" %)#Define the OTA frequency use for OTA.
... ... @@ -328,31 +328,6 @@
328 328  RU864;869.3;869.5,869.7
329 329  
330 330  
331 -== 4.6 The old version LA66 is different from the new version LA66. Can OTA_Tool be used for both versions? ==
332 -
333 -
334 -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]]
335 -
336 -[[image:image-20250122134752-6.png||height="288" width="543"]]
337 -
338 -In summary, as long as your LA66 has a boot loader, either LA66 V1 or LA66 V2 can use OTA_Tool.
339 -
340 -
341 -== 4.7 Why can't LA66 burn its own working firmware after it is used for OTA upgrade of -LB products? ==
342 -
343 -
344 -We are sorry for the inadequacy of LA66 for OTA updates in the past.
345 -
346 -* 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**(%%).
347 -
348 -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.
349 -
350 -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.
351 -
352 -[[image:image-20250122113225-5.png||height="336" width="798"]]
353 -
354 -* 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.
355 -
356 356  = 5. OTA Tool Known Bug: =
357 357  
358 358  
image-20250121093834-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -43.3 KB
Content
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
image-20250214161740-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -81.4 KB
Content
image-20250214161758-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -11.2 KB
Content
image-20250214161844-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -185.7 KB
Content
image-20250214161907-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -51.0 KB
Content
image-20250214161928-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -27.7 KB
Content
image-20250214161941-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -22.5 KB
Content
image-20250214161955-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -185.7 KB
Content
image-20250214162012-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -51.0 KB
Content
image-20250214162029-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -21.5 KB
Content
image-20250214162053-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.5 KB
Content
image-20250214162058-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.5 KB
Content
image-20250214162110-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.5 KB
Content
image-20250214162156-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -135.0 KB
Content