Add crash RAM to STM32F412xG

[boraozgen]

Summary of changes

Added crash RAM to STM32F412xG. Copied the same parts from STM32F411xE. The linker script is now identical to STM32F411xE. Tested on custom board with STM32F412CG.

Impact of changes

Migration actions required

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

[X] 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

---

Reviewers

---

[ciarmcom]

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

[boraozgen]

@jeromecoutant

[jeromecoutant]

It would be good to align ARM and IAR files ?
Thx

[boraozgen]

@jeromecoutant

The IAR linker script is considerably different from the F411RE, therefore I cannot just copy the related part. Besides I do not use the Mbed Studio therefore I cannot test it on the ARM compiler. Can you/someone else deal with this? Should be simple for someone who knows the IAR syntax.

[jeromecoutant]

The IAR linker script is considerably different from the F411RE, therefore I cannot just copy the related part.

IAR is no more mandatory in MBED. So align GCC and ARMC6 linker scripts, and I will be OK :-)

[mergify]

This PR cannot be merged due to conflicts. Please rebase to resolve them.

[boraozgen]

I applied the differences in F411RE ARMC script to F412xG. It looks simple and should not cause problems, but as I said I cannot test it as I do not use ARMC.

[jeromecoutant]

See my branch:
https://github.com/jeromecoutant/mbed/tree/REVIEW_13723
for full alignment between both families

Test platform-tests-tests-mbed_platform-crash_reporting
OK with NUCLEO_F412ZG and NUCLEO_F411RE for GCC, ARMC6, and IAR

Thx

[adbridge]

This is target specific so should be a patch rather than a feature - will fix

[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-GCC_ARM	❌
jenkins-ci/mbed-os-ci_build-ARM	❌

[0xc0170]

CI restarted, internal error

[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_build-GCC_ARM	✔️
jenkins-ci/mbed-os-ci_build-ARM	✔️
jenkins-ci/mbed-os-ci_dynamic-memory-usage	✔️
jenkins-ci/mbed-os-ci_greentea-test	✔️
jenkins-ci/mbed-os-ci_cloud-client-pytest	✔️