RIOT Board User Manual v1.1
RIOT Board User Manual v1.1
RIOT Board User Manual v1.1
0
Date: 01/20/2014
Table of Contents
1
1.2
FEATURES .................................................................................................................................... 8
PROCESSOR ............................................................................................................................... 11
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.2
2.2.1
MT41K256M16HA-125:E ................................................................................................... 15
2.2.2
MMPF0100NPAEP .............................................................................................................. 15
2.2.3
AR8035............................................................................................................................... 15
2.2.4
FE1.1 .................................................................................................................................. 16
2.2.5
SGTL5000 ........................................................................................................................... 16
2.3
2.3.1
2.3.2
2.3.3
HDMI Interface................................................................................................................... 19
2.3.4
2.3.5
2.3.6
2.3.7
2.3.8
2.3.9
Page | 2
2.3.10
2.3.11
2.3.12
2.3.13
2.3.14
2.3.15
2.3.16
2.3.17
2.3.18
2.3.19
LEDs ............................................................................................................................... 39
SOFTWARE FEATURES................................................................................................................... 40
3.2
3.3
3.4
4.2
5.1.2
5.2
5.2.1
5.2.2
Page | 3
Page | 4
Page | 5
Page | 6
1
1.1
Board Overview
Product Introduction
The RIoTboard is an evaluation platform featuring the powerful i.MX 6Solo, a
multimedia application processor with ARM Cortex-A9 core at 1 GHz from Freescale
Semiconductor. The platform helps evaluate the rich set of peripherals and includes
a 10/100/Gb Ethernet port, HDMI v1.4, LVDS, analog headphone/microphone, uSD
and SD card interface, USB, serial port, JTAG, 2 camera interfaces, GPIO boot
configuration interface, and expansion port, as shown in Figure 1-1.
The RIoTboard can be used in the following applications:
Page | 7
1.2
Features
The RIoTboard is based on the i.MX 6Solo processor from Freescale Semiconductor
integrating all the functionalities of this multimedia application processor with the
following features:
Mechanical Parameters
o Working Temperature: 0C - 50C
o Humidity Range: 20% - 90%
o Dimensions: 120mm x 75mm
o Input Voltage: +5V
Processor
o ARM Cortex A9 MPCore Processor at 1 GHz
o High-performing video processing unit which covers SD-level and HDlevel video decoders and SD-level encoders as a multi-standard video
codec engine
o An OpenGL ES 2.0 3D graphics accelerator with a shader and a 2D
graphics accelerator for superior 3D, 2D, and user interface
acceleration
Memories
o 1GByte of 16-bit wide DDR3 @ 800MHz
o 4GB eMMC
Page | 8
Media Interfaces
o Analog headphone/microphone, 3.5mm audio jack
o LVDS interface
o HDMI interface
o Parallel RGB interface(Expansion port)
o Camera interface (Support CCD or CMOS camera)
o MIPI lanes at 1 Gbps
Page | 9
Others
o
o
o
o
o
o
1 Power LED
1 Open SDA LED
2 User-defined LEDs
1 DC Jack
1 Reset button
Boot configuration interface
Page | 10
Hardware Description
2.1
Processor
Core Features
The i.MX 6Solo processor is based on the ARM Cortex A9 MPCore platform with the
following features:
Page | 11
2.1.2
Page | 12
2.1.3
Displays--Total five interfaces available. Total raw pixel rate of all interfaces is
up to 450 Mpixels/sec, 24 bpp. Up to two interfaces may be active in parallel.
o One Parallel 24-bit display port, up to 225 Mpixes/sec (for example,
WUXGA at 60 Hz or dual HD1080 and WXGA at 60 Hz)
o LVDS serial ports One port up to 165 Mpixels/sec or two ports up to
85 MP/sec (for example, WUXGA at 60 Hz) each
o HDMI 1.4 port
o MIPI/DSI, two lanes at 1 Gbps
o EPDC, Color, and monochrome E-INK, up to 1650x2332 resolution and
5-bit grayscale
Camera sensors:
o Two parallel Camera ports (up to 20 bit and up to 240 MHz peak)
o MIPI CSI-2 serial camera port, supporting from 80 Mbps to 1 Gbps
speed per data lane. The CSI-2 Receiver core can manage one clock
lane and up to two data lanes. Each i.MX 6Solo processor has two
lanes.
Expansion cards:
o Four MMC/SD/SDIO card ports all supporting:
1-bit or 4-bit transfer mode specifications for SD and SDIO
cards up to UHS-I SDR-104 mode (104 MB/s max)
1-bit, 4-bit, or 8-bit transfer mode specifications for MMC cards
up to 52 MHz in both SDR and DDR modes (104 MB/s max)
USB
o One high speed (HS) USB 2.0 OTG (Up to 480 Mbps), with integrated HS
USB PHY
o Three USB 2.0 (480 Mbps) hosts
One HS host with integrated High Speed PHY
Two HS hosts with integrated HS-IC USB (High Speed Inter-Chip
USB) PHY
Expansion PCI Express port (PCIe) v2.0 one lane
o PCI Express (Gen 2.0) dual mode complex, supporting Root complex
operations and Endpoint operations. Uses x1 PHY configuration.
Miscellaneous IPs and interfaces:
o Three I2S/SSI/AC97,up to 1.4 Mbps each
o Enhanced Serial Audio Interface ESAI), up to 1.4 Mbps per channel
o Five UARTs, up to 4.0 Mbps each
Providing RS232 interface
Supporting 9-bit RS485 multidrop mode
Page | 13
o
o
o
o
o
o
o
o
o
o
o
o
2.1.4
One of the five UARTs (UART1) supports 8-wire while the other
four support 4-wire. This is due to the SoC IOMUX limitation,
since all UART IPs are identical
Four eCSPI (Enhanced CSI)
Four I2C, supporting 400 kbps
Gigabit Ethernet Controller(IEEE1588 compliant), 10/100/1000 Mbps
Four Pulse Width Modulators (PWM)
System JTAG Controller (SJC)
GPIO with interrupt capabilities
8x8 Key Pad Port (KPP)
Sony Philips Digital Interface (SPDIF), Rx and Tx
Two Controller Area Network (FlexCAN), 1 Mbps each
Two Watchdog timers (WDOG)
Audio MUX (AUDMUX)
MLB (MediaLB) provides interface to MOST Networks (MOST25, MOST50,
MOST150) with the option of DTCP cipher accelerator
2.1.5
Hardware Accelerators
The i.MX 6Solo processor uses dedicated hardware accelerators to meet the targeted
multimedia performance. The use of hardware accelerators is a key factor in obtaining
high performance at low power consumption numbers, while having the CPU core
relatively free for performing other tasks.
The i.MX 6Solo processor incorporates the following hardware accelerators:
Page | 14
2.2.1
MT41K256M16HA-125:E
The board has 1GB of SDRAM (2x512MB). Microns MT41K256M16 is a 512MB DDR3
Synchronous DRAM, ideally suited for the main memory applications which require
large memory density and high bandwidth.
2.2.2
MMPF0100NPAEP
AR8035
AR8035 is a single port 10/100/1000 Mbps tri-speed Ethernet PHY feaured with low
power and low cost. AR8035 supports MAC.TM RGMII interface and IEEE 802.3az-2010,
Energy Efficient Ethernet (EEE) standard through proprietary SmartEEE technology,
improving energy efficiency in systems using legacy MAC devices without 802.3az
Page | 15
FE1.1
FE1.1 is a USB 2.0 high-speed 4-port hub solution. It uses USB3320 to provide 4
extended USB interface with support for high-speed (480MHz), full-speed (2MHz) and
low-speed (1.5MHz) mode.
2.2.5
SGTL5000
The SGTL5000 is a low power stereo Codec with Headphone Amp from Freescale, and is
designed to provide a complete audio solution for portable products needing line-in,
mic-in, line-out, headphone-out, and digital I/O. Deriving its architecture from best-inclass Freescale-integrated products currently on the market, the SGTL5000 is able to
achieve ultra low-power with very high performance and functionality, all in one of the
smallest footprints available.
Designed with features such as capless headphone and an integrated PLL to allow clock
reuse within the system, it helps customers achieve a lower overall system cost.
Page | 16
2.3.1
A 5V/1A AC-to-DC power supply needs to be plugged into the Power Jack (J1) on the
board. It is not recommended to use a higher voltage since possible damage to the
board may result due to failure of the protection circuitry.
Figure 2-2 Power Interface
J1
Pin
Signal
Function
GND
GND
NC
NC
+5V
Page | 17
2.3.2
LVDS Interface
Figure 2-3 LVDS Interface
J2
Pin
Signal
Function
3V3
+3.3V
LVDS_TX2_P
LVDS data2+
LVDS_TX2_N
LVDS data2-
GND
GND
LVDS_TX1_P
LVDS data1+
LVDS_TX1_N
LVDS data1-
GND
GND
LVDS_TX0_P
LVDS data0+
LVDS_TX0_N
LVDS data-
10
GND
GND
11
LVDS_CLK_P
LVDS CLK+
12
LVDS_CLK_N
LVDS CLK-
Page | 18
2.3.3
13
LCD_PWR_EN
14
Touch_Int
15
I2C_SCL
16
I2C_SDA
17
LED_PWR_EN
Backlight enable
18
5V
+5V
19
PWM
HDMI Interface
Figure 2-4 HDMI Interface
J3
Pin
Signal
Function
HDMI_D2P
GND
GND
HDMI_D2M
HDMI_D1P
GND
GND
Page | 19
HDMI_D1M
HDMI_D0P
GND
GND
HDMI_D0M
10
HDMI_CLKP
11
GND
GND
12
HDMI_CLKM
13
NC
NC
14
NC
NC
15
BI2C2_SCL
16
BI2C2_SDA
17
GND
GND
18
5Vin
5V
19
HDMI_HPD
HDMI detect
20
GNF_DVI
GND
Page | 20
2.3.4
The RIoTboard provides a 3.5mm stereo connector for a microphone input, as shown in
Figure 2-5. A mono microphone will input its signal though the tip of the 3.5mm plug.
Figure 2-5 MIC Input
J4
Pin
Signal
Function
GND_ANALOG
Analog GND
MIC_IN_P
GND_ANALOG
Analog GND
GND_ANALOG
Analog GND
MIC_IN_P
Page | 21
2.3.5
A headphone with a standard 3.5mm stereo jack can be connected to the Audio Output
jack at the point shown in Figure 2-6.
Figure 2-6 Audio Output Jack
J5
Pin
Signal
Function
GND_ANALOG
Analog GND
LINEOUT_L
Left output
LINEOUT_R
Right output
LINEOUT_R
Right output
LINEOUT_L
Left output
Page | 22
2.3.6
SD Card Interface
Figure 2-7 SD Card Interface
J6
Pin
Signal
Function
SD2_DAT3
Card data 3
SD2_CMD
Command signal
GND
GND
3P3V
3.3V
SD2_CLK
Clock
VSS
GND
SD2_DAT0
Card data 0
SD2_DAT1
Card data 1
SD2_DAT2
Card data 2
Page | 23
2.3.7
10
SD2_CD
Card detect
11
SD2_WP
12
GND
GND
13
GND
GND
14
GND
GND
15
GND
GND
The micro SD Card Connector (J7) connects a 4-bit parallel data bus to the SD3 port of
the i.MX 6 processor. The micro SD Card is inserted facing up at the location shown in
Figure 2-8.
Figure 2-8 uSD/MMC Card Interface
J7
Pin
Signal
Function
SD3_DAT2
Card data 2
SD3_DAT3
Card data 3
CMD
Page | 24
2.3.8
3P3V
3P3V
SD3_CLK
Card clock
VSS
GND
SD3_DAT0
Card data 0
SD3_DAT1
Card data 1
SD3_CD
Card detect
10
PGND
GND
CSI Interface
Figure 2-9 CSI Interface
J8
Pin
Signal
Function
5VIN
5V
5VIN
5V
GND
GND
GND
GND
Page | 25
2.3.9
P2V8_VGEN6
2.8V
CSI_MCLK
CSI clock
GND
GND
CSI_RST
CSI reset
CSI_EN
10
I2C4_SCL
11
I2C4_SDA
12
GND
GND
13
CSI_CLK0M
14
CSI_CLK0P
15
GND
GND
16
CSI_D0M
17
CSI_D0P
18
GND
GND
19
CSI_D1M
20
CSI_D1P
Camera Interface
Figure 2-10 Camera Interface
Page | 26
J9
Pin
Signal
Function
GND
GND
NC
NC
NC
NC
CSI0_DAT12
CSI0_DAT13
CSI0_DAT14
CSI0_DAT15
CSI0_DAT16
CSI0_DAT17
10
CSI0_DAT18
11
CSI0_DAT19
12
NC
NC
13
NC
NC
14
GND
GND
15
CSI0_PIXCLK
16
GND
GND
17
CSI0_HSYNC
CSIO HSYNC
18
NC
NC
19
CSI0_VSYNC
CSIO VSYNC
20
VDD_NVCC
3.3V
21
CAM_MCLK
Camera clock
22
NC
NC
23
GND
GND
24
NC
NC
25
CAM_RST
CSI0 reset
26
CAM_EN
27
I2C4_SDA
28
I2C4_SCL
29
GND
GND
30
P1V8_SW4
1.8V
Page | 27
J10
Pin
Signal
Function
VDD_NVCC
3.3V
JTAG_TMS
GND
GND
JTAG_TCK
Test clock
GND
GND
JTAG_TDO
JTAG_MOD
Test mode
JTAG_TDI
JTAG_nTRST
10
RESET_N
Reset
Page | 28
J11
Pin
Signal
Function
USB_OTG_VBUS
+5V
USB_OTG_DN
USB data-
USB_OTG_DP
USB data+
USB_OTG_ID
USB ID
GND
GND
Page | 29
J18
Pin
Signal
Function
UART2_TXD
UART2_RXD
GND
GND
Page | 30
J13
Pin
Signal
Function
VDD_NVCC
3.3V
5VIN
5V
GND
GND
GND
GND
GPIO4_16
GPIO
CSPI3_CLK
SPI3 clock
GPIO4_17
GPIO
CSPI3_MOSI
GPIO4_18
GPIO
10
CSPI3_MISO
11
GPIO4_19
GPIO
12
CSPI3_CS0
13
CSPI3_CS1
Page | 31
CSPI2_CS1
15
GPIO4_31
GPIO
16
CSPI2_MOSI
17
GPIO5_05
GPIO
18
CSPI2_MISO
19
GPIO5_06
GPIO
20
CSPI2_CS0
21
GPIO5_07
GPIO
22
CSPI2_CLK
SPI2 clock
23
GPIO5_08
GPIO
24
UART3_RXD
25
GPIO4_26
GPIO
26
UART3_TXD
27
GPIO4_27
GPIO
28
UART4_RXD
29
CSPI3_RDY
30
UART4_TXD
31
I2C3_SCL
32
UART5_RXD
33
I2C3_SDA
34
UART5_TXD
35
I2C4_SCL
36
PWM1
37
I2C4_SDA
38
PWM2
39
GND
GND
40
PWM3
Page | 32
J14
Pin
Signal
Function
V5V_SDA
+5V
SDA_USB_DN
SDA_USB_DP
NC
NC
GND
GND
Note:
The RIoTboard has hardware to support Freescales OpenSDA interface. Currently this
interface has not been enabled in software
Page | 33
J15
Pin
Signal
Function
TD1+
TD1+ output
TD1-
TD1- output
TD2+
TD2+ output
TD2-
TD2- output
TCT
RCT
RD1+
RD1+ input
RD1-
RD1- input
RD2+
RD2+ input
10
RD2-
RD2- input
Page | 34
GRLA
12
GRLC
13
YELC
14
YELA
HUB1
Pin
Signal
Function
USB_PWR3
+5V
USB_DM3
USB data-
USB_DP3
USB data+
GND
GND
USB_PWR4
+5V
USB_DM4
USB data-
USB_DP4
USB data+
GND
GND
Page | 35
HUB2
Pin
Signal
Function
USB_PWR1
+5V
USB_DM1
USB data-
USB_DP1
USB data+
GND
GND
USB_PWR2
+5V
USB_DM2
USB data-
USB_DP2
USB data+
GND
GND
Page | 36
SW1
Pin
Signal
Function
P3V0_STBY
P3V0_STBY
P3V0_STBY
P3V0_STBY
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
VDD_NVCC
EIM_DA11
BT_CFG2_3
10
EIM_DA12
BT_CFG2_4
11
EIM_DA13
BT_CFG2_5
12
EIM_DA14
BT_CFG2_6
13
EIM_DA5
BT_CFG1_5
14
EIM_DA6
BT_CFG1_6
15
BOOT_MODE0
BOOT_MODE0
16
BOOT_MODE1
BOOT_MODE1
Page | 37
S1
Pin
Signal
Function
GND
GND
POR_B
System reset
NC
NC
NC
NC
Page | 38
2.3.19 LEDs
Figure 2-20 LEDs
LED
Reference
Function
D45
User-defined LED
D46
User-defined LED
D47
Power LED
D49
OpenSDA LED
Page | 39
Getting Started
Before you start to use RIoTboard, please read the following sections to get yourself
familiar with the system images, driver code and tools which might be involved during
development process.
NOTE:
3.1
All images and tools for Android and Linux can be downloaded
from www.element14.com/riotboard
Software Features
The table shown below lists the versions of Linux and Android systems, as well as
the device drivers.
Table 3-1 OS and Drivers
Types
Linux
OS
Ubuntu
Android
Serial
RTC
Net
Display
Device
MMC/SD
Drivers
USB
Audio
Camera
LED
3.2
Notes
Version 3.0.35
Version 11.10
Version 4.3
Series driver
Hardware clock driver
10/100/Gb IEEE1588 Ethernet
Two display ports (LVDS, and HDMI 1.4a)
Two SD 3.0/SDXC card slot & eMMC
5 High speed USB ports (4xHost, 1xOTG)
Analog (headphone & mic) and Digital (HDMI)
Two camera ports (1xParallel, 1x MIPI CSI-2)
User leds driver
Linux System
The following tables list the specific images and eMMC storage patitions required to
build a Linux system.
Table 3-2 Images Required by Linux
Images
u-boot image
kernel image
rootfs image
Paths
u-boot-mx6solo-riot.bin
uImage
oneiric.tgz
Page | 40
Name
Start Offset
Size
File
System
N/A
BOOT
Loader
1MB
N/A
N/A
Kernel
1M
N/A
Primary 1
Rootfs
10M
9MB
Total Other
u-bootmx6soloriot.bin
uImage
EXT3
oneiric.tgz
Content
3.3
Android System
The following tables list the specific images and eMMC storage patitions required to
build an Android system.
Table 3-4 Images Required by Android
Images
u-boot image
boot image
Android system root image
Recovery root image
Paths
u-boot-mx6solo-riot.bin
boot.img
system.img
recovery.img
Name
BOOT
Loader
Start Offset
Size
1MB
File System
N/A
boot.img format,
a kernel +
ramdisk
boot.img format,
a kernel +
ramdisk
Primary 1
Boot
8M
8MB
Primary 2
Recovery
Follow Boot
8MB
Logic 4
(Extended 3)
DATA
follow
Recovery
> 1024MB
Logic 5
(Extended 3)
SYSTEM
Follow DATA
512MB
Logic 6 (Extended 3)
CACHE
follow
SYSTEM
512MB
Logic 7(Extended 3)
VENDOR
follow CACHE
8MB
Logic 9
(Extended 3)
Misc
Follow DATA
8M
N/A
Primary 4
MEDIA
Follow Misc
Total - Other
VFAT
EXT4 Mount at
/data
EXT4. Mount as
/system
EXT4. Mount as
/cache
Ext4 Mount at
/device
Content
bootloader
boot.img
recovery.img
Application data
storage for system
application.
Android system files
under /system/ dir
Android cache, for
image store for OTA
For Store MAC address
files.
For recovery store
bootloader message,
reserve.
For internal media
Page | 41
Name
Start Offset
Size
images
File System
Content
partition, in
/mnt/sdcard/ dir.
Under normal mode, the root file system is mounted from uramdisk. Under
recovery mode, the root file system is mounted from the RECOVERY partition.
3.4
Page | 42
NOTE:
4.1
All images and tools for Android and Linux can be downloaded
from www.element14.com/riotboard
Copy all the system files to a root directory of your hard drive (assume C:\ is
the root directory).
Use a Mini USB cable to connect USB OTG interface on RIoTboard to the USB
Host on PC, and then open a Terminal window;
Set the boot switch SW1 on the RIoTboard to Serial Download Mode
according to the configurations as shown in the following table;
Table 4-1 Boot Switch Configuration Serial Download
Switch
SW1
D1
OFF
D2
ON
D3
ON
D4
ON
D5
OFF
D6
ON
D7
ON
D8
ON
Page | 43
eMMC
--
name = Android-RIOT-eMMC
SD
--
name = Android-RIOT-SD
According to the system you want to boot, run the corresponding MFG tool
on your PC and power up the RIoTboard; the software window is shown below;
(the PC will install HID driver automatically if it is the first time connecting to
the RIoTboard)
For Linux system, the MFG tool is located at :
linux\tools\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER;
For Android system, the MFG tool is located at :
android\tools\Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER;
Page | 44
Click Start in the following window; when download process is done, click Stop to
finish.
Click Start
Page | 45
Power off the RIoTboard and set the boot switches SW1 on it to eMMC boot
mode according to the configuration as shown In the following table;
Switch
SW1
D1
ON
D2
OFF
D3
ON
D4
ON
D5
OFF
D6
ON
D7
ON
D8
ON
D7
OFF
D8
ON
Switch
SW1
D1
ON
D2
OFF
D3
ON
D4
OFF
D5
OFF
D6
ON
After the switch is set, power up the RIoTboard to boot the system.
4.2
Page | 46
Hit any key to stop autoboot: 0 ( press any key to enter u-boot command mode
MX6Solo RIOT U-Boot >
Page | 47
5 Making Images
This Chapter will introduce how to make images by using BSP contained in the ISO. The
BSP is a collection of binary, source code, and support files that can be used to create a
u-boot bootloader, Linux kernel image, and Android file system for i.MX 6Solo RIOT
Board.
Note:
Each instruction has been put a bullets before it to prevent confusion caused by the long
instructions that occupy more than one line in the context.
5.1
5.1.1
5.1.2
$ cd ~
$ cd ~
$ cd ~
$ cd ~ /u-boot-imx
$ export ARCH=arm
$export CROSS_COMPILE=~/fsl-linaro-toolchain/bin/arm-fsl-linux-gnueabi-
$ make distclean
$ make mx6solo_riot_config
Page | 48
$ make
$ mv u-boot.bin u-boot-mx6solo-riot.bin
$export PATH=~/u-boot-imx/tools:$PATH
$ cd ~/linux-imx
$ export ARCH=arm
$ make imx6_defconfig
$ make uImage
After executing the instructions, a kernel image named uImage can be found
under arch/arm/boot/.
Note:
The mkimage is used to build the kernel and ramfs images are automatically generated and
saved under tools/ after compiling u-boot.bin. So please make sure uboot is compiled first
before compiling kernel image.
Copy u-boot-mx6solo-riot.bin and uImage files that are generated by compiling to linux flash
image tool Mfgtools-Rel-4.1.0_130816_MX6DL_UPDATER\ Profiles\MX6DL Linux Update\OS
Firmware\files\ to overwrite the files with the same names and then start over the operations
from step 2) in section 4.1 to verify the Linux system built.
5.2
Please strictly follow the steps listed below to make images for Android system.
5.2.1
$ mkdir ~/bin
$ curl https://raw.github.com/android/tools_repo/stable/repo > ~/bin/repo
$ chmod a+x ~/bin/repo
$ export PATH=~/bin:$PATH
Page | 49
$ mkdir ~/android-imx6-jb4.3-1.0.0
$ cd ~/android-imx6-jb4.3-1.0.0
$ repo init --repo-url=git://github.com/android/tools_repo.git -u
git://github.com/embest-tech/imx-manifest.git m embest_android_jb4.3_1.0.0
$ cd ~/android-imx6-jb4.3-1.0.0
$ repo sync
5.2.2
eMMC Boot
--
BUILD_TARGET_LOCATION ?= emmc
SD Boot
--
BUILD_TARGET_LOCATION ?= sdmmc
$ cd ~/android-imx6-jb4.3-1.0.0
$ source build/envsetup.sh
$ lunch riot_6solo-user
$ make clean
$ make
After executing the instructions, the generated images can be found under
android-imx6-jb4.3-1.0.0/out/target/product/riot_6solo/;
Table 5-1 shown below lists all the images and directories after compilation is
completed.
Page | 50
Notes
root file system, mounted at /
system/
data/
recovery/
boot.img
boot parameters
ramdisk.img
system.img
partition of SD/eMMC card with "dd" command
userdata.img
recovery.img
u-boot.bin
Note:
Android image should be built in user mode;
$ source build/envsetup.sh
$ lunch riot_6solo-user
$ make bootimage
After executing the instructions, a boot.img image can be found under
android-imx6-jb4.3-1.0.0/out/target/product/riot_6solo/.
Note:
mx6solo-riot.bin) files created upon compilation, to the Android flash tool folder MfgtoolsRel-4.1.0_130816_MX6DL_UPDATER\
Profiles\MX6DL
Linux
Update\OS
Firmware\files\android to overwrite the files with the same names and repeat the operations
from step 2) in 4.1 to verify the Android system built.
Page | 51
Avoid carpets in cool, dry areas. Leave development kits in their anti-static
packaging until ready to be installed.
Dissipate static electricity before handling any system components (development
kits) by touching a grounded metal object, such as the system unit unpainted
metal chassis.
If possible, use antistatic devices, such as wrist straps and floor mats.
Always hold a evaluation board by its edges. Avoid touching the contacts and
components on the board.
Take care when connecting or disconnecting cables. A damaged cable can cause a
short in the electrical circuit.
Prevent damage to the connectors by aligning connector pins before you connect
the cable. Misaligned connector pins can cause damage to system components at
power-on.
When disconnecting a cable, always pull on the cable connector or strain-relief
loop, not on the cable itself.
Page | 52
53