Open main menu

DAVE Developer's Wiki β

Changes

Dacu

1,801 bytes added, 16:45, 23 February 2021
→‎Layout
{{InfoBoxTop}}
{{AppliesToDacu}}
{{AppliesToAxel}}
{{AppliesToAxelLite}}
{{AppliesToAxelEsatta}}
{{Applies To Diva}}
{{AppliesToLizard}}
{{AppliesToAndroid}}
{{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
|-
|Serial Ports
|1x UART RS232 on DB9<br>1x UART (RS232/RS422/RS485/) or CAN on DB9(hardware mount options)<br>1x UART RS232 on pin strip (debug port)
|-
|Ethernet
|-
|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 ===
|}
=== UART2 /CAN - J5 === 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. 
J5 is a standard DB9 connector for the configurable UART/CAN port. The board provides some mount options for the selection of the UART mode (RS232/RS422/RS485 with autodirection) or the CAN mode. The following table reports the connector's pinout:
{| class="wikitable"
|-
|1
|N.A./CAN_SHIELDReserved|Not connected|Not connected
|Not connected
|||Can shieldReserved
|
|-
|UART2_A/CAN_M
|UART2 rx line
|Not connected
|Not connected
|CAN bus low signal
|
|
|CAN bus low signal
|CAN mode primary mount option
|-
|3
|-
|4
|N.A./CAN_M(opt)Reserved|Not connected|Not connected
|Not connected
|Reserved
|
|
|CAN bus low signal
|CAN mode secondary mount option
|-
|5
|Ground
|Ground
|Ground|CAN bus shield(Optional)
|
|-
|6
|N.A./GND(opt)|Not connected
|Not connected
|Not connected
|Ground (Optional)
|
|
|Ground
|CAN mode secondary mount option
|-
|7
|Noninverting driver output
|CAN bus high signal
|CAN mode primary mount option
|-
|8
|UART2_B/CAN_P(opt)Reserved
|UART2 Clear To Send
|Not connected
|Not connected
|Reserved
|
|
|CAN bus high signal
|CAN mode secondary mount option
|-
|9
|5V_BT/CAN_V+
|5V for bluetooth
|5V for bluetooth|5V for bluetooth|CAN bus +5VPower (Optional)
|
|-
==== Configuration Jumpers J26 e J27 ====
These When the board is configured to provide the UART2 interface through the J5 connector, the J26 and J27 jumpers are used to configure the UART mode, as reported below:
{| class="wikitable"
|-
!Jumper
!RS232mode!RS422mode!RS485mode
|-
|1-3
=== MicroSD slot - J12 ===
J12 is a Micro-SD card header.The following table reports the connector's pinout: {| class="wikitable" |-!Pin# !Pin name!Function!Notes|-|1|MMC1_DAT2|||-|2|MMC1_DAT3|||-|3|MMC1_CMD|||-|4|MMC_3.3V|||-|5|MMC1_CLK|||-|6|DGND|||-|7|MMC1_DAT0|||-|8|MMC1_DAT1|||-|9, 11|SD_SHIELD|||-|10, 12|MMC1_DAT5|||-|}
=== SDIO slot (DWM module) - J14 ===
=== USB ports J14 is a Molex dual row 0.50mm pitch SlimStack™ receptacle. This connector is dedicated to the [[Wireless_Module_(DWM) | DWM add- J15 ===on module]].The following table reports the connector's pinout:
{| class=== I2C bus "wikitable" |-!Pin# !Pin name!Function!Notes|-|1, 2|5V|||-|3, 4|3.3V|||-|5, 6, 9, 10, 19|DGND|||-|7|MMC2_CMD|||-|8|MMC2_CLK|||-|11|MMC2_DAT0|||-|12, 14, 16, 18, 20, 22|N.C.|Not connected||-|13|MMC2_DAT1|||-|15|MMC2_DAT2|||-|17|MMC2_DAT3|||-|21|UART2_RX||Mount option|-|23|UART2_CTS||Mount option|-|24|BT_F5||Connected to DSS_DATA20/DSI_DY1|-|25|UART2_TX||Mount option|-|26|BT_F2||Connected to DSS_DATA21/DSI_DX1|-|27|UART2_RTS||Mount option|-|28|WIFI_IRQ||Connected to DSS_DATA22/DSI_DY2|-|29|BT_EN||Connected to DSS_DATA19/DSI_DX0|-|30|WIFI_EN||Connected to DSS_DATA23/DSI_DX2|- J18 ===|}
=== GPIO USB ports - J19 J15 ===
=== SPI bus - J20 ===J15 is a stacked, dual port USB Type A connector.
=== Audio - J21 = USB port 0 (''high speed'') ====
=== JTAG - J16 ===USB port 0 is mapped on the '''lower''' USB connector. The following table reports the connector's pinout:
Bottom{| class="wikitable" |-!Pin# !Pin name!Function!Notes|-|B1|5V_USBH_0|5V||-|B2|USB0_DM|USB0 Data -||-|B3|USB0_DP|USB0 Data +||-|B4|DGND_USBH_0||Ground|-|}
== Software and hardware usage notes == USB port 1 (''full speed'') ====
=== Quick start===This section describes how to quick start Dacu systemUSB port 1 is mapped on the '''higher''' USB connector.The following table reports the connector's pinout:
==={| class= "Full controlwikitable" mode ====|-!Pin# connect the serial cable, provided with the board, to J3 pin!Pin name!Function!Notes|-|A1|5V_USBH_1|5V||-strip connector# connect this cable to PC COM port through a NULL|A2|USBM1|USB0 Data -||-modem cable (not provided)# start your favourite terminal software on PC; communication parameters are:|A3|USBP1|USB1 Data +||-#* baud rate: 115200 Bps|A4#* data bits: 8|DGND_USBH_1#* stop bits: 1|Ground#* 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=== I2C bus -Boot bootloader will be executed and the following messages will be printed on serial console:J18 ===
<pre class="boardJ18 is a 8-terminal">U-Boot 2009pin 1.25mm pitch vertical header.11-00074-g34e0d5b-dirty (Jul 17 2012 - 11The following table reports the connector's pinout:00:55) [dacu-android-0.9.2]
AM35xx{| class="wikitable" |-GP ES2!Pin# !Pin name!Function!Notes|-|1, 5|DGND|Ground||-|4, 8|3.3V|3.0, L33 V||-165MHzDAVE Lizard board + LPDDR/NAND|2|I2C2_SDA|I2C: ready#2 dataDRAM: 256 MB|Flash: 32 MB|-NAND: 1024 MiB|3In: serial|I2C2_SCLOut: serial|I2C #2 clockErr: serial|Die ID |-|6|I2C3_SDA|I2C #7cf60001000000000160ae2d0b01e00a3 data||-Net: davinci_emac_initialize|7Ethernet PHY: GENERIC @ 0x11|I2C3_SCLDaVinci EMAC |I2C #3 clockHit any key to stop autoboot: 0 |=>|-|}
</pre>=== GPIO - J19 ===
Once J19 is a 8-pin 1.25mm pitch vertical header. The following table reports the boot process has completed, youconnector'll get the default Android "desktop"s pinout:
[[File:Android{| class="wikitable" |-!Pin# !Pin name!Function!Notes|-|1, 8|DGND|Ground||-|2|MCBSP1_CLKX|GPIO||-|3|MCBSP1_DX|GPIO||-|4|MCBSP1_FSX|GPIO||-dacu|5|MCBSP3_DR|GPIO||-lock|6|MCBSP3_FSX|GPIO||-screen.jpg|thumb7|noneMCBSP4_DR|borderGPIO|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.=== SPI bus - J20 ===
==== "Normal" mode ====# connect J20 is a 8-pin 1.25mm pitch vertical header. The following table reports the system to Ethernet LAN (RJ45 connector, J6)# connect a 12Vcc power supply to to the power jack (JP2) 's pinout:
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 {| class="desktopwikitable":|-!Pin# !Pin name!Function!Notes|-|1|DGND|Ground||-|2|MCSPI1_CLK|SPI1 clock||-|3|MCSPI1_CS0|SPI1 chip select #0||-|4|MCSPI1_CS1|SPI1 chip select #1||-|5|MCSPI1_CS2|SPI1 chip select #2||-|6|MCSPI1_SOMI|SPI1 slave output master input||-|7|MCSPI1_SIMO|SPI1 slave input master output||-|8|3.3V|3.3 V||-|}
You can now access the system using adb.=== Audio - J21 ===
J21 is a 8-pin 1.25mm pitch vertical header. The following table reports the connector's pinout:
{| class==== Default IP address ===="wikitable" |-!Pin# !Pin name!Function!Notes|-|1|AUD_PW2|Audio amplifier VO 2||-|2|AUD_PW1|Audio amplifier VO 1||-|3, 5, 7|DGND|Ground||-|4|LINEOUT_R|Audio coded lineout right||-|6|LINEOUT_L|Audio coded lineout left||-|8|MIC_INPUT|Microphone input||-|}
{{ImportantMessage|text='''The default IP address is 192.168.0.122'''}}== JTAG - J16 ===
J16 is a standard 20-pin 2.54mm pitch header connector (bottom side). The following table reports the connector's pinout:
{| class==== Running the Android Debug Bridge (ADB) ===="wikitable" |-!Pin# !Pin name!Function!Notes|-|1, 2[http://developer|3.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 SDK3V|3.3 V||-|3|JTAG_TRSTnTo 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|5|JTAG_TDI$ export ADBHOST=<target's ip address>|$ adb kill-server|$ adb start|-server</pre>|7|JTAG_TMSOn a '''Windows''' host machine, open a shell and launch the following commands:||<pre class="workstation|-terminal">adb tcpip 5555|9|JTAG_TCKadb connect <target's ip address>:5555|adb kill-server|adb start|-server</pre>|11|JTAG_RTCK|To check the connection, please launch||-<pre class="workstation-terminal">|13$ adb devices |JTAG_TDO</pre>||If everything is working properly, you should see the following messages: |-|15<pre class="workstation-terminal">|JTAG_RST#$ adb devices|List of devices attached|Connected to MRSTnemulator|-5554 device</pre>|4, 6, 8, 10, 12, 14, 16, 18, 20|DGNDYou can open a remote shell using the following command:|Ground|<pre class="workstation|-terminal">$ adb shell|17, 19|N.A.|Not connected</pre>||-To install an application (in .apk format), you can use the following commmand:|}
<pre class="workstation-terminal">= Versions ==$ adb install <path As stated before, different versions of DACU board exist in order to apk></pre>support several SOMs and evaluation boards.
===Useful Links===The following pages provide some additional information (including '''schematics''' and '''BOMs''') related to the mating of DACU with the supported SOMs. * [[Dacu for the Diva SOM]]* [[Dacu for the Axel SOM]]
[==Layout==* http://wwwmirror.youtubedave.comeu/diva/dacu/watch?v=VhvlZL46R5Q Video: Android Multitouch demo on Dacu]/dacu-CS091612C_component_view.pdf
[==Mechanical==* DXF: http://developermirror.androiddave.comeu/diva/dacu/dacu_2D_CS091612C.zip* IDF (3D): http://mirror.dave.eu/diva/toolsdacu/help/adbdacu_3D_CS091612C.html Android Debug Bridge]zip
U0007
Bureaucrats, dave_user, Administrators
8,226
edits
Retrieved from "https://wiki.dave.eu/index.php/Special:MobileDiff/1847...13110"