#92 STM32L1xxxE (Device Id 0x437) has wrong Option-byte-addr-range

[Edvar Klakken]

Ref table in dev_table.c, entry for device id 0c0437. The stm->dev->opt_end value is wrong. It should be 0x1FF8 00FF.
Ref STM32 Reference Manual RM0038, page 57 (cat. 5 device).
The value seems to be used only for printing of "Option RAM" size - and this is by the way read-only memory so "RAM" is not quite correct....
PS.
The BootLoader of the STM32L151RE can't access the missing bytes anyhow - it returns NACK...

[Tormod Volden]

Right. Strictly speaking the option bytes end before 0x1ff800ff but ST has come up with some additional memory fields since the table format was defined. And yes, stm32flash only lists it for informational purpose (and potential confusion) now...

[Tormod Volden]

RM0038 says up to 64 bytes of option bytes, for bank 1 at 0x1FF8 0000 - 0x1FF8 001F and for bank 2 at 0x1FF8 0080 - 0x1FF8 009F. The factory information banks fills in the rest of the 256 bytes. So the option byte range we have in oev_table.c is correct, just that there is a hole of factory info at 0x20-0x7F.

[Tormod Volden]

I have seen some other dual-bank devices like 0x471 where the two option byte ranges for each bank are far away from each other. Since our table (and the simple calculation leading to the display of the number of option bytes) only supports one range, I think it is simplest and most consistent to just ignore the second range. I have therefore corrected the range in our device table for this 0x0437 (and the similar 0x436) device to only cover the 32 bytes for the first bank. (commit cae1bb8)

And I also changed the displayed wording to "Option bytes". Thanks for the suggestion! And "System memory" while I was at it. (commit 5580827)