Adding STM32_F439 as a new MTB target

[ashok-rao]

Description

Adding STM32_F439 MCU only (on a Module Carrier Board) as a new MTB target. This will be used as a base MCU for upcoming cellular MODEMs and other connectivity Module Expansion Boards (MEB).

Greentea logs attached below:
MTB_STM32_F439_GT_Logs_ARMCC_Pass.txt
MTB_STM32_F439_GT_Logs_GCC_Pass.txt
MTB_STM32_F439_GT_Logs_IAR_Pass.txt

Pull request type

[ ] Fix
[ ] Refactor
[x] Target update
[ ] Functionality change
[ ] Docs update
[ ] Test update
[ ] Breaking change

Reviewers

@0xc0170 @jeromecoutant @cmonr

Release Notes

[ciarmcom]

@ashok-rao, thank you for your changes.
@cmonr @0xc0170 @screamerbg @ARMmbed/mbed-os-maintainers please review.

[ashok-rao]

Quick note: For GT tests, I've used IAR 8.32.1 & ARMC5.

[0xc0170]

ARMC5 - had your own config to override it ? This target would support ARCM6 by default (inherits it).

[jeromecoutant]

Maybe description needs to be updated: "Adding STM32_L475" ?

[0xc0170]

Maybe description needs to be updated: "Adding STM32_L475" ?

Files are being added to TARGET_STM32F439xI/TARGET_MTB_STM32_F439 and all its references. But the comment above is STM32_L475 - good catch. @ashok-rao Please confirm

[ashok-rao]

@jeromecoutant @0xc0170 : Description error, now corrected. Thanks, good catch!

[ashok-rao]

@jeromecoutant : General question on clock configuration, do you use STM32CubeMX to generate the clock configs or are these done manually for each of the targets?

[jeromecoutant]

do you use STM32CubeMX to generate the clock configs or are these done manually for each of the targets?

Yes, I am using CubeMX tool to check if there are no "red" values for all prescalers values.
I am also using CubeMx to build the peripheral pins files (see #9394)

[ashok-rao]

• Review comments incorporated.
• Adding GT logs for ARMC6

MTB_STM32_F439_GT_Logs_ARMC6_Pass.txt

[cmonr]

CI started

[mbed-ci]

Test run: SUCCESS

Summary: 13 of 13 test jobs passed
Build number : 1
Build artifacts