-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Disable CircuitPlayground Bluefruit speaker by default #2258
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
Comments
A little quick analysis: It looks like the related code in the samd port for the express version is:
(reset_all_pins) |
How are you observing the noise and why is it problematic? Is this on Ah, perhaps when you say noise this is just hearing audible noise from the 7.5mm speaker? |
Yup, just hear it out of the speaker when I touch the audio pad. It's not the end of the world but it is unexpected. |
I was interested in anything PAM8301 related because I somehow let the magic smoke out of mine with some rather innocent use, I added some notes to an existing thread: Adafruit Forums: Circuit Playground Express gets VERY hot. |
This allows the board to disable the onboard speaker until explicitly enabled in user code. Testing performed on a CPB: * Touching the AUDIO pin with a fingertip no longer generates noise/buzz * Generating a waveform with `simpleio.tone` produces no sound by default * When the board.SPEAKER_ENABLE is configured as a digital output and set True, `simpleio.tone` does produce sound Note that while guides should include information about SPEAKER_ENABLE, it's possible that some users who omitted it could view this as a breaking change. They can fix it by simply adding code similar to speaker_enable = digitalio.DigitalInOut(board.SPEAKER_ENABLE) speaker_enable.direction = digitalio.Direction.OUTPUT speaker_enable.value = True before using the internal speaker. Closes: adafruit#2258
We need to disable the speaker on the CircuitPlayground Bluefruit just like we do on the Express because it currently makes noise when the AUDIO pin is touched.
The text was updated successfully, but these errors were encountered: