Hi Raymond,

We have changes on GitHub with the below PR from psa-arch-tests side. https://github.com/ARM-software/psa-arch-tests/pull/184

One thing to bring to your notice is that the changes done for the test test_c050(api_tests/dev_apis/crypto) require proper nvram in place to work across system reset.

This test makes use of tf-m system reset function (tfm_platform_system_reset) to issue system reset and I believe it works for PSoC64 too.

Regards, Vinay Kumar Kotegowder

________________________________ From: Raymond Ngun Raymond.Ngun@cypress.com Sent: Wednesday, April 29, 2020 9:01 PM To: Vinay Kumar Kotegowder VinayKumar.Kotegowder@arm.com; David Hu via TF-M tf-m@lists.trustedfirmware.org; Jamie Fox Jamie.Fox@arm.com; David Hu David.Hu@arm.com Subject: RE: PSA Crypto failure with addition of persistent keys

Hi David and Vinay,

Apologies I didn’t clarify this is with the psa-arch-test.

Vinay, I didn’t see anything pushed to psa-arch-test. Is that still on it’s way. With that said, I do see this problem on the Musca-B1 as well.

Thank you,

Ray

From: Vinay Kumar Kotegowder VinayKumar.Kotegowder@arm.com Sent: Sunday, April 26, 2020 8:32 PM To: David Hu via TF-M tf-m@lists.trustedfirmware.org; Raymond Ngun Raymond.Ngun@cypress.com; Jamie Fox Jamie.Fox@arm.com; David Hu David.Hu@arm.com Subject: Re: PSA Crypto failure with addition of persistent keys

Hi Raymond,

There are some changes required for PSoC64 target with the recent changes from Jamie on persistent key support for test_c050 (api-tests/dev_apis/crypto/test_c050).

I will be pushing changes to GitHub today.

You could try them and let us know if you are still facing problem.

Regards,

Vinay

________________________________

From: TF-M <tf-m-bounces@lists.trustedfirmware.orgmailto:tf-m-bounces@lists.trustedfirmware.org> on behalf of David Hu via TF-M <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Sent: Monday, April 27, 2020 8:03 AM To: Raymond Ngun <Raymond.Ngun@cypress.commailto:Raymond.Ngun@cypress.com>; Jamie Fox <Jamie.Fox@arm.commailto:Jamie.Fox@arm.com> Cc: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org <tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] PSA Crypto failure with addition of persistent keys

Hi Raymond,

Sorry for the trouble. Sorry that I cannot find a Crypto test case with index 250.

Could you please share more details and error logs of this test case?

Best regards,

Hu Ziji

From: TF-M <tf-m-bounces@lists.trustedfirmware.orgmailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Raymond Ngun via TF-M Sent: Monday, April 27, 2020 10:26 AM To: tf-m@lists.trustedfirmware.orgmailto:tf-m@lists.trustedfirmware.org; Jamie Fox <Jamie.Fox@arm.commailto:Jamie.Fox@arm.com> Subject: [TF-M] PSA Crypto failure with addition of persistent keys

Hi Jamie,

With the addition of persistent key support, we have seen the PSA Crypto test hang at test 250. Although we originally saw this with PSoC64, I was able to reproduce this problem on a Musca-B1. Can you please have a look please? Note that the behavior is not always the same. I have 2x Musca-B1 boards and they both failed the first time I ran the PSA Crypto test suite. However, they both did not freeze on a 2nd run. Possibly a stack issue such that the behavior is dependent on what is in stack.

Thank you,

Ray

This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

This message and any attachments may contain confidential information from Cypress or its subsidiaries. If it has been received in error, please advise the sender and immediately delete this message.