FCC ID: YAISB52 Wireless SOM Module

SB52 SOM Datasheet Copyright and third-party information as required Revisions History Date Document Changes Version Number 2020/04/24 0.0 Initial Draft Disclaimer SB52 SOM is supplied as is and without warranties of any kind, express implied, or statutory including, but not limited to, any implied warranty for a particular purpose. No license is granted by implication or otherwise under any patents or other intellectual property by application or use of evaluation boards. Information furnished by InnoComm is believed to be accurate and reliable. InnoComm reserves the right to change specifications or product descriptions in this document at any time without notice. Should Buyer purchase or use InnoComms products for any such unintended or unauthorized application, Buyer shall indemnify and hold InnoComm harmless against all claims and damages. InnoComm is the trademark of InnoComm Mobile Technology Corp. Other trademarks and registered trademarks mentioned herein are the property of their respective owners. Table of Contents www.innocomm.comii 1 Overview .......................................................................................................................................................... 4 1.1 ... General Information .............................................................................................................................. 4 1.2 ... Architecture and Block Diagram ........................................................................................................... 5 1.3 ... Feature Summary ................................................................................................................................... 5 1.4 ... Dimension ............................................................................................................................................... 6 1.5 ... Electrical Specifications ......................................................................................................................... 6 1.6 ... General Application Notes..................................................................................................................... 7 2 Main Hardware Components ......................................................................................................................... 8 2.1 ... CPU .......................................................................................................................................................... 9 2.2 ... Memory .................................................................................................................................................. 9 2.3 ... Power Management IC .......................................................................................................................... 9 2.4 ... eMMC Storage ..................................................................................................................................... 10 2.5 ... Wi-Fi/Bluetooth Module ...................................................................................................................... 10 3 SB52 SOM Interfaces and Connectors ......................................................................................................... 11 3.1 ... J401 Connector ..................................................................................................................................... 11 3.2 ... J402 Connector ..................................................................................................................................... 13 3.3 ... Power Signals ....................................................................................................................................... 15 3.4 ... I2Cs Parameter Specification ............................................................................................................. 16 3.5 ... UARTs .................................................................................................................................................... 16 3.6 ... DSI Interface ......................................................................................................................................... 17 3.7 ... CSI Interface ......................................................................................................................................... 18 3.8 ... Audio ..................................................................................................................................................... 19 3.9 ... USB ........................................................................................................................................................ 20 3.10 . GPIO ...................................................................................................................................................... 20 4 Reference Documents .................................................................................................................................. 20 5 How to Process SB52 .................................................................................................................................... 21 www.innocomm.comiii 1 Overview 1.1 General Information SB52 SOM is a high-performance System on Module(SOM) designed based on the i500 processor from MediaTek. The i500 device, with integrated Bluetooth, FM, WLAN, and GPS modules, is a highly integrated baseband platform incorporating application processing subsystems. The chip integrates ARM Cortex-A73/A53 MPCore operating up to 2GHz and powerful multi-standard video codec. The application processor, a multi-core ARM Cortex-A73, ARM Cortex-A53 MPCore equipped with the NEON engine offers processing power necessary to support the latest OpenOS along with its demanding applications such as web browsing, email, GPS navigation, and games. All are viewed on a high-resolution touch screen display with graphics enhanced by the 2D and 3D graphics acceleration. The multi-standard video accelerator and an advanced audio subsystem are also integrations and services such as streaming and encoders. SB52 also embodies wireless communication devices, including WLAN and Bluetooth. The RF part is built-in MT7668 chip which can support dual-band(2.4GHz and 5GHz) single-stream 802.11 a/b/g/n/ac. It also supports a single antenna sharing 2.4 GHz antenna for Bluetooth, WLAN, and 5GHz antenna for WLAN. SB52 SOM offers a wide range of interfaces - GPIOs, I2S, I2C, SPI, DSI, CSI, ADC, UART, USB, AUDIO out, PWM. www.innocomm.com4 1.2 Architecture and Block Diagram Figure 1-1 SB52 SOM Block Diagram 1.3 Feature Summary 2GB LPDDR4X RAM 16GB eMMC 1 x MIPI DSI (4 data lanes) 2 x MIPI CSI (4 data lanes) MTK i500 CPU Wi-Fi 802.11 a/b/g/n/ac, MIMO (MT7668) GPIOs pin-mux with serial interfaces Bluetooth 5 (MT7668) 1 x USB 2.0 OTG Serial interfaces (4 x I2C, 2 x UART, 1 x SPI, 2 x I2S) Earphone interface, R/L channel output and microphone input 1x ADC www.innocomm.com5

1.4 Dimension The dimension of SB52 is 55 mm x 45 mm x 3.5 mm. Detail dimension please see Fig1-2. Figure 1-2 SB52 SOM Dimension 1.5 Electrical Specifications Symbol Parameter Minimum Maximum Unit VSYS Input Voltage 3.4 4.35 V VSYS Input Current 1.5 A Table 1-1: Input Power Absolute Maximum Ratings Symbol Parameter Minimum Maximum Unit VIO28_PMU VDDIO_2V8 2.66 2.94 V VIO18_PMU VDDIO_1V8 1.71 1.89 V Table 1-2: Output Power www.innocomm.com6 Symbol Parameter Minimum Maximum Unit T Operating Temp. 0 60* C Table 1-3 Operating Temperature Note * : Test with heat sink 1.6 General Application Notes Consider the following recommendations when designing application boards:

Use a GND plane underneath the SB52. Do not use vias in high-speed interface lines such as USB and Ethernet. Rout high-speed interface lines differentially and leave several mm gap to other signal lines when possible. Do not place any components which dissipate heat close to or underneath the module. A heat sink is suggested to allow prolonged operation under full CPU speed. Connect heat sink to CPU and WiFi via thermal pad, ensure that heat sink is not tilted or applying high force onto the module. www.innocomm.com7 2 Main Hardware Components SB52 SOM has two 75-pin M.2 E-key golden fingers to connect with another carrier board. It integrates MTK the i500, LPDDR4 Memory, eMMC, Power Manage IC (PMIC), and Wi-

Fi/Bluetooth on the module. Figure 2-1 Top side of SB52 SOM www.innocomm.com8 Figure 2-2 Bottom side of SB52 SOM 2.1 CPU MTK i500 processor integrates a multi-core ARM Cortex-A73, ARM Cortex-A53 MPCore equipped with the NEON engine offers processing power necessary to support the latest OpenOs along with its demanding applications such as web browsing, email, GPS navigation, and games. The features of i500 processors include the following:

Quad-core ARM Cortex-A73 MPCore operating at 2GHz Quad-core ARM Cortex-A53 MPCore operating at 2GHz NEON multimedia processing engine ARM TrustZone security 2.2 Memory SB52 SOM is embedded 2GB of LPDDR4X memory with the following feature, Dual channels with a 16-bit data bus width Up to 3200MHz memory clock Advanced bandwidth arbitration control Supports self-refresh/ partial self-refresh mode Supports dual-rank memory device 2.3 Power Management IC www.innocomm.com9 MTK MT6358 power management IC is used for SB52 SOM. MT6358 is a programmable power management IC that integrates 9 buck converters and 33 LDOs to provide all power rails required by SoC and peripherals. MT6358 adopts the SPI interface and two SRCLKEN control pins to control buck converters, LDOs, and various drivers; it provides enhanced safety control and protocol for handshaking with i500. For system management, it provides the following features, Support software shutdown or hardware power off 32K RTC oscillator for system timing Over-current and thermal overload protection OVP, UVLO function Precision voltage, temperature, and current measurement fuel gauge Watchdog reset 2.4 eMMC Storage The onboard eMMC device is connected to the MSDC0 interface of the i500 processor in an 8-bit width configuration. 2.5 Wi-Fi/Bluetooth Module MTK MT7668 WIFI/BT IC is used for SB52. It supports Wi-Fi 802.11 a/b/g/n/ac MIMO and BT5.0. www.innocomm.com10 3 SB52 SOM Interfaces and Connectors SB52 use two M.2 E-key golden finger to connect with the carrier board. The tables below detail the pin assignment and functionality of these connectors. J401 Pin #

Signal Name I500 Pin # MT6358 Pin #

I/O Voltage (V) Table 3-1 J401 Connector J401 Connector 3.1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 SYSRSTB VBAT PWRKEY_SW VBAT VCAMA2_PMU VBAT GND VBAT GND GND AUXIN4 VBUS GPIO9 VRTC28 GPIO17 GPIO10 UCTS1 GPIO22 SDA2 GPIO23 SCL2 GPIO24 AU_MICBIAS0 K23 AG18 W4 AB26 Y4 N26 Y26 AB1 AA26 AB2 AA23 www.innocomm.com11 D4 D2 N10 K12 M8 I PI I PI PO PI PI AI PI I/O PO I/O I/O I/O I/O OD I/O OD I/O PO 1.8/2.5/2.7/2.8/2.9/3 1.8 3.4 ~ 4.35 0 ~ 5 3.4 ~ 4.35 3.4 ~ 4.35 3.4 ~ 4.35 0 ~ 1.8 5 1.8 2.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 K5 1.7~2.6 J401 Pin#

I500 Pin # MT6358 Pin #

Voltage Signal Name 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 SPI_CSB AU_VIN2_N SPI_CLK AU_VIN0_P SPI_MI AU_VIN0_N SPI_MO AU_REFN URTS1 AU_HPR GPIO19 AU_HPL GPIO150 GND I2S1_LRCK AU_MICBIAS1 I2S1_BCK AU_VIN1_P I2S1_DO AU_VIN1_N KPROW0 ACCDET URXD1 HP_EINT UTXD1 GND KPCOL0 USB_DM KPROW1 USB_DP KPCOL1 GND SDA1 SDA3 SCL1 AG3 AF3 AJ2 AH2 P26 W24 R25 AD21 AG23 AG21 AA5 AG25 AG24 AC4 G26 AH1 F26 AE3 AF4 AG22 AE4 www.innocomm.com12 H5 AGND K3 K1 L1 G4 H4 L5 L4 L3 K6 J4 I/O I/O I/O I/O I I I I/O I/O AO I/O AO I/O GND I/O O I/O I/O I/O I/O I I I I I/O GND I/O USB I/O USB I/O GND I/O I/O I/O MICBIAS MICBIAS MICBIAS

-1.98 ~ 1.98

-1.98 ~ 1.98 1.7~2.6 MICBIAS MICBIAS 0 ~ 2.94V 0 ~ 2.94V 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 J401 Pin#

Signal Name I500 Pin # MT6358 Pin #

Voltage J402 Pin#

Signal Name I500 Pin # MT6358 Pin #

I/O Voltage Table 3-2 J402 Connector F3 J5 P8 G13 I/O I/O I/O GND I/O I/O I/O I/O I/O PO AGND PO GND I/O I/O I/O I/O I/O I I/O I/O I/O I/O I/O I/O I/O DSI I/O 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 2.8/3 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 67 68 69 70 71 72 73 74 75 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 SCL3 GPIO0 GND GPIO20 SDA0 GPIO42 SCL0 GPIO8 VIO18_PMU 3.2 J402 Connector AVSS28_AUD VLDO28_PMU GND GPIO45 UART_RXD0 DISP_PWM UART_TXD0 DISP_TE HOMEKEY GPIO21 IDDIG GPIO2 GPIO98 GPIO1 GPIO102 GPIO7 DSI0_D2N GPIO151 www.innocomm.com13 AF22 AB5 Y24 AC5 AF26 AB6 AD4 AH27 AD2 AH23 AD1 AG26 AB24 AF23 AG2 Y5 AB4 AA2 AE1 V24 L25 J402 Pin#

Signal Name I500 Pin # MT6358 Pin #

Voltage 19 20 21 22 23 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 DSI0_D2P DSI0_D3N DSI0_D1N DSI0_D3P DSI0_D1P DSI0_CKP DSI0_D0N DSI0_CKN DSI0_D0P CAM_CLK0 RDN3 RDN2 RDP3 RDP2 RDN1 RCP RDP1 RCN RDN0 GND RDP0 RDN3_A GND RDP3_A VCAMA_PMU RDN2_A VCAMD_PMU RDP2_A VCAMIO_PMU GPIO97 GPIO101 www.innocomm.com14 V25 T24 T26 T25 U26 U25 R27 U24 T27 AA4 T1 P3 T2 P4 R4 P5 R3 N5 R1 R2 P1 P2 M1 M2 W6 AA3 M10 M15 E6 I/O DSI DSI DSI DSI DSI DSI DSI DSI DSI I/O CSI CSI CSI CSI CSI CSI CSI CSI CSI GND CSI CSI GND CSI PO CSI PO CSI PO I/O I/O 1.8 1.8 1.8 1.8 1.8/2.5/2.7/

