2 ms·
The Pico was designed for battery powered projects, I for one wouldn't want a higher clock rate because it would lead to even more power issues while powered by
by Dork1234 4y ago
The Pico was designed for battery powered projects, I for one wouldn't want a higher clock rate because it would lead to even more power issues while powered by battery. Right now you can get by with powering device RP2040,sensors, and display with cheap LiPo battery back.
Anything over 200mhz and the SPI flash doesn't work anymore either. It can be pretty hard to fit all working memory and code into the 256KB.
The chip was designed to replace Arduino boards, many of which run below 50mhz, and only process 8bits at a time. 133mhz, 32bit dual core is a sizable jump in performance already.
- detrites 4y agoPimoroni's "Picosystem" clocks the RP2040 at 250Mhz, has 16MB of working SPI flash including XiP and powers an IPS display: https://github.com/pimoroni/picosystem https://github.com/pimoroni/picosystem (see the note next to the no_overclock compile flag)
- Dork1234 4y agoYou are right, but their flashchip is only supported up 133mhz. https://www.trustedparts.com/en/part/winbond/W25Q16JVSSIQ%20TR https://www.trustedparts.com/en/part/winbond/W25Q16JVSSIQ%20... The flash chip they are using is only rated to 133mhz, so they are setting the SPI clock divider. in hardware.cpp #ifndef NO_OVERCLOCK // dividing the clock by two ensures we keep the spi transfer to // around 62.5mhz as per the st7789 datasheet when overclocking sm_config_set_clkdiv_int_frac(&c, 2, 1); #endif Learned a new work around for overclocking.
- detrites 4y agoAh, good to know. Thanks!
- solarkraft 4y agoIsn't clocking higher and thus completing the calculation and going back to sleep faster usually more efficient than clocking lower and taking longer to complete?