-
Notifications
You must be signed in to change notification settings - Fork 1.3k
nrf52832 does not respond to control-C - sometimes #1003
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
Comments
Hmm, I wonder if my UART with nRFx rewrite can fix that. |
@hathach Are you looking at this? |
this appears to have been fixed. Ok to close? |
Sorry I tested this on the pca10056 dk board. Not on feather53832. |
verified that this is still not working for feather 52832 -- sorry for the confusion. |
Yes, since this is 52832, this must be in the UART driver not USB ;) |
Just a reminder that this issue is still present on the feather_nrf52832. |
@dhalbert Did you fix this? |
It was still broken as of yesterday. |
I have been try to find the issue tbut have not been successful. If you have suggestions about where to look I’ll be happy to keep working on it. |
@tannewt I just fixed pin claiming for UART, but not UART reset. I think that's still to do. |
since we have dropped nrf52832 -- should we close this? |
Since no one has complained about this in 52840, let's close. |
While testing the SPI and I2C interfaces to the STMPE610 Touch screen copntroller, I found that once I start my program running, I cannot use control-C to break out. This occurs with pot the I2C and SPI versions of the driver.
Control-C does work under the REPL -- have not tried other sensors yet.
Revetring to 3.x -- control C works properly running the same code.
No exeption handling in the program.
The text was updated successfully, but these errors were encountered: