-
Notifications
You must be signed in to change notification settings - Fork 27
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
USB device not detected on Windows #817
Comments
Potentially rust-embedded-community/usb-device#129 |
This is indeed the above issue. We're working on getting it patched up through the dependency chain and will likely take a few days. |
Ah amazing, many thanks for letting me know. Perhaps just comment here once that has been done. |
Try again with #813 |
Yeah, nothing will show up by default, you have to press |
I'm afraid nothing happens when I press Enter (whichever port I choose). I still get these errors mentioned earlier regarding Windows saying 'USB device not recognised', so I'm not even sure either of these ports is the right one. |
Also, I've just tried doing this again, but this somehow also doesn't work for me any longer (it worked with previous versions) - I need to hardcode the MQTT broker address in |
Hello - I wonder if you were able to have a look at this? |
Unfortunately no. It works fine on my machine and in the past, I have required detailed USB logs to understand why the USB enumeration fails in the past. I can look into getting that implemented to help here, but this is not a trivial issue to solve currently |
@juhaszp95 Can you please provide all of the steps that you are using to build and then flash the device? I.e. provide all the command line steps that you run exactly. That may enlighten us to a potential issue. |
The commands I run mirror exactly what is written at https://quartiq.de/stabilizer/setup.html. At the beginning, the device is powered off and disconnected from the PC. The commands I run, in this order:
These commands run without any error, saying that these components have already been installed (given I installed them previously when I flashed the stabiliser on previous occasions). I then run:
These commands finish OK. I then connect the stabiliser using an ST-Link probe and power it up. I then run It seems to flash OK and get the network, but no MQTT server (as you'd expect - nothing has been set at this point). As the program hangs in here, I press I then power off the device and then unconnect the probe. I connect the USB cable, then power the device back on at which point Windows gives me the warning 'USB device not recognised'. After this I try to run Instead of this interface, I also tried to use the previous build method, where after
I then plug the device in, power it on and run However, if I hardcode the MQTT address in This is the only way I can get it to work at the moment. |
Hmm this is indeed suspicious - thanks for the detailed list of commands, it was helpful in ruling out some potential causes of this issue. I suspect this is an issue with the usb-device stack, as I've already had to fix it a few times for various QUARTIQ projects. |
@juhaszp95 I have just written up some support for tracing the USB stack to figure out why enumeration is failing. If you have some time, it would be exceptionally helpful if you could use the |
Hello, I've got the following output:
There's no more output, but the program doesn't terminate - so I press Ctrl+C to terminate. The device now actually shows up, it's not saying it's a stabiliser, but it's listed as |
That's exactly how its supposed to work with retained MQTT messages. |
It sounds like, based on the information you provided, that the USB issues have resolved in the branch I provided. What you describe is all the normal operational behavior of the device, so I'll work on updating the USB stack in the mainline stabilizer repository and get those fixes up-streamed. |
@juhaszp95 could you verify that the current |
I can confirm the main branch still doesn't show up on the list of USB devices on Windows. It does show up and say 'Stabilizer' on Linux. This new branch now shows up on Windows (but doesn't say Stabilizer, which would be useful). |
Unfortunately this is a product of Windows that we can't control. Windows names the ports based on installed USB drivers, so we'd have to distribute a custom Windows USB driver to get Stabilizer to be named properly, which is rather complicated for simply identifying the correct serial port. As such, I don't think there's any activity that we can reasonably do to fix this. |
Sorry for having to reopen this issue, but I think the stabilizer is not detected on Windows again since the updates in the firmware. |
@juhaszp95 Can you confirm that with the latest firmware, you're still seeing USB enumeration issues on Windows? If so, please reopen this issue so we can investigate. |
I'm away at the moment, so cannot check, but perhaps @dnadlinger or @ayushagrawal2 can help. |
Hello,
I've just tried setting up a stabiliser using the docs just released, configuring the MQTT broker using pyserial running on a Windows PC. I've managed to flash the firmware on the device alright.
However, when I plug the USB cable in to set the MQTT broker, Windows gives these error messages:
Also, when I launch pyserial, it doesn't really show up in the COM ports (as far as I can tell).
I wonder if there's some driver to install or similar to get this to work? The documentation doesn't say much about this.
The text was updated successfully, but these errors were encountered: