the following is rather a question than an issue.
I noticed that the two parts of firmware, firmware0 and firmware 1 are burnt to the addresses 0x8000000 and
0x8020000. Firmware 0 is only about 14 kBytes (bootloader?). The rest of the first 64 kBytes is used by the internal flash filesystem. The following 64kB Block is not used (0xFFs), I checked this by reading out with
STM32CubeProgrammer.
So we could in principle start with program code at 0x8010000 and have 64 kByte more
program space. Or we could extend the size of the internal flash by 64 kB.
Is this right or are there other reasons/ constraints preventing this?
Hello,
the following is rather a question than an issue. I noticed that the two parts of firmware, firmware0 and firmware 1 are burnt to the addresses 0x8000000 and 0x8020000. Firmware 0 is only about 14 kBytes (bootloader?). The rest of the first 64 kBytes is used by the internal flash filesystem. The following 64kB Block is not used (0xFFs), I checked this by reading out with STM32CubeProgrammer. So we could in principle start with program code at 0x8010000 and have 64 kByte more program space. Or we could extend the size of the internal flash by 64 kB.
Is this right or are there other reasons/ constraints preventing this?