Changes

Jump to: navigation, search
no edit summary
<section begin="History" />
{| style="border-collapse:collapse; "
!colspan="4" style="width:100%; text-align:left"; border-bottom:solid 2px #ededed"|History
|-
!style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white"|Version!style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white"|Issue Date!style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#73B2C7; padding:5px; color:white"|Notes
|-
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|X1.Y0.Z0|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|Month YearSep 2021|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|TBDFirst release
|-
|-
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|[TBD_link X.Y.Z]
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|Month Year
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|TBD
|-
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|...
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|...
|style="border-left:solid 2px #73B2C7; border-right:solid 2px #73B2C7;border-top:solid 2px #73B2C7; border-bottom:solid 2px #73B2C7; background-color:#edf8fb; padding:5px; color:#000000"|...
|-
|}
<section end="History" /><section begin="Body" />
==Touchscreen interface ==
''TBD: sostituire le sezioni con le informazioni sull'uso della periferica e del suo connettore''=== Description ===''Nell'esempio di seguito c'è la descrizione dell'interfaccia UARTThe Evaluation Kit default LCD panel (provided on request) interfaces the touchscreen via USB, thus it is connected to J3 or J4, see [[ORCA SOM/console''ORCA Evaluation Kit/Interfaces and Connectors/USB ports|USB ports]] section.
=== Description ===Many touchscreen types use instead an I2C interface with two additional control signals (RST, IRQ).
The Touchscreen To use these type of touchscreens the interface available on the Evaluation Kit at signals can be routed to the expansion connector ''TBD:Jxxx''J8.
''Jxx'' An external circuit is a ''TBD:connector-type'' header connector for recommended to correctly conditioning the RS232 two-wires UART3 portinterface signals, used for debug purposes (bootloader such as buffers and operating system serial console)pull up/down, according to the touchscreen specifications.
===Signals ===
The following table describes the interface available I2C signals on J8 connector, see [[ORCA SOM/ORCA Evaluation Kit/Interfaces and Connectors/GPIOs|GPIO section]] for available control signals:
{| class="wikitable"
! latexfontsize="scriptsize"| Pin#! latexfontsize="scriptsize"| SOM Pin#! latexfontsize="scriptsize"| Pin name! latexfontsize="scriptsize"| Pin function! latexfontsize="scriptsize"| Pin Notes|-|19||ECSPI2_MOSI|I2C3_SDA||-|21||ECSPI2_MISO|I2C4_SCL||-|22||SAI5_MCLK|I2C5_SDA||-|23||ECSPI2_SCLK|I2C3_SCL||-|24||ECSPI2_SS0|I2C4_SDA||-|32||SAI5_RXFS|I2C6_SCL||-|38||SAI5_RXD0|I2C5_SCL||-|40||SAI5_RXC|I2C6_SDA|
|-
|1,2,4,6,,7,8,1017
| -
| N.A.3V3_CB| N.C+3.3V| Not connectedBOARD_PGOOD driven rail
|-
| 3| J1.189| RS232_RX| Receive line| 2, 4|-| 3| J1.187| RS232_TX5V_VIN| Transmit line+5V| Always powered
|-
| 6, 9, 14, 20, 25, 30, 34, 39
| -
| DGND| Ground|
|}
All the I2C signals use 0 - 3.3V levels, external pull-ups to <code>3V3_CB</code> are needed.
=== Device mapping ===
UART3 The device is typically mapped to <code>/dev/ttymxc2touchscreen0</code> device in Linux. The peripheral is used as the default serial console, both for the bootloader and the kernel.
=== Device usage ===The touch controller is attached to the generic Linux input event interface (evdev).
To connect For I2C touchscreen controllers a dedicated node in the device-tree has to be configured to correctly bind the debug serial port:driver.
# connect the DB9 adapter bracket === Device usage ===The touchscreen device is often passed as parameter to the J22 connector on the SBCX board# connect a serial cable between DB9 connector and PC COM port through a NULL-modem cable (not provided)# start your favorite terminal emulator software on PC (eg: PuTTY); communication parameters are: 115200,N,8,1user interface application or is automatically discovered.
Touchscreen can be tested with the <code>evtest</code> tool that prints the finger coordinates to the console.
----
[[Category:ORCA SOM]]
a000298_approval, dave_user
549
edits

Navigation menu