DFI FS051 User manual

1
FS051
2.5” Pico-ITX
User’s Manual
A40000545

2
Copyright
This publication contains information that is protected by copyright. No part of it may be re-
produced in any form or by any means or used to make any transformation/adaptation without
the prior written permission from the copyright holders.
This publication is provided for informational purposes only. The manufacturer makes no
representations or warranties with respect to the contents or use of this manual and specifi-
cally disclaims any express or implied warranties of merchantability or fitness for any particular
purpose. The user will assume the entire risk of the use or the results of the use of this docu-
ment. Further, the manufacturer reserves the right to revise this publication and make changes
to its contents at any time, without obligation to notify any person or entity of such revisions
or changes.
Changes after the publication’s first release will be based on the product’s revision. The website
will always provide the most updated information.
© 2015. All Rights Reserved.
Trademarks
Product names or trademarks appearing in this manual are for identification purpose only and
are the properties of the respective owners.
FCC and DOC Statement on Class B
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 reason-
able protection against harmful interference when the equipment is operated in a residential
installation. This equipment generates, uses and can radiate radio frequency energy and, if not
installed and used in accordance with the instruction manual, 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 encour-
aged 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 the 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.
Notice:
1. The changes or modifications not expressly approved by the party responsible for compli-
ance could void the user’s authority to operate the equipment.
2. Shielded interface cables must be used in order to comply with the emission limits.

3
Copyright.............................................................................................................2
Trademarks........................................................................................................2
FCC and DOC Statement on Class B.....................................................2
About this Manual..........................................................................................4
Warranty ............................................................................................................4
Static Electricity Precautions......................................................................4
Safety Measures..............................................................................................4
About the Package.........................................................................................5
Chapter 1 - Introduction.............................................................................6
Specifications ................................................................................................6
Chapter 2 - Hardware Installation................................................7
Board Layout.................................................................................................7
Block Diagram...............................................................................................8
Mechanical Diagram....................................................................................8
Jumper............................................................................................................9
Jumper Description.......................................................................................9
Connector.......................................................................................................9
Connector List..............................................................................................9
Connector Settings .....................................................................................10
Chapter 3 - Software User Guide............................................... 12
Introduction ................................................................................................12
Setup Build Environment......................................................................... 12
Installing and Build.....................................................................................12
Download Source Code and Checkout the Latest Version.............................. 12
Build and Flashing the SD Card...................................................................12
Create SD/MMC Card Using Linux Host.............................................. 13
Requirements............................................................................................. 13
Copying the Boot Loader Image..................................................................13
Copying the Kernel Image...........................................................................13
Copying the Root File System (Rootfs)......................................................... 13
Applications and Testing..........................................................................14
Ethernet Test.............................................................................................. 14
USB...........................................................................................................14
SD.............................................................................................................14
I2C............................................................................................................15
Create a Virtual Machine Environment................................................15
Introduction ...............................................................................................15
Setting up Work Environment......................................................................15
Setting up VM Environment......................................................................... 16
Chapter 4 - System Recovery.................................................................17
Download the SD Image......................................................................... 17
Write an SD/MMC Card Using Linux (Ubuntu)..................................17
Write an SD/MMC Card Using Windows ............................................17
Introduction ...............................................................................................17
Preparations...............................................................................................17
Create the SD-Card.....................................................................................17
Write an SD/MMC Card Using MAC OS X...........................................18
Graphical Interface .....................................................................................18
Command Line...........................................................................................18
Alternative Method......................................................................................18
Table of Contents

