Hello
I have an issue that I am hoping to resolve. I have a teensy 3.6, using host mode via the "USBHost_t36.h" method. It's been working really very well for us overall.
We have a relatively simple USB<->UART converter in front of a bluetooth module. Its a 231Xq that works great on a pc/android rig.
Unfortunately, I yet to have success in being able to have the device claimed, it looks like the FTDI 231X may not be sending the right USB class id's or something. This board is a passthrough, you can open a terminal on a pc/android and simply type things and it gets passed right through the com/tty port.
It's a custom built board, but fairly simple overall.
I tried overriding it's bDeviceClass, and bDeviceSubClass in the serial.cpp but then it just fails later, the rx/tx buffers are not allocated.
Open for ideas or suggestions.
Thanks from a forum noob.
Dean
I have an issue that I am hoping to resolve. I have a teensy 3.6, using host mode via the "USBHost_t36.h" method. It's been working really very well for us overall.
We have a relatively simple USB<->UART converter in front of a bluetooth module. Its a 231Xq that works great on a pc/android rig.
Unfortunately, I yet to have success in being able to have the device claimed, it looks like the FTDI 231X may not be sending the right USB class id's or something. This board is a passthrough, you can open a terminal on a pc/android and simply type things and it gets passed right through the com/tty port.
It's a custom built board, but fairly simple overall.
I tried overriding it's bDeviceClass, and bDeviceSubClass in the serial.cpp but then it just fails later, the rx/tx buffers are not allocated.
Open for ideas or suggestions.
Thanks from a forum noob.
Dean