AURA SOM/AURA Evaluation Kit/Interfaces and Connectors/Touchscreen
| HOME | SOMs | SBCs | ToloMEO Embedded Assistant |  GET A QUOTE
|
 ONLINE HELPDESK
|
| Roadmap | IoT Services | ML/AI services | Embedded Design Services |
| History | |||
|---|---|---|---|
| Issue Date | Notes | ||
| 2024/05/23 | First release | ||
Touchscreen interface[edit | edit source]
Description[edit | edit source]
The Evaluation Kit default LCD panel interfaces the touchscreen via USB, thus it is connected to J17, see USB port section.
Many touchscreen types use instead an I2C interface with two additional control signals (RST, IRQ). To use these type of touchscreens the interface signals can be routed to the expansion connector J33.
An external circuit is recommended to correctly condition the interface signals, such as buffers and pull up/down, according to the touchscreen specifications.
Signals[edit | edit source]
The following table describes the available I2C signals on J33 connector, see GPIO section for available control signals:
| Pin# | SOM Pin# | Pin name | Pin function | Pin Notes |
|---|---|---|---|---|
| 18 | J10.38 | GPIO2_IO29 | I2C3_SCL | |
| 20 | J10.48 | GPIO2_IO28 | I2C3_SDA | |
| 48, 50 | - | 3V3 | +3.3V | BOARD_PGOOD driven rail |
| 56, 58 | - | VIN | Always powered | |
| 2, 16, 22, 36, 46, 59, 60 | - | DGND | Ground |
All the I2C signals use 0 - 3.3V levels, external pull-ups to 3V3_CB are needed.
Device mapping[edit | edit source]
The device is typically mapped to /dev/touchscreen0 device in Linux.
The touch controller is attached to the generic Linux input event interface (evdev).
For I2C touchscreen controllers a dedicated node in the device-tree has to be configured to correctly bind the driver.
Device usage[edit | edit source]
The touchscreen device is often passed as parameter to the user interface application or is automatically discovered.
Touchscreen can be tested with the evtest tool that prints the finger coordinates to the console.
