When loading a .hex file into flash, the STM32CubeProgrammer (v 2.13.0) miscalculates which sectors to erase and as a result, the download often fails unless the region being loaded has been previously erased or happens to contain the same values.
For example (see attached image), when loading an image that is 0x23B74 bytes (142.86KB) bytes to address 0x08004000 in an STM32L471 (256 x 2K sectors), it erases sectors 4..39.
The start sector for address 0x08004000 should be 8 (8 x 2048 = 0x4000) and the end sector (0x08004000+0x23B74=0x08027B74) should be 0x4F (79 decimal)
If I'm doing something wrong, suggestions would be appreciated!
Unfortunately, no change with 2.14.0. It recognizes the device type (it is an STM32L471 - see below) but is not calculating sectors properly (the STM32L471 uses 2K sectors). So loading a file to 0x08004000 (16K offset into flash) should start at sector 8, not 4.
From the reference manual (RM0351):
The Flash memory is divided in two banks. Each bank is organized as follows:
• A main memory block containing 256 pages of 2 Kbyte. Each page is made of 8 rows of
256 bytes.
It's pretty clear that the STM32CubeProgrammer simply isn't correctly recognizing the flash layout of the STM32L471. It clearly thinks it has 4K sectors. Any chance we can get a beta fix for this?
