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

[Pi 4B] enable_uart / overclocking documentation unclear #1614

Closed
bcoppens opened this issue Jul 7, 2020 · 5 comments
Closed

[Pi 4B] enable_uart / overclocking documentation unclear #1614

bcoppens opened this issue Jul 7, 2020 · 5 comments

Comments

@bcoppens
Copy link

bcoppens commented Jul 7, 2020

Based on uart.md, one gets the impression that setting enable_uart=1 fixes the core clock to 250MHz. However, it appears that on the Pi 4B, enabling this option appears to fix the core clock to 500MHz.

Furthermore, overclocking.md explicitly mentions that changing/setting core_freq on the Pi 4 is not allowed. If enable_uart=1 is indeed supported on the Pi 4 (with a 500MHz clock), maybe enable_uart could also be mentioned in overclocking.md

@ghost
Copy link

ghost commented Jul 9, 2020

Based on uart.md, one gets the impression that setting enable_uart=1 fixes the core clock to 250MHz. However, it appears that on the Pi 4B, enabling this option appears to fix the core clock to 500MHz.

I've confirmed this on my Pi 4B. It looks like the documentation needs updated for Pi 4. No idea about the overclocking - I don't overclock.

@JamesH65
Copy link
Contributor

@pelwell @popcornmix What's the current situation with uart and this configuration item?

@pelwell
Copy link
Contributor

pelwell commented Nov 18, 2020

If the mini-UART is enabled in Device Tree then the core frequency is fixed at the maximum for the platform.

@aallan
Copy link
Contributor

aallan commented Jun 7, 2021

What's the status of this?

@aallan aallan added the waiting for comment Awaiting a response label Jun 7, 2021
@JamesH65
Copy link
Contributor

JamesH65 commented Jun 8, 2021

Inclined to close, then repair/fixup on the new site if its still a problem.

@aallan aallan removed the waiting for comment Awaiting a response label Jun 8, 2021
@aallan aallan closed this as completed Jun 8, 2021
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

No branches or pull requests

4 participants