The i.MX 7Dual delivers high-performance processing for low-power requirements with a high degree of functional integration. The i.MX 7Dual features an advanced implementation of two ARM®Cortex®-A7 cores, which operate at speeds of up to 1.2 GHz, as well as the ARM® Cortex®-M4 core. The Pico variant is pin-compatible with the Intel® Edison for sensors and low-speed I/O, but also adds additional expansion possibilities for multimedia and connectivity, giving you cutting edge technology that can easily be expanded and implemented for IoT designs.
Flashing the image
Before you begin flashing, you will need the following items in addition to your board:
- USB-C cable
To flash Android Things onto your board, download the latest preview image and follow these steps:
Step 1: Connect the Hardware
Connect the board to your host computer as shown below:
- Connect a USB-C cable from your host computer for Power and USB OTG.
Step 2: Flash Android Things
Use the following steps to flash the Android image:
Update the Android SDK Platform Tools to version 25.0.3 or later from the SDK Manager.
- Verify that the
fastbootbinary is installed in the
platform-tools/directory of your Android SDK.
- After you have the fastboot tool, add it to your
- Verify that the
Open a command line terminal and navigate to the unzipped image directory.
If your device is not already in Fastboot mode, use the adb tool to activate it:
$ adb reboot bootloader
Verify that the device has booted into Fastboot mode by executing the following:
$ fastboot devices 1b2f21d4e1fe0129 fastboot
Ensure that the bootloader is unlocked.
$ fastboot oem unlock
flash-all.shscript. This script installs the necessary bootloader, baseband firmware(s), and operating system. (On Windows systems, use
To verify that Android is running on the device, discover it using the adb tool:
$ adb wait-for-device ... $ adb devices List of devices attached 1b2f21d4e1fe0129 device
After flashing your board, it is strongly recommended to connect it to the internet. This allows your device to deliver crash reports and receive updates.
Before connecting your board to a Wi-Fi network, attach an external IPEX or u.FL Wi-Fi antenna to your board as shown:
To connect your board to Wi-Fi using
Send an intent to the Wi-Fi service that includes the SSID and passcode of your local network:
$ adb shell am startservice \ -n com.google.wifisetup/.WifiSetupService \ -a WifiSetupService.Connect \ -e ssid <Network_SSID> \ -e passphrase <Network_Passcode>
Verify that the connection was successful through
$ adb logcat -d | grep Wifi ... V WifiWatcher: Network state changed to CONNECTED V WifiWatcher: SSID changed: ... I WifiConfigurator: Successfully connected to ...
Test that you can access a remote IP address:
$ adb shell ping 22.214.171.124 PING 126.96.36.199 (188.8.131.52) 56(84) bytes of data. 64 bytes from 184.108.40.206: icmp_seq=1 ttl=57 time=6.67 ms 64 bytes from 220.127.116.11: icmp_seq=2 ttl=57 time=55.5 ms 64 bytes from 18.104.22.168: icmp_seq=3 ttl=57 time=23.0 ms 64 bytes from 22.214.171.124: icmp_seq=4 ttl=57 time=245 ms
If you want to clear all of the saved networks on the board:
$ adb shell am startservice \ -n com.google.wifisetup/.WifiSetupService \ -a WifiSetupService.Reset
Serial debug console
The serial console is a helpful tool for debugging your board and reviewing
system log information. The console is the default output location for kernel
log messages (i.e.
dmesg), and it also provides access to a full shell prompt
that you can use to access commands such as logcat.
This is helpful if you are unable to access ADB on your board through other
means and have not yet enabled a network connection.
To access the serial console, connect a micro USB cable to the board as shown below.
Open a connection to the USB serial device on your development computer using a terminal program, such as PuTTY (Windows), Serial (Mac OS), or Minicom (Linux). The serial port parameters for the console are as follows:
- Baud Rate: 115200
- Data Bits: 8
- Parity: None
- Stop Bits: 1