4
About this Manual
An electronic file of this manual is included in the CD. To view the user’s manual in the CD, in-
sert the CD into a CD-ROM drive. The autorun screen (Main Board Utility CD) will appear. Click
“User’s Manual” on the main menu.
Warranty
1. Warranty does not cover damages or failures that arised from misuse of the product, in-
ability to use the product, unauthorized replacement or alteration of components and prod-
uct specifications.
2. The warranty is void if the product has been subjected to physical abuse, improper instal-
lation, modification, accidents or unauthorized repair of the product.
3. Unless otherwise instructed in this user’s manual, the user may not, under any circum-
stances, attempt to perform service, adjustments or repairs on the product, whether in or
out of warranty. It must be returned to the purchase point, factory or authorized service
agency for all such work.
4. We will not be liable for any indirect, special, incidental or consequencial damages to the
product that has been modified or altered.
Static Electricity Precautions
It is quite easy to inadvertently damage your PC, system board, components or devices even
before installing them in your system unit. Static electrical discharge can damage computer
components without causing any signs of physical damage. You must take extra care in han-
dling them to ensure against electrostatic build-up.
1. To prevent electrostatic build-up, leave the system board in its anti-static bag until you are
ready to install it.
2. Wear an antistatic wrist strap.
3. Do all preparation work on a static-free surface.
4. Hold the device only by its edges. Be careful not to touch any of the components, contacts
or connections.
5. Avoid touching the pins or contacts on all modules and connectors. Hold modules or con-
nectors by their ends.
Safety Measures
To avoid damage to the system:
• Use the correct AC input voltage range.
To reduce the risk of electric shock:
• Unplug the power cord before removing the system chassis cover for installation or servic-
ing. After installation or servicing, cover the system chassis before plugging the power
cord.
Important:
Electrostatic discharge (ESD) can damage your processor, disk drive and other com-
ponents. Perform the upgrade instruction procedures described at an ESD worksta-
tion only. If such a station is not available, you can provide some ESD protection by
wearing an antistatic wrist strap and attaching it to a metal part of the system chas-
sis. If a wrist strap is unavailable, establish and maintain contact with the system
chassis throughout any procedures requiring ESD protection.

5
About the Package
The package contains the following items. If any of these items are missing or damaged,
please contact your dealer or sales representative for assistance.
• One FS051 board
• One COM port cable (Length: TBD)
• One Serial ATA data cable (Length: TBD)
• One DVD
• One QR (Quick Reference)
• One Heat sink (Height: TBD)
Optional Items
• USB port cable (Length: TBD)
• Power adapter (25W, 5V) (Length: TBD)
The board and accessories in the package may not come similar to the information listed
above. This may differ in accordance to the sales region or models in which it was sold. For
more information about the standard package in your region, please contact your dealer or
sales representative.
Before Using the System Board
Before using the system board, prepare basic system components.
If you are installing the system board in a new system, you will need at least the following
internal components.
• Storage devices such as hard disk drive, CD-ROM, etc.
You will also need external system peripherals you intend to use which will normally include at
least a keyboard, a mouse and a video display monitor.

6
Chapter 1 - Introduction
Specifications
Chapter 1
Chapter 1 Introduction www.dfi.com
System Processor • Freescale i.MX6 Cortex-A9 DualLite, 1.0 GHz
System Memory • 1GB SDRAM Memory Down
• Single Channel DDR3 800MHz
Flash • 8MB NOR Flash
Graphics Display • 1 x HDMI
• 1 x LVDS
• HDMI: resolution up to 1920x1080 @ 60Hz
• LVDS: 18/24-bit, resolution up to 2560x1600 @ 60Hz
Dual Displays • HDMI + LVDS
Expansion Interfaces • 1 x Full-size Mini PCIe (PCIe/USB)
• 1 x SD
• 1 x SIM
Ethernet Controller • 1 x Micrel KSZ9013RNX Ethernet PHY (10/100/1000Mbps)
Rear I/O Ethernet • 1 x GbE (RJ-45)
Serial • 1 x RS-485 (3.5mm, terminal block)
USB • 2 x USB 2.0
Display • 1 x HDMI
Internal I/O Serial • 1 x RS-232 (2.0mm pitch)
USB • 1 x USB 2.0
Display • 1 x LVDS LCD Panel Connector
SATA • 1 x SATA 2.0 (up to 3Gb/s) (Quad processor only)
DIO • 1 x 7-bit DIO
CANBus • 1 x CANBus
WatchDog
Timer Output & Interval • System Reset, Programmable via Software from 1 to 255
Seconds
Power Type • Single 5V +/-10% DC
Connector • DC Jack
Consumption • 3W
OS Support • Ubuntu 12.04 (Linux kernel 3.0.35)
• Android (Lollipop 5.0.2)
• Yocto (Daisy 1.6.2)
Environment Temperature • Operating: 0 to 60°C
• Storage: -40 to 85°C
Humidity • Operating: 5 to 95% RH
• Storage: 5 to 95% RH
Mechanical Dimensions • 2.5" Pico-ITX Form Factor
• 100mm (3.94") x 72mm (2.83")
Height • PCB: TBD
• Top Side: TBD, Bottom Side: TBD
Certification • CE, FCC

