- TF-M - lists.trustedfirmware.org

by Raef Coles

Sorry Thomas - Someday I'll get that IAR license working and stop breaking support every 5 seconds. Thanks for all the hard work and fixes. Patches look good, have reviewed. Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Thomas Törnblom via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 03 November 2020 12:22 To: DeMars, Alan via TF-M Subject: [TF-M] Current IAR support Just when you think you have nailed everfything down, you decide to start with a fresh clone and stuff don't build anymore ;) See: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6766 I have now gone over and tried building everything that has IAR support and here are my findings. I have used the following patches: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/5978 https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6766 I have built for the following targets: musca_a mps2/an519 mps2/an521 mps2/an539 mps2/sse-200_aws mps3/an524 cypress/psoc64 nxp/lpcxpresso55s69 (-DBL2=False as bl2 support appears to have been added recently to this target) stm/nucleo_l552ze_q stm/stm32l562e_dk The mps2/fvp_sse300 requires a compiler with support for the M55, and the IAR compiler with support for this is not yet released. I have run tests on the following targets: musca_a mps2/an519 mps2/an521 mps2/an539 The cypress/psoc64 board I have appears to be obsolete now and I could not flash the secure image to it. The nuvoton/m2351 appears to have IAR support, but it appears untested as it gives linking errors for the bl2 and NS startup files. There are some old and new warnings for type issues and some other minor things. The QCBOR NaN tests are still failing, see: https://developer.trustedfirmware.org/T700 This really is an issue where the ARM ABI and IEEE 754 are incompatible and we are following the ARM ABI. In reality neither ARMCLANG nor GNUARM are fully ARM ABI compliant as they are not ignoring the relevant bits. 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, 5 months

1
0
0 0

Current IAR support

by Thomas Törnblom

Just when you think you have nailed everfything down, you decide to start with a fresh clone and stuff don't build anymore ;) See: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6766 I have now gone over and tried building everything that has IAR support and here are my findings. I have used the following patches: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/5978 https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6766 I have built for the following targets: musca_a mps2/an519 mps2/an521 mps2/an539 mps2/sse-200_aws mps3/an524 cypress/psoc64 nxp/lpcxpresso55s69 (-DBL2=False as bl2 support appears to have been added recently to this target) stm/nucleo_l552ze_q stm/stm32l562e_dk The mps2/fvp_sse300 requires a compiler with support for the M55, and the IAR compiler with support for this is not yet released. I have run tests on the following targets: musca_a mps2/an519 mps2/an521 mps2/an539 The cypress/psoc64 board I have appears to be obsolete now and I could not flash the secure image to it. The nuvoton/m2351 appears to have IAR support, but it appears untested as it gives linking errors for the bl2 and NS startup files. There are some old and new warnings for type issues and some other minor things. The QCBOR NaN tests are still failing, see: https://developer.trustedfirmware.org/T700 This really is an issue where the ARM ABI and IEEE 754 are incompatible and we are following the ARM ABI. In reality neither ARMCLANG nor GNUARM are fully ARM ABI compliant as they are not ignoring the relevant bits. 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, 5 months

1
0
0 0

Re: [TF-M] Integrating a different RTOS in tf-m-test

by Kevin Townsend

Hi Antonio, There is currently an issue filed in Zephyr to add a new sample application that will make it easy to run the PSA API tests via Zephyr, but it we're currently working on finalizing higher priority changes before the 1.2 code freeze later this week: https://github.com/zephyrproject-rtos/zephyr/issues/29476 So, there isn't an 'easy' way to build these tests in Zephyr today out of the box using Zephyr as the RTOS on the NS side, unless you want to have a go at it yourself in the short term while we try to make sure Zephyr is ready for the changes in T-M 1.2. Best regards, Kevin On Mon, 2 Nov 2020 at 10:29, Antonio Ken IANNILLO via TF-M < tf-m(a)lists.trustedfirmware.org> wrote: > Hi all, > > I wanted to use some other RTOS in the NS side while testing tf-m. > > Is there a simple way to use the Zephyr kernel or FreeRTOS in the > tf-m-test (-DTEST_S=ON, -DTEST_NS=ON) instead of the default RTX? > > > > Best, > > -- > > *Antonio Ken Iannillo* > > Research Scientist – SEDAN group > > SnT – Interdisciplinary Centre for Security, Reliability and Trust > > UNIVERSITÉ DU LUXEMBOURG > > > > CAMPUS KIRCHBERG > 29, avenue John F. Kennedy > L-1855 Luxembourg Kirchberg > T +352 46 66 44 9660 > > > > Join the conversation > > News <https://wwwen.uni.lu/snt/news_events> | Twitter > <https://twitter.com/SnT_uni_lu> | Linkedin > <https://www.linkedin.com/school/snt-lu/> > > www.uni.lu/snt > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m >

4 years, 5 months

2
1
0 0

Re: [TF-M] cmake error

by Malcolm Fernandes

I've verified that reverting the tf-m-tests patch fixes the build failures that Chris outlined. Cheers, Mal On Mon, Nov 2, 2020 at 6:16 PM David Hu via TF-M < tf-m(a)lists.trustedfirmware.org> wrote: > Hi Chris, > > > > Sorry for the build failure. A patch is merged into tf-m-tests but its > peer ones in TF-M haven’t been approved yet. > > I have temporarily reverted that tf-m-tests patch. Please have another try. > > > > Best regards, > > Hu Ziji > > > > *From:* TF-M <tf-m-bounces(a)lists.trustedfirmware.org> * On Behalf Of *Christopher > Brand via TF-M > *Sent:* Tuesday, November 3, 2020 1:54 AM > *To:* tf-m(a)lists.trustedfirmware.org > *Subject:* [TF-M] cmake error > > > > I just fetched the latest master > (1655ef5120e99c62782575d0a8b3707ebfc2148e), and I’m now getting a cmake > error: > > $ cmake -S . -B build_GNUARM_Relwithdebinfo '-GUnix Makefiles' > -DTFM_PLATFORM=cypress/psoc64 -DCMAKE_TOOLCHAIN_FILE=toolchain_GNUARM.cmake > -DCMAKE_BUILD_TYPE=Relwithdebinfo -DTEST_NS=ON -DTEST_S=ON -DTFM_IRQ_TEST=ON > > […] > > CMake Error at > build_GNUARM_Relwithdebinfo/lib/ext/tfm_test_repo-src/app/CMakeLists.txt:17 > (tfm_toolchain_reload_compiler): > > Unknown CMake command "tfm_toolchain_reload_compiler". > > > > Looks like tf-tests commit c41f3a078713b17b5654851329d63bcc0672874b > introduced calls to tfm_toolchain_reload_compiler(), which I don’t see > declared anywhere. > > > > I can work around it by using a local checkout of tf-m-tests at HEAD~. > > > > Chris Brand > > Sr Prin Software Engr, MCD: WIRELESS > > > > Cypress Semiconductor Corp. > > An Infineon Technologies Company > > #320-13700 International Place, Richmond, British Columbia V6V 2X8 Canada > > www.infineon.com www.cypress.com > > > > > 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. > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m >

4 years, 5 months

1
0
0 0

Re: [TF-M] cmake error

by David Hu

Hi Chris, Sorry for the build failure. A patch is merged into tf-m-tests but its peer ones in TF-M haven't been approved yet. I have temporarily reverted that tf-m-tests patch. Please have another try. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Christopher Brand via TF-M Sent: Tuesday, November 3, 2020 1:54 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] cmake error I just fetched the latest master (1655ef5120e99c62782575d0a8b3707ebfc2148e), and I'm now getting a cmake error: $ cmake -S . -B build_GNUARM_Relwithdebinfo '-GUnix Makefiles' -DTFM_PLATFORM=cypress/psoc64 -DCMAKE_TOOLCHAIN_FILE=toolchain_GNUARM.cmake -DCMAKE_BUILD_TYPE=Relwithdebinfo -DTEST_NS=ON -DTEST_S=ON -DTFM_IRQ_TEST=ON [...] CMake Error at build_GNUARM_Relwithdebinfo/lib/ext/tfm_test_repo-src/app/CMakeLists.txt:17 (tfm_toolchain_reload_compiler): Unknown CMake command "tfm_toolchain_reload_compiler". Looks like tf-tests commit c41f3a078713b17b5654851329d63bcc0672874b introduced calls to tfm_toolchain_reload_compiler(), which I don't see declared anywhere. I can work around it by using a local checkout of tf-m-tests at HEAD~. Chris Brand Sr Prin Software Engr, MCD: WIRELESS Cypress Semiconductor Corp. An Infineon Technologies Company #320-13700 International Place, Richmond, British Columbia V6V 2X8 Canada www.infineon.com<http://www.infineon.com> www.cypress.com<http://www.cypress.com> 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.

4 years, 5 months

1
0
0 0

Mbed TLS Virtual Workshop Tomorrow

by Shebu Varghese Kuriakose

