Skip to content

Additional mentions of the 500+ #4194

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 6 commits into from
Sep 26, 2025
Merged

Additional mentions of the 500+ #4194

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
28f8db9
Additional mentions of the 500+
katshann-raspberry Sep 25, 2025
7a21e92
Updates from review.
katshann-raspberry Sep 25, 2025
ce3b4e5
Clarify the power consumption
katshann-raspberry Sep 26, 2025
3298837
Make consistent how models are listed in a table.
katshann-raspberry Sep 26, 2025
dabcb87
Update table for build config.
katshann-raspberry Sep 26, 2025
6517e5f
Updates from comments
katshann-raspberry Sep 26, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion documentation/asciidoc/accessories/monitor/monitor_intro.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,7 +65,7 @@ To switch from Power Saving mode to Full Power mode, press and hold the *increas

[TIP]
====
If the Monitor flashes on and off, your USB power supply is not capable of providing sufficient current to power the monitor. This can happen if you power the Monitor from a Raspberry Pi 5 or Pi 500 which is itself powered by a 5V/3A power supply. Try the following fixes to stop the Monitor from flashing on and off:
If the Monitor flashes on and off, your USB power supply is not capable of providing sufficient current to power the monitor. This can happen if you power the Monitor from a Raspberry Pi 5, 500, or 500+ which is itself powered by a 5V/3A power supply. Try the following fixes to stop the Monitor from flashing on and off:

* reduce the display brightness and volume (you may have to connect your monitor to another power supply to access the settings)
* switch to a different power source or cable
Expand Down
8 changes: 4 additions & 4 deletions documentation/asciidoc/computers/config_txt/boot.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,13 +5,13 @@
These options specify the firmware files transferred to the VideoCore GPU prior to booting.

`start_file` specifies the VideoCore firmware file to use.
`fixup_file` specifies the file used to fix up memory locations used in the `start_file` to match the GPU memory split.
`fixup_file` specifies the file used to fix up memory locations used in the `start_file` to match the GPU memory split.

The `start_file` and the `fixup_file` are a matched pair - using unmatched files will stop the board from booting. This is an advanced option, so we advise that you use `start_x` and `start_debug` rather than this option.

NOTE: Cut-down firmware (`start*cd.elf` and `fixup*cd.dat`) cannot be selected this way - the system will fail to boot. The only way to enable the cut-down firmware is to specify `gpu_mem=16`. The cut-down firmware removes support for codecs, 3D and debug logging as well as limiting the initial early-boot framebuffer to 1080p @16bpp - although KMS can replace this with up to 32bpp 4K framebuffer(s) at a later stage as with any firmware.

NOTE: The Raspberry Pi 5, Compute Module 5, and Raspberry Pi 500 firmware is self-contained in the bootloader EEPROM.
NOTE: The Raspberry Pi 5, 500, 500+, and Compute Module 5 firmware is self-contained in the bootloader EEPROM.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should refer to Pi4 / Pi5 family because it applies to all devices including CM4.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this sentence, I think "firmware" is referring to start.elf / start4.elf, which is still a separate file for the Pi4 family?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, Pi4 family use start4.elf by default and Pi5 family is self-contained or perhaps more precise the BCM2712 bootrom family because that's the significant thing rather than the board design.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, it's always hard to get the balance right in technical documentation like this, but I'm happy to bow to @katshann-raspberry and @JeuneseRPi 's best judgement.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems like what this note wants to emphasise is the self-contained nature of the BCM2712 family firmware. I'm unclear as to why, though. What does the information in this note change about what the customer would choose or do after reading it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This appears at https://www.raspberrypi.com/documentation/computers/config_txt.html#start_file-fixup_file so perhaps the NOTE is trying to explain that the BCM2712 (i.e. Pi5 family) doesn't use the start_file and fixup_file options? And yes, perhaps that could/should be made clearer 🙂

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the info on this one, folks. I'll pick up improving this note as a separate action for next week.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As a nit-pick, there should be no "The" at the beginning of the sentence.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In this case I believe it's talking about "The firmware..." - so perhaps the sentence should be rearranged to:
"The firmware for Raspberry Pi 5, 500, 500+, and Compute Module 5 is self-contained in the bootloader EEPROM." ?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are correct. Forgive me. It's my first day back. I'll come up with a new excuse for mistakes I make tomorrow. ;-)


=== `cmdline`

Expand All @@ -21,7 +21,7 @@ NOTE: The Raspberry Pi 5, Compute Module 5, and Raspberry Pi 500 firmware is sel

`kernel` is the alternative filename on the boot partition for loading the kernel. The default value on the Raspberry Pi 1, Zero and Zero W, and Raspberry Pi Compute Module 1 is `kernel.img`. The default value on the Raspberry Pi 2, 3, 3+ and Zero 2 W, and Raspberry Pi Compute Modules 3 and 3+ is `kernel7.img`. The default value on the Raspberry Pi 4 and 400, and Raspberry Pi Compute Module 4 is `kernel8.img`, or `kernel7l.img` if `arm_64bit` is set to 0.

The Raspberry Pi 5, Compute Module 5, and Raspberry Pi 500 firmware defaults to loading `kernel_2712.img` because this image contains optimisations specific to those models (e.g. 16K page-size). If this file is not present, then the common 64-bit kernel (`kernel8.img`) will be loaded instead.
The Raspberry Pi 5, 500, 500+, and Compute Module 5 firmware defaults to loading `kernel_2712.img` because this image contains optimisations specific to those models (e.g. 16K page-size). If this file is not present, then the common 64-bit kernel (`kernel8.img`) will be loaded instead.

=== `arm_64bit`

Expand Down Expand Up @@ -56,7 +56,7 @@ Flagship models since Raspberry Pi 5, Compute Modules since CM5, and Keyboard mo

=== `ramfsfile`

`ramfsfile` is the optional filename on the boot partition of a `ramfs` to load.
`ramfsfile` is the optional filename on the boot partition of a `ramfs` to load.

NOTE: Newer firmware supports the loading of multiple `ramfs` files. You should separate the multiple file names with commas, taking care not to exceed the 80-character line length limit. All the loaded files are concatenated in memory and treated as a single `ramfs` blob. More information is available https://forums.raspberrypi.com/viewtopic.php?f=63&t=10532[on the forums].

Expand Down
2 changes: 1 addition & 1 deletion documentation/asciidoc/computers/config_txt/common.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ To disable, set `arm_boost=0`.

==== `power_force_3v3_pwm`

NOTE: This option applies only to Raspberry Pi 5, Compute Module 5, and Pi 500.
NOTE: This option applies only to Raspberry Pi 5, 500, 500+, and Compute Module 5.

Forces PWM on 3.3V output from the GPIO header or CSI connector.

Expand Down
6 changes: 3 additions & 3 deletions documentation/asciidoc/computers/config_txt/conditional.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,13 +32,13 @@ The conditional model filters apply according to the following table.
| Model 4B, Pi 400, Compute Module 4, Compute Module 4S

| `[pi5]`
| Raspberry Pi 5, Compute Module 5, Pi 500
| Raspberry Pi 5, Compute Module 5, Pi 500, Pi 500+

| `[pi400]`
| Pi 400 (also sees `[pi4]` contents)

| `[pi500]`
| Pi 500 (also sees `[pi5]` contents)
| Pi 500/500+ (also sees `[pi5]` contents)

| `[cm1]`
| Compute Module 1 (also sees `[pi1]` contents)
Expand Down Expand Up @@ -365,5 +365,5 @@ Filters of different types can be combined by listing them one after the other,
# settings here apply to all hardware

----

Use the `[all]` filter to reset all previous filters and avoid unintentionally combining different filter types.
4 changes: 2 additions & 2 deletions documentation/asciidoc/computers/configuration/boot_folder.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,12 +85,12 @@ Various xref:linux_kernel.adoc#kernel[kernel] image files that correspond to Ras

