You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/asciidoc/accessories/display/display_intro.adoc
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -159,3 +159,7 @@ To specify these options, add them, separated by commas, to your `dtoverlay` lin
159
159
----
160
160
dtoverlay=vc4-kms-dsi-7inch,sizex=400,invx,invy
161
161
----
162
+
163
+
=== Installation on Compute Module based devices.
164
+
165
+
All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connected to the DSI connector on the Raspberry Pi board is fixed; this autodetection ensures the correct Device Tree entries are passed to the kernel. However, Compute Modules are intended for industrial applications where the integrator can use any and all GPIOs and interfaces for whatever purposes they require. Autodetection is therefore not feasible, and hence is disabled on Compute Module devices. This means that the Device Tree fragments required to set up the display need to be loaded via some other mechanism, which can be either with a dtoverlay entry in config.txt as described above, via a custom base DT file, or if present, a HAT EEPROM.
=== Installation and software setup on Compute Module based devices.
132
+
133
+
All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connected to the DSI connector on the Raspberry Pi board is fixed; this autodetection ensures the correct Device Tree entries are passed to the kernel. However, Compute Modules are intended for industrial applications where the integrator can use any and all GPIOs and interfaces for whatever purposes they require. Autodetection is therefore not feasible, and hence is disabled on Compute Module devices. This means that the Device Tree fragments required to set up the display need to be loaded via some other mechanism, which can be either with a dtoverlay entry in config.txt, via a custom base DT file, or if present, a HAT EEPROM.
134
+
135
+
Creating a custom base Device tree file is beyond the scope of this documentation, however, it is simple to add an appropriate device tree entry via `config.txt`. See this xref:../computers/compute-module.adoc#attaching-the-touch-display-2-lcd-panel[page] for configuration details.
Copy file name to clipboardExpand all lines: documentation/asciidoc/computers/compute-module/cmio-display.adoc
+28-8Lines changed: 28 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -1,20 +1,20 @@
1
-
== Attach the official 7-inch display
1
+
== Attaching the Touch Display LCD panel
2
2
3
3
Update your system software and firmware to the latest version before starting.
4
4
Compute Modules mostly use the same process, but sometimes physical differences force changes for a particular model.
5
5
6
-
=== Connect a display to DISP1
6
+
=== Connect a display to DISP1/DSI1
7
7
8
8
NOTE: The Raspberry Pi Zero camera cable cannot be used as an alternative to the RPI-DISPLAY adapter. The two cables have distinct wiring.
9
9
10
-
To connect a display to DISP1:
10
+
To connect a display to DISP1/DSI1:
11
11
12
12
. Disconnect the Compute Module from power.
13
-
. Connect the display to the DISP1 port on the Compute Module IO board through the 22W to 15W display adapter.
13
+
. Connect the display to the DISP1/DSI1 port on the Compute Module IO board through the 22W to 15W display adapter.
14
14
. _(CM1, CM3, CM3+, and CM4S only)_: Connect the following GPIO pins with jumper cables:
15
15
* `0` to `CD1_SDA`
16
16
* `1` to `CD1_SCL`
17
-
17
+
. _(CM5)_ On the Compute Module 5 IO board, add the appropriate jumpers to J6, as indicated on the silkscreen.
18
18
. Reconnect the Compute Module to power.
19
19
. Add the following line to xref:../computers/config_txt.adoc#what-is-config-txt[`/boot/firmware/config.txt`]:
20
20
+
@@ -24,15 +24,17 @@ dtoverlay=vc4-kms-dsi-7inch
24
24
----
25
25
. Reboot your Compute Module with `sudo reboot`. Your device should detect and begin displaying output to your display.
26
26
27
-
=== Connect a display to DISP0
27
+
=== Connect a display to DISP0/DSI0
28
28
29
-
To connect a display to DISP0:
29
+
To connect a display to DISP0/DSI0 on CM1, CM3 and CM4 IO boards:
30
30
31
-
. Connect the display to the DISP0 port on the Compute Module IO board through the 22W to 15W display adapter.
31
+
. Connect the display to the DISP0/DSI0 port on the Compute Module IO board through the 22W to 15W display adapter.
32
32
. _(CM1, CM3, CM3+, and CM4S only)_: Connect the following GPIO pins with jumper cables:
33
33
* `28` to `CD0_SDA`
34
34
* `29` to `CD0_SCL`
35
35
36
+
. _(CM4 only)_ On the Compute Module 4 IO board, add the appropriate jumpers to J6, as indicated on the silkscreen.
37
+
36
38
. Reconnect the Compute Module to power.
37
39
. Add the following line to `/boot/firmware/config.txt`:
38
40
+
@@ -61,3 +63,21 @@ To entirely ignore the display when connected, add the following line to `/boot/
61
63
----
62
64
ignore_lcd=1
63
65
----
66
+
67
+
== Attaching the Touch Display 2 LCD panel
68
+
69
+
Touch Display 2 is a 720x1280 7" LCD display designed specifically for Raspberry Pi devices (see https://www.raspberrypi.com/products/touch-display-2/). It connects in the same way as the original touch display, but the software setup on Compute Modules is slightly different as it uses a different display driver. See xref:../accessories/touch-display-2.adoc[Touch Display 2] for connection details.
70
+
71
+
Edit the /boot/firmware/config.txt file and add the following to enable Touch Display 2 on DISP1/DSI1. You will also need to add jumpers to J6 as indicated on the silkscreen.
0 commit comments