Hi All, Gentle reminder about the Mbed TLS workshop tomorrow (Tuesday, November 3rd) from 2 to 6pm GMT. See agenda and zoom link here - https://www.trustedfirmware.org/meetings/mbed-tls-workshop/ Thanks, Shebu -----Original Appointment----- From: Trusted Firmware Public Meetings <linaro.org_havjv2figrh5egaiurb229pd8c(a)group.calendar.google.com> Sent: Friday, October 23, 2020 12:32 AM To: Trusted Firmware Public Meetings; Shebu Varghese Kuriakose; mbed-tls(a)lists.trustedfirmware.org; Don Harbin; psa-crypto(a)lists.trustedfirmware.org; Dave Rodgman Subject: Mbed TLS Virtual Workshop When: Tuesday, November 3, 2020 2:00 PM-6:00 PM (UTC+00:00) Dublin, Edinburgh, Lisbon, London. Where: Zoom: https://linaro-org.zoom.us/j/95315200315?pwd=ZDJGc1BZMHZLV29DTmpGUllmMjB1UT… You have been invited to the following event. Mbed TLS Virtual Workshop When Tue Nov 3, 2020 7am – 11am Mountain Standard Time - Phoenix Where Zoom: https://linaro-org.zoom.us/j/95315200315?pwd=ZDJGc1BZMHZLV29DTmpGUllmMjB1UT… (map<https://www.google.com/maps/search/Zoom:+https:%2F%2Flinaro-org.zoom.us%2Fj…>) Calendar shebu.varghesekuriakose(a)arm.com<mailto:shebu.varghesekuriakose@arm.com> Who • Don Harbin - creator • shebu.varghesekuriakose(a)arm.com<mailto:shebu.varghesekuriakose@arm.com> • mbed-tls(a)lists.trustedfirmware.org<mailto:mbed-tls@lists.trustedfirmware.org> • psa-crypto(a)lists.trustedfirmware.org<mailto:psa-crypto@lists.trustedfirmware.org> • dave.rodgman(a)arm.com<mailto:dave.rodgman@arm.com> more details »<https://www.google.com/calendar/event?action=VIEW&eid=NHVvY2FxY2o4Njk3MWZkd…> Hi, Trustedfirmware.org community project would like to invite you to the Mbed TLS Virtual Workshop. The purpose of the workshop is to bring together the Mbed TLS community including maintainers, contributors and users to discuss * The future direction of the project and * Ways to improve community collaboration Here is the agenda for the workshop. Topic Time (in GMT) Welcome 2.00 - 2.10pm Constant-time code 2.10 – 2.30pm Processes - how does work get scheduled? 2.30 – 2.50pm PSA Crypto APIs 2.50 – 3.20pm PSA Crypto for Silicon Labs Wireless MCUs - Why, What, Where and When 3.20 – 3.50pm Break Roadmap, TLS1.3 Update 4.10 – 4.30pm Mbed TLS 3.0 Plans, Scope 4.30 – 5.00pm How do I contribute my first review and be an effective Mbed TLS reviewer 5.00 – 5.30pm Regards, Don Harbin Trusted Firmware Community Manager ==============Zoom details below:==================== Trusted Firmware is inviting you to a scheduled Zoom meeting. Topic: Mbed TLS Virtual Workshop Time: Nov 3, 2020 02:00 PM Greenwich Mean Time Join Zoom Meeting https://linaro-org.zoom.us/j/95315200315?pwd=ZDJGc1BZMHZLV29DTmpGUllmMjB1UT…<https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9531520…> Meeting ID: 953 1520 0315 Passcode: 143755 One tap mobile +16699009128,,95315200315# US (San Jose) +12532158782,,95315200315# US (Tacoma) Dial by your location +1 669 900 9128 US (San Jose) +1 253 215 8782 US (Tacoma) +1 346 248 7799 US (Houston) +1 646 558 8656 US (New York) +1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) 888 788 0099 US Toll-free 877 853 5247 US Toll-free Meeting ID: 953 1520 0315 Find your local number: https://linaro-org.zoom.us/u/apL3hgti4<https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fu%2FapL3hgt…> Going (shebu.varghesekuriakose(a)arm.com<mailto:shebu.varghesekuriakose@arm.com>)? Yes<https://www.google.com/calendar/event?action=RESPOND&eid=NHVvY2FxY2o4Njk3MW…> - Maybe<https://www.google.com/calendar/event?action=RESPOND&eid=NHVvY2FxY2o4Njk3MW…> - No<https://www.google.com/calendar/event?action=RESPOND&eid=NHVvY2FxY2o4Njk3MW…> more options »<https://www.google.com/calendar/event?action=VIEW&eid=NHVvY2FxY2o4Njk3MWZkd…> Invitation from Google Calendar<https://www.google.com/calendar/> You are receiving this courtesy email at the account shebu.varghesekuriakose(a)arm.com<mailto:shebu.varghesekuriakose@arm.com> 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 organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More<https://support.google.com/calendar/answer/37135#forwarding>.

4 years, 5 months

1
0
0 0

cmake error

by Christopher Brand

