|-
|}
== Software and hardware usage notes ==
=== Linux board support package for Dacu ===
The Linux version that runs on Dacu derives from the version provided with the [[Lizard_Embedded_Linux_Kit_(LELK) | Lizard Embedded Linux Kit 1.2.0]].
{| class="wikitable" style="border:1px solid #505050 "
|-
|style="background-color:#B0B0B0;font-weight:bold; border:1px solid #505050 " | Bootloader
|style="border:1px solid #505050 " | U-Boot
|-
|style="background-color:#B0B0B0;font-weight:bold; border:1px solid #505050 " | Linux version
|style="border:1px solid #505050 " |2.6.32-dacu
|-
|style="background-color:#B0B0B0;font-weight:bold; border:1px solid #505050 " | Drivers list
|valign="top" style="border:1px solid #505050 " | NOR flash<br>NAND flash<br>Ethernet<br>LCD controller - AM800480STM display (LVDS version)<br>Backlight PWM<br>UART (RS232/RS485/RS422)<br>CAN<br>SPI<br>I2C<br>USB Host<br>MMC/SD/SDIO<br>Resistive touch screen<br>RTC<br>UDA1374 audio codec<br>1-Wire<br>INA226 sensors
|-
|style="background-color:#B0B0B0;font-weight:bold; border:1px solid #505050 " | Root file system
|style="border:1px solid #505050 " |Same as LELK 1.2.0
|-
|}
=== Android board support package description ===
The Android version that runs on Dacu is derived from the Android BSP provided by Texas Instruments, applying the patches that add support for Dacu/Lizard (see above). The root file system provided by the Android BSP from Texas Instruments.
=== Linux quick start ===
To run Linux on the board, please follow the steps reported below:
# connect the serial cable, provided with the board, to J25 pin-strip connector
# connect this cable to PC COM port through a NULL-modem cable (not provided)
# start your favourite terminal software on PC; communication parameters are:
#* baud rate: 115200 Bps
#* data bits: 8
#* stop bits: 1
#* parity: none
# connect the system to Ethernet LAN (RJ45 connector, J6)
# connect a 12Vcc power supply to to the power jack (JP2)
Once power has been applied, U-Boot bootloader will be executed and the following messages will be printed on serial console:
<pre class="board-terminal">
U-Boot 2009.11-00074-g34e0d5b-dirty (Jul 17 2012 - 11:00:55) [dacu-android-0.9.2]
AM35xx-GP ES2.0, L3-165MHz
DAVE Lizard board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
Flash: 32 MB
NAND: 1024 MiB
In: serial
Out: serial
Err: serial
Die ID #7cf60001000000000160ae2d0b01e00a
Net: davinci_emac_initialize
Ethernet PHY: GENERIC @ 0x11
DaVinci EMAC
Hit any key to stop autoboot: 0
=>
</pre>
Please note that you need to modify some u-boot environment variables before running the net_nfs configuration and start Linux. For further information, please refer to [[Booting_Linux_Kernel#Configuration_net_nfs | Configuration net_nfs]].
=== Android quick start ===
This section describes how to quick start Android operating system on Dacu.
==== "Full control" mode ====
# connect the serial cable, provided with the board, to J25 pin-strip connector
# connect this cable to PC COM port through a NULL-modem cable (not provided)
# start your favourite terminal software on PC; communication parameters are:
#* baud rate: 115200 Bps
#* data bits: 8
#* stop bits: 1
#* parity: none
# connect the system to Ethernet LAN (RJ45 connector, J6)
# connect a 12Vcc power supply to to the power jack (JP2)
Once power has been applied, U-Boot bootloader will be executed and the following messages will be printed on serial console:
<pre class="board-terminal">
U-Boot 2009.11-00074-g34e0d5b-dirty (Jul 17 2012 - 11:00:55) [dacu-android-0.9.2]
AM35xx-GP ES2.0, L3-165MHz
DAVE Lizard board + LPDDR/NAND
I2C: ready
DRAM: 256 MB
Flash: 32 MB
NAND: 1024 MiB
In: serial
Out: serial
Err: serial
Die ID #7cf60001000000000160ae2d0b01e00a
Net: davinci_emac_initialize
Ethernet PHY: GENERIC @ 0x11
DaVinci EMAC
Hit any key to stop autoboot: 0
=>
</pre>
Once the boot process has completed, you'll get the default Android "desktop":
[[File:Android-dacu-lock-screen.jpg|thumb|none|border|450px|Android default lock screen]]
Moreover, you'll have immediate access to the Android shell, so you can use the shell commands to interact with the system and see the output messages on the console. Using the serial console doesn't prevent you from using also the adb tool to access the system.
==== "Normal" mode ====
# connect the system to Ethernet LAN (RJ45 connector, J6)
# connect a 12Vcc power supply to to the power jack (JP2)
Once power has been applied, the system will boot loading the software components from the internal flash. Once the boot process has completed, you'll get the default Android "desktop":
You can now access the system using adb.
==== Default IP address ====
{{ImportantMessage|text='''The default IP address is 192.168.0.122'''}}
==== Running the Android Debug Bridge (ADB) ====
[http://developer.android.com/tools/help/adb.html ADB] is a fundamental development tool and enables remote access to the Android device. ADB is provided with the Android SDK, so before using it you must install the SDK.
To establish the ADB connection, on a '''Linux''' host machine open a shell and launch the following commands:
<pre class="workstation-terminal">
$ export PATH=${PATH}:<your_sdk_dir>/platform-tools
$ export ADBHOST=<target's ip address>
$ adb kill-server
$ adb start-server
</pre>
On a '''Windows''' host machine, open a shell and launch the following commands:
<pre class="workstation-terminal">
adb tcpip 5555
adb connect <target's ip address>:5555
adb kill-server
adb start-server
</pre>
To check the connection, please launch
<pre class="workstation-terminal">
$ adb devices
</pre>
If everything is working properly, you should see the following messages:
<pre class="workstation-terminal">
$ adb devices
List of devices attached
emulator-5554 device
</pre>
You can open a remote shell using the following command:
<pre class="workstation-terminal">
$ adb shell
</pre>
To install an application (in .apk format), you can use the following commmand:
<pre class="workstation-terminal">
$ adb install <path to apk>
</pre>
===Useful Links===
[http://www.youtube.com/watch?v=VhvlZL46R5Q Video: Android Multitouch demo on Dacu]
[http://developer.android.com/tools/help/adb.html Android Debug Bridge]
