I feel like this is going to end up being something simple that I'm missing, but I'm stumped.
I have built 2 units that use Teensy 4.0.
Each unit is supplied power from a wall adapter, so each Teensy has the VUSB pads cut.
Unit A uses only the Teensy Device USB (Serial + MIDI Type).
Unit B has both the Teensy Device USB (Serial + MIDI Type) and USB Host (USBHost_t36.h) with D+, D- connected to Teensy, +5V from the power plane and GND from the ground plane.
When I connect Unit A to a computer, it is registered as a MIDI Device and I've verified MIDI is being sent into a DAW.
On Unit B, if I connect a class-compliant USB Keyboard into the USB Host port, the Keyboard becomes powered and I've verified MIDI is being sent from the keyboard into Unit B's midi event handlers.
So separately, they both work as intended plugged into other commercial hardware, but if I connect Unit A (Device) into Unit B (Host), I can't get any of Unit B's midi event handlers to respond to Unit A at all.
I have built 2 units that use Teensy 4.0.
Each unit is supplied power from a wall adapter, so each Teensy has the VUSB pads cut.
Unit A uses only the Teensy Device USB (Serial + MIDI Type).
Unit B has both the Teensy Device USB (Serial + MIDI Type) and USB Host (USBHost_t36.h) with D+, D- connected to Teensy, +5V from the power plane and GND from the ground plane.
When I connect Unit A to a computer, it is registered as a MIDI Device and I've verified MIDI is being sent into a DAW.
On Unit B, if I connect a class-compliant USB Keyboard into the USB Host port, the Keyboard becomes powered and I've verified MIDI is being sent from the keyboard into Unit B's midi event handlers.
So separately, they both work as intended plugged into other commercial hardware, but if I connect Unit A (Device) into Unit B (Host), I can't get any of Unit B's midi event handlers to respond to Unit A at all.