From 3b822205e066a932a60e6dd292132e379dce14d2 Mon Sep 17 00:00:00 2001 From: James Hughes Date: Wed, 16 Apr 2025 10:55:33 +0100 Subject: [PATCH 1/4] Add information on setting up TD2 on Compute modules --- .../accessories/touch-display-2/about.adoc | 20 +++++++++++++++++++ .../compute-module/cmio-display.adoc | 18 +++++++++++++++++ 2 files changed, 38 insertions(+) diff --git a/documentation/asciidoc/accessories/touch-display-2/about.adoc b/documentation/asciidoc/accessories/touch-display-2/about.adoc index 35763f58e..2476c8156 100644 --- a/documentation/asciidoc/accessories/touch-display-2/about.adoc +++ b/documentation/asciidoc/accessories/touch-display-2/about.adoc @@ -127,3 +127,23 @@ To specify these options, add them, separated by commas, to your `dtoverlay` lin ---- dtoverlay=vc4-kms-dsi-ili9881-7inch,sizex=400,invx,invy ---- + +=== Installation and software setup on Compute Module based devices. + +All Raspberry Pi SBCs auto-detect the official touch displays as the wiring to them is known, and this autodetection ensures the correct Device Tree entries are passed to the kernel. However, Compute Modules are intended for industrial applications where the integrator is entitled to 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 or via a custom base DT file. + +Creating a custom base Device tree file is beyond the scope of this documenation, however, it is simple to add an appropriate device tree entry via `config.txt` + +Edit the /boot./firmware/config.txt file and add the following to enable Touchdisplay 2 on DSI1, on a compute module based device. + +[source,ini] +---- +dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi1 +---- + +To use DSI0 use the following: + +[source,ini] +---- +dtoverlay=vc4-kms-dsi-ili9881-7inch, dsi0 +---- diff --git a/documentation/asciidoc/computers/compute-module/cmio-display.adoc b/documentation/asciidoc/computers/compute-module/cmio-display.adoc index c883a8648..bb28b6072 100644 --- a/documentation/asciidoc/computers/compute-module/cmio-display.adoc +++ b/documentation/asciidoc/computers/compute-module/cmio-display.adoc @@ -61,3 +61,21 @@ To entirely ignore the display when connected, add the following line to `/boot/ ---- ignore_lcd=1 ---- + +== Attaching the Touch Display 2 LCD panel + +Touch Display 2 is a 720p 7" LCD display designed specifailly for Raspberry Pi devices (see https://www.raspberrypi.com/products/touch-display-2/). It connects in much 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/about.adoc[Touch Display 2] for connection details. + +Edit the /boot./firmware/config.txt file and add the following to enable Touch Display 2 on DSI1. + +[source,ini] +---- +dtoverlay=vc4-kms-dsi-ili9881-7inch +---- + +To use DSI0 use the following: + +[source,ini] +---- +dtoverlay=vc4-kms-dsi-ili9881-7inch, dsi0 +---- From e8a4aa7b6b990e6943b6a12f38cf500c5295bae6 Mon Sep 17 00:00:00 2001 From: James Hughes Date: Thu, 17 Apr 2025 11:29:01 +0100 Subject: [PATCH 2/4] Updated from review comments --- .../accessories/display/display_intro.adoc | 4 ++++ .../accessories/touch-display-2/about.adoc | 17 ++--------------- .../computers/compute-module/cmio-display.adoc | 6 +++--- 3 files changed, 9 insertions(+), 18 deletions(-) diff --git a/documentation/asciidoc/accessories/display/display_intro.adoc b/documentation/asciidoc/accessories/display/display_intro.adoc index 424540ab6..d272cab15 100644 --- a/documentation/asciidoc/accessories/display/display_intro.adoc +++ b/documentation/asciidoc/accessories/display/display_intro.adoc @@ -159,3 +159,7 @@ To specify these options, add them, separated by commas, to your `dtoverlay` lin ---- dtoverlay=vc4-kms-dsi-7inch,sizex=400,invx,invy ---- + +=== Installation on Compute Module based devices. + +All Raspberry Pi SBCs auto-detect the official touch display's as the circuitry connecting it to the DSI connector is fixed, and 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. \ No newline at end of file diff --git a/documentation/asciidoc/accessories/touch-display-2/about.adoc b/documentation/asciidoc/accessories/touch-display-2/about.adoc index 2476c8156..82df603f8 100644 --- a/documentation/asciidoc/accessories/touch-display-2/about.adoc +++ b/documentation/asciidoc/accessories/touch-display-2/about.adoc @@ -130,20 +130,7 @@ dtoverlay=vc4-kms-dsi-ili9881-7inch,sizex=400,invx,invy === Installation and software setup on Compute Module based devices. -All Raspberry Pi SBCs auto-detect the official touch displays as the wiring to them is known, and this autodetection ensures the correct Device Tree entries are passed to the kernel. However, Compute Modules are intended for industrial applications where the integrator is entitled to 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 or via a custom base DT file. +All Raspberry Pi SBCs auto-detect the official touch display's as the circuitry connecting it to the DSI connector is fixed, and 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. -Creating a custom base Device tree file is beyond the scope of this documenation, however, it is simple to add an appropriate device tree entry via `config.txt` +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/cmio-display.adoc#Attaching-the-Touch-Display-2-LCD-panel[page] for connection details. -Edit the /boot./firmware/config.txt file and add the following to enable Touchdisplay 2 on DSI1, on a compute module based device. - -[source,ini] ----- -dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi1 ----- - -To use DSI0 use the following: - -[source,ini] ----- -dtoverlay=vc4-kms-dsi-ili9881-7inch, dsi0 ----- diff --git a/documentation/asciidoc/computers/compute-module/cmio-display.adoc b/documentation/asciidoc/computers/compute-module/cmio-display.adoc index bb28b6072..044628d72 100644 --- a/documentation/asciidoc/computers/compute-module/cmio-display.adoc +++ b/documentation/asciidoc/computers/compute-module/cmio-display.adoc @@ -64,9 +64,9 @@ ignore_lcd=1 == Attaching the Touch Display 2 LCD panel -Touch Display 2 is a 720p 7" LCD display designed specifailly for Raspberry Pi devices (see https://www.raspberrypi.com/products/touch-display-2/). It connects in much 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/about.adoc[Touch Display 2] for connection details. +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 much 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/about.adoc[Touch Display 2] for connection details. -Edit the /boot./firmware/config.txt file and add the following to enable Touch Display 2 on DSI1. +Edit the /boot/firmware/config.txt file and add the following to enable Touch Display 2 on DSI1. [source,ini] ---- @@ -77,5 +77,5 @@ To use DSI0 use the following: [source,ini] ---- -dtoverlay=vc4-kms-dsi-ili9881-7inch, dsi0 +dtoverlay=vc4-kms-dsi-ili9881-7inch,dsi0 ---- From 6d5f6830d21a3fec0a06e5141b8d3b425583d794 Mon Sep 17 00:00:00 2001 From: James Hughes Date: Tue, 22 Apr 2025 14:52:02 +0100 Subject: [PATCH 3/4] Updated after review comments --- documentation/asciidoc/accessories/display/display_intro.adoc | 2 +- documentation/asciidoc/accessories/touch-display-2/about.adoc | 4 ++-- .../asciidoc/computers/compute-module/cmio-display.adoc | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/asciidoc/accessories/display/display_intro.adoc b/documentation/asciidoc/accessories/display/display_intro.adoc index d272cab15..27417481b 100644 --- a/documentation/asciidoc/accessories/display/display_intro.adoc +++ b/documentation/asciidoc/accessories/display/display_intro.adoc @@ -162,4 +162,4 @@ dtoverlay=vc4-kms-dsi-7inch,sizex=400,invx,invy === Installation on Compute Module based devices. -All Raspberry Pi SBCs auto-detect the official touch display's as the circuitry connecting it to the DSI connector is fixed, and 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. \ No newline at end of file +All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connecting it to the DSI connector 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. \ No newline at end of file diff --git a/documentation/asciidoc/accessories/touch-display-2/about.adoc b/documentation/asciidoc/accessories/touch-display-2/about.adoc index 82df603f8..e502b6cd2 100644 --- a/documentation/asciidoc/accessories/touch-display-2/about.adoc +++ b/documentation/asciidoc/accessories/touch-display-2/about.adoc @@ -130,7 +130,7 @@ dtoverlay=vc4-kms-dsi-ili9881-7inch,sizex=400,invx,invy === Installation and software setup on Compute Module based devices. -All Raspberry Pi SBCs auto-detect the official touch display's as the circuitry connecting it to the DSI connector is fixed, and 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. +All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connecting it to the DSI connector 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. -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/cmio-display.adoc#Attaching-the-Touch-Display-2-LCD-panel[page] for connection details. +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/cmio-display.adoc#attaching-the-touch-display-2-lcd-panel[page] for configuration details. diff --git a/documentation/asciidoc/computers/compute-module/cmio-display.adoc b/documentation/asciidoc/computers/compute-module/cmio-display.adoc index 044628d72..01c5b8e10 100644 --- a/documentation/asciidoc/computers/compute-module/cmio-display.adoc +++ b/documentation/asciidoc/computers/compute-module/cmio-display.adoc @@ -64,7 +64,7 @@ ignore_lcd=1 == Attaching the Touch Display 2 LCD panel -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 much 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/about.adoc[Touch Display 2] for connection details. +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 much 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. Edit the /boot/firmware/config.txt file and add the following to enable Touch Display 2 on DSI1. From 706602063e23e9f0dd000e452b3bec6c5202ed63 Mon Sep 17 00:00:00 2001 From: Andrew Scheller Date: Wed, 23 Apr 2025 11:42:25 +0100 Subject: [PATCH 4/4] Fix xref URL --- documentation/asciidoc/accessories/touch-display-2/about.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/asciidoc/accessories/touch-display-2/about.adoc b/documentation/asciidoc/accessories/touch-display-2/about.adoc index e502b6cd2..680aa27aa 100644 --- a/documentation/asciidoc/accessories/touch-display-2/about.adoc +++ b/documentation/asciidoc/accessories/touch-display-2/about.adoc @@ -132,5 +132,5 @@ dtoverlay=vc4-kms-dsi-ili9881-7inch,sizex=400,invx,invy All Raspberry Pi SBCs auto-detect the official Touch Displays as the circuitry connecting it to the DSI connector 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. -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/cmio-display.adoc#attaching-the-touch-display-2-lcd-panel[page] for configuration details. +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.