Skip to content

Default I2S output to different GPIO pins? #3

@colonelwatch

Description

@colonelwatch

When I was building usb_sound_card from the pico-playground repo, I had to define a different set of GPIO pins in the CMakeLists.txt file because GP25 was not exposed on the Raspberry Pi Pico.

#ifndef PICO_AUDIO_I2S_DATA_PIN
//#warning PICO_AUDIO_I2S_DATA_PIN should be defined when using AUDIO_I2S
#define PICO_AUDIO_I2S_DATA_PIN 27
#endif
#ifndef PICO_AUDIO_I2S_CLOCK_PIN_BASE
//#warning PICO_AUDIO_I2S_CLOCK_PIN_BASE should be defined when using AUDIO_I2S
#define PICO_AUDIO_I2S_CLOCK_PIN_BASE 25
#endif

So, a default PICO_AUDIO_I2S_CLOCK_PIN_BASE of 25 doesn't sound great. Shouldn't this be a different pin? In my case, I set PICO_AUDIO_I2S_CLOCK_PIN_BASE to 26 and PICO_AUDIO_I2S_DATA_PIN to 28. This leaves the WS signal, which then is 27 because that is PICO_AUDIO_I2S_CLOCK_PIN_BASE+1. All of these pins are exposed on the Pico.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions