But where exactly in the MicroPython executable are you invoking a break, and how are you determining where the "count" variable is in the heap, obtaining its value, printing it out ? What exactly is your data showing ?Source: the example presented above by the authors of the book
Debugger: Eclipse + GDB + openocd + debugprobe attached through SWD to the both cores running live MicroPython
Result: confirmed down to disassembly, the locks are not working between the cores.
I am not saying you are wrong but without the detail it's not possible to replicate your test, not possible to confirm your conclusion.
None of it is particularly of interest to me as I accept that threading is broken, and maybe MicroPython locks are too, but it would undoubtedly be useful to the MicroPython team when it comes to identifying and fixing thread related issues.
Statistics: Posted by hippy — Sat Dec 07, 2024 2:24 pm