Skip to content
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.

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

Fix core frequency in config.txt to repair UART console #32

Closed
wants to merge 1 commit into from
Closed

Fix core frequency in config.txt to repair UART console #32

wants to merge 1 commit into from

Conversation

vstehle
Copy link
Contributor

@vstehle vstehle commented Jun 7, 2021

I propose that we fix the core frequency to 250 MHz to repair the UART console.

Arguably, we might be losing a bit of performance here, but the UART console is so useful for debug and headless operation that I think this is well worth it. Don't hesitate to let me know if you disagree.

Best regards,
Vincent.

The UART console becomes garbled during boot, shortly after the baud rate
change and the trusted firmware boot.

On Raspberry Pi 3, the mini UART clock is linked to the VPU core clock, so
that when the core clock frequency changes, the UART baud rate will also
change (see [1]).

Fix the core frequency to 250 MHz to repair the UART console.

[1]: https://www.raspberrypi.org/documentation/configuration/uart.md

Signed-off-by: Vincent Stehlé <vincent.stehle@arm.com>
@bzfbd
Copy link

bzfbd commented Oct 3, 2021

This helps on FreeBSD to keep serial console on a 3B+. Thank you!

@pbatard
Copy link
Member

pbatard commented Jun 5, 2023

I don't think we want to enable that unconditionally because this will indeed result in loss of performance for people who don't care about the UART console and, ideally, it should be the OS job to provide a UART driver that handles VPU frequency changes.

What we can do then is add the following section in config.txt so that people who need this just have to uncomment the relevant line:

# Uncomment if you have trouble with the UART console during boot
#core_freq=250

@pbatard pbatard closed this in 8e602ad Jun 5, 2023
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.

None yet

3 participants