Multitech MultiConnect xDot MTXDOT-NA1 Series Developer's Manual page 14

FOTA
Chapter 3 – FOTA
External Flash Components for FOTA
AT firmware on the xDot supports FOTA when a compatible external flash component or block device is connected
to the xDot. In this configuration, multicast and fragmentation sessions are managed by the xDot. Messages for
multicast (port 200) and fragmentation (port 201) are handled by the xDot and are not passed through to the AT
terminal.
File space is statically allocated. There is no traditional file system. The xDot will reserve space for new application
firmware, a backup of the current application, and an upgrade result file. A total of 436 KB (0x6A000 bytes) of free
space is required.
External Flash Component Requirements
For a flash component or block device to work with the xDot, it must meet the following criteria:
Work with MBed OS DataFlashBlockDevice or SPIFBlockDevice classes
Maximum 4 KB sector erase size
Maximum 512 byte page size
SPIF type components must support Serial Flash Discoverable Parameters (SFDP)
External Flash Components Tested for Compatibility
Part Number
MX25R8035
AT45DB041E
Host MCU
When no external flash component is present, fragmentation messages (port 201) must be handled by a host MCU
implementing the Fragmented Data Block
FOTA (FUOTA) Overview
This requires xDot firmware Version 4.0 or higher and a Conduit
Firmware Over the Air (FOTA) also known as Firmware Upgrade Over the Air (FUOTA) is a way to upgrade Dot end
devices using multicast and file fragmentation packages defined in the LoRaWAN specification. FOTA allows the
14
Type Manufacturer
SPIF Macronix
DATAFLASH Adesto
Transport.
Density Page Size
8 MB 512 bytes
4 MB 256 bytes
®
with AEP (mPower) 5.2 or higher.
Erase Size
4 KB
2 KB
®
xDot Developer Guide