767
edits
Changes
Dacu
,→Introduction
{{InfoBoxTop}}
{{AppliesToDacu}}
{{AppliesToAxel}}
{{AppliesToAxelLite}}
{{AppliesToAxelEsatta}}
{{Applies To Diva}}
{{AppliesToLizard}}
{{InfoBoxBottom}}
==Introduction==
[[File:Dacu-top-view.png|600px|frameless|border]] Dacu is an ARM Cortex-A8 industrial tablet platform, built around a '''carrier board hosting ''' that can host various '''DAVE Embedded Systems''' SOMs, like, for example, the [[:Category:Lizard|Lizard]] CPU module. The main {{ImportantMessage|text=Please note that DACU supports several BOM variants in order to mate with different SOMs or evaluation boards.}} Dacu's system specifications are the following:
{| class="wikitable"
|-
|MicroprocessorSupported SOMs|ARM Cortex-A8 @ 500 MHz[[:Category:AxelUltra|Axel Ultra]]<br>[[:Category:AxelLite|Axel Lite]]<br>[[:Category:Diva|Diva]]<br>[[:Category:Lizard|Lizard]]
|-
|Power
|-
|USB
|1x 2x USB Host full speed port<br>1x USB Host high speed port2.0 ports
|-
|Audio
== Block Diagram ==
The following picture shows block diagram of the Dacucarrier board (the version for the Lizard SOM):
[[File:dacu-bd.png|thumbnail|center|400px]]
The following picture shows the mechanical layout of Dacu:
[[File:Dacu-top.png|thumbnail|center|400px]]
== Available options ==
=== RS232/RS485/RS422 or CAN ===
=== Male or female DB9 connector ===
== Connectors pinout ==
Power is provided through the JP2 DC Power Jack. Power voltage range is [12-24 V]
=== Lizard CPU module connectors – J1, J2 ===
J1 and J2 are the 140-pin mating connectors for Lizard CPU modulethe hosted SOM.
=== UART1 - J4 ===
J5 is a standard DB9 '''male''' connector for the configurable UART/CAN port. The board provides some '''hardware''' mount options for the selection of the UART mode (RS232/RS422/RS485 with auto-direction) or the CAN mode. The board default configuration provides the CAN interface on this port, while the RS232/RS422/RS485 interface is provided as an option to customers who choose the alternative configuration.
Please note that this port can be used to connect a [http://www.rovingnetworks.com/products/RN240 Bluetooth serial adapter] powered by the 5V_BT signal.
=== SDIO slot (DWM module) - J14 ===
J14 is a Molex dual row 0.50mm pitch SlimStack™ receptacle. This connector is dedicated to the [[Wireless_Module_(DWM) | DWM add-on module]]. The following table reports the connector's pinout:
{| class="wikitable"
|-
|}
=== USB ports - J15 ===
|}
== Software and hardware usage notes == === Linux quick start === To run Linux on the board, please follow the steps reported below: # connect the serial cable, provided with the board, to J3 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 classVersions ="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-165MHzDAVE Lizard board + LPDDR/NANDI2C: readyDRAM: 256 MBFlash: 32 MBNAND: 1024 MiBIn: serialOut: serialErr: serialDie ID #7cf60001000000000160ae2d0b01e00aNet: davinci_emac_initializeEthernet PHY: GENERIC @ 0x11DaVinci EMAC Hit any key to stop autoboot: 0 =></pre> Please note that you need to modify some u-boot environment variables As stated 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 different versions of DACU board, to J3 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 exist in order to to the power jack (JP2) Once power has been applied, U-Boot bootloader will be executed support several SOMs and the following messages will be printed on serial console: <pre class="board-terminal">U-Boot 2009evaluation boards.11-00074-g34e0d5b-dirty (Jul 17 2012 - 11:00:55) [dacu-android-0.9.2] AM35xx-GP ES2.0, L3-165MHzDAVE Lizard board + LPDDR/NANDI2C: readyDRAM: 256 MBFlash: 32 MBNAND: 1024 MiBIn: serialOut: serialErr: serialDie ID #7cf60001000000000160ae2d0b01e00aNet: davinci_emac_initializeEthernet PHY: GENERIC @ 0x11DaVinci 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 5555adb connect <target's ip address>:5555adb kill-serveradb 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 devicesList of devices attachedemulator-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>
