Hello,
The next Technical Forum is planned on Thursday, August 20 at 6:00-07:00 UTC (Asia time zone).
Please reply on this email with your proposals for agenda topics.
Recording and slides of previous meetings are here:
https://www.trustedfirmware.org/meetings/tf-m-technical-forum/
Best regards,
Anton Komlev
Hello,
This is a kind reminder on TF-M repository change below.
The old URL will be alive for the following 3 months before depreciation.
Regards,
Anton
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M
Sent: 14 May 2020 15:32
To: tf-m(a)lists.trustedfirmware.org
Cc: nd <nd(a)arm.com>
Subject: [TF-M] TF-M repository restructure
Hello,
Let me announce the changes in TF-M project repository structure. To allow project grow up in a more organized way the existing codebase will be split on multiple repositories and placed under TF-M folder. This is the similar structure as all other projects have in git.trustedfirmware.org<https://git.trustedfirmware.org>.
This weekend TF-M git repository will be moved
from https://git.trustedfirmware.org/trusted-firmware-m.git
to https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git
The original URL will be supported for some time (as a link to the new one) giving time for adjustment. Current plan is to keep the redirection for 6 months but let me know please, if it makes any conflict and another depreciation period is better.
Best regards,
Anton Komlev
Hi Everyone
The following patch updates the crypto service in TF-M to use the latest mbedTLS tag v2.23.0. All reviews for the same will be much appreciated.
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5252/1
With this update, additional PSA APIs psa_hash_compute() and psa_hash_compare() are now supported.
There is also another patch for platforms to update the ITS_MAX_ASSET_SIZE when testing with PSA Crypto API compliance test as one of the tests require a larger size: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5253/1 . Could the platform owners review the same and let me know whether the size changes are OK ?
With the above patches, the API compliance remains the same as v1.0 Beta 3 and the PSA Crypto compliance test suite gives the below results (as tested on AN521) :
************ Crypto Suite Report **********
TOTAL TESTS : 61
TOTAL PASSED : 42
TOTAL SIM ERROR : 0
TOTAL FAILED : 17
TOTAL SKIPPED : 2
******************************************
Best Regards
Soby Mathew
Hello,
The agenda for this forum:
1. Musca-B1 Secure Enclave solution
2. Platform specific vs common scatter/link scripts
3. Any Other Business
See you,
Anton Komlev
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Mark Horvath via TF-M
Sent: 03 August 2020 12:13
To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org>
Subject: Re: [TF-M] TF-M Technical Forum call - August 6
Hi,
I would like to talk a little about the Musca-B1 Secure Enclave solution
I plan it to 15 minutes +questions.
Best regards,
Mark
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Anton Komlev via TF-M
Sent: 28 July 2020 19:24
To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>>
Cc: nd <nd(a)arm.com<mailto:nd@arm.com>>
Subject: [TF-M] TF-M Technical Forum call - August 6
Hello,
The next Technical Forum is planned on Thursday, August 6 at 15:00-16:00 UTC (US time zone).
Please reply on this email with your proposals for agenda topics.
Best regards,
Anton Komlev
Hi all,
There are many differences in linker scripts between each platform. Using a common_s.sct/ld makes it too complicated.
And at the same time, in order to achieve isolation level 3, the position of the sessions in scatter and linker script file needs to be adjusted.
The common linker scripts would be more complicated with isolation L3.
So I would like to propose to have dedicated linker scripts for platforms with enough differential arrangements.
What's your opinion on this?
Best regards,
Shawn
Hi Thomas
>From the log, Your folder seems to indicate trusted-firmware-m and you are trying to push to tf-m-tests. The trusted-firmware-m.git<https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/> and tf-m-tests.git<https://git.trustedfirmware.org/TF-M/tf-m-tests.git/> do not have a common ancestor. You might need to create a patch file and then apply to the tests repo manually I think.
Best Regards
Soby Mathew
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M
Sent: 03 August 2020 15:43
To: tf-m(a)lists.trustedfirmware.org
Subject: [TF-M] Fail pushing, no common ancestry
I've tried fixing a minor issue in one of my already pushed changes, but for some reason I get an error.
To avoid anything I've done today I tried to push the local repo with no changes at all since I pushed it last, and I'm still getting an issue, and it seems related to tf-m-tests
---
PS C:\Users\thomasto\Projects\tf-m1\trusted-firmware-m> git push ssh://review.trustedfirmware.org/TF-M/tf-m-tests.git HEAD:refs/for/master
Enumerating objects: 24547, done.
Counting objects: 100% (24547/24547), done.
Delta compression using up to 4 threads
Compressing objects: 100% (8849/8849), done.
Writing objects: 100% (24547/24547), 12.14 MiB | 1.07 MiB/s, done.
Total 24547 (delta 17058), reused 21946 (delta 15111), pack-reused 0
remote: Resolving deltas: 100% (17058/17058)
remote: Processing changes: refs: 1, done
To ssh://review.trustedfirmware.org/TF-M/tf-m-tests.git
! [remote rejected] HEAD -> refs/for/master (no common ancestry)
error: failed to push some refs to 'ssh://review.trustedfirmware.org/TF-M/tf-m-tests.git'
---
What am I missing?
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(a)iar.com<mailto:thomas.tornblom@iar.com> Website: www.iar.com<http://www.iar.com>
Twitter: www.twitter.com/iarsystems<http://www.twitter.com/iarsystems>
I've tried fixing a minor issue in one of my already pushed changes, but
for some reason I get an error.
To avoid anything I've done today I tried to push the local repo with no
changes at all since I pushed it last, and I'm still getting an issue,
and it seems related to tf-m-tests
---
PS C:\Users\thomasto\Projects\tf-m1\trusted-firmware-m> git push
ssh://review.trustedfirmware.org/TF-M/tf-m-tests.git HEAD:refs/for/master
Enumerating objects: 24547, done.
Counting objects: 100% (24547/24547), done.
Delta compression using up to 4 threads
Compressing objects: 100% (8849/8849), done.
Writing objects: 100% (24547/24547), 12.14 MiB | 1.07 MiB/s, done.
Total 24547 (delta 17058), reused 21946 (delta 15111), pack-reused 0
remote: Resolving deltas: 100% (17058/17058)
remote: Processing changes: refs: 1, done
To ssh://review.trustedfirmware.org/TF-M/tf-m-tests.git
! [remote rejected] HEAD -> refs/for/master (no common ancestry)
error: failed to push some refs to
'ssh://review.trustedfirmware.org/TF-M/tf-m-tests.git'
---
What am I missing?
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(a)iar.com <mailto:thomas.tornblom@iar.com>
Website: www.iar.com <http://www.iar.com>
Twitter: www.twitter.com/iarsystems <http://www.twitter.com/iarsystems>
Hi,
I would like to talk a little about the Musca-B1 Secure Enclave solution
I plan it to 15 minutes +questions.
Best regards,
Mark
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M
Sent: 28 July 2020 19:24
To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org>
Cc: nd <nd(a)arm.com>
Subject: [TF-M] TF-M Technical Forum call - August 6
Hello,
The next Technical Forum is planned on Thursday, August 6 at 15:00-16:00 UTC (US time zone).
Please reply on this email with your proposals for agenda topics.
Best regards,
Anton Komlev
Hi Everyone
Just a reminder, I plan to merge this proposal by end of this week.
Best Regards
Soby Mathew
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Soby Mathew via TF-M
Sent: 16 July 2020 14:00
To: TF-M mailing list <tf-m(a)lists.trustedfirmware.org>
Subject: [TF-M] Process for deprecating and removing platforms
Hi Everyone,
The document in tf.org defines the different "Platform Support Life Cycle":
https://developer.trustedfirmware.org/w/collaboration/project-maintenance-p…
Although a platform can be implicitly in deprecated state due to lack of support or maintenance, a process to explicitly declare a platform as deprecated with the intention to remove it in future is needed as well. So I have attempted to define a process as described here:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4962/1/docs/…
Comments welcome.
Best Regards
Soby Mathew
Hi all,
Thanks a lot for the reviews and comments on Profile Medium patches. I'd like to merge those patches by this Thursday if no further critical issue.
Please access https://review.trustedfirmware.org/q/topic:%22profile-m-config%22+(status:o… if you are interested to take another look.
Thank you.
Best regards,
Hu Ziji
