-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[xtask] serial-term not working on windows #156
Comments
Thank you @njordr and apologies! Edit: This is a previous debugging attempt that failed. Please ignore.I had run into this on a previous debugging session but did not backtrack properly and come back to resolve this once I had solved my own issue. I think the fix is quick but it's in our dependency, The bug isn't known about but probably related to their windows-sys migration - I've filed a MWE and will try to upstream the fix this week and a hotfix for you as well. If I had to guess, the let port = serialport::new(&dongle.port_name, 115200).port.open()? that comes up in Good news! I found someone else who ran into the issue and found a workaround. zephyrproject-rtos/zephyr#17266 They added a
@jonathanpallant should have a better idea of how we can fix this. Thanks for the report! |
The bug is that whilst I used the IAD device class and sub-class to tell Windows to load a different driver for each interface, I didn't include the extra magic information Windows needs. The |
Today I loaded the puzzle-fw into the nRF52840 dongle and tried to run the terminal console, but it failed:
the dongle is recognized in the usb-list
And I could change the channel
The text was updated successfully, but these errors were encountered: