Integrate our own PID code into USB class
Closed, ResolvedPublic


If you’re a maker, hobbyist, or startup company producing your own USB device, you’ve probably discovered that you need a USB Vendor ID and Product ID to uniquely identify your device to computers. The USB-IF’s position is that the only way to do this is for each organisation to pay $6000 for a unique Vendor ID, which they may not share with other individuals or organisations.

For many makers and small companies, this is a prohibitive amount of money, and forces them to resort to workarounds, such as using other organisations’ VIDs without permission, or simply making up a VID and PID. These solutions make things worse for everyone, by damaging the assumption that a VID/PID combination is unique to a given device. seeks to solve this issue for anyone producing open-source hardware. We have been gifted a Vendor ID by a company that was issued one by USB-IF and has since ceased trading; they obtained the Vendor ID before the USB-IF changed their licensing terms to prohibit transfers or subassignments. will assign PIDs on any VID we own to any open-source hardware project needing one.

We have been granted a PID code for the AXIOM Remote:

This now needs to be integrated into our AXIOM Remote firmware in the USBCDCDevice-Class by altering the Descriptor.

idVendor and idProduct
Note the correct order of the vlaues
currently: 6666:1234
39-5559-[ 261.979715] usb 1-1: New USB device found, idVendor=6666, idProduct=1234, bcdDevice= 1.00

Read our Google Summer of Code Overview page:


Language Skills:

  • C / C++

Difficulty: Very Easy

Mentors: Andrej

To get in touch with any mentor check the Mentor Contact List.

sebastian updated the task description. (Show Details)
sebastian triaged this task as Normal priority.Jan 21 2021, 11:16 AM
sebastian updated the task description. (Show Details)Jan 25 2021, 9:33 AM
sebastian updated the task description. (Show Details)Feb 18 2021, 6:48 PM
sebastian updated the task description. (Show Details)Feb 22 2021, 4:51 PM

Thanks Vinayak

Lets verify this on the actual hardware and then it can be marked as resolved.

sebastian closed this task as Resolved.Feb 15 2022, 9:40 PM