Skip to Content
Last modified by Mengting Qiu on 2025/06/17 09:18
From version 54.1
edited by Mengting Qiu
on 2025/01/22 14:27
Change comment: There is no comment for this version
To version 52.1
edited by Mengting Qiu
on 2025/01/22 13:48
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -129,14 +129,8 @@
129 129  == 4.1 OTA_Tool supports two upgrade methods for -LB products. ==
130 130  
131 131  
132 -(% style="color:red" %)**Note: The premise of using OTA_Tool is that all your devices have bootloaders.**
132 +* For OTA_Tool, you can choose to use the OTA upgrade method, refer to the above upgrade steps in this user manual.
133 133  
134 -(% style="color:red" %)**1. **(%%)Only devices with bootloader can perform OTA upgrades(OTA upgrade method).
135 -
136 -(% 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**(%%).
137 -
138 -* 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.
139 -
140 140  [[image:image-20250122104151-4.png||height="318" width="673"]]
141 141  
142 142  * 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.
... ... @@ -164,13 +164,8 @@
164 164  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.
165 165  
166 166  
167 -== 4.4 How to update the LA66 OTA Dongle V1.1 via mobile phone? ==
161 +== 4.4 How to update the LA66 OTA Dongle via mobile phone? ==
168 168  
169 -
170 -[[image:image-20250122113225-5.png||height="259" width="615"]]
171 -
172 -* 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.
173 -
174 174  [[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]].
175 175  
176 176  Tool Download: [[Download link form Dropbox.>>https://www.dropbox.com/scl/fo/gyscmfn1s03oz3n8rif8w/AJW7JoMQsQ56dtlls2SNf9c?rlkey=3q2cxwriyzh26vuairx01yebc&st=be5jv92w&dl=0]] 
... ... @@ -177,11 +177,8 @@
177 177  
178 178  Operation instructions: [[Reference for operating procedures.>>https://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/#H3.1.3.3LA66upgrade]]
179 179  
180 -* 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]]
181 181  
182 - Please refer to FAQ 4.7 for detailed reasons.
183 183  
184 -
185 185  == 4.5 Will OTA update effect the Local LoRaWAN Network. ==
186 186  
187 187  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.