Skip to the content
4 layers50 × 20 mmPicoarc, the printed circuit board in 3D

Use your HDMI ARC capable soundbar with your computer

Size
50 × 20 mm
Copper layers
4
Thickness
1.2 mm
Parts
72
Nets
77
Pads
250
Tracks, vias
457, 116
Pours
7
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
20 May 2026
Updated
21 Oct 2026

Overview

Picoarc is an open-source printed circuit board by naorunaoru, from the naorunaoru/picoarc repository on GitHub. It is a 4-layer board of 50 × 20 mm with 72 parts on 77 nets, routed with 457 tracks and 116 vias.

It is built around the RP2040, W25Q16JVSSIQ and AP2112K-3.3TRG1, with the PCA9306DCUR, USBLC6-2SC6 and CL05B104KB54PNC among its other parts. Its parts include 23 resistors, 15 capacitors, 5 ICs, 3 diodes and 2 connectors. It belongs with the interfaces and adapters boards and the RP2040 boards of this library.

Main components

12

README

README.md
01-clean-isometric

PicoARC

PicoARC is a device that appears to the host as a USB audio interface and passes through incoming audio as an S/PDIF-style stream to an ARC-compatible device. In simpler terms, this allows you to output audio from your computer to a soundbar or an ARC-capable receiver. It builds as USB Audio Class 1 by default for broad host compatibility; USB Audio Class 2 remains available as an opt-in target.

It also allows you to control the soundbar's volume. Somewhat. Because apparently supporting absolute volume control over CEC is not something that vendors are eager to implement.

Host volume and mute changes propagate to the soundbar in both USB modes. The latest soundbar state is returned by subsequent USB control queries. UAC2 also sends AudioControl change notifications; UAC1 has no notification endpoint, so host volume controls generally remain stale after an on-device adjustment. Host interfaces may ignore the UAC2 notifications as well.

Did I tell you it does HDMI-CEC too? Yes, it does, because it's required for ARC negotiation.

Why?

There's no off-the-shelf way of doing this exact thing, surprisingly. The closest thing is using S/PDIF, which has limited bandwidth, sometimes incurs additional latency and definitely does not allow you to control the soundbar from the host.

How does it work?

On the USB side, it acts as an audio interface, grabs the audio stream and passes it through.

On the HDMI side, it pretends to be a TV: responds to DDC queries with a plausible EDID, negotiates ARC with the connected audio system over CEC and drives the ARC line within the constraints defined by the HDMI 1.4 spec.

Supported audio formats

  • PCM at 32/44.1/48/88.2/96 kHz (higher sample rates are out of the question because RP2040 only has USB Full Speed)
  • 16/20/24-bit

The optional UAC2 target additionally exposes separate IEC 61937 Dolby Digital (AC-3) and DTS passthrough alternates. They are omitted from the default UAC1 target because host-driver support for Type III transport is inconsistent.

Hardware

The PCB design lives under hardware/. The schematic source is written in Zener, so hardware/picoarc.zen is the schematic/netlist source of truth rather than a .kicad_sch; the KiCad layout and JLCPCB production files are checked in alongside it.

See hardware/README.md for the hardware file map, Zener/KiCad workflow, and the old hand-wired Pico prototype wiring.

License

PicoARC uses a split license. Hardware design materials are licensed under CERN-OHL-W-2.0, and firmware plus general project documentation are licensed under MIT. See LICENSE for the exact scope and full license text locations.

Build requirements

  • Git
  • CMake and Ninja
  • Arm GNU toolchain
  • picotool

The Pico SDK and TinyUSB sources are pinned as git submodules under firmware/third_party; builds do not use SDK copies installed on the host. PicoARC uses Pico SDK 2.2.0 and upstream TinyUSB 0.21.0.

Build

From this directory:

sh
git submodule update --init --recursive
make build

This configures and builds both firmware variants:

text
firmware/build-release/picoarc-release.uf2
firmware/build-debug/picoarc-debug.uf2

Those are UAC1 builds. To build the opt-in UAC2 target instead:

sh
make build-uac2

Its artifacts use separate build directories and names so CMake and host USB caches cannot mix the two personalities:

text
firmware/build-release-uac2/picoarc-release-uac2.uf2
firmware/build-debug-uac2/picoarc-debug-uac2.uf2

UAC1 is the recommended full-speed target and is the mode tested for Windows compatibility. Treat UAC2 as experimental on full-speed hosts; it is retained for IEC 61937 and uses an adaptive OUT endpoint without explicit feedback. The firmware follows the host's delivery rate by servoing the S/PDIF PIO clock from the receive-buffer level.

The equivalent helper option is --usb-audio-class uac2 (or --uac uac2), for example ./picoarc build release --uac uac2. Direct CMake builds can set -DPICOARC_USB_AUDIO_CLASS=uac2; omitting the option selects UAC1.

By default PicoARC keeps sending silence for five minutes after the host closes its audio stream, then stops the ARC/S/PDIF carrier so the soundbar can go to standby. This can prevent short notification sounds from being swallowed while the soundbar wakes during gaps between playback. To change the timeout, edit firmware/src/picoarc_config.h before building:

c
#define PICOARC_IDLE_AUDIO_TIMEOUT_SECONDS 300

Use 0 to stop immediately, positive seconds for a timeout, or -1 to keep sending silence forever. Reopening the stream cancels the countdown; the next close starts a fresh countdown. Silent audio within an open stream and temporary buffer refills do not start it. With a finite timeout, the carrier stays off at boot until a stream opens; -1 sends silence from boot.

The release variant is audio-only with logging compiled out. It waits for an HDMI ARC device, completes ARC/SAD capability discovery, asks the soundbar for its OSD name, and then enumerates as USB audio using that name when the soundbar provides one. USB sample rates are limited to the connected soundbar's reported capabilities. UAC1 lists rates separately for each PCM bit depth; UAC2 reports the available rates on its shared clock and validates the selected format when starting a stream. Unsupported bit depths and codecs are omitted. UAC2 rejects unsupported rate requests; UAC1 rounds them to a supported rate and reports the selected value through GET_CUR. When SAD discovery is unavailable, the existing fallback remains 16-bit PCM at 48 kHz.

Capabilities are frozen for each USB connection and refreshed by re-enumerating when they change. The initial rate is 48 kHz if supported, otherwise the nearest supported rate. The debug variant initially exposes its serial log and reset interface with no streaming alternates, then briefly reconnects USB when audio capabilities become available or change.

Host sanitizer tests

The host tests require CMake, Ninja, and a native Clang or GCC installation with AddressSanitizer and UndefinedBehaviorSanitizer runtimes. They do not need the Pico SDK or Arm compiler, but the TinyUSB submodule must be initialized. Run them with the default C compiler or select one before the first configure:

sh
make test-sanitizers
CC=clang make test-sanitizers

The compiler selection is cached in firmware/build-host-sanitizers; remove that generated directory before switching compilers. The tests compile the same USB audio sample decoder used by the firmware and cover the supported 16-, 20-, and 24-bit subslots, including IEC 61937 words, unaligned byte input, buffer bounds, and the maximum audio-task batch. They also compile the real USB descriptors and control callbacks for both audio classes and debug layouts, checking sample-rate negotiation, sink changes, fallback capabilities, and unsupported format/rate requests.

Run the idle timeout checks for both USB audio classes with a simulated clock:

sh
python3 firmware/tests/test_idle_audio.py

The RP2040 firmware remains on its normal embedded build path and is not instrumented. Host tests cannot validate DMA and PIO timing, multicore races, interrupt behavior, or flash-blackout behavior on the device.

Flash

Connect the Pico over USB, then run:

sh
make flash

The helper script builds the release firmware first, then uses picotool to load and run the UF2. If the Pico is not detected, hold BOOTSEL while plugging it in and run the command again.

To flash the optional UAC2 release build, use make flash-uac2.

Monitor

