Update STM32F7 cube from v1.6.0 to v1.7.0

[adustm]

Description

This is an update of the STM32 F7 STM32 cube (SDK)

CMSIS up to date
STM32F7 HAL v1.2.0 => v1.2.2
Detailed information in targets/TARGET_STM/TARGET_STM32F7/device/Release_Notes_stm32f7xx_hal.html

Status

READY

Tests

OS2 and OS5 tests have been checked with ARM, IAR and GCC for the 5 ST available targets

[AnotherButler]

@adustm Thanks for the PR.

Also, we recommend our contributors follow Chris Beam’s seven rules of great commit messages to keep the commit history clear. To match this format, please change your subject line to the imperative mood. We recommend changing it to "Update STM32F7 cube from v1.6.0 to v1.7.0". Thanks for your contributions.

[theotherjimmy]

@adustm Please note that PR titles are used in the release notes. I recommend updating the PR title to match the commit message @AnotherButler suggested.

[adustm]

Thanks @0xc0170 for the title change
Cheers

[theotherjimmy]

/morph test-nightly

[mbed-bot]

Result: FAILURE

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 640

Test failed!

[adustm]

Hi,
another morph test failure, with another board build failure... I think it's not related to this PR.
Either somebody solves the morph test unstability, or somebody should accept to bypass the broken morph test...

Kind regards
Armelle

[0xc0170]

@adustm Yes, will retrigger this job here.
There's PR opened to fix the host tests but still fails for one platform that is being looked at the moment, that is a real target failure.

/morph test-nightly

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test-nightly

Output

mbed Build Number: 664

All builds and test passed!

[theotherjimmy]

retest uvisor