Links

OTA compatibility‌

The Waspmote IDE v05 generates the binary file to be used in OTA programmings. There is a specific option in the Waspmote IDE that permits to generate the necessary binary file for OTA in: "Sketch" → "Export binary to OTA file". When this option is chosen, the program is compiled and two files are generated inside /sketchbook/OTA-FILES folder: a hexadecimal and a binary file. The second one is valid for OTA via FTP with 4G/3G/GPRS/WiFi modules.
STEP 1: Click "Sketch" → "Export binary to OTA file" to generate the binary file:
Figure: Waspmote IDE generates binary files ‌
STEP 2: Search the binary file in the correct folder:
Figure: OTA-FILES folder ‌
For instance, we are managing a program called _4G_20_OTA.pde. When the binary files are exported, two files are created inside the sketchbook sub-folder called OTA-FILES:
  • _4G_20_.hex is the program compiled
  • _4G_20_ is the binary file needed for OTA via 4G (always defined by seven characters)
The Waspmote IDE gives these filenames truncating to seven characters the name of the Waspmote program.
For instance, we are managing a program called OTA_06_GPRS.pde. When the program is compiled, two files are created inside the sketchbook sub-folder called OTA-FILES:
  • OTA_06_.hex is the hexadecimal file used for conventional OTA programming.
  • OTA_06_ (seven characters) is the binary file needed for OTA via 3G or GPRS.
The Waspmote IDE gives these filenames truncating to seven characters the name of the Waspmote program.
It is important to remark that the filename given by the Waspmote IDE to the binary files CAN NOT be changed. Otherwise, OTA will not work. More information about OTA programming in http://www.libelium.com/ota/