www.dfi.com
7
Chapter 2 Hardware Installation
Chapter 2
Chapter 2 - Hardware Installation
This chapter introduces the startup procedures of FS051, including jumper setting and device
integration. It also introduces the setting of switches, indicators and also shows the mechani-
cal drawings. Be sure to real all safety precautions before you begin installation procedure.
Board Layout
Top View
Bottom View

www.dfi.com
8
Chapter 2 Hardware Installation
Chapter 2
Block Diagram Mechanical Diagram
13
41
#2 #1
69.08
72.00
3.04
69.08
72.00
3.04
13.95 30.70 49.50 63.40 78.00 90.03 97.05
100.00
3.00
Freescale
i.MX6
Engine
DDR3 800MHz
Memory Down
PCIe x1
DIO
CANBus CANBus
NOR Flash
Full-size
Mini PCIe
USB 2.0
GLAN RGMII
SATA 2.0 SATA 1x
7-bit DIO
SPI
SD
SD
SIM
UART RS-485 1x
UART RS-232 1x
I2C
USB2514BUSB HSIC
USB 3x
USB 2.0
HDMI HDMI
LVDS LVDS

www.dfi.com
9
Chapter 2 Hardware Installation
Chapter 2
Connector
Connector List
Jumper
Jumper Description
Cards can be configured by setting jumpers. A jumper is a metal bridge used to close an elec-
tric circuit. It consists of two metal pins and a small metal clip (often protected by a plastic
cover) that slides over the pins to connect them. To close a jumper, you connect the pins with
the clip. To open a jumper, you remove the clip. Sometimes a jumper will have three pins, la-
beled 1, 2 and 3. In this case you would connect either pins 1 and 2 or 2 and 3.
The jumper settings are schematically depicted in this manual as follows.
A pair of needle-nose pliers may be helpful when working with jumpers. If you have any
doubts about the best hardware configuration for your application, contact your local distribu-
tor or sales representative before you make any changes. Generally, you simply need a stan-
dard cable to make most connections.
Warning:
To avoid damaging the computer, always turn off the power supply before setting
jumpers.
DC in DC power input connector DC power jack
RS-485 RS-485 connector 2 x 1 connector, pitch 3.5mm
HDMI HDMI connector
JCOM1 RS-232 pin header 5 x 2 header, pitch 2.0mm
JDC in Power input pin header 2 x 1 connector, pitch 4.2mm
JEMBUX Proprietary connector DF13-20DP-1-25V
JFP Front panel connector 5 x 2 header, pitch 2.0mm
JI2C I2C connector 4 x 1 header, pitch 2.54mm
JLVDS LVDS connector DF13-20DP-1-25V
JMISC Miscellaneous connector 5 x 2 header, pitch 2.0mm
JRS-485 Reserved for X-Port connect 2 x 1 header, pitch 2.0mm
JSIM SIM connector + SATA PWR 4 x 2 header, pitch 2.54mm
LAN Ethernet connector RJ-45
MPCIE Mini PCI Express connector
SATA SATA connector
USB USB connector USB Type A

