Many thanks for the explanation. I had missed that.See errata E10 in the datasheet for why this block is necessary, and why it has the wrong num_blocks.
Are you sure of that ? When I was playing with Flash on the RP2040 I recall a 2MB Flash simply mirrored itself to appear 8 times to fill the full 16 MB address space. Unfortunately I don't have a Pico 2 or any other RP235X board to test with.Ideally it wouldn't actually be written to flash, hence targeting the end of flash which will only be present on 16M flash chips.
If it does write to the top of a 4MB Flash that's a problem for things like MicroPython where their Pico 2 build has a file system running right up to the end of Flash. That's how I became aware of the issue -
Code:
Program Name : MicroPythonProgram Version : v1.24.0-preview.201.g269a0e0e1Target Device : RP2350Target Chip : Cortex-M33Target ISA : ARMv8-MTarget Code : ARM-S - RP2350 Secure ARM ImageTarget Board : Pico 2Code Execution Type : Run from FlashBuild Date : Aug 8 2024Pico SDK Version : 2.0.0-developBuild Attributes : MinSizeRelProgram Area Used : 10000000 to 1004F174 316 KB 323,956 bytes 10FFFF00 to 10FFFFFF 256 bytesBinary Info Root Entry : 10000124 to 10000134 5 quads 20 bytesCopy Table Information : 100001A8 to 100001CC 10 quads 40 bytesUSB Configuration Info : 10043CFA to 10043D44 Configuration 1USB Device Descriptor : 10043D45 to 10043D56 2E8A:0005 [1.0]Binary Info Pointers : 1004B244 to 1004B2A4 25 quads 100 bytesUSB Device Descriptor : 1004CD7C to 1004CD8D F244:1003 [240.1]Included File System : 10100000 to 103FFFFF 'MP' "MicroPython" 3 MBBinary Info Tag Name : 'RP' - Raspberry Pi Pico SDKBinary Info Tag Name : 'MP' - frozen modulesUSB Device Information : 2E8A:0005 [1.0] Raspberry Pi MicroPythonUSB Device Information : F244:1003 [240.1]***** MEMORY ***** : 10100000 to 103FFFFF "MicroPython" File System***** CONFLICT ***** : 103FF000 to 103FFFFF Mirrored to 4MB FlashStatistics: Posted by hippy — Tue Aug 13, 2024 4:37 pm