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

Fixed Bluetooth breaking on Raspbian Stretch and Buster #38

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Kostadin
Copy link

Adding dtoverlay=pi3-miniuart-bt to /boot/config.txt without anything else breaks all Bluetooth functionality on Raspberry Pi models with a Bluetooth chip. Setting core_freq=250 and core_freq_min=250 fixes the problem.

p3-miniuart-bt has been renamed to miniuart-bt but the previous name was kept as an alias for compatibility reasons.

More info on miniuart-bt:
https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L1571

Adding dtoverlay=pi3-miniuart-bt to /boot/config.txt without anything else breaks all Bluetooth functionality on Raspberry Pi models with a Bluetooth chip. Setting core_freq=250 and core_freq_min=250 fixes the problem.

p3-miniuart-bt has been renamed to miniuar-bt but the previous name was kept as an alias for compatibility reasons.

More info on miniuart-bt:
https://github.com/raspberrypi/firmware/blob/master/boot/overlays/README#L1571
@Gadgetoid
Copy link
Member

I can see what you're trying to achieve. But this, as far as I understand this may have other unintended side-effects to performance which may be an extremely bold choice for an easy-installer particularly for the Pi 4.

I'm going to wager that more users would expect their Pi to run full-speed than expect functional bluetooth in this case, but I could be wrong. I think this fix needs to be communicated, and maybe even offered as an option for install, but not without clearly documenting the tradeoff (which, I must admit, I'm not well-versed on since the documentation with respect to Pi 4 is limited.)

From what I can tell (source: https://www.raspberrypi.org/documentation/configuration/config-txt/overclocking.md):

  1. core_freq might default to 400 on the Pi 4, but I'm struggling to find confirmation of this?
  2. Changing core_freq on the Pi 4 does not affect the SDRAM frequency
  3. Does changing core_freq affect the L2 cache performance on Pi 4?

@Gadgetoid Gadgetoid added the notice This issue is resolved, but left open for posterity/visibility label Feb 25, 2020
@Gadgetoid
Copy link
Member

I'm leaving this unmerged and marked as notice so that others running into this issue can decide if they want to use this fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
notice This issue is resolved, but left open for posterity/visibility
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants