Mbed-os: Incorrect behavior working with Crypto HW accelerator on STM32F439xI chipset

[alekshex]

Description

Incorrect behavior working with Crypto HW accelerator on STM32F439xI chipset.
initially detected on UBLOX_EVK_ODIN_W2 board.
Running compliance test suite fails in test037 using PSA_ALG_CBC_PKCS7 algorithm
Attestation test also fails when SHA in HW is enabled.

Toolchains: GCC ARM, IAR8
Target platform: UBLOX_EVK_ODIN_W2

Steps to reproduce:

• git clone [email protected]:ARMmbed/mbed-os-psa-compliance-tests-example.git
• cd mbed-os-psa-compliance-tests-example
• mbed deploy

Compile and run latest mbedOS with the following command:

• mbed test -m UBLOX_EVK_ODIN_W2 -t GCC_ARM -n *psa*compliance* -DMBEDTLS_USER_CONFIG_FILE=\"../comp_config.h\" -v

Expected result:
components-target_psa-tests-compliance_crypto-test_c037 test should FAIL
components-target_psa-tests-compliance_attestation-test_a001 test should FAIL

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug

[0xc0170]

cc @ARMmbed/team-st-mcd @ARMmbed/team-ublox

[jeromecoutant]

Hi @ARMmbed/team-ublox

Is it possible to check #12747 (#10088 has been reverted) ?

Thx

[aqib-ublox]

@jeromecoutant Yes we verified solution working on master branch but we have paused ODIN_W2 migration to Mbed6. @MarceloSalazar can u find feasibility of supporting it for mbed 5.15 as well because we are getting merge conflicts with 5.15. is it possible?
cc @qasim-ublox

[0xc0170]

what merge conflicts? 5.15 is a different base. In case something from PR 12747 is needed in 5.15, it needs to be backported (cherry picked to 5.15 branch) - conflicts might appear due to the diverged branches.

[jeromecoutant]

@0xc0170 @MarceloSalazar
Please close this issue as #12747 is now merged.

In mbed-os-5.15 branch, you have to backport #12626 first before #12747

[ciarmcom]

@avolinski thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.