Skip to content
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

[windows] bldc-tool hangs after reboot or firmware upload #9

Open
pabloxid opened this issue Jan 22, 2016 · 2 comments
Open

[windows] bldc-tool hangs after reboot or firmware upload #9

pabloxid opened this issue Jan 22, 2016 · 2 comments

Comments

@pabloxid
Copy link

Using bldc-tool under Windows, every time I upload new firmware to the board, the program freezes. It also happens when pressing "reboot" button. Whenever USB device is shutted off while the connection with bldc-tool was established, then bldc-tool hangs.

@vedderb
Copy link
Owner

vedderb commented Jan 22, 2016

This is not the case under Linux, where the error from the serial port is reported properly on disconnect so that the port can be closed. I don't have any windows computer and I never use windows, so I have never used or tested the windows build of bldc tool. Maybe someone who has windows and some qt experience can help out here.

@pabloxid
Copy link
Author

I did some research on this. Apparently, qt under Windows has problems with
USB virtual serial ports. When an error occurs, the
handler MainWindow::serialPortError() tries to make a mSerialPort->close()
but that generates a new error, and the program goes into an infinite loop.
If I comment out that line, the program fails to connect again, but don't
freezes.

2016-01-22 4:49 GMT-02:00 Benjamin Vedder [email protected]:

This is not the case under Linux, where the error from the serial port is
reported properly on disconnect so that the port can be closed. I don't
have any windows computer and I never use windows, so I have never used or
tested the windows build of bldc tool. Maybe someone who has windows and
some qt experience can help out here.


Reply to this email directly or view it on GitHub
#9 (comment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants