Over-the-Air Updates

Vital to an array of Internet of Things (IoT) and other connected applications, Over-the-Air (OTA) updates enable product manufacturers to send new information—like an updated weather forecast—or perform system software updates to their devices via a wireless radio transmission.

Our wireless products can be used to implement OTA updates, which are also known as Device Firmware Updates (DFUs), to install new system software for the following use cases:

• Firmware updates:
  • To support new features that were not previously implemented
  • To fix bugs present in earlier versions
  • To protect against security threats like the Wi-Fi^® Protected Access II (WPA2) vulnerability
• Certificate provisioning for granting access to new cloud services
• Certificate updates when keys are changed
• Device tuning

Based on our standalone Wi-Fi MCU and Wi-Fi network controller, these four examples show you how to use the OTA application to update the firmware and security content of a Wi-Fi MCU, a Wi-Fi network controller and a general host MCU.

Having enough memory space available is a key requirement for performing OTA updates. However, because memory adds costs, most systems offer limited memory space. If you would like to enable your application to perform OTA updates, you will need to plan on generally providing memory that offers storage for more than twice the size of the code to be updated. The bootloader or application that will be managing the OTA update will also need adequate memory space.

New code for the OTA update should be filed locally when downloaded. This enables the download to be checked for authenticity and integrity before the actual update is performed. If the download is interrupted or corrupted, the downloaded file should not be used. Only after the download is checked, the bootloader or the application that is managing the OTA update will be able to update the previous software using one of these two methods:

• Erasing and overwriting the code with the new version, which is a good option for a certificate update
• Placing the new image on a new partition and updating the bootloader to point to the new partition, which is a safer option for code updates
  

The local memory can be placed in various locations in the system. You might choose to use the host controller’s memory, the wireless network controller’s memory or external Flash or other memory.  However, to guarantee higher reliability, using a dual-partition memory on the target itself allows the old and new software versions to coexist in parallel. Instead of overwriting the old version with the new version, this will allow the system to simply update a pointer onto the new code after it is checked for authenticity and integrity.  It also makes it easy to roll back to the previous version of the software as a failsafe in case of issues with the new version.