Repository navigation
Add 1209:4D32 for the Mbox 2 Mini open firmware - #1322
Open
ItsMeATaco wants to merge 1 commit into
Open
ItsMeATaco wants to merge 1 commit into
ItsMeATaco wants to merge 1 commit into
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This requests 1209:4D32 for the Mbox 2 Mini open firmware, and adds the org ItsMeATaco.
Project: https://github.com/ItsMeATaco/mbox2-mini-open-firmware (GPL-3.0, LICENSE at the root)
It's an open source replacement firmware for the Avid Mbox 2 Mini, a USB audio interface built on a TI TUSB3200A. Avid's driver for it doesn't run on current Windows with Memory Integrity on, so the firmware turns the Mbox into a USB Audio Class device that works on the built-in driver. Owners flash it once with a Raspberry Pi; after that, updates go over USB from the project's Windows app.
About it being firmware only: the hardware is a commercial device, so there are no PCB files, and every owner runs the same prebuilt release image. The PID is in that image's device descriptor, so it has to belong to the firmware rather than to each owner's unit. It's the same situation as the MD-380 open firmware (1209:F380, #261).
So far the releases (v1.0.0 and v1.0.1) use the test PID 1209:0001, and the tools now also check the product name so another test device on that ID isn't taken for the Mbox. A PID of its own fixes it properly: Windows caches the maintenance interface's Microsoft OS descriptors per VID/PID, and the tools find the Mbox by its ID.
🤖 Generated with Claude Code