| `kernel8.img`
| BCM2837, BCM2711, BCM2712
| Pi Zero 2 W, Pi 2 (later revisions), Pi 3, CM3, Pi 3+, CM3+, Pi 4, CM4, CM4S, Pi 400, CM5, Pi 5, Pi 500
| Pi Zero 2 W, Pi 2 (later revisions), Pi 3, CM3, Pi 3+, CM3+, Pi 4, CM4, CM4S, Pi 400, CM5, Pi 5, Pi 500, Pi 500+
| xref:config_txt.adoc#boot-options[64-bit kernel]. Earlier revisions of Raspberry Pi 2 (with BCM2836) do not support 64-bit kernels.

| `kernel_2712.img`
| BCM2712
| Pi 5, CM5, Pi 500
| Pi 5, CM5, Pi 500, Pi 500+
| Pi 5-optimized xref:config_txt.adoc#boot-options[64-bit kernel].
|===

Expand Down
10 changes: 5 additions & 5 deletions documentation/asciidoc/computers/configuration/device-tree.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ User-provided parameters in `config.txt` are scanned, along with any overlays an
[[part1]]
=== Device Trees

A Device Tree (DT) is a description of the hardware in a system. It should include the name of the base CPU, its memory configuration, and any peripherals (internal and external). A DT should not be used to describe the software, although by listing the hardware modules it does usually cause driver modules to be loaded.
A Device Tree (DT) is a description of the hardware in a system. It should include the name of the base CPU, its memory configuration, and any peripherals (internal and external). A DT should not be used to describe the software, although by listing the hardware modules it does usually cause driver modules to be loaded.

NOTE: It helps to remember that DTs are supposed to be OS-neutral, so anything which is Linux-specific shouldn't be there.

Expand Down Expand Up @@ -57,13 +57,13 @@ The following is a simple tree in the `.dts` format:
This tree contains:

* a required header: `/dts-v1/`
* The inclusion of another DTS file, conventionally named `*.dtsi` and analogous to a `.h` header file in C
* The inclusion of another DTS file, conventionally named `*.dtsi` and analogous to a `.h` header file in C
* a single root node: `/`
* a couple of child nodes: `node1` and `node2`
* some children for node1: `child-node1` and `child-node2`
* a label (`cousin`) and a reference to that label (`&cousin`)
* several properties scattered through the tree
* a repeated node (`/node2`)
* a repeated node (`/node2`)

Properties are simple key-value pairs where the value can either be empty or contain an arbitrary byte stream. While data types are not encoded in the data structure, there are a few fundamental data representations that can be expressed in a Device Tree source file.

Expand Down Expand Up @@ -528,7 +528,7 @@ Each node has the name of an overlay that requires special handling. The propert

* `bcm2835` for all Raspberry Pis built around the BCM2835, BCM2836, BCM2837, and RP3A0 SoCs
* `bcm2711` for Raspberry Pi 4B, CM4, CM4S, and Pi 400
* `bcm2712` for Raspberry Pi 5, CM5, and Pi 500
* `bcm2712` for Raspberry Pi 5, CM5, Pi 500, and Pi 500+

A platform name with no value (an empty property) indicates that the current overlay is compatible with the platform; for example, `uart5` is compatible with the `bcm2711` platform. A non-empty value for a platform is the name of an alternative overlay to use in place of the requested one; asking for `disable-bt` on BCM2712 results in `disable-bt-pi5` being loaded instead. Any platform not included in an overlay's node is not compatible with that overlay. Any overlay not mentioned in the map is assumed to be compatible with all platforms.

Expand Down Expand Up @@ -833,7 +833,7 @@ For a list of supported overlays and parameters, see the https://github.com/rasp
[[part4]]
=== Firmware parameters

The firmware uses the special https://www.kernel.org/doc/html/latest/devicetree/usage-model.html#runtime-configuration[/chosen] node to pass parameters between the bootloader and/or firmware and the operating system.
The firmware uses the special https://www.kernel.org/doc/html/latest/devicetree/usage-model.html#runtime-configuration[/chosen] node to pass parameters between the bootloader and/or firmware and the operating system.

