NUCLEO_F303ZE: Enable all I2C instances

[jeromecoutant]

Description

A few sentences describing the overall goals of the pull request's commits.

Status

READY

OS2 and OS5 tests are still all OK

[bridadan]

@jeromecoutant Can you provide some details on the potential consequence of this change? I see quite a few warning comments on the lines that were uncommented.

[jeromecoutant]

If user is using USB, he will not be able to use I2C2 and I2C3 instances (HW connection).
But if user doesn't use USB, he should be able to use multiple I2C instances.

[bridadan]

Do we need to add any additional warnings to this target's page on the mbed site? Would this cause any existing applications to fail?

[sg-]

/morph test

[sg-]

@mbed-bot: TEST

HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

[mbed-bot]

Result: SUCCESS

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

/morph test

Output

mbed Build Number: 0

All builds and test passed!

[mbed-bot]

[Build 1032]
FAILURE: Something went wrong when building and testing.

[sg-]

Failure unrelated.

Scan: TARGET_NUMAKER_PFM_NUC472
Compile [  1.7%]: aes_alt.c
[Error] aes_alt.c@25,0:  #5: cannot open source input file "mbedtls/config.h": No such file or directory
"C:\Jenkins\workspace\mbed-2-build-library\targets\TARGET_NUVOTON\TARGET_NUC472\crypto\aes\aes_alt.c", line 25: Error:  #5: cannot open source input file "mbedtls/config.h": No such file or directory
C:\Jenkins\workspace\mbed-2-build-library\targets\TARGET_NUVOTON\TARGET_NUC472\crypto\aes\aes_alt.c: 0 warnings, 1 error