-
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
coproc.halt
frequently misbehaves
#7109
Comments
As I re-test today I'm getting different results. Of course, I'm also using different boards and different builds of CircuitPython. Notably, these boards are non-PSRAM boards, but at least they're in the feather form factor and have the LED on GPIO13. The build is 8.0.0-beta.4-25-g195ad4e479 which is the same as b8a2d3f except for the addition of these boards. Here's a full example with all necessary files: The main file is called "do_coproc.py"; you can rename it to "code.py" or "import do_coproc" to run the test. On esp32-s2 (adafruit feather esp32s2 reverse tft prototype), CircuitPython never freezes. However, after a few runs the LED stops blinking. This condition persists until the module is reset. Just hitting ctrl-c and re-starting with on esp32-s3 (adafruit feather esp32s3 reverse tft prototype), many runs completed successfully. After hitting ctrl-c and re-starting of course, the LEDs blink at different rates on the two boards when using the same source program, because the "cycles per microsecond" figure is different. |
coproc.halt
frequently crashescoproc.halt
frequently misbehaves
Moving this back to 8.0.0. I think it's going to get fixed by @tannewt's work? |
I never tested with this repro code so I'm not sure. I didn't see any issues with my (different) tests. |
@jepler I will close this since the underlying modules are so different now. If you'd like to retest with a new trial, that'd be great, and we can start a new issue if necessary. |
CircuitPython version
Code/REPL
Behavior
The device disconnects from USB when the
coproc.halt()
is called.Description
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: