Closed beyonlo closed 2 years ago
freq(270_000_000)
@beyonlo !!!
Does this also happen at the rated 133MHz?
Hello @jimmo
Does this also happen at the rated 133MHz?
Yes. Below the test running at 133MHz.
Output:
$ mpremote run rpico_th1.py
Clock running at: 133000000
os.uname(): (sysname='rp2', nodename='rp2', release='1.19.1', version='v1.19.1 on 2022-06-18 (GNU 11.2.0 MinSizeRel)', machine='Raspberry Pi Pico with RP2040')
8 1
8 1
8 0
8 1
8 1
8 0 <- Congeals/stop here!
Fixed by 662dc8602bf0ab99332748d178b0e950189df9e7
Hello.
I'm using
RPico
with MicroPython version1.19.1
. I'm using the ready MicroPython firmware from the the download page: https://micropython.org/resources/firmware/rp2-pico-20220618-v1.19.1.uf2This example write data on flash using
core0
and use thecore1
just for watch the pin_outCode:
Output:
Ps 1: Sometimes the Bug happen, sometimes not. So, if Bug do not happen at the first time, just try more times. It is very easy to repeat until problem happen. If example do not congeals/stop, it will happen another Bug: watch the second value printed (pin value), it will stop to change. Ps 2: I tested in two different
RPico
to be sure that is not board problem Ps 3: If you invert the example: writing data on flash usingcore1
and use thecore0
just for watch the pin_out, will be very worst, I mean, the problem always happen!Thank you.