You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the Bluetooth stack is initialized before calling the begin function on any of the Adafruit_TinyUSB instances, the descriptors that Adafruit_TinyUSB uses don't include the descriptors for any of those instances.
The Pico does show up correctly after forcing the USB bus to rescan (but just resetting the Pico does not help).
How to reproduce ?
Select the Raspberry Pi Pico W in the IDE
Enable the Bluetooth stack (Tools > IP/Bluetooth Stack: "IPv4 + Bluetooth")
Enable Adafruit TinyUSB as USB stack (Tools > USB Stack: "Adafruit TinyUSB")
Upload the sketch above (which includes an instance of Adafruit_USBD_MIDI).
Verify that the board does not show up as a MIDI device, there's no hint of MIDI in the descriptors.
Some debugging was already done by earlephilhower in earlephilhower/arduino-pico#2022, where he was able to rule out any problems with the earlephilhower/arduino-pico core specifically, which is why I've opened an issue here.
From the previous issue:
earlephilhower
Yup, the Adafruit library of TinyUSB is not signaling the PC to re-read the descriptor when this happens and hence the PC will keep the old one. If you cause the USB bus to rescan, the device does show up properly:
[...]
So this is a TinyUSB issue most likely. Adafruit is making a new descriptor and informing TinyUSB about it, but for some reason TinyUSB can't tell the PC about it. Might want to ping them with this info, it may be a simple fix...
Debug Log
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered:
A long delay to bring up the BT HCI interface lets the host enumerate the USB device listing before the MIDI interface is added. Need to manually disconnect/reconnect to get it going, like in the examples.
tttapa
added a commit
to tttapa/Control-Surface
that referenced
this issue
Nov 3, 2024
Operating System
Linux
Arduino IDE version
Arduino 2.3.2
Board
Raspberry Pi Pico (FQBN:
rp2040:rp2040:rpipicow:usbstack=tinyusb,ipbtstack=ipv4btcble
)ArduinoCore version
https://github.com/earlephilhower/arduino-pico 3.7.2
TinyUSB Library version
2.3.0 (bundled with core)
Sketch as ATTACHED TXT
Sketch that reproduces the issue (minimal)
Compiled Log as ATTACHED TXT
picow-usb-ble-problem.txt
What happened ?
→ Previously reported at earlephilhower/arduino-pico#2022, which contains more information
If the Bluetooth stack is initialized before calling the
begin
function on any of theAdafruit_TinyUSB
instances, the descriptors thatAdafruit_TinyUSB
uses don't include the descriptors for any of those instances.The Pico does show up correctly after forcing the USB bus to rescan (but just resetting the Pico does not help).
How to reproduce ?
Raspberry Pi Pico W
in the IDETools
>IP/Bluetooth Stack
:"IPv4 + Bluetooth"
)Tools
>USB Stack
:"Adafruit TinyUSB"
)Adafruit_USBD_MIDI
).Some debugging was already done by earlephilhower in earlephilhower/arduino-pico#2022, where he was able to rule out any problems with the earlephilhower/arduino-pico core specifically, which is why I've opened an issue here.
From the previous issue:
Debug Log
No response
Screenshots
No response
The text was updated successfully, but these errors were encountered: