Add MBEDTLS_ENTROPY_NV_SEED to NUCLEO_F411RE to fix the build

[orenc17]

Description

Add MBEDTLS_ENTROPY_NV_SEED to support psa_crypto on NUCLEO_F411RE

The platform does not have TRNG and must have a source of entropy to use psa-crypto

Pull request type

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

Reviewers

[0xc0170]

Any other target that was fixed in #9605 needs this or only nucleo affected?

[orenc17]

other target that

No, all the other have TRNG

[0xc0170]

Ci started

[0xc0170]

This fixes nightly client breakage from the last run

[mbed-ci]

Test run: SUCCESS

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

[0xc0170]

@ARMmbed/team-st-mcd Please review. We would like to have this fix on master today to resolve nightly failure

[Patater]

This may fix the build failure, but does the device work properly at run-time? Can a fresh F411 successfully initialize and use crypto functionality?

I'm OK with this PR as-is since it's important to fix the nightly build, but more follow up is needed as to how we want to handle entropy with F411 targets.

[deepikabhavnani]

I got build failure for Nucleo_F411RE in PR #9571 is this related? It was not for nightly build though

http://mbed-os-ci.s3-website-eu-west-1.amazonaws.com/?prefix=jenkins-ci/artifacts/9571/5/build-ARM/FAIL/NUCLEO_F411RE/

./features/device_key/source/DeviceKey.cpp
[Error] check_config.h@502,0:  #35: #error directive: "MBEDTLS_PSA_CRYPTO_C defined, but not all prerequisites"
[DEBUG] Return: 1
[DEBUG] Output: "./features/mbedtls/inc/mbedtls/check_config.h", line 502: Error:  #35: #error directive: "MBEDTLS_PSA_CRYPTO_C defined, but not all prerequisites"
[DEBUG] Output: ./features/device_key/source/DeviceKey.cpp: 0 warnings, 1 error
Failed to build library

[0xc0170]

Yes related, this needs to get in asap.

[cmonr]

@ARMmbed/mbed-os-psa Thoughts about #9677 (comment) ?

[orenc17]

@cmonr @Patater We do not know, or have the man power to research that

[0xc0170]

@cmonr @Patater We do not know, or have the man power to research that

So either we make sure this works or we revert also psa additions that caused this build failures

[0xc0170]

Fix went to 5.11.5 so this one as well

[0xc0170]

Moved to 5.12 due to failures with 5.11 branch