Check CAN DLC length value

[Martyx00]

Summary of changes

Change on how the incoming CAN message DLC field is processed by the STM HAL. Previously, any value up to 0xF was allowed. The updated code limits this to value maximum of 8. Values higher than 8 are only used in CANFD which is not affected by this code change.

Impact of changes

CAN message DLC value can no longer be higher than 8 in standard CAN mode.

Migration actions required

None

Documentation

None

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

---

[jeromecoutant]

Hi
Maybe could you reference here tickets with issue and discussion for this topic ?
Thx

[Martyx00]

#15361

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

[0xc0170]

@jeromecoutant as you already approved previous PR, I'll merge this now.

I am creating generic fix PR now

[0xc0170]

@jeromecoutant can you verify this is required also for Mbed OS 5.15 ? If yes, can you send PR fixing it?