Hello,
The pico sdk allows changing the speed dynamically.
I've had one run stable at 400 MHz for a frequency counter project,
executing from RAM, not from flash. It required pushing the core voltage
to 1.30V. The stuff does not even heat, and I did not check power draw.
USB serial was still working fine.
It was a simple bare metal program, no rtos involved.
Sebastien
On 22/02/2025 04:12, Tomek CEDRO wrote:
On Fri, Feb 21, 2025 at 7:53 PM Matteo Golin <matteo.go...@gmail.com> wrote:
Recently the RP2040 has officially been rated up to 200MHz by Raspberry Pi, a
bump from the 125MHz speeds it was
initially rated for. It appears the Pico SDK has been updated recently to allow
users to use the new rated speed.
Here's an interesting conversation about the topic on the Arduino project:
https://github.com/earlephilhower/arduino-pico/issues/2814
I think we should discuss the same thing here for NuttX. Should we update the
RP2040 to now use 200MHz as the default,
since that is its rated speed? And we should then update the version of the
Pico SDK mentioned in our documentation so
that users can leverage the new clock speed. I would propose that at the same
time we update that in the documentation,
we perhaps include the installation/build procedure for the SDK and picotool on
a common doc page (the RP2040 chip page)
so that we don't need to update every single RP2040 board page with the new
version when we upgrade on the NuttX side.
That way each board page can simply link to the installation procedure (afaik
none of them have a different procedure).
Good idea Matteo :-) I bought rPI-Pico(-W) and rpi-Pico-2(-W) 4 boards
just for testing but I am not familiar with the hw :-)
Would it be good to allow users to select clock frequency? If 125MHz
-> 200MHz that would imply increased power consumption too? Can it be
easily changed at runtime?
