Page MenuHomePhabricator

Failing PSA Compliance Crypto test suite - ARM_MUSCA_B1 target
Open, Needs TriagePublic

Description

We see a failure for this test suite where one of the tests set the hardware to boot again

TEST: 250 | DESCRIPTION: Testing crypto key management APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_open_key 16 Byte AES
[Sec Thread] Secure image initializing!
Booting TFM v1.1
Non-Secure system starting...

TEST: 250 | DESCRIPTION: Testing crypto key management APIs
[Info] Executing tests from non-secure
[Check 1] Test psa_open_key 16 Byte AES
[Check 2] Test psa_open_key 24 Byte AES
[Sec Thread] Secure image initializing!
Booting TFM v1.1
Non-Secure system starting...

TEST: 250 | DESCRIPTION: Testing crypto key management APIs
[Info] Executing tests from non-secure
[Check 2] Test psa_open_key 24 Byte AES
[Check 3] Test psa_open_key 32 Byte AES
[Sec Thread] Secure image initializing!
Booting TFM v1.1
Non-Secure system starting...

TEST: 250 | DESCRIPTION: Testing crypto key management APIs
[Info] Executing tests from non-secure
[Check 3] Test psa_open_key 32 Byte AE
[Check 4] Test psa_open_key 2048 RSA public key
[Sec Thread] Secure image initializing!
Booting TFM v1.1

This is on commit

commit a6b336c1509fd5f5522450e3cec0fcd6c060f9c8 (HEAD -> tfm-base--TF-Mv1.1, tag: TF-Mv1.1)
Author: Mate Toth-Pal <mate.toth-pal@arm.com>
Date:   Thu Jul 9 11:46:03 2020 +0200

PSA Compliance commit

commit 1f96094734897674fa907fba2050bc52e1b3d0fe (origin/master, origin/HEAD)
Merge: f1b732c 61968e3
Author: Vinay Kumar Kotegowder <vinaykumar.kotegowder@arm.com>
Date:   Fri Jun 26 11:32:55 2020 +0530

Event Timeline

jf549 added a subscriber: jf549.Wed, Jul 22, 8:53 PM

Looks like same cause as T696