To open the USB serial log:

sh
make monitor

To build, flash, and then open the monitor in one step:

sh
make run

This flashes the debug variant, because the release variant does not expose a USB serial log.

make run-uac2 does the same with the optional UAC2 debug build.

Press Ctrl-] to close the monitor.

Inspect silent audio

For a connected adapter that stops producing sound while volume controls still work, an optional release build exposes read-only USB audio diagnostics while keeping the same audio interfaces and descriptors:

sh
cmake -S firmware -B firmware/build-diagnostics-uac2 -G Ninja \
  -DPICOARC_VARIANT=release -DPICOARC_USB_AUDIO_CLASS=uac2 \
  -DPICOARC_USB_DIAGNOSTICS=ON
cmake --build firmware/build-diagnostics-uac2

Flash firmware/build-diagnostics-uac2/picoarc-release-uac2-diagnostics.uf2 using BOOTSEL, then capture during playback or a failure before reconnecting USB:

sh
python3 tools/audio_probe.py --seconds 30 > audio-diagnostics.jsonl

The probe requires libusb and reports audio counters, ARC gating, DMA progress, output hardware state, and reset cause without clearing counters or claiming interfaces. During a bounded capture it waits for the adapter to return after a KVM switch; an uptime reset means the board rebooted, while watchdog_timeout and watchdog_forced distinguish watchdog resets from hardware resets. Reset-cause flags require diagnostic protocol version 2; output registers, nonzero encoded-frame counts, and encoder/buffer hashes require version 3, and unavailable fields are omitted for older firmware. Growing USB/frame counters with a stopped DMA block counter indicate a stuck output core; a closed format gate points to ARC/capability state, while growing DMA blocks with admitted nonzero audio require checking the carrier and receiver. Diagnostics are disabled by default and provide evidence for debugging rather than changing recovery behavior.

Protocol 3 diagnostics also provide an explicit software BOOTSEL command; ordinary captures remain read-only, and rebooting requires the board's USB serial number:

sh
python3 tools/audio_probe.py --bootsel --serial YOUR_BOARD_SERIAL

Protocol 4 can also copy the encoded 192-frame buffer currently being consumed by DMA, without pausing playback:

sh
python3 tools/audio_probe.py --spdif-block --serial YOUR_BOARD_SERIAL

The snapshot includes the encoded words, current PIO instruction and pin-pad configuration. The host decoder checks preambles, BMC transitions, parity and sample validity, and reports PCM peak/RMS levels and channel-status bytes. Copies that cross a DMA buffer handoff are marked unstable and must be retried. This checks the data supplied to PIO; it does not measure the HDMI waveform or confirm that the soundbar has locked onto it. Ordinary captures omit this larger snapshot.

Protocol 5 adds two explicit recovery commands, both requiring the matching USB serial number:

sh
python3 tools/audio_probe.py --recover output --serial YOUR_BOARD_SERIAL
python3 tools/audio_probe.py --recover usb --serial YOUR_BOARD_SERIAL

Capture the failed stream first, then try one recovery at a time. output asks core 1 to restart its S/PDIF state machine and DMA without restarting USB or ARC negotiation. usb reconnects the USB audio device without rebooting the adapter or reinitializing the S/PDIF state machine. Both briefly interrupt playback. Read-only captures report output request/completion counters and USB reconnect requests; an accepted command is not proof that sound has returned. These commands are diagnostic experiments, not automatic recovery policies.

Protocol 6 adds read-only HPD/DDC controller state and cached soundbar volume and mute reports, plus an explicit HDMI recovery command:

sh
python3 tools/audio_probe.py --recover hdmi --serial YOUR_BOARD_SERIAL

This reconnects USB, resets the EDID responder and ARC session, and pulses HPD while retaining processor uptime and the S/PDIF transmitter configuration. It briefly interrupts playback and reports the request in subsequent captures. Test it during a captured silent failure to determine whether that boundary restores sound; an accepted request alone does not establish recovery.