I just fetched the latest master (1655ef5120e99c62782575d0a8b3707ebfc2148e), and I'm now getting a cmake error: $ cmake -S . -B build_GNUARM_Relwithdebinfo '-GUnix Makefiles' -DTFM_PLATFORM=cypress/psoc64 -DCMAKE_TOOLCHAIN_FILE=toolchain_GNUARM.cmake -DCMAKE_BUILD_TYPE=Relwithdebinfo -DTEST_NS=ON -DTEST_S=ON -DTFM_IRQ_TEST=ON [...] CMake Error at build_GNUARM_Relwithdebinfo/lib/ext/tfm_test_repo-src/app/CMakeLists.txt:17 (tfm_toolchain_reload_compiler): Unknown CMake command "tfm_toolchain_reload_compiler". Looks like tf-tests commit c41f3a078713b17b5654851329d63bcc0672874b introduced calls to tfm_toolchain_reload_compiler(), which I don't see declared anywhere. I can work around it by using a local checkout of tf-m-tests at HEAD~. Chris Brand Sr Prin Software Engr, MCD: WIRELESS Cypress Semiconductor Corp. An Infineon Technologies Company #320-13700 International Place, Richmond, British Columbia V6V 2X8 Canada www.infineon.com<http://www.infineon.com> www.cypress.com<http://www.cypress.com> 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.

4 years, 5 months

1
0
0 0

Code freeze heads up for TF-M v1.2

by Anton Komlev

Hi All, This is a reminder and heads up that TF-Mv1.2 release is planned for the end of November and TF-M code repository is aimed for freeze on Nov 4th (Wed), tagged by TF-Mv1.2-RC1 for testing. Availability of the tag will be notified via this mailing list. Thanks, Anton

4 years, 5 months

1
0
0 0

Integrating a different RTOS in tf-m-test

by Antonio Ken IANNILLO

Hi all, I wanted to use some other RTOS in the NS side while testing tf-m. Is there a simple way to use the Zephyr kernel or FreeRTOS in the tf-m-test (-DTEST_S=ON, -DTEST_NS=ON) instead of the default RTX? Best, -- Antonio Ken Iannillo Research Scientist – SEDAN group SnT – Interdisciplinary Centre for Security, Reliability and Trust UNIVERSITÉ DU LUXEMBOURG CAMPUS KIRCHBERG 29, avenue John F. Kennedy L-1855 Luxembourg Kirchberg T +352 46 66 44 9660 Join the conversation News | Twitter | Linkedin www.uni.lu/snt

4 years, 5 months

1
0
0 0

Re: [TF-M] Feature branch 'feature-isolation-level3' is created for related patches merging

by Kevin Peng

Hi all, As the isolation level 3 PoC targets for AN521 and MUSCA_B1 only at the first stage, two level-3-specific linker script files are created for these two platforms. And the common linker scripts are not changed now. This would avoid affecting the platforms who do not support isolation level 3 with a big changed linker script. The patch for specific linker scripts can be found here: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6717 Best Regards, Kevin From: Kevin Peng Sent: Wednesday, October 21, 2020 5:27 PM To: 'tf-m(a)lists.trustedfirmware.org' <tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org>> Subject: RE: Feature branch 'feature-isolation-level3' is created for related patches merging Hi all, We've finished the PoC of isolation level 3 along with the new TFM HAL on the feature branch. And now we are migrating the patches to master branch by cherry-picking, squashing and refining. Here are the several topics ongoing parallel: * Linker script changes for isolation L3<https://review.trustedfirmware.org/q/topic:%22linker_script_isolation%22+(s…> * Isolation HAL API<https://review.trustedfirmware.org/q/topic:%22isolation_api_implementation%…> * SPM log<https://review.trustedfirmware.org/q/topic:%22SPM_LOG%22+(status:open%20OR%…> * SP log<https://review.trustedfirmware.org/q/topic:%22tfm_sp_log%22+(status:open%20…> And the HAL API docs: * Docs: Design of the TF-M isolation HAL<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4829> More patches will be coming soon, will keep you update-to-date. Please help on reviews, thanks. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Ken Liu via TF-M Sent: Wednesday, September 9, 2020 3:21 PM To: 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] Feature branch 'feature-isolation-level3' is created for related patches merging Hi, A new branch created for two repos 'TF-M/tf-m-tests' and 'TF-M/trusted-firmware-m', this feature branch is for isolation related patches merging. The POC patches would come in following days, first platform would be AN521. If you want to try this branch, please: IMPORTANT: Checkout 'feature-isoaltion-level3' branch for both 'TF-M/tf-m-tests' and 'TF-M/trusted-firmware-m'. BR /Ken

4 years, 5 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

TF-M