Skip to content

Conversation

katshann-raspberry
Copy link
Contributor

No description provided.

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. ;-)

@katshann-raspberry katshann-raspberry merged commit bf8ea41 into develop Sep 26, 2025
1 check passed
@katshann-raspberry katshann-raspberry deleted the 500-tidyup branch September 26, 2025 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants