Skip to main content

USBSID-Pico connects vintage SID chips to USB, but the board revision matters

Hackaday's retrocomputing coverage highlights a bridge for real Commodore 64 sound chips. Voltage settings, controller choice and software support need a closer look.

Two unmarked rectangular integrated circuits on a dark mat beside a blurred green circuit board.
TechKili · AI-generated conceptual illustration with Cloudflare FLUX.2 klein; not a photograph of USBSID-Pico or a specific SID chip.
Share this article:
In this article

USBSID-Pico gives modern computers a way to control one or two physical Commodore 64 SID sound chips over USB. For a chiptune listener or maker with suitable chips, its value is access to the hardware from current software, rather than having to build the entire listening setup around an old computer.

Hackaday highlighted the project on October 13, 2026 in its Retrocomputing Challenge coverage. That is the reporting event, not a new product launch: the creator's project history traces development back to 2024. Readers should also distinguish the certified v1.3 board from the later v1.5 documentation.

The Pico controls the sound source

The project uses a Raspberry Pi Pico-family microcontroller to bridge software and SID hardware. It supports original MOS 6581/8580 chips and documented hardware replacements, with USB, WebUSB, MIDI and ASID connection paths. ASID carries SID register data over MIDI; it is a control route, rather than a recording of the finished audio.

That makes the bridge useful for working with real chips, but it does not establish that physical hardware sounds better than software emulation. Chip choice and the listening setup are separate decisions. This is a documentation-based explanation, not a listening test.

Read the revision before configuring the sockets

The v1.5 PCB manual, generated September 12, describes firmware-controlled settings that replace earlier jumpers. Its detection routine associates the 8580 with 9V and the 6581 with 12V, and locks the board after detecting a change until the socket configuration is checked in the configuration tool.

The practical consequence is to follow the manual for the actual board in hand, including chip orientation and configuration. Automatic detection does not remove the need to check a changed setup. Instructions for one PCB revision should not be treated as universal wiring instructions.

OSHWA's NL000045 record is dated July 11, 2026 and explicitly identifies v1.3. It lists hardware and software licensing information and links the design documentation. That record gives readers a traceable open-hardware reference; it is not an audio-quality rating or blanket certification of later revisions.

Match the controller and software to the music

The project README identifies a concrete controller tradeoff: demanding, cycle-exact tunes with dense register writes may not run at full speed on RP2040-based Pico1 boards. The author recommends RP2350-based Pico2 boards for that workload. That is a documented compatibility recommendation, not a comparative benchmark conducted by TechKili.

Existing owners need not replace a controller simply because a newer one is supported. Start with the intended player and music, check the project's software manual, and investigate a limitation if it affects that use. MIDI support is described as beta in the README, so a supported USB path should not be mistaken for a guarantee that every MIDI workflow is finished.

The README also describes a four-socket USBSID-Pro in development without a planned release date. It should remain outside a decision about what the current two-socket board can do.

Sources