www.dfi.com
10
Chapter 2 Hardware Installation
Chapter 2
Connector Settings
Pin Description
1RS-485-
2RS-485+
RS-485
Pin Description Pin Description
1NC 2RS-232_RX
3RS-232_TX 4NC
5GND 6NC
7NC 8NC
9NC 10 NC
JCOM 1
Pin Description
1GND
2+5V
JDC in
Pin Description Pin Description
1+5V 2+3.3V
3+5V 4+3.3V
5GND 6GPIO0
7MCU_SS 8GPIO1
9MCU_CLK 10 GPIO2
11 MCU_MOSI 12 GPIO3
13 MCU_MISO 14 GPIO4
15 GND 16 GPIO5
17 I2C CLK 18 GPIO6
19 I2C DAT 20 NC
JEMBUX
Remark:
GPIO pin control by MCU (level 3.3V)
MCU_SS: SPI Slave Select (active low, output from master)
MCU_CLK: SPI Serial Clock (output from master)
MCU_MOSI: SPI Master Output, Slave Input (output from master)
MCU_MISO: Master Input, Slave Output (output from slave)
Pin Description Pin Description
1+5V 2LED control by MCU
3+5V 4LED control by CPU
5CPU power on 6GND
7GPIO7 8GND
9GPIO8 10 GND
JFP
Pin Description
1+3.3V
2I2C_SCL
3I2C_SDA
4GND
JI2C
Remark:
GPIO pin control by MCU (level 3.3V)
Pin Description Pin Description
1+5V 2+3.3V
3+5V 4+3.3V
5LVDS0_CLK- 6Backlight EN (3.3V)
7LVDS0_CLK+ 8Backlight CTL (3.3V)
9GND 10 GND
11 LVDS0_TX0- 12 LVDS0_TX1-
13 LVDS0_TX0+ 14 LVDS0_TX1+
15 GND 16 GND
17 LVDS0_TX2- 18 LVDS0_TX3-
19 LVDS0_TX2+ 20 LVDS0_TX3+
JLVDS

www.dfi.com
11
Chapter 2 Hardware Installation
Chapter 2
Pin Description Pin Description
1X-Port RS-485 TX- 2+5V
3X-Port RS-485 TX+ 4USB D-
5GND 6USB D+
7CAN_H 8GND
9CAN_L 10 GND
JMISC
Pin Description
1RS-485TX-
2RS-485TX+
JRS-485
Pin Description Pin Description
1PCIe_UIM_PWR 2PCIe_UIM_RST
3PCIe_UIM_CLK 4GND
5PCIe_UIM_VPP 6PCIe_UIM_DATA
7+5V 8GND
JSIM
Remark:
UIM: User Identity Module (UIM) Signals
UIM_VPP: Variable supply voltage (e.g., programming voltage) for class A devices. This signal
is reserved for future use for devices of other classes. Compliant to the ISO/IEC 7816-3 speci-
fication (VPP).
5V on pin 7 is reserved for SATA power

www.dfi.com
12
Chapter 3 Software User Guide
Chapter 3
Chapter 3 - Software User Guide
This chapter details the Linux operation on FS051.
Introduction
This chapter details the Linux operation on FS051 platform. This platform is an embedded
system with Linux kernel 3.0.35. It contains all system-required shell commands and drivers
ready. You can evaluate and develop under Ubuntu 12.04 LTS environment.
There are three major boot components for Linux, “u-boot.bin”, “uImage” and “root file sys-
tem”. The “u-boot.bin” is for initializing peripheral hardware parameters; the “uIm- age” is the
Linux kernel image and the “File System” is for Linux O.S. used.
It will not be able to boot into Linux environment successfully if one of above three files is
missing from booting media (in FS051, we use SD/MMC card).
Setup Build Environment
This section explains how to set up the build environment, install and build, and set up the
host environment.
Download Source Code and Checkout the Latest Version
# 1.1 u-boot source (u-boot-2009)
git clone https://github.com/embux/u-boot-imx.git u-boot-imx_2009
cd u-boot-imx_2009
git checkout imx_2009_ebx
# 1.2 Kernel source(imx_3.0.35)
$ git clone https://github.com/embux/linux-imx6.git
$ cd linux-imx6.git
$ git checkout imx_3.0.35_1.0.0_ebx
Build and Flashing the SD Card
- u-boot
$make distclean
$make mx6dl_sabresd_config
$make
$ sudo dd if=u-boot.bin of=/dev/sdb bs=512 seek=2 skip=2 conv=fsync
- Kernel build and flash to SD Card (sdb, mounted /mnt)
$make clean
$make imx6_defconfig
$make -j4 uImage
Note:
If you need, more detailed instructions can be found at L3.0.35_4.1.0_LINUX_DOCS in
the file Setting_Up_LTIB_Host.pdf (https://cache.freescale.com/secured/32bit/doc/sup-
port_info/L3.0.35_4.1.0_docs.tar.gz? gda =1428423300_12712125f6c749dde454e0
f5d9b338d5&fileExt=.gz)
Installing and Build
Follow the steps below to preparing the build environment. Entering the command without “$”.
# 0.1 pre-install
$ sudo apt-get install git u-boot-tools lzop
# 0.2 Cross Compiler As a result of the first two points, we now recommend these simple
steps to install a cross-compiler:
$ sudo apt-get install gcc-arm-linux-gnueabihf
# check gcc version
$ arm-linux-gnueabihf-gcc -v
# 0.3 add export to .bashrc
export ARCH=arm
export CROSS_COMPILE=arm-linux-gnueabihf-

