ESP32 Bit Pirate

ESP32-S3 I2S audio debugging

Test I2S microphones and speakers with ESP32

ESP32 Bit Pirate turns a compatible ESP32-S3 board into an I2S audio debugging workbench. Use it to configure BCLK, LRCK and DATA pins, play test tones, record microphone samples and verify speaker or microphone wiring.

Start with an I2S test recipe Flash ESP32 Bit Pirate
I2S audio debugging visual with an ESP32 board, microphone or speaker module, BCLK, LRCK and DATA lines

Quick I2S workflow

Start by confirming the three signal lines and the audio direction. Use built-in tests before spending time on custom firmware or audio processing code.

  1. 01

    Wire BCLK, LRCK or WS, DATA, VCC and GND to the I2S microphone, amplifier or audio module.

  2. 02

    Start I2S mode and configure pins, sample rate and bit depth for the target module.

  3. 03

    For output, play a known test tone or run the speaker test before trying real audio data.

  4. 04

    For input, run the microphone test, then record and compare silence versus sound levels.

  5. 05

    Use a logic analyzer on BCLK, LRCK and DATA if the audio path stays silent or unstable.

mode i2s
config
play 440 1000
test speaker
test mic
record
reset

Example CLI flow. See the I2S wiki for exact syntax, pin prompts, sample settings and firmware-specific behavior.

I2S workflows covered by ESP32 Bit Pirate

Use this overview to choose the right I2S audio workflow before opening a detailed recipe.

Configure

I2S pin and sample setup

Set BCLK, LRCK, DATA, sample rate and bit depth so the ESP32-S3 and audio module agree before any test.

Play

I2S test tone output

Generate a known tone to confirm that the output clocking, data line and speaker or amplifier path are alive.

Test

I2S speaker checks

Run repeatable speaker patterns before debugging playback data, file handling or higher-level audio code.

Record

I2S microphone recording

Record microphone activity and compare silence versus sound to confirm that the input path is producing samples.

Measure

Signal visualization

Watch level changes, peak-to-peak movement or sample activity before interpreting audio quality.

Debug

Clock and data line checks

Separate swapped BCLK/LRCK, wrong DATA direction, bad power and sample setting mistakes before replacing hardware.

When an ESP32-S3 I2S workbench helps

I2S problems are often wiring, direction or configuration issues. A small external workflow can confirm the audio path before you add application code.

Audio bring-up

Before writing a sketch

Use tone and microphone tests to answer whether the module is wired and clocked correctly before writing custom firmware.

Direction check

Before blaming samples

Microphones drive DATA toward the ESP32, while speaker or amplifier paths receive DATA from the ESP32. Mixing directions creates silent tests.

Clock visibility

Before changing modules

Capture BCLK and LRCK with a logic analyzer when a module stays silent, then check whether the clocks match the expected sample setup.

I2S hardware reminders

These notes stay short. The detailed command references live in the project documentation and firmware repository.

BCLK

The bit clock must reach the I2S target. If BCLK is missing, most microphones, DACs and amplifiers will look completely silent.

LRCK / WS

The word select or left-right clock separates audio channels and sample frames. Swapping it with BCLK is a common first wiring error.

DATA direction

Check whether DATA is input from a microphone or output to a speaker amplifier. Direction mistakes are easy to miss on a three-wire audio bus.

Power and levels

Use a module voltage compatible with the selected hardware path, share ground and avoid driving ESP32 GPIO outside its safe logic range.

Common I2S problems

Most I2S failures come from swapped clocks, wrong data direction, unsupported module type, missing ground or sample settings that do not match the target.

No microphone activity

Check DATA direction, module power, shared ground, BCLK, LRCK and whether test mic detects any signal before interpreting record.

No speaker output

Run a known tone first, then check BCLK, LRCK, DATA output wiring, amplifier enable pins, gain and speaker power.

Swapped clocks

LRCK and BCLK are easy to confuse. Use the labels WS, LRCLK, LRCK and BCLK on the module silkscreen carefully.

Wrong microphone type

Analog microphones do not speak I2S. Use an actual I2S digital microphone module for this workflow.

Unstable or distorted audio

Check sample rate, bit depth, clock stability, wire length, module voltage and whether the target expects mono or stereo framing.

Detailed I2S recipes

These pages are the task-level I2S workflows. This overview keeps the protocol-level guidance here, while each recipe covers setup, commands and troubleshooting in detail.

Useful I2S references

This page is a protocol overview. Use the site index for the full web experience, or GitHub for source code, firmware documentation and the I2S command reference.

Flash ESP32 Bit Pirate

Flash a supported ESP32-S3 board before testing I2S audio mode from the browser.

Open Web Flasher

I2S command reference

Open the maintained firmware wiki for I2S commands, pin configuration, tests and usage notes.

Open I2S command reference

Logic Analyzer

Capture BCLK, LRCK and DATA timing when you need to inspect I2S clocks and data activity.

Open Logic Analyzer

ESP32 Bit Pirate GitHub

Check firmware source, issues and releases that affect I2S audio support.

Open GitHub repository

I2S debugging FAQ

Short answers for common questions before moving into a detailed workflow.

Can ESP32 Bit Pirate test an I2S microphone?

Yes. I2S mode can record from an I2S microphone, visualize signal activity and run a microphone test to check input presence.

Can ESP32 Bit Pirate play an I2S test tone?

Yes. I2S mode can play tones and speaker test patterns through a compatible I2S output path after BCLK, LRCK and DATA are configured.

What I2S lines should I check first?

Start with BCLK, LRCK or WS, DATA, shared ground and the correct data direction for microphone input or speaker output.