Industrial Tablet
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
Info Box
|
Introduction[edit | edit source]
DAVE Embedded Systems Industrial Tablet is a ARM Cortex-A8 platform based on the Lizard SOM and the Dacu carrier board.
Main Features[edit | edit source]
- Up to 256 MB DDR2 SDRAM
- Flash memory storageFlash NOR and Flash NAND on board
- USB Host
- USB OTG
- 1 x SD/MMC
- Fast Ethernet LAN
- 800x480 7" LCD display
- Capacitive touch screen
- Touch Screen controller
- 1 x RS232 UART, 1x RS485 UART, 2 x I²C, 1 x SPI
- Audio
- +12V/+24V power
Video[edit | edit source]
Android Multitouch demo on Dacu
Software and hardware usage notes[edit | edit source]
Linux board support package for Dacu[edit | edit source]
The Linux version that runs on the Industrial Tablet derives from the version provided with the Lizard Embedded Linux Kit 1.2.0.
| Bootloader | U-Boot |
| Linux version | 2.6.32-dacu |
| Drivers list | NOR flash NAND flash Ethernet LCD controller - AM800480STM display (LVDS version) Backlight PWM UART (RS232/RS485/RS422) CAN SPI I2C USB Host MMC/SD/SDIO Resistive touch screen RTC UDA1374 audio codec 1-Wire INA226 sensors |
| Root file system | Same as LELK 1.2.0 |
Android board support package description[edit | edit source]
The Android version that runs on the Industrial Tablet 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[edit | edit source]
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:
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 =>
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 Configuration net_nfs.
Android quick start[edit | edit source]
This section describes how to quick start Android operating system on Dacu.
"Full control" mode[edit | edit source]
- 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:
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 =>
Once the boot process has completed, you'll get the default Android "desktop":
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[edit | edit source]
- 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[edit | edit source]
 The default IP address is 192.168.0.122 |
Running the Android Debug Bridge[edit | edit source]
Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device. With adb, developers can remotely access the Android device (via USB, USB-ETH or ETH) to check the status, open a shell, etc. (http://developer.android.com/guide/developing/tools/adb.html).
To enable adb (via ethernet), the following commands must be launched on the target:
target #> setprop service.adb.tcp.port 5555 target #> stop adbd target #> start adbd
On the host machine, after Android SDK installation, launch:
$ export PATH=${PATH}:<your_sdk_dir>/platform-tools
$ export ADBHOST=<target's ip address>
$ adb kill-server
$ adb start-server
To check the connection, from the host machine launch:
$ adb devices
If the device is properly connected and detected, the output will be the following:
$ adb devices List of devices attached emulator-5554 device
A remote shell can be started with the following command:
$ adb shell
To install an application (in .apk format), launch:
$ adb install <path to apk>
