-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Nucleo-F401RE: Communication hangs after a while #225
Comments
I found a way to reliably kill the connection with the Nucleo: Run a program that writes lots of stuff to USART2 on the Nucleo (which is forwarded as an usb-serial device over the stlink on the board), then read from that usb-serial device on the computer (for example with
(I have not yet updated the firmware on the nucleo for want of a windows machine so the cause of the hangup may be a bug there, but a segfault is usally a bug in the segfaulting program). |
Please test against latest stlink master tools, and latest ST programmer firmware. Reopen a new issue when the problem still remains. |
This problem is similar to a previously observed issue in #194. As the toolset-related issue has been addressed and one can safely assume that this is also the case for the aspects that derive from external tools, I am finally closing this issue now as resolved. |
After a while, communication between st-util and my nucleo board fails.
It starts just fine, I can load a program and run it and use gdb on it as expected. Verbose output during this phase looks like:
The ST-LINK LED blinks red/green to signal ongoing communication.
But then after a while I get:
The program on the board continues running, and gdb still thinks it can talk to the server, but it can no longer actually affect the board, the ST-LINK LED swiches to green ("communication finished and successful"). st-util still continues to print the "core status: running" messages.
If I then quit st-util with Ctrl-C and restart it, I get:
Powercycling the Nucleo board puts it in a usable state again.
The text was updated successfully, but these errors were encountered: