Skip to content

Commit 8d5f016

Browse files
Merge pull request #4207 from raspberrypi/develop
Trixie image updates and accessibility changes
2 parents b4b85f0 + 8ac282a commit 8d5f016

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

51 files changed

+127
-145
lines changed

.github/workflows/build.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,8 +16,8 @@ jobs:
1616
echo "Pull requests based on master can only come from the develop branch of this repository"
1717
echo "Please check your base branch as it should be develop by default"
1818
exit 1
19-
- uses: actions/checkout@v4
20-
- uses: actions/setup-python@v5
19+
- uses: actions/checkout@v5
20+
- uses: actions/setup-python@v6
2121
with:
2222
python-version: 3.9
2323
- name: Install Python dependencies

.github/workflows/stale.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ jobs:
1313
pull-requests: write
1414

1515
steps:
16-
- uses: actions/stale@v9
16+
- uses: actions/stale@v10
1717
with:
1818
repo-token: ${{ secrets.GITHUB_TOKEN }}
1919
stale-issue-message: 'This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.'
-441 KB
Loading

documentation/asciidoc/accessories/build-hat/preparing-build-hat.adoc

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22

33
NOTE: Before starting to work with your Raspberry Pi Build HAT you should xref:../computers/getting-started.adoc#setting-up-your-raspberry-pi[set up] your Raspberry Pi, xref:../computers/getting-started.adoc#installing-the-operating-system[install] the latest version of the operating system using https://www.raspberrypi.com/downloads/[Raspberry Pi Imager].
44

5-
Attach 9mm spacers to the bottom of the board. Seat the Raspberry Pi Build HAT onto your Raspberry Pi. Make sure you put it on the right way up. Unlike other HATs, all the components are on the bottom, leaving room for a breadboard or LEGO® elements on top.
5+
Attach 9mm spacers to the bottom of the board. Seat the Raspberry Pi Build HAT onto your Raspberry Pi. Make sure you put it on the right way up. Unlike other HATs, all the components are on the bottom, leaving room for a breadboard or LEGO® elements on top.
66

77
video::images/fitting-build-hat.webm[width="80%"]
88

@@ -18,22 +18,22 @@ The following pins are used by the Build HAT itself and you should not connect a
1818
[cols="^1,^1,^1", width="75%", options="header"]
1919
|===
2020
| GPIO| Use | Status
21-
| GPIO0/1 | ID prom |
22-
| GPIO4| Reset |
23-
| GPIO14| Tx |
24-
| GPIO15| Rx |
21+
| GPIO0/1 | ID prom |
22+
| GPIO4| Reset |
23+
| GPIO14| Tx |
24+
| GPIO15| Rx |
2525
| GPIO16 | RTS | unused
2626
| GPIO17 | CTS | unused
2727
|===
2828

2929

3030
=== Set up your Raspberry Pi
3131

32-
Once the Raspberry Pi has booted, open the Raspberry Pi Configuration tool by clicking on the Raspberry Menu button and then selecting "Preferences" and then "Raspberry Pi Configuration".
32+
Once the Raspberry Pi has booted, open the Control Centre tool by selecting the Raspberry Menu button and then selecting **Preferences > Control Centre**.
3333

34-
Click on the "interfaces" tab and adjust the Serial settings as shown below:
34+
Select the **Interfaces** tab and adjust the serial settings as shown in the following image:
3535

36-
image::images/setting-up.png[width="50%"]
36+
image::images/setting-up.png["The Interfaces tab. SSH, VNC, and Serial Port are enabled. The rest of the options are not enabled.", width="50%"]
3737

3838
==== Use your Raspberry Pi headless
3939

documentation/asciidoc/accessories/display/display_intro.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ image::images/display.png[The Raspberry Pi 7-inch Touch Display, width="70%"]
77

88
The Touch Display is compatible with all models of Raspberry Pi, except the Zero series and Keyboard series, which lack a DSI connector. The earliest Raspberry Pi models lack appropriate mounting holes, requiring additional mounting hardware to fit the stand-offs on the display PCB.
99

10-
The display has the following key features:
10+
The display has the following key features:
1111

1212
* 800×480px RGB LCD display
1313
* 24-bit colour
@@ -79,7 +79,7 @@ Raspberry Pi OS _Bookworm_ and later include the Squeekboard on-screen keyboard
7979

8080
For applications which do not support text entry detection, use the keyboard icon at the right end of the taskbar to manually show and hide the keyboard.
8181

82-
You can also permanently show or hide the on-screen keyboard in the Display tab of Raspberry Pi Configuration or the `Display` section of `raspi-config`.
82+
You can also permanently show or hide the on-screen keyboard in the **Display** tab of Control Centre or the `Display` section of `raspi-config`.
8383

8484
TIP: In Raspberry Pi OS releases prior to _Bookworm_, use `matchbox-keyboard` instead. If you use the wayfire desktop compositor, use `wvkbd` instead.
8585

667 KB
Loading

documentation/asciidoc/accessories/touch-display-2/about.adoc

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
The https://www.raspberrypi.com/products/touch-display-2/[Raspberry Pi Touch Display 2] is a portrait orientation touchscreen LCD (with rotation options) designed for interactive projects like tablets, entertainment systems, and information dashboards.
1+
The https://www.raspberrypi.com/products/touch-display-2/[Raspberry Pi Touch Display 2] is a portrait orientation touchscreen LCD (with rotation options) designed for interactive projects like tablets, entertainment systems, and information dashboards.
22

