Physical service visits do not scale
When a firmware change requires a technician, cable and laptop at every site, even a small release can become a scheduling and travel task.
Industrial IoT Solution ·
Cellular OTA Updates
OTA Updates for Deployed ESP32 Fleets Over Cellular
Update firmware on remote ESP32 controllers over cellular networks without relying on site Wi-Fi. Use HTTPS firmware delivery, version checks and controlled release workflows for industrial devices deployed in remote locations.
ESP32 / ESP32-S3
4G LTE
EC25
SIM7500
HTTPS OTA
Version Control
Cellular OTA Flow
Firmware host
HTTPS
Cellular link
EC25 / SIM7500
01 · Check VersionHTTPS
Sourceversion.txt
ActionCompare
02 · DownloadCellular
FileFirmware .bin
TransportHTTPS
03 · Apply UpdateESP32
TargetOTA partition
ActionFinalize update
04 · RestartUpdated
BootNew firmware
StatusReport version
Version check → download → install → restart
Why Fleet OTA Matters
A field firmware update becomes an operations problem when devices are distributed
A USB upload is simple on a workbench. It is not simple when controllers sit in pump stations, OEM machines, energy sites, water assets or customer facilities. Cellular OTA turns firmware delivery into a networked process, but commercial deployments also need recovery logic, release control and confirmation that each device returned to normal operation.
Cellular links are variable
Signal strength, carrier behavior and intermittent connectivity mean the updater must tolerate interrupted transfers and delayed check-ins.
Fleet version drift creates uncertainty
Without remote version reporting, it becomes difficult to know which sites received a fix, which are queued and which need intervention.
Transport security is only one layer
HTTPS protects the transfer path, but production designs should also consider trusted firmware, release authorization and downgrade protection.
A bad image needs a recovery path
A successful download is not the same as a successful release. The device should verify the new application and recover if critical checks fail.
Commercial rollouts need visibility
Release status, retry state, firmware version and post-boot health should be observable remotely instead of only through a local serial monitor.
Cellular OTA Architecture
Treat OTA as a release pipeline, not only a firmware download
A cellular OTA workflow checks a remote version, downloads the firmware binary over HTTPS, writes the update and restarts the controller. For deployed fleets, add release control, device health checks, retry handling and a recovery path.
Recommended field release path
Build → publish → select → update → verify
01 / BUILD
Create the release
Build the ESP32 application and assign an explicit firmware version or release channel.
02 / HOST
Publish metadata + binary
Host the version information and firmware image on a reachable HTTPS endpoint.
03 / CELLULAR
Device checks in
The ESP32 reaches the update service through the cellular modem and compares versions.
04 / APPLY
Download + install
The device receives the image, writes the OTA application slot and prepares the new version for boot.
05 / VERIFY
Confirm device health
Run application checks, report the new version and keep a recovery path if validation fails.
Fleet OTA controls
Define how releases are published, which devices receive each version, how update status is reported and how the controller recovers when an update cannot be completed successfully.
Release channels or device cohorts
Post-boot health confirmation
Rollback and retry strategy
Remote version and update status telemetry
Firmware authenticity and anti-rollback policy
Operational Benefits
What cellular OTA can improve in the field
Remote firmware delivery reduces the operational effort required to keep distributed controllers current and gives engineering teams better control over software releases in the field.
Fewer firmware-only site visits
Apply software fixes and feature releases remotely when physical inspection or wiring work is not required.
Shorter patch deployment cycles
Move from scheduling technicians to scheduling releases, with the option to update distributed sites in controlled groups.
Better version consistency
Report device firmware remotely so operations can see which assets are current, queued or unable to update.
Safer change control
Use firmware signing, controlled release approval and recovery policies to reduce the risk of untrusted or unsuitable firmware.
More visible release health
Replace local serial observation with remote status events, update errors and post-reboot application confirmation.
Predictable cellular data use
Control when large binaries download, avoid unnecessary checks and plan releases around modem and data-plan constraints.
NORVI OTA Guides
Start from a working cellular OTA reference
NORVI provides cellular OTA implementation guides for Quectel EC25 and SIMCom SIM7500. Both examples check a remote version on GitHub, download the firmware over HTTPS and apply the update on the ESP32.
Quectel
EC25
NORVI GuideOTA Updates on ESP32 with EC25
The reference checks a remote firmware version, downloads the binary over HTTPS through the Quectel EC25 and applies the update using the ESP32 update process.
- ESP32 + Quectel EC25 cellular path
- HTTPS firmware delivery from GitHub
- Version comparison and automatic reboot
- CA certificate setup and basic troubleshooting
SIMCom
SIM7500
NORVI GuideOTA Updates on ESP32 with SIM7500
The SIM7500 guide follows the same release pattern over cellular using TinyGSM, ArduinoHttpClient, SSLClient and the ESP32 Update library.
- ESP32 + SIMCom SIM7500 cellular path
- TinyGSM and HTTPS client workflow
- Version check, binary download and reboot
- Error handling guidance for cellular and HTTPS failures
NORVI Hardware Fit
Choose the cellular controller for the required I/O and connectivity
NORVI GSM provides fixed-I/O ESP32 cellular controllers, while NORVI X3 provides an ESP32-S3 modular controller with Quectel EC25 LTE Cat 4 connectivity.
NORVI GSM
ESP32-WROOM32 industrial controller family with 2G and 4G LTE models, built-in RS-485 and fixed I/O options including relay, transistor, 0-10V and 4-20mA. LTE models are documented with Quectel EC25 or SIMCom SIM7500 modem options depending on the controller variant.
NORVI X3
Modular industrial controller based on the ESP32-S3-WROOM-1U-N16R2 with 16 MB flash and 2 MB PSRAM. NORVI X3 includes Quectel EC25 LTE Cat 4, Ethernet, RS-485, Wi-Fi, Bluetooth and support for NORVI X expansion modules.
For applications requiring independent remote firmware management, explore the NORVI XN industrial ESP32 controller, featuring a dedicated OTA Manager for cellular connectivity, firmware updates, and remote diagnostics.
FAQs
Common Questions
Can't find what you're looking for? Our team is available for a free technical consultation.
Can an ESP32 receive OTA firmware updates over 4G LTE?
Yes. The ESP32 updater can receive firmware through an internet
connection provided by a cellular modem. NORVI publishes cellular
OTA examples for both Quectel EC25 and SIMCom SIM7500 modems.
Does cellular OTA remove the need for Wi-Fi at the site?
Yes. The firmware can be downloaded through the cellular modem as
long as the controller has an active data connection and can reach
the update server.
Is HTTPS enough to make ESP32 OTA secure?
HTTPS protects the connection to the update server when certificate
validation is configured correctly. For production designs, ESP-IDF
also provides security features such as signed application
verification, Secure Boot and OTA rollback controls.
What happens if cellular connectivity drops during an update?
If the update cannot complete, the controller can remain on the
current firmware and retry later. A robust deployment should use
appropriate OTA partitions, retry handling and rollback or recovery
logic for interrupted or faulty updates.
Can one firmware release be deployed across multiple ESP32 devices?
Yes. A fleet OTA workflow can make the same approved firmware
version available to multiple compatible devices. For larger
deployments, releases can be staged by device group before wider
rollout.
Which NORVI hardware is suitable for ESP32 cellular OTA projects?
NORVI GSM LTE variants use ESP32-WROOM32 with Quectel EC25 or SIMCom
SIM7500 modem options depending on the model. NORVI X3 uses
ESP32-S3-WROOM-1U-N16R2 with Quectel EC25 LTE Cat 4, Ethernet,
RS-485 and modular expansion I/O.
Can NORVI help build the fleet update workflow, not only the device code?
NORVI offers custom IoT product development covering hardware,
firmware, communications integration and production support. A fleet
OTA project can be scoped around the device firmware, release
method, connectivity, telemetry and validation requirements.
View IoT Product Development.
NORVI IoT Product Development
Need OTA engineered into a product that is already going into the field?
NORVI can support device-side OTA firmware, cellular modem integration, remote update-state reporting and deployment validation for ESP32 and ESP32-S3 industrial products.
ESP32 and ESP32-S3 firmware development
4G LTE modem integration and field validation
Remote telemetry and update-state reporting
Rollback, recovery and production validation
