What to do about USB VID and PID?
As @chrismas9 pointed out to me, there are a few options, none of which are optimal:
- Buy your own VID from USB-IF for $US5000.
- Request free PIDs from Openmoko http://wiki.openmoko.org/wiki/USB_Product_IDs
- Buy PIDs from MCS Electronics for EUR9.95. Their VID has been revoked so they are only selling a guarantee that no one else will have the same PID.
- Use VID=0xf055; see http://hackaday.com/2013/10/22/usb-implementers-forum-says-no-to-open-source/
ESP32-S3 sdkconfig custom PID no longer working after commit 0a11832cd (...esp_console config for ESP32-C3)
Port, board and/or hardware
esp32, boards: UM_TINYS3, UM_PROS3, etc...
MicroPython version
commit 0a11832cd esp32: Use the ESP-IDF default esp_console config for ESP32-C3.
Reproduction
Build UM_TINYS3 or any other board that sets CONFIG_TINYUSB_DESC_CUSTOM_PID in sdkconfig and observe the VID:PID.
Expected behaviour
Up to commit fbb02d3ae, CONFIG_TINYUSB_DESC_CUSTOM_PID sets the PID. 0a11832cd onwards the PID is always the default VID:PID=303A:1001.
Observed behaviour
The commit describes C3 specific behavior regarding console. I don't have a C3 on hand so I don't fully understand the specifics of what was being addressed here, but does look like S3 port is affected and reporting this in case this was not intended.
Would still like to be able to control USB parameters. Eg. sdkconfig a la:
CONFIG_TINYUSB_DESC_CUSTOM_VID=0x303A
CONFIG_TINYUSB_DESC_CUSTOM_PID=0x80D1
CONFIG_TINYUSB_DESC_BCD_DEVICE=0x0100
CONFIG_TINYUSB_DESC_USE_ESPRESSIF_VID=n
CONFIG_TINYUSB_DESC_USE_DEFAULT_PID=n
CONFIG_TINYUSB_DESC_MANUFACTURER_STRING="Unexpected Maker"
CONFIG_TINYUSB_DESC_PRODUCT_STRING="TinyS3"
CONFIG_TINYUSB_DESC_SERIAL_STRING="_ts3_"
Additional Information
No, I've provided everything above.
Code of Conduct
Yes, I agree