Protocol 8 retains the last 128 observed USB/ARC state changes, streaming-alt requests, parsed CEC frames and CEC transmit results in memory, with timestamps and sequence numbers. Capture this history before a reset; reads preserve it, while a processor restart clears it:

sh
python3 tools/audio_probe.py --trace --spdif-block --serial YOUR_BOARD_SERIAL

The following manual tests separate parts of the combined HDMI recovery:

CommandDirect action
--recover ddcReset only the EDID I2C controller, FIFOs and byte parser
--recover cec-rxReset only the CEC receiver and parser
--recover cecResend the existing system-audio and ARC-initiation requests
--recover hpdPulse HPD low for 200 ms, retaining cached ARC and EDID state

Each command requires --serial; none explicitly reconnects USB or restarts the audio transmitter, although soundbar replies can trigger normal ARC/USB state changes. Try one command at a time during a captured silent failure and check audibility and the trace before proceeding; these diagnostics introduce no automatic recovery or idle refresh.

Parts

72
QtyValueFootprintReferences
14?naorunaoru_picoarc_footprints_picoarc:TestPad_1.0x1.0mm_RoundRectTP1, TP2, TP3, TP4, TP5, TP6, TP7, TP8, TP9, TP10, TP11, TP12, TP13, TP14
7CL05B104KB54PNCkicad_libraries_kicad-footprints_Capacitor_SMD@9.0.3:C_0402_1005MetricC5, C8, C9, C10, C11, C12, C13
6?kicad_libraries_kicad-footprints_TestPoint@9.0.3:TestPoint_Pad_D1.0mmTP16, TP17, TP18, TP19, TP20, TP21
40402WGF1001TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR4, R5, R16, R23
40402WGF2201TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR8, R9, R10, R11
30402WGF1003TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR6, R7, R13
20402CG330J500NTkicad_libraries_kicad-footprints_Capacitor_SMD@9.0.3:C_0402_1005MetricC14, C15
20402WGF1002TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR19, R20
20402WGF330JTCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR21, R22
20402WGF5101TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR17, R18
2CL05A105KA5NQNCkicad_libraries_kicad-footprints_Capacitor_SMD@9.0.3:C_0402_1005MetricC6, C7
2CL10A106MA8NRNCkicad_libraries_kicad-footprints_Capacitor_SMD@9.0.3:C_0603_1608MetricC3, C4
10402CG101J500NTkicad_libraries_kicad-footprints_Capacitor_SMD@9.0.3:C_0402_1005MetricC2
10402WGF1000TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR14
10402WGF1200TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR15
10402WGF2003TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR12
10402WGF2200TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR2
10402WGF2202TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR1
10402WGF3300TCEkicad_libraries_kicad-footprints_Resistor_SMD@9.0.3:R_0402_1005MetricR3
12N7002kicad_libraries_kicad-footprints_Package_TO_SOT_SMD@9.0.3:SOT-23Q1
1?naorunaoru_picoarc_footprints_picoarc:SWD_EdgePads_1x03_P1.50mmTP15
1AP2112K-3.3TRG1kicad_libraries_kicad-footprints_Package_TO_SOT_SMD@9.0.3:SOT-23-5U2
1CL05B103KB5NNNCkicad_libraries_kicad-footprints_Capacitor_SMD@9.0.3:C_0402_1005MetricC1
1D5V0M5B6LP16-7naorunaoru_picoarc_footprints_picoarc:DFN1616-6_L1.6-W1.6-P0.50-BL-EPD2
1GT-USB-7014Gnaorunaoru_picoarc_footprints_picoarc:USB-C-SMD_GT-USB-7014DJ2
1H7VH10Unaorunaoru_picoarc_footprints_picoarc:SOD-882_L1.0-W0.6-BID3
1HC-HDMI0019T-3naorunaoru_picoarc_footprints_picoarc:HDMI-SMD_HC-HDMI0019T-3_PicoARC_R6J1
1KT-0603Rkicad_libraries_kicad-footprints_LED_SMD@9.0.3:LED_0603_1608MetricD1
1PCA9306DCURkicad_libraries_kicad-footprints_Package_SO@9.0.3:VSSOP-8_2.3x2mm_P0.5mmU1
1RP2040kicad_libraries_kicad-footprints_Package_DFN_QFN@9.0.3:QFN-56-1EP_7x7mm_P0.4mm_EP3.2x3.2mmU5
1TS-1088-AR02016naorunaoru_picoarc_footprints_picoarc:SW-SMD_L3.9-W3.0-P4.45SW1
1USBLC6-2SC6kicad_libraries_kicad-footprints_Package_TO_SOT_SMD@9.0.3:SOT-23-6U3
1W25Q16JVSSIQkicad_libraries_kicad-footprints_Package_SO@9.0.3:SOIC-8_5.3x5.3mm_P1.27mmU4
1X322512MSB4SIkicad_libraries_kicad-footprints_Crystal@9.0.3:Crystal_SMD_3225-4Pin_3.2x2.5mmY1

