User's Manual

Page 9 of 36
May 16, 2019
Data Sheet and User Manual
AES-MS-MT3620-M-G Module
Data Sheet and User Manual
Module Integration onto an OEM Board
Module Power Interfaces
To power this module, the OEM board must be able to supply a maximum of 2.5 Watts at 3.3V.
Prior to power-up of the module, the following interfaces need to be attended to:
Interface Pins
Description
Notes
3V3
Main input voltage to the module.
3.3V (+/- 10%)
Powered by an external PMU
or DC/DC convertor
3V3_RTC
Real Time Clock power input to module
Powered by external battery,
or connect this to the 3V3 rail
VREF_ADC
Reference voltage for on-chip A/D
convertor
Powered by external reference
voltage, or connect to the
MT3620 2.5V LDO output
EXT_PMU_EN
MT3630 output to enable / disable
external PMU or DC/DC convertor
May be left unconnected
PMU_EN
MT3630 input to enable / disable the
internal PMU
May be left unconnected
WAKEUP
MT3630 input to wake-up the A7
processor from power-saving sleep mode
May be left unconnected
Wi-Fi Network Settings
For Wi-Fi connected user applications, the module’s Wi-Fi network settings need to be configured by one of
the following methods:
a) In the application software (using #define statements), OEM factory-programmed into the module
b) Via a companion nRF52840 BLE device integrated onto the OEM’s end-product board
c) Via the SERVICE UART interface with a Windows-10 development computer running the
azsphere command-line utility (See Appendix-A detail of the suggested PCB footprint to support
temporary attachment of an FTDI FT4232HQ based USB to serial adaptor)
Upon power-up and connection to the designated Wi-Fi network, the module will communicate with the
Microsoft Azure Sphere Security Service, which authenticates and manages one or more of the following
downloads/uploads with the module:
 Push of Azure Sphere OS firmware updates to the module
 Deployment of custom application software to the module
 Reporting of Sphere OS and application versions plus error information to the Azure Sphere Server
The Microsoft Azure Sphere Security Service will also authenticate data transfers between the custom user
application executing on the module and Microsoft Azure (or other) cloud services