The code runs but careful inspection of output indicates misbehaviour and Control-C appears to work but doesn't go all the way to REPL and maybe 15 seconds later the desktop o/s says there's a USB problem (serial connection running over USB).
It takes a few minutes to occur, it's not at an exact time. Here it's 241 seconds from time.monotonic_ns() and I've had other runs around 138 and 196.
This is on an EDU PICO but that's basically a Pi Pico W sitting on some hardware. I wasn't using displayio console. I'd assume this will reproduce on a Pi Pico W.
May not be synthio, small chance it's ulab or something else...
Noted while benchmarking for functionality workaround in #9780
CircuitPython version
Code/REPL
v1.1 of synthio-pwm-workaround-benchmark.py - I'm not sure what part of that is causing problem
Behavior
The code runs but careful inspection of output indicates misbehaviour and Control-C appears to work but doesn't go all the way to REPL and maybe 15 seconds later the desktop o/s says there's a USB problem (serial connection running over USB).
It takes a few minutes to occur, it's not at an exact time. Here it's 241 seconds from time.monotonic_ns() and I've had other runs around 138 and 196.
And this is what a control-c looks like, no
>>>
REPL` prompt.Description
No response
Additional information
This is on an EDU PICO but that's basically a Pi Pico W sitting on some hardware. I wasn't using displayio console. I'd assume this will reproduce on a Pi Pico W.
May not be
synthio
, small chance it'sulab
or something else...Noted while benchmarking for functionality workaround in #9780