Similar boards

  • 4 layers40.6 × 40.6 mmRtk gps module, the printed circuit board in 3D

    Rtk gps module

    Lucas-Poulos/rtk-gps-module

    Cheap dual-band L1+L5 RTK GNSS module. LC29H rover, discrete 50 ohm front end, USB-C + castellated. Schematic generated from Python and verified by a 146-check gate.

    67 partsCERN-OHL-P-2.0
  • 2 layers50 × 40 mmTimer board, the printed circuit board in 3D

    Timer board

    Dominik-Workshop/lap-timer

    Lap timer, EKA 2 sem PWR

    70 partsGPL-3.0
  • 4 layers110 × 80 mmSpin rig controller, the printed circuit board in 3D

    Spin rig controller

    Tinkerbug-Robotics/TinkerRocket

    Model rocket flight computer, ground station, iOS app, and simulation

    170 parts1GPL-3.0
  • 4 layers80 × 105.5 mmNetdaq, the printed circuit board in 3D

    Netdaq

    Gherkin/netdaq

    913 partsCERN-OHL-P-2.0
  • 6 layers133 × 102 mmIasis, the printed circuit board in 3D

    Iasis

    hydazz/iasis

    An optional Raspberry Pi Compute Module 5 carrier for Iasis. It plugs into the main board's HubPD population and carries Ethernet, NVMe storage, an accessory USB-C port and a service USB-C port.

    723 partsApache-2.0
  • 2 layers97.8 × 17.8 mmRtl8762ckf dev board, the printed circuit board in 3D

    Rtl8762ckf dev board

    simplexion/rtl8762c-dev-board

    RTL8762C Development Board

    140 parts2CERN-OHL-P-2.0
  • 2 layers78.4 × 90.4 mmIphoneFM panel, the printed circuit board in 3D

    IphoneFM panel

    louisflakes/IphoneFM

    KiCad project for IphoneFM Rev A. Built step by step from ../../design/rev-a/kicad-build-procedure.md; checked with ../../tools/kicadcheck.py.

    134 parts
  • 2 layers96 × 99.9 mmHorizons Badges, the printed circuit board in 3D

    Horizons Badges

    Taran-the-Idiot/Horizons-Badges

    E-ink badges for Horizons Crux! Made in Kicad. They use 2.66" E-ink screens with an RP2040 mcu. And they are made in the shape of a mantaray :D

    58 partsMIT

Questions

How big is the Picoarc PCB?

It measures 50 × 20 mm and has 4 copper layers, 1.2 mm thick.

What parts does the Picoarc use?

72 parts, built around the RP2040, W25Q16JVSSIQ, AP2112K-3.3TRG1 and PCA9306DCUR. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.

Where can I download the Picoarc KiCad files?

From the naorunaoru/picoarc repository on GitHub, at the commit this page was made from: the board is hardware/layout/layout.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.

Can I use the Picoarc design in my own project?

Its repository states no licence, so its author keeps all rights: ask naorunaoru before reusing the design.