Add hardware CRC support to STM32G4

[augustozanellato]

Summary of changes

Added support for hardware CRC calculation on STM32G4 based targets

Impact of changes

Migration actions required

Documentation

I think no documentation update is needed.

---

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

Not sure where/how tests should be added.

---

Reviewers

---

[jeromecoutant]

target	platform_name	test suite	result	elapsed_time (sec)	copy_method
NUCLEO_G474RE-ARMC6	NUCLEO_G474RE	drivers-tests-tests-mbed_drivers-crc	OK	12.75	default
NUCLEO_G474RE-ARMC6	NUCLEO_G474RE	hal-tests-tests-mbed_hal-crc	OK	12.74	default
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	drivers-tests-tests-mbed_drivers-crc	OK	14.99	default
NUCLEO_G431RB-ARMC6	NUCLEO_G431RB	hal-tests-tests-mbed_hal-crc	OK	16.39	default

[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_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-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-greentea-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	❌

[augustozanellato]

@jeromecoutant thanks for the review. I’m mentioning you directly because I saw you work for ST.
I have a nucleo-g491re that advertises itself to the host computer as Mbed compatible (MSD contains a MBED.htm that redirects to https://os.mbed.com/platforms/ST-NUCLEO-G491RE/) but there isn’t an official target.
I got it to work by more or less copying stuff from the nucleo-g474re target. Would a PR here be reviewed/eventually accepted for that?

[jeromecoutant]

@0xc0170 failed tests are strange, maybe you could restart ?

[jeromecoutant]

@augustozanellato I will be pleased to review a PR to introduce NUCLEO-G491RE !

As ex, you can have a look on #15343 or #15199

[0xc0170]

CI restarted

[0xc0170]

There was anothe breakage in CI earier this week, I restarted CI again.

[mbed-ci]

Jenkins CI Test : ✔️ SUCCESS

Build Number: 4 | 🔒 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	✔️