2.8/2.9/3 0.9/1.0/1.05/1.1

/1.2/1.3/1.5/1.8 J402 Pin#

Signal Name I500 Pin # MT6358 Pin #

Voltage R10 2.9/3/3.3 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 GND RCP_A GPIO3 RCN_A VMCH_PMU GND GPIO177 CAM_CLK1 I2S1_DI GND I2S1_MCK RDN1_A GPIO6 RDP1_A GPIO5 RDN0_A GPIO4 RDP0_A N1 AG1 N2 AC2 AD27 AD20 N4 AE2 N3 AF2 M4 AC3 M3 I/O GND CSI I/O CSI PO GND I/O I/O I/O GND I/O CSI I/O CSI I/O CSI I/O CSI 1.8 1.8 1.8 1.8 1.8 1.8 1.8 1.8 O O O O O O O O O 3.3 Power Signals Connector#

PIN#

Function I/O Description Table 3-3 Power Signal Pins 2,4,6,8 VSYS VRTC28 I Input power 3.4 ~ 4.35V I/O RTC power 2.8V VCAMA2_PMU Camera2 power 2.8V AU_MICBIAS0 AU_MICBIAS1 VIO18_PMU VCAMA_PMU VCAMD_PMU VCAMIO_PMU VLDO28_PMU VMCH_PMU Microphone0 Bias power 1.7~2.6V Microphone1 Bias power 1.7~2.6V IO power 1.8V Camera1 power 2.8V Camera1 power 1.2V Camera1 power 1.8V IO power 2.8V IO power 3.3V J401 J401 J401 J401 J401 J401 J402 J402 J402 J402 J402 14 5 23 47 75 51 53 55 2 62 www.innocomm.com15 I2Cs Parameter Specification SB52 SOM I2C is an open-drain interface, the specification is shown in Table 3-5. Parameters Description Typ Max Unit Table 3-4 I2C parameter specificaition 0.65*VDD Min

-0.3 VDD+0.3 0.35*VDD 0.2*VDD V V V Input logic high voltage Input logic low voltage DC output low voltage

* VDD is 1.8V Connector#

PIN#

PIN name Description Table 3-5 I2C Signal Pins 71 73 64 66 19 21 65 67 40 17 SDA0 SCL0 SDA1 SCL1 SDA2 SCL2 SDA3 SCL3 URTS1 UCTS1 I/O OD*

OD*

OD*

OD*

OD*

OD*

OD*

OD*

OD*

OD*

I2C0_SDA I2C0_SCL I2C1_SDA I2C1_SCL I2C2_SDA I2C2_SCL I2C3_SDA I2C3_SCL I2C6_SDA I2C6_SCL 3.4 VIH VIL VOL J401 J401 J401 J401 J401 J401 J401 J401 J401 J401

* OD is Open drain 3.5 UARTs www.innocomm.com16 SB52 supports two UARTs. UART0 is not recommended to use since this port is default for debug trace log function. UART1 has HW flow control with another two control pins for CTS and RTS function. Connector#

PIN#

PIN name I/O Description Table 3-6 UART Signal Pins 3.6 DSI Interface SB52 SOM provides a 4-lanes MIPI DSI display interface operating up to 2400x1080@60fps resolution Connector#

PIN#

PIN name I/O Description Table 3-7 DSI Signal Pins I O I O I O O O O O O O O O O O UART0_RXD UART0_TXD UART1_RXD UART1_TXD UART1_CTS UART1_RTS DSI_D0M DSI_D0P DSI_D1M DSI_D1P DSI_D2M DSI_D2P DSI_D3M DSI_D3P DSI_CLKM DSI_CLKP UART_RXD0 UART_TXD0 URXD1 UTXD1 UCTS1 URTS1 DSI0_D0N DSI0_D0P DSI0_D1N DSI0_D1P DSI0_D2N DSI0_D2P DSI0_D3N DSI0_D3P DSI0_CKN DSI0_CKP 5 7 54 56 17 40 33 35 21 23 17 19 20 22 34 35 J402 J402 J401 J401 J401 J401 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 www.innocomm.com17 3.7 CSI Interface SB52 SOM provides 2 MIPI CSI high-speed camera serial interface with 4 data lane ( for main and sub ) and throughput up to 2.8G bps for 1 data lane. Connector#

