Coral Dev Board Micro Datasheet-3009759
Coral Dev Board Micro Datasheet-3009759
Version 1.0
Features
Description
The Coral Dev Board Micro is a microcontroller board with a dual-core MCU, Coral Edge TPU, camera, and microphone.
With this board, you can build low-power systems with fast on-device inferencing for vision and audio ML applications. You
can also expand the hardware with custom add-on boards using the high-density board-to-board connectors.
The Edge TPU is a small ASIC designed by Google that accelerates TensorFlow Lite models in a power efficient manner.
One Edge TPU is capable of performing 4 trillion operations per second (4 TOPS). This on-device ML processing reduces
latency, increases data privacy, and removes the need for a constant internet connection.
Ordering information
Table of contents
Features 1
Description 1
Ordering information 1
Table of contents 2
1 System components 3
1.1 Block diagram 5
2 Mechanical dimensions 6
3 Electrical specifications 7
3.1 Recommended operating conditions 7
3.2 Logic threshold levels 7
3.3 Power consumption 8
4 Hardware interfaces 8
4.1 Buttons 8
4.2 USB-C port 8
4.3 LEDs 9
4.4 Camera 9
4.5 Microphone 9
4.6 GPIO headers 10
4.7 Board-to-board connectors 10
5 Peripheral interfaces 11
5.1 Ethernet 11
5.2 SDIO 12
5.3 CSI camera 12
5.4 DSI display 13
5.5 PDM audio 13
5.6 SAI audio 14
5.7 ADC 14
5.8 DAC 14
5.9 I2C 15
5.10 UART 15
5.11 SPI 16
5.12 GPIO 16
5.13 PWM 17
5.14 JTAG 17
6 Board operation 18
6.1 Power supply 18
6.2 Boot modes 18
8 Document revisions 22
1 System components
Memory ● 2 MB SRAM:
○ 512 KB of TCM for Cortex-M7
○ 256 KB of TCM for Cortex-M4
○ 1.25 MB OCRAM
● 4 KB secure always-on RAM
● 256 KB boot ROM
Secure element
ML accelerator
Coral Edge TPU coprocessor ● High performance inferencing for TensorFlow Lite models
● 4 trillion operations per second (TOPS)
● USB 2.0 interface with the RT1176 MCU
On-board sensors
Hardware connections
User interface
2 Mechanical dimensions
Weight 10.4 g
3 Electrical specifications
Operating temperature 0 °C – 50 °C
Typical operation is based on a 5 V / 2 A power supply via USB. For more details, see section 6.1 Power supply.
Caution: The board can become hot during operation and might burn you if touched. If using a case, the board might
require cooling to maintain proper operating temperatures. You must validate safe operation before you deploy.
Warning: Do not connect devices to the voltage rails (VSYS, VDD_3V3, VDD_1V8) that draw significant power. Doing so
can exceed the board's ability to supply power and might cause the board to malfunction or overheat, possibly causing
fire and serious injury. For details about available power on each rail, consult the Dev Board Micro schematic (table 20).
Low-level max (VOL) High-level min (VOH) Low-level max (VIL) High-level min (VIH)
Note: There is considerable variation in capability between I/O banks on the RT1176 MCU, so only the worst case
numbers are provided in table 4. For complete details on I/O drive strengths, refer to the RT1176 datasheet.
When operating within the voltage thresholds in table 4, each I/O pin supports a maximum current of 6 mA, except for the
DAC pin, which can supply a maximum current of 1 mA. Some signals that are available only through the board-to-board
connectors and belong to the GPIO_SNVS domain are limited to 170 µA drive strength.
Warning: If you exceed the max I/O pin current, you can damage the board, possibly causing fire and serious injury.
The power consumed by the Dev Board Micro depends on a variety of application behaviors, but most importantly, the
extent to which the Edge TPU is being used. Typical test scenarios when the Edge TPU is active show average power
peaks around 3 W.
Beware that, depending on the type of ML model you're using, the Edge TPU can cause significant spikes in current draw.
For more details about the Edge TPU power consumption, see the Coral Accelerator Module datasheet.
4 Hardware interfaces
4.1 Buttons
● User button / Power cycle (USR): Programmable for application behaviors with a short press (active low). If held for
7 seconds, it power-cycles the board. If held while booting, it enables Serial Downloader mode.
● Reset button (RST): Resets the MCU.
There is one USB-C port (USB 2.0) that provides board power and data I/O with a computer.
You can access the serial console through USB while FreeRTOS is running (the connection is lost during resets). You can
instead access the serial console with the UART pins on the GPIO header and maintain the connection during resets.
4.3 LEDs
All LEDs are programmable, but they have some default behaviors (except the User LED) as described in table 5.
Table 5. Description of the on-board LEDs (see figure 3 for LED locations)
Name Color Description
Camera Green Indicates camera activity. By default, it is on during image capture, for a minimum of 500 ms.*
TPU White Indicates Edge TPU status. By default, it is on while the Edge TPU is powered. It is
programmable, but only while the Edge TPU is powered.
Status Orange Indicates board operating status. By default, it turns on briefly when the board boots from flash
and it is programmable.
* The Camera LED gives people awareness that images are being captured by an image sensor for storage, processing,
and/or transmission. We strongly recommend this LED behavior remain unchanged and always be visible to users.
4.4 Camera
There is also one 2-lane MIPI CSI interface available through the board-to-board connectors for add-on boards.
4.5 Microphone
The Dev Board Micro has one on-board digital PDM microphone (left channel).
There are also 3 unused PDM lanes available through the board-to-board connectors for add-on boards.
Each I/O pin on the two 12-pin headers supports a max current of 6 mA when operating with 1.8 V, except for the DAC pin,
which must be treated differently and can supply a maximum current of 1 mA. However, drive strengths may be lower and
vary between pins. For information about voltage levels and logic thresholds, see section 3 Electrical specifications.
Once FreeRTOS is booted, all I/O pins are set to a high-Z (floating) state, with two exceptions: The I2C pins default to high,
and the UART6_TX and UART6_RX lines are configured for serial port communication so their states vary based on serial
port activity. During reset and boot-up, all pin states may change. If enabled, internal pull-ups and pull-downs are typically
35 kOhms (for more detail, see the RT1176 datasheet).
Figure 4 shows the primary function for each pin, along with the MCU pin name, and the name you can use to address each
pin either as a GPIO with the coralmicro library or as a digital/analog pin with Arduino.
Note: UART6_TX and UART6_RX are configured for serial port communication and should not be used for other
purposes.
Note: Header pins are not included. For compatibility with Coral cases, solder the header pins facing down.
The Dev Board Micro includes high-density board to board connectors on the bottom of the board (indicated in figure 3),
allowing you to connect add-on hardware such as the Coral Wireless Add-on board (sold separately), the Coral PoE Add-on
board (sold separately), or other custom add-on hardware.
For details about designing add-on hardware, see section 7 Add-on board developer guide.
5 Peripheral interfaces
The following interfaces are available through the board-to-board connectors ("B2B pins") and, in some cases, also through
the GPIO headers ("HDR pins").
5.1 Ethernet
Supports 10/100 Mbps Ethernet/IEEE 802.3 networks via RGMII lanes in the board-to-board connectors. Requires an
Ethernet PHY provided by an add-on board.
Table 6. Ethernet pins (all these pins are used by the Coral PoE Add-on)
MCU name Net name Type B2B pin Voltage Description
GPIO_EMC_B2_20 ENET_RGMII_MDIO I/O J6:46 1.8 V RGMII MDIO data for PHY.
5.2 SDIO
One 2-lane MIPI CSI bus with up to 1.5 GHz bit rate clock. Supports 24-bit RGB888/YUV444, CCIR656 video interface, 8-bit
YCbCr, YUV or RGB, and 8-bit/10-bit/16-bit/24-bit Bayer data input. Compatible with MIPI Alliance Standard for Camera Serial
Interface 2 (CSI-2) Version 1.1.
Note: The CSI channels have not been not tested with real-world applications. They have been tested only for nominal
impedance during manufacturing testing.
One 2-lane MIPI DSI bus with up to 1.5 GHz bit rate clock. Conforms to the MIPI D-PHY electrical specifications MIPI Display
Serial Interface (DSI) Version 1.1 and D-PHY specification Rev. 1.0 (and also MIPI Display Pixel Interface version 2.0, MIPI
Display Bus Interface version 2.0, DSC version 1.0a at protocol layer) for MIPI display port x2 lanes.
Note: The DSI channels are not tested with real-world applications. They are only tested for nominal impedance during
manufacturing testing.
5.7 ADC
5.8 DAC
5.9 I2C
5.10 UART
5.11 SPI
5.12 GPIO
5.13 PWM
GPIO_AD_02 FLEXPWM1_PWM1_A Output J5:11 - 1.8 V Used internally for TPU LED.
5.14 JTAG
GPIO_LPSR_10 JTAG_nTRST Output J5:48 J10:6 (SPI) 1.8 V Shared with LPSPI6_SCK.
GPIO_LPSR_11 JTAG_TDO Output J5:46 J10:7 (SPI) 1.8 V Shared with LPSPI6_TDO.
GPIO_LPSR_12 JTAG_TDI Input J5:44 J10:8 (SPI) 1.8 V Shared with LPSPI6_SDI.
6 Board operation
You can power the Dev Board Micro through either the USB-C port or the VSYS pins available on the GPIO header and
board-to-board connectors.
The Dev Board Micro requires a DC power supply that can provide 5 V at 2 A. Although applications can operate at lower
currents, the Edge TPU can produce significant power spikes during inferencing, so the supply must be able to handle peak
current transients.
The power supply is intended to support the Dev Board Micro's power requirements only. If using the Dev Board Micro to
control a device that draws significant loads, you should provide that device with a separate power supply. For details about
the Dev Board Micro's output voltage rails, refer to section 3.1 Recommended operating conditions.
Caution: If your power supply cannot deliver 5 V at 2 A, the Dev Board Micro might not operate reliably. If powering the
board from a computer that can't deliver sufficient power, you should connect the board through a powered USB hub.
Warning: Do not connect more than one power source at a time. For example, do not connect the USB port to a power
supply when also delivering power through the Coral PoE Add-on board (or other add-on board) or through the VSYS
header. Doing so can degrade the USB power supply's ability to power the board, and can cause damage to the power
supply at the VSYS pin, possibly causing fire and serious injury.
The Dev Board Micro has two primary boot modes: Boot from flash memory or boot the Serial Downloader.
During a normal boot, the Dev Board Micro loads an application from flash memory. To instead boot the Serial Downloader,
hold the User button (the button at the center of the board) as the board boots. That is, either tap the Reset button or plug
in the board while you hold the User button.
Note: If you start the Serial Downloader by holding the User button as you connect power to the Dev Board Micro, the
Status LED remains solid because its line is pin-strapped high. (When booting from flash, the Status LED quickly turns off
because the pin changes to an input.) Whereas, if you start the Serial Downloader by holding the User button as you
press the Reset button, all pins maintain their prior state, so the Status LED could be either on or off, depending on the
application that was running at the time.
You can flash the Dev Board Micro while it's in either boot mode. To flash the board, connect it to your computer via the
USB port, and use the Python flashtool provided with the coralmicro source code. For details, see the Dev Board Micro
setup guide.
This section provides information to help you build custom hardware ("add-on boards") that attaches to the Coral Dev Board
Micro using the board-to-board connectors on the bottom of the board.
For help designing add-on boards, refer to the mechanical and electrical documents in table 20.
Dev Board Micro schematic Electrical schematic for the main board
Dev Board Micro models 3D model files for the main board
Add-on board KiCad templates Design file templates for add-on boards
The connector layout dimensions are indicated in figure 2, in section 2 Mechanical dimensions.
Table 21 specifies the 100-pin connectors that are compatible with the Dev Board Micro.
Table 21. Dev Board Micro and matching add-on board connectors
Dev Board Micro connector Add-on board connector
For pinout details, refer to the Dev Board Micro schematic in table 20.
The maximum component height on the bottom is nominally 1 mm, when ignoring the board-to-board connectors. The
minimum board-to-board spacing between the Dev Board Micro and any add-on boards is 1.5 mm.
For detailed component heights, see the Dev Board Micro model files in table 20.
Figure 5. Top view of the Dev Board Micro showing keepout regions for the add-on board antennas
Differential signals: including Ethernet, MIPI (CSI and DSI) 100 Ohm differential 10%
MIPI signals for the CSI/DSI buses are high-speed signals that require that the total etched trace lengths for each line within
a group (the paired clock lanes and four data lanes) be equal to each other. Due to space constraints on the board, the MIPI
signal traces lengths are not exactly equal (as indicated in tables 23 and 24). You must incorporate the length difference on
your add-on hardware traces, as necessary, such that the trace lengths for each MIPI group match each other.
● When placing a pull-up or pull-down resistor on any signals broken out from the Dev Board Micro, check the Dev
Board Micro schematic (table 20) to confirm that pull up/down resistors do not already exist on these signals.
8 Document revisions
Authorized Distributor
Google:
G650-07968-01 G650-07974-01