EVALUATION GUIDE
AMOS-820
VAB-820
Android BSP 3.2
1.03-08062015-102700
Copyright
Copyright © 2015 VIA Technologies Incorporated. All rights reserved.
No part of this document may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language,
in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual or otherwise without the prior written
permission of VIA Technologies, Incorporated.
Trademarks
All brands, product names, company names, trademarks and service marks are the property of their respective holders.
Disclaimer
No license is granted, implied or otherwise, under any patent or patent rights of VIA Technologies. VIA Technologies makes no
warranties, implied or otherwise, in regard to this document and to the products described in this document. The information
provided in this document is believed to be accurate and reliable as of the publication date of this document. However, VIA
Technologies assumes no responsibility for the use or misuse of the information (including use or connection of extra
device/equipment/add-on card) in this document and for any patent infringements that may arise from the use of this document.
The information and product specifications within this document are subject to change at any time, without notice and without
obligation to notify any person of such change.
VIA Technologies, Inc. reserves the right the make changes to the products described in this manual at any time without prior
notice..
ii
Revision History
Revision
Date
1.00
2015/6/3
Initial external release
Remarks
1.01
2015/7/9
Modified testing item: “Wired LAN static IP“
1.02
2015/7/29
Added 3.3.22 Shutdown option
1.03
2015/8/3
Corrected spelling errors
iii
Table of Contents
1.
Introduction ................................................................
................................................................................................
..........................................................................
.......................................... 1
1.1.
Overview ....................................................................................................... 1
2.
Making Android System Booting
Booting Media ............................................................
............................................................ 2
2.1.
Requirements................................................................................................ 2
2.2.
Procedure ...................................................................................................... 2
2.2.1.
Setting the display devices ................................................................... 6
3.
Testing ................................................................
................................................................................................
...................................................................................
................................................... 9
3.1.
Installing APK through file manager........................................................ 9
3.2.
Installing APK through Android SDK (optional) ........................................ 9
3.3.
Testing Items............................................................................................... 13
3.3.1.
OpenGL ES 2.0 ...................................................................................... 13
3.3.2.
OpenVG .................................................................................................. 13
3.3.3.
Network................................................................................................... 14
3.3.3.1.
Wired LAN Network.................................................................. 14
3.3.3.2.
WiFi ................................................................................................ 14
3.3.3.3.
Wired LAN static IP.................................................................... 15
3.3.4.
COM port................................................................................................ 15
3.3.4.1.
COM1............................................................................................ 15
3.3.4.2.
COM2............................................................................................ 16
3.3.4.3.
Test in SmartETK ......................................................................... 17
3.3.5.
Audio ....................................................................................................... 18
3.3.5.1.
Line-out......................................................................................... 18
3.3.5.2.
Mic-in............................................................................................. 18
3.3.5.3.
Line-in............................................................................................ 19
3.3.6.
I²C ............................................................................................................. 20
3.3.6.1.
Detect device ADV7180 ........................................................... 20
3.3.6.2.
Detect device HDMI EDID........................................................ 20
3.3.6.3.
Detect device SGTL5000 .......................................................... 20
3.3.7.
GPIO......................................................................................................... 21
iv
3.3.7.1.
Test in debug port (COM2) ..................................................... 21
3.3.7.2.
Test in SmartETK ......................................................................... 22
3.3.8.
Watchdog ............................................................................................... 23
3.3.8.1.
Test in debug port (COM2) ..................................................... 23
3.3.8.2.
Test in SmartETK ......................................................................... 24
3.3.9.
RTC ........................................................................................................... 25
3.3.10. USB ........................................................................................................... 25
3.3.10.1. USB storage.................................................................................. 25
3.3.10.2. USB OTG ...................................................................................... 25
3.3.11. MicroSD storage.................................................................................... 26
3.3.12. Dual Display........................................................................................... 26
3.3.13. Camera..................................................................................................... 27
3.3.13.1. Basic operation............................................................................ 27
3.3.13.2. ADV7180 testing......................................................................... 28
3.3.13.3. UVC testing .................................................................................. 29
3.3.14. Touch panel ........................................................................................... 29
3.3.15. Video........................................................................................................ 30
3.3.16. WiFi as the preferred network ........................................................... 30
3.3.17. FlexCAN.................................................................................................. 31
3.3.17.1. Test in debug port (COM2) ..................................................... 31
3.3.17.2. Test in SmartETK ......................................................................... 33
3.3.18. 3G ............................................................................................................. 35
3.3.19. SPI ROM .................................................................................................. 36
3.3.20. GPS ........................................................................................................... 37
3.3.21. OTA.......................................................................................................... 39
3.3.22. Shutdown option .................................................................................. 40
v
List of Figures
Figure 1: Boot select jumper ......................................................................................... 3
Figure 2: Boot select jumper ......................................................................................... 4
Figure 3: U-boot parameter ........................................................................................... 5
Figure 4: LVDS power selection jumper ..................................................................... 7
Figure 5: LVDS power selection jumper ..................................................................... 8
Figure 6: SDK Manager .................................................................................................. 10
Figure 7: APK installation setting ................................................................................ 12
Figure 8: OpenGL ES 2.0 .............................................................................................. 13
Figure 9: VT9271 connector ........................................................................................ 14
Figure 10: WiFi enable .................................................................................................. 14
Figure 11: COM1 ............................................................................................................ 15
Figure 12: COM1 test .................................................................................................... 16
Figure 13: COM2 ............................................................................................................ 16
Figure 14: Test in SmartETK (COM Port) .................................................................. 17
Figure 15: Audio connector ......................................................................................... 18
Figure 16: Tinymix .......................................................................................................... 18
Figure 17: i2cdetect adv7180 ...................................................................................... 20
Figure 18: i2cdetect HDMI EDID ................................................................................ 20
Figure 19: i2cdetect SGTL5000 ................................................................................... 20
Figure 20: Test in SmartETK (GPIO) ........................................................................... 22
Figure 21: WDOG reboot............................................................................................. 23
Figure 22: Test in SmartETK(WatchDog)................................................................... 24
Figure 23: Test in SmartETK(WatchDog)................................................................... 24
Figure 24: RTC setting ................................................................................................... 25
Figure 25: Camera.apk................................................................................................... 27
Figure 26: Camera function1........................................................................................ 27
Figure 27: Camera function2........................................................................................ 27
Figure 28: Camera function3........................................................................................ 28
Figure 29: eGalaxCalibrator......................................................................................... 29
Figure 30: CAN bus H/W connection........................................................................ 31
Figure 31: Test in SmartETK(CAN) ............................................................................. 33
vi
Figure 32:
Figure 33:
Figure 34:
Figure 35:
Figure 36:
Figure 37:
Figure 38:
Figure 39:
Figure 40:
Test in SmartETK(CAN) ............................................................................. 33
Test in SmartETK(CAN_filter) .................................................................. 34
Test in SmartETK(CAN_filter) .................................................................. 34
APN setting .................................................................................................. 35
SPI ROM test result..................................................................................... 36
RIL OEM HOOK Test setting.................................................................... 37
GPS messages .............................................................................................. 38
QuickSettings menu ................................................................................... 40
Shutdown option menu............................................................................. 40
vii
List of Tables
Table 1: LVDS power selection jumper settings ...................................................... 7
Table 2: LVDS power selection jumper settings ...................................................... 8
Table 3: GPIO pins ........................................................................................................ 21
viii
1. Introduction
The purpose of this document is to provide a practical introduction on
evaluating Android 4.4.2 for the AMOS-820 (Bare board: VAB-820 Freescale
i.MX6 Quad).
1.1. Overview
The VIA VAB-820 platform is an embedded system powered by ARM
processor with Android 4.4.2 operating system by default. VAB-820’s Android
BSP offers a development package. Users can develop it under an Ubuntu
environment.
There are four major boot components for Android, the “u-boot.bin”
boot.bin”,
“boot.img”,
boot.img”, “system.img” and “recovery.img”.
“recovery.img” The system will not boot
successfully into an Android environment if one of these files does not exist in
the boot media.
1
2. Making Android System
Booting Media
VAB-820 Android BSP only supports booting from onboard eMMC. This
section will guide you through making the Android system boot media for
VAB-820 from EVK folder.
2.1. Requirements
Linux development computer
Micro SD storage card. Recommended size is 4GB, class 4 at least.
EVK folder
2.2. Procedure
Step 1
Insert the Micro SD card to your Linux development computer.
Step 2
Open the “Terminal”
Terminal” utility.
Step 3
The Micro SD storage card can be identified and auto mounted once inserted
to the computer. You can check Micro SD card code name by $ df -h
user@ubuntu:~$ df –h
...
Filesystem
Size
Used
Avail
Use%
/dev/sdb1
531M
6.3G
8%
7.2G
Mounted on
/media/usb
However, there are some instances that the Micro SD storage card cannot be
identified or auto mounted after inserting to the computer. In that case, you
can try the other way to identify the Micro SD card.
user@ubuntu:~$ dmesg | grep –i removable
[105.502517] sd 9:0:0:0 [sdb] Attached SCSI removable disk
2
The Micro SD storage card code name for this example is identified as sdb.
sdb
Step 4
The EVK path for this example is /home/user/EVK,
/home/user/EVK user can enter the folder
Images_autoinstall_sd/scripts”” which is under EVK.
“Images_autoinstall_sd/scripts
EVK
user@ubuntu:~$ sudo cd /home/user/EVK/Images_autoinstall_sd/scripts
user@ubuntu:~/EVK/Images_autoinstall_sd/scripts$ ls
mk_install_sd.sh
Step 5
User can run the script “mk_install_sd.sh”
mk_install_sd.sh” to make a bootable Micro SD card.
Thus, user can install the Android image into VAB-820 eMMC through the
Micro SD card. The target Micro SD storage card code name for this example
is identified as sdb
sdb.
user@ubuntu:~/EVK/Images_autoinstall_sd/scripts$
sudo ./mk_install_sd.sh /dev/sdb
User can unplug the Micro SD card from Linux development PC after the
message “Done!
Done!”
Done! appears.
Step 6
Insert the Micro SD card into VAB-820. Make sure to set the jumper setting to
make it bootable from Micro SD. For more details about the boot select
jumper, please refer to the VAB-820 User Manual.
Figure 1: Boot select jumper
3
Notes:
1. It is recommended to connect COM2 debug cable to make sure the U-boot parameter is correct.
2. Make sure the U-boot parameter is clean. User can type the command below in U-boot:
u-boot> destroyenv
u-boot> reset
Here, the VAB-820 should boot into Linux.
Step 7
Type this command to format/partition/flash Android image into SPI/eMMC.
$./fsl-eMMC-partition.sh –f /dev/mmcblk0
The U-boot will flash into SPI ROM and the others will flash into eMMC.
Shutdown Linux by this command
$poweroff
Step 8
Set the J11 jumper (short pin 2-3) to SPI booting selection. Then power on the
VAB-820 and set U-boot parameter through COM2 debug port.
For more details about the boot select jumper, please refer to the VAB-820
User Manual.
Make sure the U-boot parameter is clean. User can type the command below
in U-boot:
u-boot> destroyenv
u-boot> reset
Figure 2: Boot select jumper
4
Step 9
Setting U-boot parameter for eMMC.
Connect the VAB-820 and host PC through J5 (COM2) of VAB-820. Run
“putty” on host PC to receive the booting message. Power on the VAB-820
and press any key to stop the booting process as shown in Figure 3.
Figure 3: U-boot parameter
5
2.2.1. Setting the display devices
[HDMI]
To set HDMI as boot display:
setenv display run hdmi
To set HDMI resolution:
setenv hdmi ‘setenv bootargs ${bootargs}
video=mxcfb0:dev=hdmi,1920x1080M@60,bpp=32 video=mxcfb1:off
video=mxcfb2:off video=mxcfb3:off fbmem=28M vmalloc=400M
androidboot.hardware=freescale audio=hdmi’
To replace the resolution, change the red color part with the desired
resolution mode.
For example: To set the 1280 x 720, change the 1920 x 1080 to 1280 x 720.
setenv hdmi ‘setenv bootargs ${bootargs}
video=mxcfb0:dev=hdmi,1280x720M@60,bpp=32 video=mxcfb1:off
video=mxcfb2:off video=mxcfb3:off fbmem=28M vmalloc=400M
androidboot.hardware=freescale audio=hdmi’
The HDMI only supports CEA mode, here is the list of the supporting modes:
Width
640
Height
480
Frame rate
60
720
480
60
1280
720
60
1440
240
60
1440
480
60
1920
1080
60
720
576
50
1280
720
50
1440
288
50
1440
576
50
1920
1080
50
1920
1080
24
1920
1080
25
1920
1080
30
1280
720
100
1280
720
120
6
[LVDS]
There are three LVDS panels supported by VAB-820. Here is the list:
AUO 22” G220SVN01.0
AUO 10.4” G104XVN01.0
AUO 7" G070VW01 V0
The LVDS type for this example is AUO 22” G220SVN01.0.
Check the LVDS power selection setting:
IVDD
J3 : LVDS power select
PVDD
*1-3
+12V
2-4
+3.3V
3-5
+5V
*4-6
+5V
Table 1: LVDS power selection jumper
jumper settings
Figure 4: LVDS power selection
selection jumper
jumper
To set LVDS AUO 22” G220SVN01.0 as display device:
setenv display run lvds_auo_g220
7
The LVDS type for this example is AUO 10.4” G104XVN01.0.
Check the LVDS power selection setting:
J3 : LVDS power select
IVDD
PVDD
*1-3
+12V
*2-4
+3.3V
3-5
+5V
4-6
+5V
Table 2: LVDS power selection jumper
jumper settings
Figure 5: LVDS power selection jumper
jumper
To set LVDS AUO 10.4” G104XVN01.0 as display device:
setenv display run lvds_auo_g140
To set LVDS AUO 7" G070VW01 V0 as display device:
setenv display run lvds_auo_g007
To set the other LVDS panels, user can add a customized lvds parameter when
finish porting lvds driver (ldb.c). Here is an example; the “red” words depend
on LVDS SPEC.
setenv lvds_custmize ‘setenv bootargs ${bootargs}
video=mxcfb0:dev=ldb,LDB-WSXGA+,if=RGB24,bpp=32 ldb=spl0
video=mxcfb1:off video=mxcfb2:off video=mxcfb3:off fbmem=28M
androidboot.hardware=freescale audio=sgtl5000’
setenv display run lvds_custmize
8
3. Testing
This chapter will guide you through evaluating VAB-820 Android evaluation
image.
3.1. Installing APK through file manager
An “open
“open Manager”
Manager” file manager is prebuilt into image. User can install
necessary testing APK.
Note:
There are known copy/paste issues in open Manager, it is recommended to use it only when installing
the APK.
Installing
Installing APK from USB disk
1. Open the “Open
Open Manager”.
Manager
2. Choose “udisk
udisk”
udisk folder.
3. Select the app you want to install. The program will ask you “Do
Do you
Install”.
want to install this application?”,
application? then press “Install
Install
3.2. Installing APK through Android SDK (optional)
[Host PC: Windows XP]
Step 1
Download JDK (jdk
jdkjdk-7u407u40-windowswindows-i586.exe)
i586.exe from
http://www.oracle.com/technetwork/java/javase/downloads/index.html and
install it.
Step 2
Download the Android SDK (adt-bundle-windows-x86-20130729.zip) and
install it.
9
Step 3
Execute the SDK manager and select the packages.
Figure 6: SDK Manager
Step 4
Open a text console utility in Windows XP.
Run -> cmd
cd <<Your SDK Installation Path>>\tools\
#run command in the console
android.bat update adb
Step
Step 5
Go to C:\Documents and Settings\ {User Account} \.android
Modify the file adb_usb.ini:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x18d1
Step 6
Unpack android_usb_fsl.zip from Tools under EVK folder.
10
Step 7
Connect your PC to VAB-820. Windows XP will detect a new android device.
Install the driver by choosing android_winusb.ini which is in the
android_usb_fsl folder
Run -> cmd
cd <<Your SDK Installation Path>>\platform-tools
#run below command in the consle
adb.exe kill-server
adb.exe start-server
adb.exe devices
You will see as below:
List of devices attached
0123456789ABCDEF
device
[Host PC: Linux]
Step 1
Download JDK6 package and install it.
Step 2
Download the Android SDK.
Step 3
Update the adb configuration to scan for freescale's pid:
Run SDK's tools to generate a configuration file:
./android-sdk-linux_86/tools/android update adb
Modify the files:~/.android/adb_usb.ini, to add freescale vendor id:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x18d1
Create a new udev rule file under the PC's /etc/udev/rules.d/ named:
imx-android.rules. Fill in the following line into the file:
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"
11
Change the new udev rule file's permission:
chmod a+r /etc/udev/rules.d/imx-android.rules
Connect the Android Device through USB OTG.
To ensure that Android device is connected, find the adb first in androidsdk/platform-tools
./adb devices
List of devices attached: 0123456789ABCDEF device
Step 4
Install APK through adb
After setup, you can use adb to install app.
Go to Settings->Security and enable the checkbox of “Unknown Sources”
Figure 7: APK installation
installation setting
adb.exe install {your apk file}
12
3.3. Testing Items
3.3.1. OpenGL ES 2.0
Install the ApiDemo.apk obtained from EVK/app folder.
Run “A
API Demos
Demos”
Figure 8: OpenGL ES 2.0
3.3.2.
Select Graphics-> OpenGL ES->OpenGL ES 2.0
OpenVG
OpenVG is not originally supported by Android; however, it is possible to use
OpenVG in Android by downloading AndroidVG. Get more detailed
information on:
http://code.google.com/p/androidvg/wiki/Installation_Guide_Linux
To install the “AppleVG.apk
AppleVG.apk”
TigerVG.apk”
AppleVG.apk and “TigerVG.apk
TigerVG.apk files into Android for testing.
13
3.3.3. Network
3.3.3.1.
Wired LAN Network
Plug in the cable before booting.
Run “Browser” and verify the network.
Unplug the cable and plug it back immediately, check whether the
network is still working or not.
Unplug the cable and reboot, plug in again after booting and check
the network.
3.3.3.2.
WiF
WiFi
Connect the VT9271 WLAN device to VAB-820.
Figure 9: VT9271 connector
Go to Settings and enable the Wi-Fi. You will see AP list.
Figure 10:
10: WiF
WiFi enable
Run “Browser” and verify the network.
14
3.3.3.3.
Wired LAN static IP
Set Ethernet in Settings-> More -> Configure Ethernet. Fill the “IP
address”, “DNS address”, “Prefix length”, and “gateway”, then choose
“OK”.
You can input “busybox ifconfig” and “busybox route” through COM
port to check the settings.
After setting, you can use static IP function
Note:
The prefix length means the size of the subnet and is the number of 1 bits in the netmask.
For example:
Netmask: 255.255.248.0
= 1111,1111,1111,1111,1111,1000,0000,0000
Prefix length = 21.
Netmask: 255.255.255.0
= 1111,1111,1111,1111,1111,1111,0000,0000
Prefix length = 24.
3.3.4. COM port
3.3.4.1.
COM1
Install the SerialPort_1.1.apk obtained from EVK/app folder.
After setting up the serial port API, open the Console item
o
Device : ttymxc0
o
Baud rate : 115200
Connect from VAB-820 to host PC via J4.
Figure 11:
11: COM1
15
Execute “putty
putty”
putty on host PC.
o
Serial -> Flow control : RTS/CTS
Type any key in putty and Serial Port API, you will see the words in
the other machine.
Figure 12:
12: COM
COM1
OM1 test
3.3.4.2.
COM2
Connect from VAB-820 to host PC via J5.
Figure 13:
13: COM2
Execute “putty
putty”
putty on host PC.
Power on the VAB-820.
Booting message will be shown on the screen of putty.
PS. Putty setting: “Speed” : 115200 “Connection type” serial
Type command through COM2.
16
3.3.4.3.
Test in SmartETK
SmartETK
Install VAB820StandardExample.apk (SmartETK demo APK)
Select “UART”
Set “Device” as ttymxc0 (COM1) and “BaudRate”
Click “Connect” and input the message then press “Send”
Figure 14:
14: Test in SmartETK (COM Port)
17
3.3.5. Audio
3.3.5.1.
LineLine-out
Connect the headphone plug to the green jack socket.
Figure 15:
15: Audio connector
3.3.5.2.
MicMic-in
Install Hi-Q MP3 Rec (Lite).apk obtained from EVK/app folder.
Plug the microphone to the red jack socket.
User needs tinymix to set the Mic-in.
root@android:/# tinymix
Figure 16:
16: Tinymix
18
root@android:/# tinymix 24 0
root@android:/# tinymix 26 1
Run “Hi-Q” app in the Android to test the sound record.
Note:
Tinymix does not support Mic-in for headphone.
3.3.5.3.
LineLine-in
Plug audio cable to the blue jack socket. Here, user can use an audio
cable to connect.
It is recommended to download Hi-Q MP3 Rec (Llite) 1.6.12 to test.
Audio-out on player, Line-in on I/O board, and play the music.
Line-in cannot be used directly. User needs tinymix to set Line-in.
root@android:/# tinymix
root@android:/# tinymix 24 1
root@android:/# tinymix 27 1
If you want to set the line-in to headphone, set the tinymix argument as:
root@android:/# tinymix 23 1
root@android:/# tinymix 25 1
root@android:/# tinymix 27 1
Run “Hi-Q” app
After setting the line-in to headphone, and if you want to hear the system
voice, set the tinymix argument as:
root@android:/# tinymix 23 0
19
3.3.6. I²C
3.3.6.1.
Detect device ADV7180
ADV7180 could be found at address 0x21 on I2C1.
Figure
Figure 17:
17: i2cdetect adv7180
3.3.6.2.
Detect device HDMI EDID
EDID could be found at address 0x50 on I2C2
Figure 18:
18: i2cdetect HDMI EDID
3.3.6.3.
Detect device SGTL5000
SGTL5000 could be found at address 0x0A on I2C3
Figure
Figure 19:
19: i2cdetect SGTL5000
20
3.3.7. GPIO
3.3.7.1.
Test in debug port (COM2)
Change the directory to /sys/class/gpio
Generate the numbers corresponding to the GPIO pins.
Pin
T4
VABVAB-820 name
GPIO_1
FSL name
GPIO1_1
T1
GPIO_2
GPIO1_2
R6
GPIO_4
GPIO1_4
R4
GPIO_5
GPIO1_5
R3
GPIO_7
GPIO1_7
R5
GPIO_8
GPIO1_8
T2
GPIO_9
GPIO1_9
R2
GPIO_16
GPIO7_11
Table 3: GPIO pins
The number is (X-1)*32+Y for each GPIOX_Y.
Example: The number for GPIO7_11 is (7-1)*32+11=203
The number for GPIO1_5 is (1-1)*32+5=5
echo 203 > export
echo 5 > export
The directories “gpio203” and “gpio5” will be created under /sys/class/gpio/
Set GPIO IN/OUT
echo out > gpio203/direction
echo in > gpio5/direction
Notes
Notes:
1, 2, 4, and 5 are IN. 7, 8, 9 and 203 are OUT.
Test
The following GPIO are connected by jumper, we can test them together.
gpio1 --- gpio7
gpio2 --- gpio8
gpio4 --- gpio9
21
gpio5 --- gpio203
Write value 0 or 1 to “out” and read value from “in”.
echo 0 > /sys/class/gpio/gpio203/value
cat /sys/class/gpio/gpio5/value
Check if the value is the same as you wrote it.
3.3.7.2.
Test in SmartETK
Install VAB820StandardExample.apk (SmartETK demo APK).
Select “GPIO
GPIO”
GPIO
Click “Enable” to test GPIO.
Test example:
o
Pin 1 - Pin 7: Without jumper connection. User select GPO to
up, GPI won’t change voltage.
o
Pin 5 - Pin 203: With jumper connection. User select GPO to
up, GPI will change voltage.
Figure 20:
20: Test in SmartETK (GPIO)
22
3.3.8. Watchdog
3.3.8.1.
Test in debug port (COM2)
ioctl –r /dev/watchdog 2
The system will reboot in 60 seconds.
[WDOG] will be shown in the line of “Boot Reason”.
Figure 21:
21: WDOG reboot
23
3.3.8.2.
Test in SmartETK
Install VAB820StandardExample.apk (SmartETK demo APK).
Select “WatchDog”.
Select ”Enable WatchDog” and enter “Timeout value”(1~128sec.),
then press “SetTimeout” button.
The system will be reset by watchdog in one minute (default) or in
the value (sec.) you set.
Pressing the “Keep Alive” button will feed the WatchDog, reset the
timer.
Figure 22:
22: Test in SmartETK(WatchDog)
Figure 23:
23: Test in SmartETK(WatchDog)
24
3.3.9. RTC
Test way: Setup hardware time in Settings
Figure 24:
24: RTC setting
setting
Reboot the system (power off first and power on again) and check the
time.
3.3.10. USB
3.3.10.1. USB storage
Android will detect the USB disk automatically. Once the USB disk is detected,
system will inform you and mount it to /storage/ automatically.
You can also mount the USB disk manually.
Go to Settings->Storage
Select “Mount udisk”
3.3.10.2. USB OTG
Connect the Android device to Linux or XP PC through USB OTG. Go to
android-sdk/platform-tools and type:
./adb devices
If the device is detected successfully, terminal will show a message:
List of devices attached:
0123456789ABCDEF device
25
3.3.11. MicroSD storage
MicroSD card as storage: Detection and Access
Find the device node of MicroSD card under /dev/block as ”mmcblk1”.
Android should mount MicroSD card automatically. Check files under
/storage/extsd.
Copy file to/from /storage/extsd.
3.3.12. Dual Display
Note:
VAB-820 DualLite does not support dual display.
To set Dual display (auo 10.4” + hdmi 720p):
In U-boot set,
setenv display ‘run dual_display’
To set the other configuration of dual display. Here is an example; the “red”
words depend on the LVDS SPEC and HDMI mode that user wants to set.
setenv dual_display ‘setenv bootargs ${bootargs}
video=mxcfb0:dev=ldb,LDB-XGA,if=RGB24,bpp=32 ldb=sin0
video=mxcfb1:dev=hdmi,1280x720M@60,bpp=32 video=mxcfb2:off
video=mxcfb3:off fbmem=28M vmalloc=400M androidboot.hardware=freescale
audio=sgtl5000’
setenv display run dual_display
26
3.3.13. Camera
3.3.13.1. Basic operation
Open the Camera.apk.
Figure 25:
25: Camera.apk
You can switch to video mode or photo mode.
Figure 26:
26: Camera function1
Take a photo or record a video by pressing the round button.
Figure 27:
27: Camera function2
27
Android has two camera lenses: back_camera and front_camera
front_camera.
ra Back_camera
is ADV7180, and front_camera is UVC. You can switch them by using the
following icon.
Figure 28:
28: Camera function3
The following settings are only for ADV7180.
Switch video input source by the command through COM2.
root@android:/ # setprop adv7180_src 2
The value ”1” is composite and value ”2” is S-Video.
You have to re-open the camera.apk after doing the above settings.
Check the settings by the command ”getprop”.
root@android:/ # getprop adv7180_src
2
3.3.13.2. ADV7180 testing
1. Open the camera.apk. The default camera is back_camera (ADV7180) with
composite source and NTSC format.
2. Take a photo. Photo is jpg format.
3. Switch to video mode and test video recording. The codec of video
recording should be:
fileFormat="mp4"
<Video codec="h264"
bitRate="3000000"
frameRate="30" />
<Audio codec="aac"
bitRate="96000"
28
sampleRate="44100"
channels="1" />
Width and height are based on the format. NTSC is 720 x 480 and PAL is 720 x
576.
3.3.13.3. UVC testing
1. Open the camera.apk and switch to front_camera.
2. Take a photo. The photo is in jpg format.
3. Switch to video mode and test video recording. The codec of video
recording should be:
fileFormat="mp4"
<Video codec="h264"
bitRate="3000000"
width="640"
height="480"
frameRate="30" />
<Audio codec="aac"
bitRate="96000"
sampleRate="44100"
channels="1" />
3.3.14. Touch panel
Install the eGalaxCalibrator.apk obtained from EVK/app folder.
Connect the USB cable on touch panel to VAB-820.
Run eGalaxCalibrator and choose 4 or 9 Points Calibration.
Figure 29:
29: eGalaxCalibrator
After calibration, you can surf android with your finger.
29
3.3.15. Video
Install the MX Player_1.7.31.apk obtained from EVK/app folder.
Select the video file to play. The MX player will use hardware
acceleration to decode the video by default and show “HW” on the
top right corner. If the file cannot be decoded by hw, player will
decode by sw and show “SW” on the top right corner.
3.3.16. WiFi as the preferred network
Make sure the Ethernet cable is unplugged and connected to a WiFi
AP.
Check the connection by entering the following command :
root@android:/ # logcat | grep ‘ConnectivityService’
Connection status will be shown on the screen:
D/ConnectivityService(
D/ConnectivityService(
CONNECTED/CONNECTED
D/ConnectivityService(
same reset per doReset
D/ConnectivityService(
2555): Active connection : WIFI(CONNECTED)
2555): ConnectivityChange for WIFI:
2555): handleConnectivityChange: address are the
linkProperty[1]: resetMask=0
2555): Active connection : WIFI(CONNECTED)
Plug the Ethernet cable in the VAB-820, and the following message
will be shown on the screen:
PHY: 1:07 - Link is Up
D/ConnectivityService(
CONNECTED/CONNECTED
D/ConnectivityService(
down network ETHERNET
D/ConnectivityService(
- 100/Full
2555): ConnectivityChange for ETHERNET:
2555): Not broadcasting CONNECT_ACTION to torn
2555): Active connection : WIFI(CONNECTED)
30
3.3.17. FlexCAN
3.3.17.1. Test in debug port (COM2)
Connect the VAB-820-A to VAB-820, and use a non-jumper cable to
connect can0 and can1 as shown in Figure 30.
Figure 30:
30: CAN bus H/W connection
connection
Testing command: cansend and candump
#
#
#
#
ip link
ip link
candump
cansend
#
#
#
#
ip link
ip link
cantest
cantest
set can0 up type can bitrate 500000
set can1 up type can bitrate 500000
can1 &
can0 -i0x123 0xaa 0xbb 0xcc 0xdd
Testing command: cantest
set can0 up type can bitrate 500000
set can1 up type can bitrate 500000
can1 &
can0 123#aabbccdd
If the setting is successful, it will show “ID” and “DATA”.
The other testing (reference).
Simple Tx/Rx Test. All receive.
# ip link set can0 up type can bitrate 500000
# ip link set can1 up type can bitrate 500000
# candump can1 &
# cansend can0 -i0x123 0x11 0x22 0x33 0x44 0x55 0x66 0x77 0x88
-> <0x123> [8] 11 22 33 44 55 66 77 88
Add Filter to candump, kill the older candump at first.
# candump can1 --filter=0x123:0x7ff &
# cansend can0 -i0x111 0x11 0x22 0x33 0x44 0x55 0x66 0x77 0x88
31
-> not received(filter not hit)
# cansend can0 -i0x123 0x11 0x22 0x33 0x44 0x55 0x66 0x77 0x88
-> <0x123> [8] 11 22 33 44 55 66 77 88
Change Bitrate and send message part 1.
# ifconfig can0 down
# ip link set can0 up type can bitrate 250000
# candump can1 &
# cansend can0 -i0x123 0x11 0x22 0x33 0x44 0x55 0x66 0x77 0x88
-> not received(different bitrate)
# ifconfig can1 down
# ip link set can1 up type can bitrate 250000
# candump can1 &
# cansend can0 -i0x123 0x11 0x22 0x33 0x44 0x55 0x66 0x77 0x88
-> <0x123> [8] 11 22 33 44 55 66 77 88
Change Bitrate and send message part 2.
# ifconfig can0 down
# ifconfig can1 down
(BITRATE = 1000000, 500000, 250000, 125000, 100000, 50000)
# ip link set can0 up type can bitrate 50000
# ip link set can1 up type can bitrate 50000
# candump can1 &
# cansend can0 -i0x123 0x11 0x22 0x33 0x44 0x55 0x66 0x77 0x88
-> <0x123> [8] 11 22 33 44 55 66 77 88
32
3.3.17.2. Test in SmartETK
Install VAB820StandardExample.apk (SmartETK demo APK)
Select “CAN”
Set “BitRate”
Click “Connect” and then press “Send” to send the input messages
Figure 31:
31: Test in SmartETK(CAN)
Figure 32:
32: Test in SmartETK(CAN)
33
Figure 33:
33: Test in SmartETK(CAN_filter)
Figure 34:
34: Test
Test in SmartETK(CAN_filter)
34
3.3.18. 3G
Connect the u-blox LISA U-200 to VAB-820.
Open the APN setting menu (Settings->WIRELESS & NETWORKS>More->Mobile networks->Access Point Names).
Add a new APN (set the suitable Name and APN for SIM card) and
choose the APN.
Figure 35:
35: APN setting
Run “Browser” and verify the network.
35
3.3.19. SPI ROM
Connect the VAB-820-B to VAB-820.
These 2 SPI ROMs could be found under /dev/block as “mtdblock1”
and “mtdblock2”.
Copy spi_test.sh from “/EVK/tool” to android system “/data”.
Use this command to run the script.
# sh spi_test.sh /dev/block/mtdblock1
# sh spi_test.sh /dev/block/mtdblock2
We can see the test result as shown in Figure 36.
Figure 36:
36: SPI ROM test
test result
36
3.3.20. GPS
Connect the u-blox LISA U-200 to VAB-820 and enable 3G.
Install the uCenter.apk obtained from EVK/app folder.
Open the RIL OEM Hook Test menu (Settings->WIRELESS &
NETWORKS->More->RIL OEM HOOK Test).
Figure 37:
37: RIL
RIL OEM HOOK Test setting
Choose API 4 type command and input below commands line by line.
AT+UGPRF=1
AT+UGRMC=1
AT+UGGSV=1
AT+UGGGA=1
AT+UGPS=1,0
Before running the uCenter, you need to take the GPS antenna out of
window, and then GPS can find more satellite and locate your
position.
Run uCenter and scroll display menu to see the messages, and after
about 10 minutes, GPS will locate your position.
37
Figure 38:
38: GPS messages
messages
38
3.3.21. OTA
Please refer to VAB-820_OTA.pdf to create an upgrade package and OTA
server.
Then:
1. Create a new ota.conf file and fill in your server address. ex:
server=192.168.144.14
port=8888
2. Put ota.conf into udisk .
3. Insert udisk to VAB-820.
4. Do upgrade.
39
3.3.22. Shutdown option
1. Find QuickSettings menu and press on “Shutdown”.
Figure 39:
39: QuickSettings menu
2. There are 3 options:
a. Sleep
b. Reboot
c. Power off
Figure 40:
40: Shutdown option menu
40