www.dfi.com
13
Chapter 3 Software User Guide
Chapter 3
Create SD/MMC Card Using Linux Host
Requirements
An SD/MMC card reader, like a USB card reader, is required. It will be used to transfer the
boot loader and kernel images to initialize the partition table and copy the root file system. To
simplify the instructions, it is assumed that a 4GB SD/MMC card is used.
Any Linux distribution can be used for the following procedure. It is recommended to use a
Linux distribution that LTIB has been tested against such as Ubuntu 9.04.
The Linux kernel running on the Linux host will assign a device node to the SD/MMC card
reader. The kernel might decide the device node name or udev rules might be used. In the fol-
lowing instructions, it is assumed that udev is not used.
To identify the device node assigned to the SD/MMC card, enter the command:
$ cat /proc/partitions
major minor #blocks name
8 0 175825944 sda
8 1 254976 sda
8 2 1 sda
8 5 175567872 sda
8 0 7761920 sdb
8 0 2048000 sdb
In this example, the device node assigned is /dev/sdb (a block is 512B large).
Copying the Boot Loader Image
Enter the following command to copy the U-Boot image to the SD/MMC card:
$ sudo dd if=u-boot.bin of=/dev/sdb bs=512 seek=2 skip=2 conv=fsync
This assumes a pre-built U-Boot image delivered with the BSP or built from the U- Boot source
code. If using a non-padded U-Boot image, "skip=2" should be omitted from the above com-
mand line. The first 1 KB of the SD/MMC card, that includes the partition table, will be pre-
served.
Copying the Kernel Image
The following command will copy the kernel image to the SD/MMC card:
$ sudo dd if=uImage of=/dev/sdb bs=512 seek=2048 conv=fsync
This will copy uImage to the media at offset 1 MB (bs x seek = 512 x 2048 = 1MB).
Copying the Root File System (Rootfs)
First, a partition table must be created. If a partition already exists and it is big enough for the
file system you want to deploy, then you can skip this step.
To create a partition, at offset 16384 (in sectors of 512 bytes) enter the following command:
$ sudo fdisk /dev/sdb
Note:
On most Linux host operating systems, SD card will be mounted automatically upon
insertion. Therefore, before running fdisk, please make sure that SD card is unmount-
ed (via ‘sudo umount /dev/sdb’).
Type the following parameters (each followed by <ENTER>):
u [switch the unit to sectors instead of cylinders]
d [repeat this until no partition is reported by the ‘p’ command]
n [create a new partition]
p [create a primary partition]
1 [the firs partition]
16384 [start at offset sector #16384, i.e. 8MB, which leaves enough space for the kernel, the
boot loader and its configuration data]
<enter> [using the default value will create a partition that spans to the last sector of the
medium]
w [this writes the partition table to the medium and fdisk exits]
The file system format ext3 or ext4 is a good option for removable media due to the built- in
journaling. Run the following command to format the partition:
$ sudo mkfs.ext3 /dev/sdb1
Or
$ sudo mkfs.ext4 /dev/sdb1
Copy the target file system to the partition:
$ mkdir /home/user/mountpoint
$ sudo mount /dev/sdb1 /home/user/mountpoint

