Blackaddr
Well-known member
Why would I want to do such a thing?
I've recommended the Teensy 4.1 to a company looking to make a commercial product. They will require a USB port on the enclosure for user programming and updates, preferably a USB-B. They do not wish to use a micro-USB to panel mount cable (there simply isn't room in the enclosure). Mounting the Teensy such that it's micro-USB port is exposed through a panel cutout is also not desirable.
The USB2 (host) connections are available on header pins. If I could switch the functionality normally provided by the USB from USB1 to USB2 the solutions becomes easy because the USB connector can be mounted on the main PCB with the rest of the product jacks.
I don't mind having to customize files in the cores repo but I'm suspicious it would require changes to the code running on the Cortex M0+ which I believe Paul considers his secret sauce.
Perhaps I'm going about this the wrong way? I simply need the normal USB behaviour you get through the micro-USB connector to be exposed in a way that it can be moved to a USB jack on the enclosure. I would expect others attempting to use a Teensy in a commercial product would run into the same issue. It also needs to be a viable method for large scale manufacturing. E.g. no fly-wires, etc.
Thoughts?
I've recommended the Teensy 4.1 to a company looking to make a commercial product. They will require a USB port on the enclosure for user programming and updates, preferably a USB-B. They do not wish to use a micro-USB to panel mount cable (there simply isn't room in the enclosure). Mounting the Teensy such that it's micro-USB port is exposed through a panel cutout is also not desirable.
The USB2 (host) connections are available on header pins. If I could switch the functionality normally provided by the USB from USB1 to USB2 the solutions becomes easy because the USB connector can be mounted on the main PCB with the rest of the product jacks.
I don't mind having to customize files in the cores repo but I'm suspicious it would require changes to the code running on the Cortex M0+ which I believe Paul considers his secret sauce.
Perhaps I'm going about this the wrong way? I simply need the normal USB behaviour you get through the micro-USB connector to be exposed in a way that it can be moved to a USB jack on the enclosure. I would expect others attempting to use a Teensy in a commercial product would run into the same issue. It also needs to be a viable method for large scale manufacturing. E.g. no fly-wires, etc.
Thoughts?