Add correct flash map for F4 device

[GoogleCodeExporter]

Now F2 and F4 devices have sectors of different page sizes and only the first 
sectors (of one page size) are included in dev_table.c

If I write to flash, for example, binary file 104028 bytes started from 
0x08000000 address, I expect that only first 5 sectors will be erased. But in 
fact it erased ceil(104028/16384) = 7 sectors.

In patch below I've fixed that.

I don't know how is organized memory in other stm devices, so I remove it. If 
someone could add flash map for all devices it would be cool.

Original issue reported on code.google.com by alenyas...@gmail.com on 19 Dec 2014 at 1:06

Attachments:

• 0001-Add-correct-flash-map-for-F4.patch

[GoogleCodeExporter]

Thanks for the report. This is a known issue, and it will require some work.

Original comment by lists.to...@gmail.com on 24 Feb 2015 at 8:56

• Changed state: Accepted