www.dfi.com
14
Chapter 3 Software User Guide
Chapter 3
Download and save the demo rootfs from https://releases.linaro.org/12.04/ubuntu/precise- im-
ages/ubuntu-desktop/linaro-precise-ubuntu-desktop-20120426-119.tar.gz
Extract rootfs package to certain directory: extract rootfs.ext2.gz to /home/user/rootfs for ex-
ample:
$ gunzip rootfs.ext2.gz
$ mount -o loop -t ext2 rootfs.ext2 /home/user/rootfs
Assume that the root file system files are located in /home/user/rootfs as in the previous step:
$ cd /home/user/rootfs
$ sudo cp -a * /home/user/mountpoint
$ sudo umount /home/user/mountpoint
$ sync
The file system content is now on the media.
Applications and Testing
Ethernet Test
A simple ping test. You can increase the size of the packet press -s switch
# ping -s 500 192.168.0.100
PING 192.168.0.100 (192.168.0.100): 1000 data bytes
1008 bytes from 192.168.0.100: seq=0 ttl=64 time=1.980 ms
1008 bytes from 192.168.0.100: seq=1 ttl=64 time=0.459 ms
1008 bytes from 192.168.0.100: seq=2 ttl=64 time=0.461 ms
1008 bytes from 192.168.0.100: seq=3 ttl=64 time=0.475 ms
--- 192.168.0.100 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss.
USB
Plug in a USB memory stick, you will see a message like this (possible use dmesg command to
see how your USB is detected).
# usb 1-1.1: device v17ef p3818 is not supported sd 1:0:0:0: [sdc] No Caching mode page
present
sd 1:0:0:0: [sdc] Assuming drive cache: write through sd 1:0:0:0: [sdc] No Caching mode
page present
sd 1:0:0:0: [sdc] Assuming drive cache: write through sd 1:0:0:0: [sdc] No Caching mode
page present
sd 1:0:0:0: [sdc] Assuming drive cache: write through
Mount the USB (in this example the USB is formatted as FAT)
# mount /dev/sdc1 /media
# ls -la /media
Now, you can copy a video to /media and play it. This will perform a simple USB test.
SD
Plug the SD card and find out where the card is mapped. After typing dmesg at you will see
something like this:
# dmesg | tail
mmc0: new high speed SD card at address aaaa
mmcblk1: mmc0:aaaa SU02G 7.8 GiB
mmcblk1: p1
Your card is mapped in /dev/mmcblk0.

www.dfi.com
15
Chapter 3 Software User Guide
Chapter 3
Create a Virtual Machine Environment
Introduction
The use of a virtual machine running a specific Linux Ubuntu distribution is highly recom-
mended. A virtual machine will create a dedicated, close environment that will ensure that a
step-by-step procedure will guide the user until the end without problems.It also prevent risks
ofsystem corruption or that compiling environment is not clean It also allows to be sure that
used libraries are always the same, and updated.
System Requirements. To run the procedure described in the following sections, it is necessary
to have: PC with virtual machine running Linux Ubuntu 10.04 with at least 40 GB of free disk
space.
This procedure can be performed also on native Linux OS. The use of a VM only reduces sys-
tem differences and can follow a standard procedure to compile.
Setting up Work Environment
Install the Virtual Machine
VMware PlayerTM is recommended for this operation. A step-by-step installation procedure is
provided.
Download the VM player Download the player from VMware Player website:
You can find the latest st version at http://www.vmware.com/products/player/ .
Choose the version dedicated to the OS used.
Install the VM on your system Open the installer and follow the instructions.
For more information, check the VMware documentation:
http://www.vmware.com/pdf/VMwarePlayerManual10.pdf
Download Ubuntu disk image A 64 bit 10.04 Ubuntu distro to run this procedure is recom-
mended. It can be downloaded from http://old- releases.ubuntu.com/releases/lucid/
Create a new VM running Ubuntu 10.04 Click on VMware Player icon.
Choose “Create a New Virtual Machine” from menu on the right Choose “Installer disk image
file (iso)” and select the downloaded ubuntu iso image.. Press Next button. Then choose your
name, the username and the password. Fill these fields and click on next button. Choose the
VM name: EA21-10.04 and click next. Set harddisk size at least 20 GB. Select “split virtual disk
into multiple files” option. Now it is necessary to set VM performances by clicking on “custom-
ize hardware” button.
I2C
# sudo apt-get install i2c-tool
# i2cdetect 1
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1. I will probe address range 0x03-0x77. Continue? [Y/n] y
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- 27 -- -- -- -- -- -- -- --
30: 30 -- -- -- -- -- -- 37 -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- 48 -- 4a 4b -- -- -- --
50: UU 51 -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- -- # [/code]

