fix STM32L1 FLASH_SIZE for cat.3 devices with DEV_ID 0x436

[caoddx]

Summary of changes

FLASH_SIZE incorrectly reports flash size for cat.3 devices with DEV_ID 0x436.

STM32L1 Reference Manual RM0038:

31.1.1 Flash size register
F_SIZE: Flash memory size
For DEV_ID = 0x416 or 0x427 or 0x429 or 0x437, this field value indicates the Flash memory size of the device in Kbytes.
Example: 0x0080 = 128 Kbytes.
For DEV_ID = 0x436, the field value can be ‘0’ or ‘1’, with ‘0’ for 384 Kbytes and ‘1’ for 256 Kbytes.

Documentation

None.

---

Pull request type

• Patch update (Bug fix / Target update / Docs update / Test update / Refactor)
• Feature update (New feature / Functionality change / New API)
• Major update (Breaking change E.g. Return code change / API behaviour change)

---

Test results

• No Tests required for this change (E.g docs only update)
• Covered by existing mbed-os tests (Greentea or Unittest)
• Tests / results supplied as part of this PR

[caoddx]

The previous pull request #15362 was closed by mistake, and this pull request is a recreated one.

[0xc0170]

CI started

[0xc0170]

CI started

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 1 | 🔒 Jenkins CI Job | 🌐 Logs & Artifacts

CLICK for Detailed Summary

jobs	Status
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_unittests	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-example-ARM	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️