- TF-M - lists.trustedfirmware.org

Proposal to separate SCT/LD into each platform folder

by Shawn Shan

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

4 years, 8 months

1
0
0 0

Re: [TF-M] Fail pushing, no common ancestry

by Soby Mathew

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>

4 years, 8 months

2
1
0 0

Fail pushing, no common ancestry

by Thomas Törnblom

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>

4 years, 8 months

1
0
0 0

Re: [TF-M] TF-M Technical Forum call - August 6

by Mark Horvath

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

4 years, 8 months

1
0
0 0

Re: [TF-M] Process for deprecating and removing platforms

by Soby Mathew

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

4 years, 8 months

1
0
0 0

Call for final review of Profile Medium patches

by David Hu

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

4 years, 8 months

1
0
0 0

TF-M Technical Forum call - August 6

by Anton Komlev

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

4 years, 8 months

1
0
0 0

Re: [TF-M] Ninja builds broken

by Ken Liu

Looks like some mistake happened in the cmake file which causes trouble under windows. I have created a patch for this: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5100 Could you check if this would help? Thanks. BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Tuesday, July 28, 2020 12:33 PM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Ninja builds broken Looks like Ninja builds are now broken for some targets. AN519, AN521, AN539, and possibly others, fails to link tfm_ns.axf with the following error: --- Usage: wrapper.py [OPTIONS] INFILE OUTFILE Try "wrapper.py --help" for help. Error: Got unexpected extra argument (C:/Users/thomasto/Projects/tf-m1/trusted-firmware-m/cmake_build_gcc/tfm_s_signed.bin) ninja: build stopped: subcommand failed. --- 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>

4 years, 8 months

1
0
0 0

Ninja builds broken

by Thomas Törnblom

Looks like Ninja builds are now broken for some targets. AN519, AN521, AN539, and possibly others, fails to link tfm_ns.axf with the following error: --- Usage: wrapper.py [OPTIONS] INFILE OUTFILE Try "wrapper.py --help" for help. Error: Got unexpected extra argument (C:/Users/thomasto/Projects/tf-m1/trusted-firmware-m/cmake_build_gcc/tfm_s_signed.bin) ninja: build stopped: subcommand failed. --- 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>

4 years, 8 months

1
0
0 0

Invitation: TF-M Tech Forum @ Thu 17 Sep 2020 07:00 - 08:00 (BST) (tf-m@lists.trustedfirmware.org)

by Bill Fletcher

You have been invited to the following event. Title: TF-M Tech Forum About TF-M Tech forum:This is an open forum for anyone to participate and it is not restricted to Trusted Firmware project members. It will operate under the guidance of the TF TSC.Feel free to forward it to colleagues.Details of previous meetings are here: https://www.trustedfirmware.org/meetings/tf-m-technical-forum/Tr… Firmware is inviting you to a scheduled Zoom meeting.Join Zoom Meetinghttps://zoom.us/j/9159704974Meeting ID: 915 970 4974One tap mobile+16465588656,,9159704974# US (New York)+16699009128,,9159704974# US (San Jose)Dial by your location        +1 646 558 8656 US (New York)        +1 669 900 9128 US (San Jose)        877 853 5247 US Toll-free        888 788 0099 US Toll-freeMeeting ID: 915 970 4974Find your local number: https://zoom.us/u/ad27hc6t7h   When: Thu 17 Sep 2020 07:00 – 08:00 United Kingdom Time Calendar: tf-m(a)lists.trustedfirmware.org Who: * Bill Fletcher- creator * tf-m(a)lists.trustedfirmware.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=NjZuNjVnbmNmZG1qZ24xa… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account tf-m(a)lists.trustedfirmware.org because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively, you can sign up for a Google Account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organiser and be added to the guest list, invite others regardless of their own invitation status or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

4 years, 8 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

TF-M