PIN#

PIN name I/O Description Table 3-8 CSI0 Signal Pins I I I I I I I I I I I I I I I I I I I I CSI0_D0P CSI0_D0M CSI0_D1P CSI0_D1M CSI0_D2P CSI0_D2M CSI0_D3P CSI0_D3M CSI0_CLKP CSI0_CLKM CSI1_D0P CSI1_D0M CSI1_D1P CSI1_D1M CSI1_D2P CSI1_D2M CSI1_D3P CSI1_D3M CSI1_CLKP CSI1_CLKM RDP0 RDN0 RDP1 RDN1 RDP2 RDN2 RDP3 RDN3 ROP RCN RDP0_A RDN0_A RDP1_A RDN1_A RDP2_A RDN2_A RDP3_A RDN3_A ROP_A RCN_A J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 J402 47 45 43 41 40 38 39 37 42 44 75 73 71 69 54 52 50 48 59 61 www.innocomm.com18 Connector#

PIN#

PIN name I/O Description Table 3-9 CSI1 Signal Pins 3.8 Audio SB52 SOM provides a Master I2S input/output interface from I500, 2 PDM interface for DMIC and 1 earphone interface from MT6358. SB52SOM supports I2S audio interface with below feature,

- Audio content sampling rates supported: 8kHz to 192kHz

- Audio content sample formats supported: 8-bit/16-bit/24-bit, Mono/stereo

- Interface supported: I2S, PCM

- External CODEC I2S interface supports 16-bit/24-bit, Mono/Stereo, 8kHz to 192kHz Connector#

PIN#

PIN name I/O Description Table 3-10 I2S Signal Pins J401 J401 J401 J402 J402 J401 J401 J401 J401 J401 J401 J401 J401 J401 J401 46 48 50 68 66 37 35 51 49 33 39 41 43 53 55 www.innocomm.com19 Connector#

PIN#

PIN name I/O Description Table 3-11 other Audio Signal Pins I2S1_LRCK I2S1_BCK I2S1_DO I2S1_MCK I2S2_DI AU_VIN0_N AU_VIN0_P AU_VIN1_N AU_VIN1_P AU_VIN2_N AU_REFN AU_HPR AU_HPL ACCDET HP_EINT I2S LRCK I2S BCK I2S DO I2S MCLK I2S DI PDM for DMIC PDM for DMIC earphone MIC input earphone MIC input PDM for DMIC earphone line out earphone line out Accessory detection input HPL detection GND earphone line out reference GND O O O O I I I I I I O O I I 3.9 USB SB52 SOM provides high speed USB functionality conforms to the USB2.0. The OTG controller conforms to OTG2.0 specification. Connector#

PIN#

PIN name Description Table 3-12 USB Signal Pins I/O I/0 I/0 I P USB DP USB DM USB ID USB VBUS J401 J401 J402 J401 61 59 11 12 USB_DP USB_DM IDDIG VBUS 3.10 GPIO All the IOs from i500 can be configured to GPIO purposes. For more detail pin-mux table please see the reference documents [1]. 4 Reference Documents 1. MT8167A_Technical _Brief datasheet. 2. MT6385_PMIC_Data_Sheet. 3. MT7668AUN_MT7668AEN_MT7668ASN_Datasheet www.innocomm.com20 5 How to Process SB52 SB52 is base on Android 10 OS , to access SB52, please install display share tools in PC If you have no ADB driver, You can find ADB driver from web side or download form android link There are many APPs you can use, you can download tools from web side:

For example:

1. Google Vyser 2. Scrcpy APP, Vysor lets you view and control your Android on your computer. Easy peasy. Please find Vysor App under link: http://www.vysor.io/download/

This application provides display and control of Android devices connected on USB (or over TCP/IP). It does not require any root access. It works on GNU/Linux, Windows and MacOS Please find scrcpy App under link: https://github.com/Genymobile/scrcpy Getting Started The Module can function with external EVB board and only DC power input only, and no battery included. Once youve plug in the DC adapter, you can turn on your SB52 and start using it. Set up your SB52 for the first time Please follow the instruction showed on the SB52. www.innocomm.com21 Home www.innocomm.com22 The Home screen is your starting point for using the applications on your SB52. There are many programs on applications , Enjoy the SB52 !!

Setting Wireless connection:

1.Quick setting: Swipe down to show quick setup options 2.1 Normal setting: To have WLAN and BT connection www.innocomm.com23 1. Make device discoverable: Under Settings, choose Connected devices. Tap Bluetooth to turn on it and tap Search for devices. The Bluetooth indicator then appears in the status bar. 2. Scan for devices: After scanning, there will be a list of the IDs of all available Bluetooth devices in range. If the device you want to pair with isnt in the list, ensure that the other device is turned on and set to be discoverable. 3. Pair with the Bluetooth device: Tap the name of an available Bluetooth device to pair with. In the popup Bluetooth pairing request dialog, type a PIN. If the pairing is successful, your SB52 connects to the device. 2.2 Normal setting: To have WLAN www.innocomm.com24 1. Make device discoverable: Under Settings, choose Network and internet. Tap Wi-iFi to turn on it and Searching Access Point devices. Scan for devices: After scanning, there will be a list of the APs SSID of all available APs devices in range. If the device you want to connect with isnt in the list, ensure that the other device is turned on and set to be discoverable. Connect to the WLAN APs: Tap the name of an available Bluetooth device to pair with. In the popup Bluetooth pairing request dialog, type a PIN. If the pairing is successful, your SB52 connects to the device. 2. 3. www.innocomm.com25 Federal Communication Commission Interference Statement This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. 15.19 15.105 15.21 This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. Any changes or modifications not expressly approved by the party responsible for compliance could void the authority to operate equipment. This device and its antenna must not be co-

located or operating in conjunction with any other antenna or transmitter. End-users and installers must be provided with antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. For product available in the USA/Canada market, only channel 1~11 can be operated. Selection of other channels is not possible FCC RF Radiation Exposure Statement:

This module is intended for OEM integrator. The OEM integrator is still responsible for the FCC compliance requirement of the end product, www.innocomm.com26 which integrates this module. 20cm minimum distance has to be able to be maintained between the antenna and the users for the host this module is integrated into. Under such configuration, the FCC radiation exposure limits set forth for an population/uncontrolled environment can be satisfied. Any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. USERS MANUAL OF THE END PRODUCT:

In the users manual of the end product, the end user has to be informed to keep at least 20cm separation with the antenna while this end product is installed and operated. The end user has to be informed that the FCC radio-frequency exposure guidelines for an uncontrolled environment can be satisfied. The end user has to also be informed that any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. END PRODUCT LABELING :

This transmitter module is authorized only for use in devices where the antenna may be installed such that 20 cm may be maintained between the antenna and users (for example access points, routers, wireless ASDL modems, certain laptop configurations, and similar equipment). The final end product must be labeled in a visible area with the following: "Contains TX FCC ID: YAISB52". If the size of the end product is larger than 8x10cm, then the following FCC part 15.19 statement has to also be available on the label: This device complies with Part 15 of FCC rules. Operation is subject to the following two conditions:

(1) this device may not cause harmful interference and

(2) this device must accept any interference received, including interference that may cause undesired operation. www.innocomm.com27 Antennas Brand name Model name Antenna type Antenna gain Antenna connector BJTEK TH96-120mm-

ipex & Holder Monopole 3.14(dBi) ipex Label and Compliance Information Product manufacturers need to provide a physical or e-label stating Contains FCC ID: YAISB52 with finished product Information on Test Modes and Additional Testing Requirements Test tool: Android debug bridge shall be used to set the module to transmit continuously. www.innocomm.com28

Date: 2022/5/4 Subject: Product Certification Representative Authorization Letter Federal Communications Commission 7435 Oakland Mills Rd Columbia MD 21046-1609 FCC ID: YAISB52 Product name: Wireless SOM Module To whom it may concern:

We the undersigned, hereby authorize following person to act as our agent in the preparation of an application for equipment authorization of model SB52 to the FCC Rules and Regulations. International Certification Corp. Address :

No.3-1, Lane 6, Wen San 3rd St. Kwei Shan Dist., TaoYuan City 333, Taiwan (R.O.C.)

: Gary Chang Name Job Title : Manager e-mail

: garychang@icertifi.com.tw Webs We further certifies that neither the applicant nor any party to this application, as defined in 47 CFR Ch. 1.2002(b), is subject to a denial to Federal benefits, that include FCC benefits, pursuant to section 5301 of the Anti-Drug Abuse Act of 1998, 21 U.S.C. 862. This appointment also includes the authority to complete FCC Form 731 on our behalf and sign the application as an authorized agent. Bruno Tsai/ Product Manager Tel: 886-3-5781868 Ext.: 652 Fax: 886-3-5781187 E-mail: bruno.tsai@innocomm.com

