STM32L1: enable USBDEVICE

[chrJost]

Summary of changes

Enables the USBDEVICE for STM32L1 devices.

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]

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

[chrJost]

So far this is just a test pull request, as I don't have a STM32L1 test board. I am waiting for a response from the forum before moving forward:
https://forums.mbed.com/t/usb-device-support-on-stm32l1-is-there-any-chance/12464

[rudolfdobias]

Tested on NUCLEO_L152RE, seems everything works OK,

[chrJost]

There might be some issues with the XDOT_L151CC board, and maybe some other boards, depending on the generator for the main clock. Unfortunately I don't have these boards for testing. I therefore excluded at least the XDOT board from using the USBDEVICE.

[jeromecoutant]

I am sorry, but we can't add "USBDEVICE" in the default STM32L1 configuration.
In ARM MBED, "USBDEVICE" doesn't mean that USB device feature is supported,
but means targets has a user USB connector...
You have to add this in you local custom_board.json or mbed_app.json file.

[chrJost]

Sorry, I was not aware the board does not have a USB port.

[0xc0170]

CI started

[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_build-greentea-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-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-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-test	❌
jenkins-ci/mbed-os-ci_greentea-test	❌

[jeromecoutant]

@0xc0170 need to restart ?

[0xc0170]

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-cloud-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-ARM	✔️
jenkins-ci/mbed-os-ci_cmake-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-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-greentea-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-cloud-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-example-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_cmake-example-test	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️