diff options
| author | Phil Howard <github@gadgetoid.com> | 2025-05-29 13:46:05 +0100 |
|---|---|---|
| committer | Damien George <damien@micropython.org> | 2025-06-17 11:40:42 +1000 |
| commit | b725c26b4e351b71b8f72ad8e55bbbd5ccce4602 (patch) | |
| tree | 3ddabe84e673b0f24d93038027eab1380a008895 /tests/frozen | |
| parent | c1196cadb185a6834146c358ecbf495bd556c303 (diff) | |
| download | micropython-master.tar.gz micropython-master.zip | |
Assuming a 133MHz capable flash in 91cff8e4f10ea665c5f3f4b16d62c98d6ca22037
caused `rp2_flash_set_timing_internal` to set out of range dividers for
some boards (anything with value of 4 and flash that doesn't tolerate
higher speeds).
This affected (at least) the XIAO RP2350 board, making it non-bootable.
Since Pico SDK's `PICO_FLASH_SPI_CLKDIV` is entirely unreliable on a system
with a variable system clock (users can change it at runtime) then use it
only to work out a default `MICROPY_HW_FLASH_MAX_FREQ`.
This value can be overridden in board config.
Note that RP2350's default clock is 150MHz, RP2040's is 125MHz and it has
been certified at 200MHz so it's quite possible that
`PICO_FLASH_SPI_CLKDIV` is unreliable even at standard RP2 clocks.
(If flash timings are marginal then this can manifest as instability rather
than outright failure.)
Fixes issue #17375.
Signed-off-by: Phil Howard <github@gadgetoid.com>
Diffstat (limited to 'tests/frozen')
0 files changed, 0 insertions, 0 deletions