User's Manual

Page 35 of 36
May 16, 2019
Data Sheet and User Manual
AES-MS-MT3620-M-G Module
Data Sheet and User Manual
Appendix-A: Programming Adaptor Footprint
A key aspect of the operation of the MT3620 device are the Over-the-Air (OTA) updates of the Azure Sphere
OS firmware and the application software. There are however specific use cases where wired device
interfaces are needed (see table below). It is therefore recommended that a 10-pin connector footprint be
added to the OEM host board to interface with the module signals tabled below:
#
Use Case
MT3620 Interface
1
Wi-Fi network settings are missing
or incorrectly configured
SERVICE UART
(4 pins)
2
A7 DEBUG UART access is
required
DEBUG UART
(2 of 4 pins)
3
M4 IO0 and IO1 TXD output are
needed (eg. for debug of M4 code)
M4F IO0 and IO1 TXD pins
(2 pins)
Notes:
1) There is currently a need to facilitate the configuration of the Wi-Fi network settings via the
SERVICE UART interface (the need for this will be reduced when Microsoft at later date adds
support for configuration of Wi-Fi settings via Wi-Fi A/P mode)
2) Once Wi-Fi has been configured, the Sphere OS can be “recovered” to latest version OTA via Wi-Fi
3) Access to the DEBUG UART output (of the A7 core) provides valued log-file status information that
can prove useful during software development debugging.
4) Access to the M4 TXD outputs can likewise provide status information to the software developer
To support these interfaces, an FTDI-based USB to serial adaptor is to be available for purchase from
Avnet, with 2x5 pin header connectors to support two different footprint options on the OEM host board:
a) “Tag-Connect” connector-less footprint (2x5 pads, 1.27mm pitch)
http://www.tag-connect.com/TC2050-IDC or
b) Dual-row header pins (2x5 pins, 1.27mm pitch)