Hello all!
Has the Teensy 4.x been tested with USB Hubs? I'm developing the second version of an interface board for a project that uses Teensies that are always connected to a central hub.
Here's a pic of the first version for reference:
In the second version, I'm gunning for a fully embedded solution - this time with the iMXRT1062 for more horsepower at the edge (processing LiDAR data). This means no more daughterboards, so I'm really looking forward to the release of the chip only offering from pjrc for the 4.x series.
I was checking out the errdata for the chip just to verify that there won't be any show stoppers, and saw ERR050101. This states that there are endpoint conflict problems when in device mode w/ isochronous comm. We use isochronous since we're streaming live LiDAR data. At least, I think we do - I didn't write the ROS driver & firmware. What mode does teensy use default?
Here is the err from NXP for convenience:
Does anyone have any insight on this?
Thanks so much
Has the Teensy 4.x been tested with USB Hubs? I'm developing the second version of an interface board for a project that uses Teensies that are always connected to a central hub.
Here's a pic of the first version for reference:
In the second version, I'm gunning for a fully embedded solution - this time with the iMXRT1062 for more horsepower at the edge (processing LiDAR data). This means no more daughterboards, so I'm really looking forward to the release of the chip only offering from pjrc for the 4.x series.
I was checking out the errdata for the chip just to verify that there won't be any show stoppers, and saw ERR050101. This states that there are endpoint conflict problems when in device mode w/ isochronous comm. We use isochronous since we're streaming live LiDAR data. At least, I think we do - I didn't write the ROS driver & firmware. What mode does teensy use default?
Here is the err from NXP for convenience:
Does anyone have any insight on this?
Thanks so much