* Each property is stored as a 32-bit unsigned integer unless indicated otherwise.
* Numbers in device-tree are stored in binary and are big-endian.
Expand Down
6 changes: 5 additions & 1 deletion documentation/asciidoc/computers/getting-started/setting-up.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,10 @@ You can use any high-quality power supply that provides the correct power mode.
|Recommended power supply (voltage/current)
|Raspberry Pi power supply

|Raspberry Pi 500+
|5V/5A
|https://www.raspberrypi.com/products/27w-power-supply/[27W USB-C power supply]

|Raspberry Pi 5 and Raspberry Pi 500
|5V/5A, 5V/3A limits peripherals to 600mA
|https://www.raspberrypi.com/products/27w-power-supply/[27W USB-C power supply]
Expand Down Expand Up @@ -101,7 +105,7 @@ Raspberry Pi models have the following display connectivity:
|Model
|Display outputs

|Raspberry Pi 5, Raspberry Pi 400 and Raspberry Pi 500
|Raspberry Pi 5, Raspberry Pi 400, Raspberry Pi 500, and Raspberry Pi 500+
|2× micro HDMI

|Raspberry Pi 4 Model B
Expand Down
2 changes: 1 addition & 1 deletion documentation/asciidoc/computers/linux_kernel/building.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ $ cd linux
$ KERNEL=kernel_2712
$ make bcm2712_defconfig
----
| Pi 500
| Pi 500/500+
| Compute Module 5

.14+^.^| 32-bit
Expand Down
4 changes: 2 additions & 2 deletions documentation/asciidoc/computers/processors/bcm2712.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
== BCM2712

Broadcom BCM2712 is the 16nm application processor used in Raspberry Pi 5, Compute Module 5, and Pi 500. It is the successor to the BCM2711 device used in Raspberry Pi 4, and shares many common architectural features with other devices in the BCM27xx family, used on earlier Raspberry Pi products.
Broadcom BCM2712 is the 16nm application processor used in Raspberry Pi 5, 500, 500+, and Compute Module 5. It is the successor to the BCM2711 device used in Raspberry Pi 4, and shares many common architectural features with other devices in the BCM27xx family, used on earlier Raspberry Pi products.

Built around a quad-core Arm Cortex-A76 CPU cluster, clocked at up to 2.4GHz, with 512KB per-core L2 caches and a 2MB shared L3 cache, it integrates an improved 12-core VideoCore VII GPU; a hardware video scaler and HDMI controller capable of driving dual 4Kp60 displays; and a Raspberry Pi-developed HEVC decoder and Image Signal Processor. A 32-bit LPDDR4X memory interface provides up to 17GB/s of memory bandwidth, while ×1 and ×4 PCI Express interfaces support high-bandwidth external peripherals; on Raspberry Pi 5 the latter is used to connect to the Raspberry Pi RP1 south bridge, which provides the bulk of the external-facing I/O functionality on the platform.

Headline features include:
Headline features include:

* Quad-core Arm Cortex-A76 @ 2.4GHz
** ARMv8-A ISA
Expand Down
6 changes: 3 additions & 3 deletions documentation/asciidoc/computers/raspberry-pi/eeprom-bootloader.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -190,7 +190,7 @@ Default: `0`
[[SD_OVERCURRENT_CHECK]]
==== `SD_OVERCURRENT_CHECK`

Raspberry Pi 4, Raspberry Pi 5 and Raspberry Pi 500 only.
Raspberry Pi 4, Raspberry Pi 5, Raspberry Pi 500, and Raspberry Pi 500+ only.

Before booting, the bootloader checks the SD power switch overcurrent signal. The overcurrent signal occurs if the SD card is damaged and has a short circuit which will cause it to get hot.

Expand Down Expand Up @@ -334,7 +334,7 @@ MAC_ADDRESS_OTP=0,1
The first value (row 0 in the example) contains the OUI and the most significant 8 bits of the MAC address. The second value (row 1 in the example) stores the remaining 16-bits of the MAC address.
This is the same format as used for the Raspberry Pi MAC address programmed at manufacture.

Any two customer rows may be selected and combined in either order.
Any two customer rows may be selected and combined in either order.

The `Customer OTP` rows are OTP registers 36 to 43 in the `vcgencmd otp_dump` output so if the first two rows are programmed as follows then `MAC_ADDRESS_OTP=0,1` would give a MAC address of `e4:5f:01:20:24:7e`.

Expand Down Expand Up @@ -564,7 +564,7 @@ Default: 0
==== `PARTITION_WALK`
This property is designed to improve the reliability of `A/B` boot schemes using `autoboot.txt` by searching for bootable partitions if the specified partition does not appear to be bootable. If `PARTITION_WALK=1` and the requested partition is not bootable and does not have a valid `autoboot.txt` then the bootloader will check each partition in turn (up to 8 and wrapping to 0) to see if it is bootable (contains `start4.elf` on a Pi4, or `config.txt` and a suitable device-tree on Pi 5 or newer).

During the "partition walk" `autoboot.txt` files are not processed to avoid cycling dependencies. It is assumed that the requested boot partition has failed and the system is attempting recovery.
During the "partition walk" `autoboot.txt` files are not processed to avoid cycling dependencies. It is assumed that the requested boot partition has failed and the system is attempting recovery.

Default: `0`

Expand Down
19 changes: 12 additions & 7 deletions documentation/asciidoc/computers/raspberry-pi/power-supplies.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,11 @@ All Raspberry Pi models with a PoE-capable Ethernet jack require a HAT to draw p
| 1.6A (600mA if using a 3A power supply)
| 800mA

| Pi 500+
| 5.0A
| 1.6A
| 800mA

| Zero
| 1.2A
| Limited by PSU, board, and connector ratings only
Expand Down Expand Up @@ -122,15 +127,15 @@ $ vcgencmd get_config usb_max_current_enable
The following table describes the amount of power (in amps) drawn by different Raspberry Pi models during various workloads:

|===
| | | Raspberry Pi 1B+ | Raspberry Pi 2B | Raspberry Pi 3B | Raspberry Pi Zero | Raspberry Pi 4B
| | | Raspberry Pi 1B+ | Raspberry Pi 2B | Raspberry Pi 3B | Raspberry Pi Zero | Raspberry Pi 4B
| Boot | Max | 0.26 | 0.40 | 0.75 | 0.20 | 0.85
| | Avg | 0.22 | 0.22 | 0.35 | 0.15 | 0.7
| | Avg | 0.22 | 0.22 | 0.35 | 0.15 | 0.7
| Idle | Avg | 0.20 | 0.22 | 0.30 | 0.10 | 0.6
| Video playback (H.264) | Max | 0.30 | 0.36 |0.55 |0.23 | 0.85
| | Avg | 0.22 | 0.28 | 0.33 | 0.16 | 0.78
| Stress | Max | 0.35 | 0.82 | 1.34 | 0.35 | 1.25
| | Avg | 0.32 | 0.75 | 0.85 | 0.23 | 1.2
| Halt current | | | | 0.10 | 0.055 | 0.023
| Video playback (H.264) | Max | 0.30 | 0.36 |0.55 |0.23 | 0.85
| | Avg | 0.22 | 0.28 | 0.33 | 0.16 | 0.78
| Stress | Max | 0.35 | 0.82 | 1.34 | 0.35 | 1.25
| | Avg | 0.32 | 0.75 | 0.85 | 0.23 | 1.2
| Halt current | | | | 0.10 | 0.055 | 0.023
|===

NOTE: These measurements used a standard Raspberry Pi OS image (current as of 26 Feb 2016, or June 2019 for the Raspberry Pi 4), at room temperature, with the Raspberry Pi connected to a HDMI monitor, USB keyboard, and USB mouse. The Raspberry Pi 3 Model B was connected to a wireless LAN access point, the Raspberry Pi 4 was connected to Ethernet. All these power measurements are approximate and do not take into account power consumption from additional USB devices; power consumption can easily exceed these measurements if multiple additional USB devices or a HAT are connected to the Raspberry Pi.
Expand Down