Hi Thomas,

Thanks your mail.

For your 1st question. There is indeed a problem to build the PSA arch crypto test on the Musca_a board for the RAM size is too small. I suggest you split the crypto tests into different test images on the Musca_a board.

For the 2nd question, I only test that on FVP AN521 but never met this problem. We will test that on the MPS2 AN521 board soon to check if it is a real problem. If yes, we will try to fix that quickly.

Thanks,

Edison

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M
Sent: Wednesday, March 18, 2020 9:38 PM
To: tf-m@lists.trustedfirmware.org
Subject: [TF-M] psa-arch-tests console baud rate

Triggered by Rays mail on slow RSA key pair generation, I built and tried to run the tests, but ran into a couple of issues:

1) I attempted to build it for the Musca A, but apparently that doesn't have enough RAM to run these tests

2) Switching to an MPS2+ with AN521 configuration I see that the baud rate on the UART appears wrong when running the tests.

mcuboot produces correct messages at 115200 bps, as does the normal ConfigRegression* tests, but the ConfigPsaApiTest* appears to produce just garbage.

Is there a setting I need to set to get any useful data on the terminal when running the ConfigPsaApiTests?

Cheers,
Thomas

--

Thomas T�rnblom, Product Engineer
IAR Systems AB
Box 23051, Strandbodgatan 1
SE-750 23 Uppsala, SWEDEN
Mobile: +46 76 180 17 80 Fax: +46 18 16 78 01
E-mail: thomas.tornblom@iar.com Website: www.iar.com
Twitter: www.twitter.com/iarsystems