www.dfi.com
16
Chapter 3 Software User Guide
Chapter 3
Memory Options:
- 2 GB minimum (memory swapping especially during java compiling)
- 4 GB+ perfect (no memory swapping during build operations)
Attention
The memory size must be chosen according to the amount of free memory on the host com-
puter. When large amount of memory are assigned to VM, then the host OS could repeatedly
swap or page, leading to a drastic decrease of computer’ s performances.
CPUs: All the available CPU cores of the host PC should be assigned to VM execution, espe-
cially for the first compiling which requires a lot of time. After the first phase, it is possible to
reduce the number of CPU cores, if desired.
Then click on “Finish” button and Ubuntu installation will start. When the installation has
ended, it is possible that it is necessary to login from console and launch the GUI by running
the command:
startx
Setting up VM Environment
Update the system:
$ sudo apt-get update
Install required libraries for compiling process:
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \ x11proto-core- dev
libx11-dev lib32readline5-dev lib32z-dev \ libgl1-mesa-dev g++- multilib
mingw32 tofrodos python-markdown \ libxml2-utils xsltproc uuid-devliblzo2-dev

www.dfi.com
17
Chapter 4 System Recovery
Chapter 4
Chapter 4 - System Recovery
This chapter describes the steps to create an new SD/MMC card to boot up an FS051 board.
When things go wrong, we could take this SD/MMC card as the backup or the new system to
start.
Download the SD Image
Downloaded the SD card image: go to https://github.com/embux/, and choose the right im-
age for your platform (in this case: ICM-2010_Ubuntu), in Readme.md part, you will find the
link for “The Linux Ubuntu12 SD Card Image for ICM-2010 download from Google Driver”, just
click on it and it will start download immediately. Once download has finished, you’ll have a .xz
file (ex: ea2mx6dl-ubuntu12-full.img.xz).
Write an SD/MMC Card Using Linux (Ubuntu)
• From the terminal run df -h.
• Connect the SD card reader with the SD card inside.
• Run df -h again and look for the new device that wasn’t listed last time.
Record the device name of the filesystem’s partition, for example:
/dev/sdc1.
• Unmount the partition so that you will be allowed to overwrite the disk:
sudo unmount /dev/sdc1
• Decompressed the xz file which download in sec 4.1
$ xz –d ubuntu12-full.img.xz
• In the terminal, write the image to the card with this command, using the disk device name
from above. Read the above step carefully to be sure you use the correct disk number here:
(This will take a few minutes)
$ sudo dd if=<image_path>/ubuntu12-full.img of=/dev/sdc bs=8M conv=fsync
Write an SD/MMC Card Using Windows
Introduction
This guide describes the process of writing these images to a SD-Card on a Windows PC (un-
der Linux you would use the dd command).
Preparations
• Download the SD-Card image which described in the section of “Download the SD image“.
• The downloaded file is in the xz file format and needs to be uncompressed. xz utility
(http://tukaani.org /xz/) can be used if no suitable application is installed on your computer.
• Make sure that your target SD-Card is big enough to contain this file (8G recommend)
• Download and unzip Image Writer for Windows
(http://sourceforge.net/projects/win32diskimager/files/)
Create the SD-Card
• Insert the SD-Card into your computer and check which drive letter it got assigned.
• Open Win32DiskImager.exe
- Click the FileOpen Icon and select the unzipped .bin file
- Select the letter of your SD-Card in the device drop-down menu
- Double check if you have chosen the right drive! You may damage your PC or data other-
wise.

www.dfi.com
18
Chapter 4 System Recovery
Chapter 4
• Press write to start writing the image to the card. (This may take a couple of minutes).
• After the Program is finished, you can eject your SD-Card.
• Insert it into your target device, plug-in power cable and you could start using the device.
Write an SD/MMC Card Using MAC OS X
On Mac OS we could use the command line dd tool or using the graphical tool ImageWriter to
write the image to the SD/MMC card.
Graphical Interface
• Connect the SD card reader with the SD card inside. Note that it must be formatted in
FAT32.
• From the Apple menu, choose About This Mac, then click on More info...; if you are using
Mac OS X 10.8.x Mountain Lion or newer then click on System Report.
• Click on USB (or Card Reader if using a built-in SD card reader) then search for your SD
card in the upper right section of the window. Click on it, then search for the BSD name in the
lower right section; it will look something like ‘diskn’ where n is a number (for example, disk4).
Make sure you take a note of this number.
• Unmount the partition so that you will be allowed to overwrite the disk; to do this, open
Disk Utility and unmount it (do not eject it, or you will have to reconnect it). Note that On Mac
OS X 10.8.x Mountain Lion, “Verify Disk” (before unmounting) will display the BSD name as “/
dev/disk1s1” or similar, allowing you to skip the previous two steps.
• From the terminal run:
sudo dd bs=1m if=<image_path>/ubuntu12-full-image.img of=/dev/diskn
Remember to replace n with the number that you noted before!
Command Line
• If you are comfortable with the command line, you can image a card without any additional
software. Run:
diskutil list
• Identify the disk (not partition) of your SD card e.g. disk4 (not disk4s1):
diskutil unmountDisk /dev/<disk# from diskutil>
e.g. diskutil unmountDisk /dev/disk4
sudo dd bs=1m if=image.img of=/dev/<disk# from diskutil>
e.g. sudo dd bs=1m if=2015-02-16-raspbian-wheezy.img of=/dev/disk4
This may result in an dd: invalid number ‘1m’ error if you have GNU coreutils installed. In that
case you need to use 1M:
sudo dd bs=1M if=image.img of=/dev/<disk# from diskutil>
This will take a few minutes.
Alternative Method
Note: Some users have reported issues with using Mac OS X to create SD cards.
These commands and actions need to be performed from an account that has administrator
privileges.
• From the terminal run df -h.
• Connect the SD card reader with the SD card inside.
• Run df -h again and look for the new device that wasn't listed last time.
Record the device name of the filesystem's partition, for example /dev/disk3s1.
• Unmount the partition so that you will be allowed to overwrite the disk:
sudo diskutil unmount /dev/disk3s1
(or open Disk Utility and unmount the partition of the SD card (do not eject it, or you will
have to reconnect it)
• Using the device name of the partition, work out the raw device name for the entire disk by
omitting the final "s1" and replacing "disk" with "rdisk". This is very important as you will lose
all data on the hard drive if you provide the wrong device name. Make sure the device name
is the name of the whole SD card as described above, not just a partition of it (for example,
rdisk3, not rdisk3s1). Similarly, you might have another SD drive name/number like rdisk2 or
rdisk4; you can check again by using the df -h command both before and after you insert your
SD card reader into your Mac. For example,
/dev/disk3s1 becomes /dev/rdisk3.
• In the terminal, write the image to the card with this command, using the raw disk device
name from above. Read the above step carefully to be sure you use the correct rdisk number
here:
sudo dd bs=1m if=2015-02-16-raspbian-wheezy.img of=/dev/rdisk3
If the above command reports an error (dd: bs: illegal numeric value), please change bs=1m
to bs=1M.

www.dfi.com
19
Chapter 4 System Recovery
Chapter 4
If the above command reports an error dd: /dev/rdisk3: Permission denied then that is be-
cause the partition table of the SD card is being protected against being overwritten by Ma-
cOS. Erase the SD card's partition table using this command:
sudo diskutil partitionDisk /dev/disk3 1 MBR "Free Space" "%noformat%" 100%
That command will also set the permissions on the device to allow writing. Now try the dd
command again.
Note that dd will not feedback any information until there is an error or it is finished; informa-
tion will be shown and the disk will re-mount when complete. However if you wish to view the
progress you can use ‘ctrl-T’; this generates SIGINFO, the status argument of your tty, and
will display information on the process.
• After the dd command finishes, eject the card:
sudo diskutil eject /dev/rdisk3
(or: open Disk Utility and eject the SD card)