- TF-M - lists.trustedfirmware.org

Invitation: TF-M tech forum @ Thu 3 Sep 2020 16:00 - 17: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 3 Sep 2020 16:00 – 17: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=M2R2cW8ycGhvbGk0bWM0M… 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

Invitation: TF-M Tech Forum @ Thu 20 Aug 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 20 Aug 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=MmhydThhczM3N3RrNnNmY… 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

Invitation: TF-M Tech forum @ Thu 6 Aug 2020 16:00 - 17: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 6 Aug 2020 16:00 – 17: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=MjZua2JubGhybjJlMGswM… 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

[RFC]Patches for migrating testing codes from TF-M to tf-m-tests

by Kevin Peng

Hi, As have shared on the tech forum yesterday, there is the activity to move the test codes from tf-m to tf-m-tests. Here are the patches for the step 1 - moving the codes without modifications: https://review.trustedfirmware.org/q/topic:%22Migration_of_test_code%22+(st… Please help on review. Thanks. The review window would be closed in one week in case of no comments. Best Regards, Kevin

4 years, 9 months

1
0
0 0

TF-M: v1.1 and Ecosystem Enablement Blog

by Shebu Varghese Kuriakose

Hi All, Here is a blog about TF-M v1.1 and recent Ecosystem enablement - https://www.trustedfirmware.org/blog/tfm-v1-1-blog/ Regards, Shebu TF-M Technology Manager

4 years, 9 months

1
0
0 0

Re: [TF-M] New TrustedFirmware.org security incident process is now live

by Anton Komlev

Hi, Let me remind you about the security incident process and open registration for Trusted Stakeholders. Best regards, Anton Komlev From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Dan Handley via TF-M Sent: 30 June 2020 15:13 To: tsc(a)lists.trustedfirmware.org; tf-a(a)lists.trustedfirmware.org; tf-m(a)lists.trustedfirmware.org; op-tee(a)lists.trustedfirmware.org; mbed-tls(a)lists.trustedfirmware.org; mbed-tls-announce(a)lists.trustedfirmware.org; hafnium(a)lists.trustedfirmware.org Subject: [TF-M] New TrustedFirmware.org security incident process is now live Hi all The new TrustedFirmware.org security incident process is now live. This process is described here: https://developer.trustedfirmware.org/w/collaboration/security_center/repor… Initially the process will be used for the following projects: TF-A, TF-M, OP-TEE and Mbed TLS. The security documentation for each project will be updated soon to reflect this change. If you are part of an organization that believes it should receive security vulnerability information before it is made public then please ask your relevant colleagues to register as Trusted Stakeholders as described here: https://developer.trustedfirmware.org/w/collaboration/security_center/trust… Note we prefer individuals in each organization to coordinate their registration requests with each other and to provide us with an email alias managed by your organization instead of us managing a long list of individual addresses. Best regards Dan. (on behalf of the TrustedFirmware.org security team)

4 years, 9 months

1
0
0 0

Re: [TF-M] TF-M Technical Forum call - July 23

by Kevin Peng

Hi Anton, I'd like to give a brief introduction on the changes (both happened and proposal) for TF-M testing. The duration would be ~30 minutes. Best Regards, Kevin From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: Monday, July 20, 2020 4:14 PM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M Technical Forum call - July 23 Hello, The next Technical Forum is planned on Thursday, July 23 at 6:00-07:00 UTC (Asia time zone). Please reply on this email with your proposals for agenda topics. Best regards, Anton Komlev

4 years, 9 months

2
1
0 0

New build system WIP

by Raef Coles

Hi all The new buildsystem (work in progress) is now available at https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5039. Comment would be very much appreciated. There have been some minor interface changes to how the buildsystem is invoked. a sample invocation is: cmake -S .. \ -B . \ -G"Unix Makefiles" \ -DTFM_PLATFORM=musca_s1 \ -DCMAKE_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake \ -DCMAKE_BUILD_TYPE=release -DBL2=ON \ -DNS=ON \ -DTFM_PSA_API=ON \ -DTEST_NS=ON -DTEST_S=ON \ -DTFM_ISOLATION_LVL=2 More specifically cmake -S [Source_dir (often ..)] \ -B [build_dir (often .)] \ -G ["Unix Makefiles" OR Ninja] \ -DTFM_PLATFORM=[musca_b1 OR musca_s1 OR mps2/an521 OR cypress/psoc64 ETC...] -DCMAKE_TOOLCHAIN_FILE=[build_dir/toolchain_GNUARM.cmake OR build_dir/toolchain_ARMCLANG.cmake] -DCMAKE_BUILD_TYPE=[release OR debug OR minsizerel OR relwithdbginfo] -DBL2=[OFF OR ON] -DNS=[OFF OR ON] -DTFM_PSA_API=[OFF OR ON] -DTEST_NS=[OFF OR ON] -DTEST_S=[OFF OR ON] -DTFM_ISOLATION_LVL=[1 OR 2] Note that this interface is not set in stone and may change before these patches are merged. The new buildsystem is currently missing a few of the platforms, as well as some features. All of these are planned to be added prior to merging. Notable are dualcpu/Cypress PSoC64 which is currently being finalized, documentation building, and image signing for some of the boot modes which is on the TODO list. Note that unlike previous versions, this should work "out the box" with regard to dependencies. The paths for dependencies can be set, but some patches to mbedtls that are in the process of being upstreamed are used. These patches are stored in the lib/ext/mbedcrypto directory and can easily be applied manually. Regards, Raef Coles

4 years, 9 months

1
0
0 0

MCUBoot related changes

by Tamas Ban

Hi, Just a heads-up for the coming changes related to MCUBoot. Some of them requires installing new tools in build system others could affect devices on the field (if there is any) after SW upgrade. Short term, within one week: 1. Official imgtool enablement: * The official released version of the image signings script will be used. * Must be installed in the build system. It is a PyPI package: imgtool v1.6 * https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4564/6 2. Encrypted image support: * This feature already exists in the upstream repo for a while * This change makes possible to turn it on in TF-M build system * https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4565/6 Long term, but still expected in Q3: 1. Removal of forked MCUBoot from TF-M: * Only upstream MCUBoot will supported * Platform and project related files will be kept: i. shim layer to match MCUBoot HAL's to TF-M's HAL ii. bl2_main.c, example signing keys, keys.c iii. platform code: flash and UART drivers, implementation of boot_hal.h * When building TF-M with upstream MCUboot it is a mixture of files from the two repo + crypto code from mbedcrypto repo. * https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4953 * The removal of the fork depends on the feature upstream to MCUBoot repo: i. https://github.com/JuulLabs-OSS/mcuboot/pull/739 ii. RAM_LOAD: PR will come a bit later 1. Removal of LEGACY_TFM_TLV_HEADER support * This is a compatibility mode. It was introduced to hide the difference in the definition of the TLV header int he shared data between bootloader and runtime SPE. * If forked removed, then this is not necessary anymore, unless an forked version of MCUBoot wants to cooperate new SPE. * Please check and indicate if you think that this is a valid use case and compatibility mode must be kept! Tamas

4 years, 9 months

1
1
0 0

TF-M/FreeRTOS blog

by Shebu Varghese Kuriakose

Hi All, Here is a blog post about FreeRTOS/TF-M integration - https://freertos.org/2020/07/security-for-arm-cortex-m-devices-with-freerto… Regards, Shebu

4 years, 9 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

TF-M