You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems there's something detail about how Orbtrace implements USB that results in the interface strings not being recognized/cached on macOS.
That is, the interface strings are available when the device is opened, but not when going through the IO-less code path that nusb has recently implemented (which uses IORegistryEntrySearchCFProperty), which probe-rsis now making use of, which now leads to my issue posted there (some details there might be of interest):
For comparison, my MCU-LINK is detected just fine. Given that, it would seem that there's probably some quirk in Orbtrace's handling of USB that could be resolved, allowing probe-rs to discover it again.
If there's any other info you'd like me to provide, I'd be more than happy to.
The text was updated successfully, but these errors were encountered:
Hello!
It seems there's something detail about how Orbtrace implements USB that results in the interface strings not being recognized/cached on macOS.
That is, the interface strings are available when the device is opened, but not when going through the IO-less code path that
nusb
has recently implemented (which usesIORegistryEntrySearchCFProperty
), whichprobe-rs
is now making use of, which now leads to my issue posted there (some details there might be of interest):For comparison, my MCU-LINK is detected just fine. Given that, it would seem that there's probably some quirk in Orbtrace's handling of USB that could be resolved, allowing
probe-rs
to discover it again.If there's any other info you'd like me to provide, I'd be more than happy to.
The text was updated successfully, but these errors were encountered: