Thread on Core 1 on PICO hangs when accessing io
Port, board and/or hardware
Raspberry Pi Pico
MicroPython version
MicroPython v1.23.0 on 2024-06-02; Raspberry Pi Pico with RP2040
Reproduction
import os
import time
import _thread
def core1_thread():
try:
print("entering core1_thread")
text = "some text to log"
# Open log file in append mode
f = open("test.log", "a")
f.write(text)
except OSError as ex:
print(ex)
finally:
f.close()
def create_log():
"""
Check if the log file exists. If the log file does not exist, create the log file and write a header line.
Parameters:
None
Returns:
None
"""
_log_fn = "/test.log"
try:
# File exists
os.stat(_log_fn)
return
except OSError:
idx = _log_fn.rfind("/")
dir = _log_fn[1:idx]
if dir and not dir in os.listdir():
os.mkdir(dir)
# File does not exist
try:
t = f"file {_log_fn} created\n"
with open(_log_fn, "a") as f:
f.write(t)
print(t.rstrip())
except OSError as ex:
raise OSError(f"exception {ex}")
def main():
create_log()
thread = _thread.start_new_thread(core1_thread, ())
if __name__ == "__main__":
main()
time.sleep(1) # if 'mpremote run', allow thread to run before we soft reset
Expected behaviour
Expected to see 'some text to log' in file test.log on pico.
Observed behaviour
After starting the thread it hangs after printing 'entering core1_thread'.
Additional Information
No, I've provided everything above.
Code of Conduct
Yes, I agree
Raspberry Pi Pico _thread OSError: TinyUSB callback can't recurse
Port, board and/or hardware
Raspberry Pi Pico
MicroPython version
MicroPython v1.23.0 on 2024-06-02; Raspberry Pi Pico with RP2040
Reproduction
import time
import _thread
def test(name):
... print(1)
... time.sleep(1)
...
...
...
_thread.start_new_thread(test,('name',))
2
1
FATAL: uncaught exception 200127f0
OSError: TinyUSB callback can't recurse
Expected behaviour
I found that this problem does not exist in version 1.22.2
Observed behaviour
My previous program didn't work after I updated the firmware. I was sure the program would work, so I changed the firmware to 1.22.2 and it worked.I found when the "while True" in "_thread.start_new_thread" , this problem must occur. I guess it is caused by USB-related changes.
Additional Information
No, I've provided everything above.
Code of Conduct
Yes, I agree