I wonder if Paul or someone could update on the current status of the USB Host library for models of Teensy with second USB port.
1) The USB Host library is the one here, right?
https://github.com/PaulStoffregen/USBHost_t36
2) Does this work on the Teensy 3.5 as well as the 3.6? I ask because a message in USBHost_t36.h says "USBHost_t36 only works with Teensy 3.6.", similar to comment on https://www.pjrc.com/store/cable_usb_host_t36.html.
3) What is the best source of documentation?
4) What level of prime-time-readiness is the library at with respect to keyboard client? I read in earlier posts that it could be hit or miss which keyboards would communicate successfully, but perhaps that's been solved?
5) ... including handling intervening hubs (possibly built-in to fancy keyboard)?
6) ... also I see in keyboard.cpp a number of comments "TODO: queue events, perform callback from Task". Do I infer that there was an intent not to call user code from USB interrupt or something like that? How much of an obstacle is that apparently not being implemented yet?
7) I See the library's example folder has distinct examples for various client devices, but not keyboard (though basic keyboard OnPress handling is shown in example "Test".) Are there other keyboard examples somewhere?
Thanks! -- Graham
1) The USB Host library is the one here, right?
https://github.com/PaulStoffregen/USBHost_t36
2) Does this work on the Teensy 3.5 as well as the 3.6? I ask because a message in USBHost_t36.h says "USBHost_t36 only works with Teensy 3.6.", similar to comment on https://www.pjrc.com/store/cable_usb_host_t36.html.
3) What is the best source of documentation?
4) What level of prime-time-readiness is the library at with respect to keyboard client? I read in earlier posts that it could be hit or miss which keyboards would communicate successfully, but perhaps that's been solved?
5) ... including handling intervening hubs (possibly built-in to fancy keyboard)?
6) ... also I see in keyboard.cpp a number of comments "TODO: queue events, perform callback from Task". Do I infer that there was an intent not to call user code from USB interrupt or something like that? How much of an obstacle is that apparently not being implemented yet?
7) I See the library's example folder has distinct examples for various client devices, but not keyboard (though basic keyboard OnPress handling is shown in example "Test".) Are there other keyboard examples somewhere?
Thanks! -- Graham