Date: May 4, 2020 Subject: Ad Hoc Mode Function Declaration FCC ID: YAISB52 To Whom it may concern, We, InnoComm Mobile Technology Corp declare that the device does not support any non-US channels, country code selection and Channel 12 and 13 in 2.4 GHz band in all the operational mode(s). Also, the client software and associated drivers will not initiate any transmission on DFS frequencies without initiation by a master and the device without support DFS detection capability. This includes restriction on transmissions for beacons and support for ad-hoc peer-to-peer modes. Regards, Applicant Address Signature E-mail Tel.

: InnoComm Mobile Technology Corp 3F,No. 6, Hsin Ann Rd., Hsinchu Science Park, Hsinchu

City 30078, Taiwan Name and Job Title.

: Keller Lin / DQA mamager keller.lin@innocomm.com

+886-3-5781868

Date : May 4, 2020 We have declared below featured for FCC equipment authorization, Device FCC ID: YAISB52 UNII Declaration Letter

(1) DFS Device --

Client with Radar detection capability , Client without radar detection capability

(2) Active / Passive Scanning , Ad hoc mode access point capability Frequency Band

(MHz) Active Scanning

(the device can transmit a probe passive scanning

(where the device is can listen only with no Ad Hoc Mode capability Access point capability

(beacon)) Yes , Yes , Yes , Yes , No No No No probes) Yes , Yes , Yes , Yes , No No No No Yes , Yes , Yes , Yes , No No No No Yes , Yes , Yes , Yes , No No No No 5150 5250 5250 5350 5470 5725 5725 5850

(3) Country code selection ability -

Yes , If no, pls explain how was implemented :

No

(4) Meet 15.202 requirement -

Yes , No , pls check below :

A client device is defined as a device operating in a mode in which the transmissions of the device are under control of the master. A device in client mode is not able to initiate a network.

(5) For client devices that have software configuration control to operate in different modes (active scanning in some and passive scanning in others) in different bands (devices with multiple equipment classes or those that operate on non-DFS frequencies) or modular devices which configure the modes of operations through software, the application must provide software and operations description on how the software and / or hardware is implemented to ensure that proper operations modes can not be modified by end user or an installer. Apply , No Apply ,

(If apply , pls help to provide explanation on how it was implement (By hardware or software , and how software was controlled) On DFS channels, the WLAN driver on the device operates under the control of an AP at all times, except when in ad-hoc mode, on US non-DFS channels. As described in the answer to question (2), the device passively scans DFS frequencies until a master device is detected. The control of this functionality is not accessible to anyone under any conditions. Furthermore, the firmware is locked by proprietary password and cannot be changed or modified by end user.

: InnoComm Mobile Technology Corp

3F,No. 6, Hsin Ann Rd., Hsinchu Science Park, Hsinchu City 30078, Taiwan Applicant Address Signature

Name and Job Title.

: Keller Lin /DQA manager E-mail Tel.

: keller.lin@innocomm.com

: +886-3-5781868

RF_734_02 04 April 16 Modular Approval Request FCC (KDB 996369 D01 & Part 15.212) FCC ID: YAISB52 Items to be covered by Single modular transmitters. 1. The modular transmitter must have its own RF shielding. 2. The modular transmitter must have buffered modulation/data inputs (if such inputs are provided) to ensure that the module will comply with Part 15 requirements under conditions of excessive data rates or over-modulation. 3. The modular transmitter must have its own power supply regulation. 4. The modular transmitter must comply with the antenna requirements of Section 15.203 and 15.204(b)(c). The antenna must either be permanently attached or employ a unique antenna coupler (at all connections between the module and the antenna, including the cable). 5. The modular transmitter must be tested in a stand-alone configuration, i.e., the module must not be inside another device during testing. This is intended to demonstrate that the module is capable of complying with Part 15 emission limits regardless of the device into which it is eventually installed. 6. The modular transmitter must be equipped with either a permanently affixed label or must be capable of electronically displaying its FCC identification number in accordance with 15.212 (a)(1)(vi)(A) / (B). 8. there are very strict operational and 7. The modular transmitter must comply with any specific rule or operating requirements applicable to the transmitter and the manufacturer must provide adequate instructions along with the module to explain any such requirements. A copy of these instructions must be included in the application for equipment authorization. For example, timing requirements that must be met before a transmitter is authorized for operation under Section 15.231. For instance, data transmission is prohibited, except for operation under Section 15.231(e), in which case there are separate field strength level and timing requirements. Compliance with these requirements must be assured. The modular transmitter must comply with any applicable RF exposure requirements. For example, FCC Rules in Sections 1.1310, 2.1091, 2.1093, and specific Sections of Part 15, including 15.319(i), 15.407(f), 15.253(f) and 15.255(g), require that Unlicensed PCS, UNII and millimeter wave devices perform routine environmental evaluation for RF Exposure to demonstrate compliance. In addition, spread spectrum transmitters operating under Section 15.247 are required to address RF Exposure compliance. Modular transmitters approved under other Sections of Part 15, when necessary, may also need to address certain RF Exposure concerns, typically by providing specific installation and operating instructions for users, installers and other interested parties to ensure compliance. Answer from applicant The modular has a shielding Case. Please refer to EUT Photo. The component number is MT7668 The component number is MT6358 Antenna Connectors are UFL. And no external amplifier will be used with this modular. This modular is tested under stand-alone configuration. Please refer to Test setup photo. The modular transmitter is labeled with its own FCC ID number. Please refer to label sample and label location. The modular complies with this requirement. Please refer to user manual. The device complies with this requirement. Please refer to RF exposure report. RF_734_02 04 April 16 Answer from applicant Items to be covered by Split modular transmitters. 1. The modular transmitter must comply with all requirements of a single modular transmitter except for items (1) & (5) of the above single modular approval requirements. 2. Only the radio front end must be shielded. The physical crystal and tuning capacitors may be located external to the shielded radio elements. The interface between the split sections of the modular system must be digital with a minimum signalling amplitude of 150 mV peak-to-peak. 3. Control information and other data may be exchanged between the transmitter control elements and radio front end. 4. The sections of a split modular transmitter must be tested installed in a host device(s) similar to that which is representative of the platform(s) intended for use. 5. Manufacturers must ensure that only transmitter control elements and radio front end components that have been approved together are capable of operating together. The transmitter module must not operate unless it has verified that the installed transmitter control elements and radio front end have been authorized together. Manufacturers may use means including, but not limited to, coding in hardware and electronic signatures in software to meet these requirements, and must describe the methods in their application for equipment authorization. Note: A limited modular approval (LMA) may be granted for single or split modular transmitters that comply partially with the requirements above. Name and surname of applicant (or authorized representative): __________________ Date: ___28 May 2020____ Signature: ___________________________

Date: May 4, 2020 Federal Communications Commission Authorization and Evaluation Division 7435 Oakland Mills Rd Columbia MD 21046-1609 Subject: Request for confidentiality FCC ID: YAISB52 To whom it may concern:

Short-term confidentiality Internal Photographs External Photographs User's manual Test Set up photo Permanent confidentiality Block Diagram Schematics Operational Description Pursuant to DA 04-1705 of the Commissions pubic notice, in order to comply with the marketing regulations in 47CFR 2.803 and the importation rules in 47 CFR 2.1204, while ensuring that business sensitive information remains confidential until the actual marketing of newly authorized devices. We are requesting the commission to grant short-term confidentiality request on the following attachments for 180 days. Pursuant to Sections 0.457 and 0.459 of the Commissions Rules, the Applicant Hereby requests confidential treatment of information accompanying this Application As outlined below:

The above materials contain trade secrets and proprietary information not customarily released to the public. The public disclosure of these materials may be harmful to the applicant and provide unjustified benefits to its competitors. The applicant understands that pursuant to Section 0.457 of the Rules, disclosure of this application and all accompanying documentation will not be made before the date of the Grant for this application. Should you require any further information, please contact the undersigned. Thank you for your consideration in this matter. Applicant

: InnoComm Mobile Technology Corp 3F,No. 6, Hsin Ann Rd., Hsinchu Science Park, Hsinchu City 30078, Taiwan

Address Signature E-mail Tel. Name and Job Title.

: Keller Lin / DQA manager

: keller.lin@innocomm.com

: +886-3-5781868