33
.The Raspberry Pi Touch Display 2
44
image::images/touch-display-2-hero.jpg[width="80%"]
@@ -36,7 +36,7 @@ The Touch Display 2 is available in two sizes: 5-inch and 7-inch (measured diago
3636
Touch Display 2 (both 5-inch and 7-inch) includes the following features:
3737

3838
* **720 x 1280 pixel resolution.** High-definition output.
39-
* **24-bit RGB display.** Capable of showing over 16 million colours.
39+
* **24-bit RGB display.** Capable of showing over 16 million colours.
4040
* **Multitouch.** Supports up to five simultaneous touch points.
4141
* **Mouse-equivalence.** Supports full desktop control without a physical mouse, for example, selecting, dragging, scrolling, and long-pressing for menus.
4242
* **On-screen keyboard.** Supports a visual keyboard in place of a physical keyboard.
@@ -62,7 +62,7 @@ image::images/touch-display-2-whats-in-the-booooox.jpg["Parts included in the To
6262
The Touch Display 2 connects to a Raspberry Pi using:
6363

6464
- A **DSI connector** for video and touch data.
65-
- The **GPIO header** for power.
65+
- The **GPIO header** for power.
6666

6767
To make the DSI connection, use a **Flat Flexible Cable (FFC)** included with your display. The type of FFC you need depends on your Raspberry Pi model:
6868

@@ -78,7 +78,7 @@ After determining the correct FFC for your Raspberry Pi model, you can connect y
7878
.A Raspberry Pi 5 connected and mounted to the Touch Display 2
7979
image::images/touch-display-2-installation-diagram.png["A Raspberry Pi 5 connected and mounted to the Touch Display 2", width="80%"]
8080

81-
IMPORTANT: Disconnect your Raspberry Pi from power before completing the following steps.
81+
IMPORTANT: Disconnect your Raspberry Pi from power before completing the following steps.
8282

8383
=== Step 1. Connect FFC to Touch Display 2
8484

@@ -90,16 +90,16 @@ IMPORTANT: Disconnect your Raspberry Pi from power before completing the followi
9090

9191
=== Step 2. Connect FFC to Raspberry Pi
9292

93-
. Slide the retaining clip upwards from both sides of the DSI connector of your Raspberry Pi.
94-
- This port should be marked with some variation of the term **DISPLAY**, **CAM/DISP**, or **DISP**.
93+
. Slide the retaining clip upwards from both sides of the DSI connector of your Raspberry Pi.
94+
- This port should be marked with some variation of the term **DISPLAY**, **CAM/DISP**, or **DISP**.
9595
- If your Raspberry Pi has multiple DSI connectors, we recommend using the port labelled **1**.
9696
. Insert the other end of your FFC into the Raspberry Pi DSI connector, with the metal contacts facing the Ethernet and USB-A ports.
9797
. Hold the FFC firmly in place and simultaneously push the retaining clip back down on the FFC connector of the Raspberry Pi to secure the cable.
9898

9999
=== Step 3. Connect the GPIO power cable
100100

101101
. Plug the smaller end of the GPIO power cable into the **J1** port on the Touch Display 2.
102-
. Connect the three-pin end of the GPIO power cable to your xref:../computers/raspberry-pi.adoc#gpio[Raspberry Pi's GPIO].
102+
. Connect the three-pin end of the GPIO power cable to your xref:../computers/raspberry-pi.adoc#gpio[Raspberry Pi's GPIO].
103103

104104
This connects the red cable (5 V power) to pin 2 and the black cable (ground) to pin 6. Viewed from above, with the Ethernet and USB-A ports facing down, these pins are located in the top-right corner of the board, with pin 2 in the top right-most position.
105105

@@ -123,7 +123,7 @@ Raspberry Pi OS **Bookworm** and later already includes the **Squeekboard on-scr
123123

124124
For applications that don't support text entry detection, you can manually show or hide the keyboard using the keyboard icon at the right side of the taskbar. You can also permanently show or hide the on-screen keyboard using the Raspberry Pi graphical interface or the command line.
125125

126-
- **Raspberry Pi desktop interface:** From the Raspberry Pi menu, go to **Preferences > Raspberry Pi Configuration > Display** and choose your on-screen keyboard setting.
126+
- **Raspberry Pi desktop interface:** From the Raspberry Pi menu, go to **Preferences > Control Centre > Display** and choose your on-screen keyboard setting.
127127
- **Command line:** Open a terminal and enter `sudo raspi-config`. Navigate to the **Display** section of `raspi-config` and then choose your keyboard setting.
128128

129129
== Change screen orientation
@@ -135,7 +135,7 @@ You have four rotation options:
135135
- **0** maintains the default display position, which is a portrait orientation.
136136
- **90** rotates the display 90 degrees to the right (clockwise), making it a landscape orientation.
137137
- **180** rotates the display 180 degrees to the right (clockwise), which flips the display upside down.
138-
- **270** rotates the display 270 degrees to the right (clockwise), which is the same as rotating the display 90 degrees to the left (counterclockwise), making it a landscape orientation.
138+
- **270** rotates the display 270 degrees to the right (clockwise), which is the same as rotating the display 90 degrees to the left (counterclockwise), making it a landscape orientation.
139139

140140
=== With a desktop
141141
If you have the Raspberry Pi OS desktop running, you can rotate the display through the **Screen Configuration** tool:
@@ -160,14 +160,14 @@ NOTE: You can't rotate the DSI display separately from the HDMI display with `cm
160160

161161
== Customise touchscreen settings
162162

163-
You can use the Device Tree overlay to tell Raspberry Pi OS how to configure the Touch Display 2 at boot.
163+
You can use the Device Tree overlay to tell Raspberry Pi OS how to configure the Touch Display 2 at boot.
164164

165165
- For the 5-inch display, the overlay is called `vc4-kms-dsi-ili9881-5inch`.
166166
- For the 7-inch display, the overlay is called `vc4-kms-dsi-ili9881-7inch`.
167167

168168
You can modify the Device Tree overlay in the boot configuration file (`/boot/firmware/config.txt`).
169169

170-
Open `/boot/firmware/config.txt` and then add the required Device Tree parameters to the `dtoverlay` line, separated by commas.
170+
Open `/boot/firmware/config.txt` and then add the required Device Tree parameters to the `dtoverlay` line, separated by commas.
171171

172172
- Booleans (`invx`, `invy`, `swapxy`, and `disable_touch`) default to true if present, but you can set them to false using the suffix `=0`.
173173
- Integers (`sizex` and `sizey`) require a number, for example, `sizey=240`.
@@ -210,14 +210,14 @@ dtoverlay=vc4-kms-dsi-ili9881-7inch,invx,invy
210210

211211
== Connect to a Compute Module
212212

213-
Unlike Raspberry Pi single board computers (SBC), which automatically detect the official Raspberry Pi Touch displays, Raspberry Pi Compute Modules don't automatically detect connected devices; you must tell it what display is attached.
213+
Unlike Raspberry Pi single board computers (SBC), which automatically detect the official Raspberry Pi Touch displays, Raspberry Pi Compute Modules don't automatically detect connected devices; you must tell it what display is attached.
214214

215-
This is because the connections between the SoC and DSI connectors on a Raspberry Pi are fixed and the system knows what hardware is connected; auto-detection ensures that the correct Device Tree settings are passed to the Linux kernel, so the display works without additional configuration.
215+
This is because the connections between the SoC and DSI connectors on a Raspberry Pi are fixed and the system knows what hardware is connected; auto-detection ensures that the correct Device Tree settings are passed to the Linux kernel, so the display works without additional configuration.
216216

217217
Compute Modules, intended for industrial and custom applications, expose all GPIOs and interfaces. This provides greater flexibility for connecting hardware, but means that a Compute Module can't automatically detect devices like the Touch Display 2. This means that, for Compute Modules, the Device Tree fragments, which tell the kernel how to interact with the display, must be manually specified. You can do this in three ways:
218218

219219
- By adding an overlay entry in `config.txt`. This is the simplest option. For configuration instructions, see the xref:../computers/compute-module.adoc#attaching-the-touch-display-2-lcd-panel[Compute Module hardware documentation].
220220
- Using a custom base device tree file. This is an advanced method not covered in this online documentation.
221-
- Using a HAT EEPROM (if present).
221+
- Using a HAT EEPROM (if present).
222222

223223

documentation/asciidoc/computers/config_txt/overclocking.adoc

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ WARNING: Setting any overclocking parameters to values other than those used by
5757
| SDRAM phy voltage adjustment. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Not supported on Raspberry Pi 4 or later devices.
5858

5959
| force_turbo
60-
| Forces turbo mode frequencies even when the ARM cores are not busy. Enabling this may set the warranty bit if `over_voltage_*` is also set.
60+
| Forces turbo mode frequencies even when the Arm cores are not busy. Enabling this may set the warranty bit if `over_voltage_*` is also set.
6161

6262
| initial_turbo
6363
| Enables https://forums.raspberrypi.com/viewtopic.php?f=29&t=6201&start=425#p180099[turbo mode from boot] for the given value in seconds, or until `cpufreq` sets a frequency. The maximum value is `60`. The November 2024 firmware update made the following changes:
@@ -339,17 +339,17 @@ NOTE: There is no need to use `hdmi_enable_4kp60` on Flagship models since Raspb
339339

340340
==== `force_turbo`
341341

342-
By default (`force_turbo=0`) the on-demand CPU frequency driver will raise clocks to their maximum frequencies when the ARM cores are busy, and will lower them to the minimum frequencies when the ARM cores are idle.
342+
By default (`force_turbo=0`) the on-demand CPU frequency driver will raise clocks to their maximum frequencies when the Arm cores are busy, and will lower them to the minimum frequencies when the Arm cores are idle.
343343

344-
`force_turbo=1` overrides this behaviour and forces maximum frequencies even when the ARM cores are not busy.
344+
`force_turbo=1` overrides this behaviour and forces maximum frequencies even when the Arm cores are not busy.
345345

346346
=== Clocks relationship
347347

348348
==== Raspberry Pi 4
349349

350350
The GPU core, CPU, SDRAM and GPU each have their own PLLs and can have unrelated frequencies. The h264, v3d and ISP blocks share a PLL.
351351

352-
To view the Raspberry Pi's current frequency in KHz, type: `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`. Divide the result by 1000 to find the value in MHz. Note that this frequency is the kernel _requested_ frequency, and it is possible that any throttling (for example at high temperatures) may mean the CPU is actually running more slowly than reported. An instantaneous measurement of the actual ARM CPU frequency can be retrieved using the vcgencmd `vcgencmd measure_clock arm`. This is displayed in Hertz.
352+
To view the Raspberry Pi's current frequency in KHz, type: `cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`. Divide the result by 1000 to find the value in MHz. Note that this frequency is the kernel _requested_ frequency, and it is possible that any throttling (for example at high temperatures) may mean the CPU is actually running more slowly than reported. An instantaneous measurement of the actual Arm CPU frequency can be retrieved using the vcgencmd `vcgencmd measure_clock arm`. This is displayed in Hertz.
353353

354354
=== Monitoring core temperature
355355
[.whitepaper, title="Cooling a Raspberry Pi device", subtitle="", link=https://pip.raspberrypi.com/documents/RP-003608-WP-Cooling-a-Raspberry-Pi-device.pdf]
@@ -368,7 +368,7 @@ Divide the result by 1000 to find the value in degrees Celsius. Alternatively, y
368368

369369
Hitting the temperature limit is not harmful to the SoC, but it will cause the CPU to throttle. A heat sink can help to control the core temperature, and therefore performance. This is especially useful if the Raspberry Pi is running inside a case. Airflow over the heat sink will make cooling more efficient.
370370

371-
When the core temperature is between 80°C and 85°C, the ARM cores will be throttled back. If the temperature exceeds 85°C, the ARM cores and the GPU will be throttled back.
371+
When the core temperature is between 80°C and 85°C, the Arm cores will be throttled back. If the temperature exceeds 85°C, the Arm cores and the GPU will be throttled back.
372372

373373
For the Raspberry Pi 3 Model B+, the PCB technology has been changed to provide better heat dissipation and increased thermal mass. In addition, a soft temperature limit has been introduced, with the goal of maximising the time for which a device can "sprint" before reaching the hard limit at 85°C. When the soft limit is reached, the clock speed is reduced from 1.4GHz to 1.2GHz, and the operating voltage is reduced slightly. This reduces the rate of temperature increase: we trade a short period at 1.4GHz for a longer period at 1.2GHz. By default, the soft limit is 60°C. This can be changed via the `temp_soft_limit` setting in `config.txt`.
374374

@@ -378,7 +378,7 @@ It is essential to keep the supply voltage above 4.8V for reliable performance.
378378

379379
To monitor the Raspberry Pi's PSU voltage, you will need to use a multimeter to measure between the VCC and GND pins on the GPIO. More information is available in the xref:raspberry-pi.adoc#power-supply[power] section of the documentation.
380380

381-
If the voltage drops below 4.63V (±5%), the ARM cores and the GPU will be throttled back, and a message indicating the low voltage state will be added to the kernel log.
381+
If the voltage drops below 4.63V (±5%), the Arm cores and the GPU will be throttled back, and a message indicating the low voltage state will be added to the kernel log.
382382

383383
The Raspberry Pi 5 PMIC has built in ADCs that allow the supply voltage to be measured. To view the current supply voltage, run the following command:
384384

documentation/asciidoc/computers/configuration/configuring-networking.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ NOTE: Starting with Raspberry Pi OS _Bookworm_, Network Manager is the default n
1010

1111
Access Network Manager via the network icon at the right-hand end of the menu bar. If you are using a Raspberry Pi with built-in wireless connectivity, or if a wireless dongle is plugged in, click this icon to bring up a list of available wireless networks. If you see the message 'No APs found - scanning...', wait a few seconds, and Network Manager should find your network.
1212

13-
NOTE: Devices with dual-band wireless automatically disable networking until you assign a wireless LAN country. Flagship models since Raspberry Pi 3B+, Compute Modules since CM4, and Keyboard models support dual-band wireless. To set a wireless LAN country, open the Raspberry Pi Configuration application from the Preferences menu, select *Localisation* and select your country from the menu.
13+
NOTE: Devices with dual-band wireless automatically disable networking until you assign a wireless LAN country. Flagship models since Raspberry Pi 3B+, Compute Modules since CM4, and Keyboard models support dual-band wireless. To set a wireless LAN country, open the Control Centre application from the **Preferences** menu, select *Localisation* and select your country from the menu.
1414

1515
image::images/wifi2.png[wifi2]
1616

0 commit comments

Comments
 (0)