K64F: Add MMCAU driver needed for mbedtls

[mmahadevan108]

Description

Include the MMCAU K64 SDK driver needed to supporting mbedtls

Status

**READY

[mmahadevan108]

@sg- @0xc0170 @RonEld

[mmahadevan108]

cc @MartinLatal

[RonEld]

All the mbedtls related files should be in the features target, and not the mbed-os target (except entropy), so these files should be added to : features/mbedtls/targets/TARGET_Freescale/TARGET_MCUXpresso_MCUS/TARGET_MCU_K64F/drivers/ and not targets/TARGET_Freescale/TARGET_MCUXpresso_MCUS/TARGET_MCU_K64F/drivers/

[mmahadevan108]

Thank you. All the drivers associated with the hardware IP blocks are placed in the HAL drivers folder.

[mmahadevan108]

Renamed the ARM library file to use the .ar extension.

[0xc0170]

I restarted travis. Failed for not related change, lets review again once it finishes.

All the mbedtls related files should be in the features target, and not the mbed-os target (except entropy), so these files should be added to : features/mbedtls/targets/TARGET_Freescale/TARGET_MCUXpresso_MCUS/TARGET_MCU_K64F/drivers/ and not targets/TARGET_Freescale/TARGET_MCUXpresso_MCUS/TARGET_MCU_K64F/drivers/

As these files are driver files, and those reside in hal under MCUXpresso folder, all good with this PR? Please review (there's one more PR for another targets).

[RonEld]

Personally I would put the mbedtls related files in the mbedtls targets folder, but since all of the driver files are in the HAL I would keep them here as well

[0xc0170]

retest uvisor

[bridadan]

/morph test-nightly

[mbed-bot]

Result: FAILURE

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

/morph test-nightly

Output

mbed Build Number: 1830

Test failed!

[gilles-peskine-arm]

Looks fine to me. Of course I did not review the binaries.

[daniel-cesarini-tridonic-com]

@sg- @mmahadevan108 will the outcome of this workshop eventually make it into master?
We would be interested in this support for the hardware acceleration for security primitives in the K64 to come with mbed-os + mbedtls.
So, shall we expect this support anytime soon in mbed-os master, or shall we somehow pick the original branch and make it work on our own (not really preferred approach currently)?

FYI: @MarceloSalazar

Organization internal: @markus-becker-tridonic-com @andreas-myka-tridonic-com