STM32L1 update drivers version to CUBE V1.10.2

[jeromecoutant]

Summary of changes

ST Cube drivers version is updated from V1.8.1 to V1.10.2
which is the latest official version from:

https://github.com/STMicroelectronics/STM32CubeL1/

• directories have been restructured to be aligned with other STM32 families
• Sub-family MCU has been introduced in targets.json to help custom boards use

@ARMmbed/team-st-mcd

@chrissnow

Impact of changes

Migration actions required

Documentation

---

Pull request type

[x] 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)
[x] Covered by existing mbed-os tests (Greentea or Unittest)
[] Tests / results supplied as part of this PR

---

Reviewers

---

[ciarmcom]

@jeromecoutant, thank you for your changes.
@ARMmbed/mbed-os-maintainers please review.

[0xc0170]

@jeromecoutant can you share the tests run ?

[jeromecoutant]

Tests have been done:

• with GCC, ARM and IAR
• with OS and baremetal
• MBED CLI2 also verified

[ciarmcom]

This pull request has automatically been marked as stale because it has had no recent activity. @ARMmbed/mbed-os-maintainers, please complete review of the changes to move the PR forward. Thank you for your contributions.

[chrissnow]

@jeromecoutant I'm getting the following

Building project mbed-os-example-blinky (XDOT_L151CC, ARMC6)
Scan: mbed-os-example-blinky

[Error] gpio_api.c@162,27: no member named 'BRR' in 'GPIO_TypeDef'; did you mean 'BSRR'?
[ERROR] .\mbed-os\targets\TARGET_STM\gpio_api.c:162:27: error: no member named 'BRR' in 'GPIO_TypeDef'; did you mean 'BSRR'?
    obj->reg_clr = &gpio->BRR;
                          ^~~
                          BSRR
./mbed-os/targets/TARGET_STM/TARGET_STM32L1/STM32Cube_FW/CMSIS/stm32l151xc.h:339:17: note: 'BSRR' declared here
  __IO uint32_t BSRR;         /*!< GPIO port bit set/reset registerBSRR,        Address offset: 0x18      */
                ^
1 error generated.

[mbed] ERROR: "C:\Python27\python.exe" returned error.
       Code: 1
       Path: "C:\Code\SmartSentry\mbed-os-example-blinky"
       Command: "C:\Python27\python.exe -u C:\Code\SmartSentry\mbed-os-example-blinky\mbed-os\tools\make.py -t arm -m xdot_l151cc --profile DEBUG --source . --build .\BUILD\XDOT_L151CC\ARM-DEBUG"
       Tip: You could retry the last command with "-v" flag for verbose output
---

[0xc0170]

I started CI although the failure above should be looked at

[mbed-ci]

Jenkins CI Test : ❌ FAILED

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

CLICK for Detailed Summary

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

[jeromecoutant]

@chrissnow
I am checking STMicroelectronics/STM32CubeL1#8

Pull request has been modified.

[jeromecoutant]

@0xc0170 could you restart CI ?
Thx

[0xc0170]

CI restarted

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

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

CLICK for Detailed Summary

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