- TF-M - lists.trustedfirmware.org

by Soby Mathew

Hi Øyvind Yes, you are right, we don't use wchar_t within TF-M and it does seem a trivial optimization without much benefit for TF-M other than introducing incompatibilities. Could you submit a patch to remove the same from GCC and ARMCLANG ? Best Regards Soby Mathew From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Rønningstad, Øyvind via TF-M Sent: 05 October 2020 09:12 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] -fshort-wchar Hi guys. I'm curious why -fshort-wchar is enabled for ARMCLANG and GNUARM (not IAR, interestingly). This should have little or no impact since wchar_t is so rarely used, and causes incompatibility when I try to link my Zephyr app with TF-M libs. Øyvind

5 years, 1 month

2
1
0 0

Re: [TF-M] Running Tests on Musca-A

by Tamas Ban

Hi Antonio, Could you try to do a debug build? By default the build type is release and in this case the MCUboot does not log anything. Set '-DCMAKE_BUILD_TYPE=Debug' in the command line when invoking the CMake generation phase. Tamas -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Antonio Ken IANNILLO via TF-M Sent: 05 October 2020 16:13 To: Raef Coles <Raef.Coles(a)arm.com>; tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] Running Tests on Musca-A Thank you. However, it seems to flash without problem but after reset I don't get the expected output. The most I can get from the UART is the message "Musca A Firmware Version 3.0" when I power off and on, but none of the logging message expected from tf-m. Am I missing something? -- Antonio Ken Iannillo On 05/10/2020, 15:41, "Raef Coles" <Raef.Coles(a)arm.com> wrote: Apologies for the difficulties that you're having. We've recently done an upgrade to the buildsystem and some of the documentation hasn't been properly updated to reflect the new files. There is a patch in review to rectify this. For now, updated (plaintext) documentation can be found at https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/…. It should also be updated on the website sometime this week. Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Antonio Ken IANNILLO via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 05 October 2020 14:06 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Running Tests on Musca-A Dear all, I’m a researcher exploring TF-M. I have a Musca-A board, and I was able to build it with tests. Now, it seems that the examples running the tests [1] are outdated: I simply do not have the same files. My understanding is that I should merge two files (secure and non-secure) but it is not clear which ones and how the offset are computed. Can somebody help me on this? The output files in the /bin folder are: bl2, tfm_ns, and tfm_s in .axf, .bin, .elf, .hex, .map; tfm_s_ns.bin; and tfm_s_ns_signed.bin. Best, [1] https://ci.trustedfirmware.org/view/TF-M/job/tf-m-build-docs-nightly/lastSt… -- Antonio Ken Iannillo, PhD 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 | antonioken.iannillo(a)uni.lu<mailto:antonioken.iannillo@uni.lu> 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<http://www.uni.lu/snt> https://akiannillo.github.io/ P Please consider the environment before printing this e-mail

5 years, 1 month

2
1
0 0

Re: [TF-M] Running Tests on Musca-A

by Raef Coles

Apologies for the difficulties that you're having. We've recently done an upgrade to the buildsystem and some of the documentation hasn't been properly updated to reflect the new files. There is a patch in review to rectify this. For now, updated (plaintext) documentation can be found at https://review.trustedfirmware.org/plugins/gitiles/TF-M/trusted-firmware-m/…. It should also be updated on the website sometime this week. Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Antonio Ken IANNILLO via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 05 October 2020 14:06 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Running Tests on Musca-A Dear all, I’m a researcher exploring TF-M. I have a Musca-A board, and I was able to build it with tests. Now, it seems that the examples running the tests [1] are outdated: I simply do not have the same files. My understanding is that I should merge two files (secure and non-secure) but it is not clear which ones and how the offset are computed. Can somebody help me on this? The output files in the /bin folder are: bl2, tfm_ns, and tfm_s in .axf, .bin, .elf, .hex, .map; tfm_s_ns.bin; and tfm_s_ns_signed.bin. Best, [1] https://ci.trustedfirmware.org/view/TF-M/job/tf-m-build-docs-nightly/lastSt… -- Antonio Ken Iannillo, PhD 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 | antonioken.iannillo(a)uni.lu<mailto:antonioken.iannillo@uni.lu> 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<http://www.uni.lu/snt> https://akiannillo.github.io/ P Please consider the environment before printing this e-mail

5 years, 1 month

2
1
0 0

Re: [TF-M] Running Tests on Musca-A

by Minos Galanakis

Hi Antonio, And welcome to the TF-M community. To get a better understanding of your issue it I would like to ask from some further details, such as the HEAD of the TF-M which you are trying to build, as well as the HEAD of the test branche. There has been a large overhaul of several components on the TF-M project, including the build system, so it would be good to have a common point of reference / By examples, do you refer to the official user guide? https://ci.trustedfirmware.org/view/TF-M/job/tf-m-build-docs-nightly/lastSt… For Musca_A you only need the hex file to flash it, which is generated using the srec_cat command mentioned above which utilises the platform specific offsets and merges the signed secure and non-secure binaries with the bootloader. If you are facing any issues flashing the HEX file, make sure that you have an up-to date daplink firmware. https://community.arm.com/developer/tools-software/oss-platforms/w/docs/554… If your output folder contains the HEX file, you can try flashing it by dragging and dropping, and see if it runs the regression tests. Regards, Minos Galanakis ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Antonio Ken IANNILLO via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 05 October 2020 14:06 To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org> Subject: [TF-M] Running Tests on Musca-A Dear all, I’m a researcher exploring TF-M. I have a Musca-A board, and I was able to build it with tests. Now, it seems that the examples running the tests [1] are outdated: I simply do not have the same files. My understanding is that I should merge two files (secure and non-secure) but it is not clear which ones and how the offset are computed. Can somebody help me on this? The output files in the /bin folder are: bl2, tfm_ns, and tfm_s in .axf, .bin, .elf, .hex, .map; tfm_s_ns.bin; and tfm_s_ns_signed.bin. Best, [1] https://ci.trustedfirmware.org/view/TF-M/job/tf-m-build-docs-nightly/lastSt… -- Antonio Ken Iannillo, PhD 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 | antonioken.iannillo(a)uni.lu<mailto:antonioken.iannillo@uni.lu> 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<http://www.uni.lu/snt> https://akiannillo.github.io/ P Please consider the environment before printing this e-mail

5 years, 1 month

1
0
0 0

Running Tests on Musca-A

by Antonio Ken IANNILLO

Dear all, I’m a researcher exploring TF-M. I have a Musca-A board, and I was able to build it with tests. Now, it seems that the examples running the tests [1] are outdated: I simply do not have the same files. My understanding is that I should merge two files (secure and non-secure) but it is not clear which ones and how the offset are computed. Can somebody help me on this? The output files in the /bin folder are: bl2, tfm_ns, and tfm_s in .axf, .bin, .elf, .hex, .map; tfm_s_ns.bin; and tfm_s_ns_signed.bin. Best, [1] https://ci.trustedfirmware.org/view/TF-M/job/tf-m-build-docs-nightly/lastSt… -- Antonio Ken Iannillo, PhD 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 | antonioken.iannillo(a)uni.lu Join the conversation News | Twitter | Linkedin www.uni.lu/snt https://akiannillo.github.io/ P Please consider the environment before printing this e-mail

5 years, 1 month

1
0
0 0

Re: [TF-M] CORE_TEST and the new build system

by Raef Coles

Patches are now up for review. for TF-M: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/6095/1 for tf-m-tests: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/6097 Any comments / reviews would be appreciated Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Raef Coles via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 01 October 2020 10:33 To: tf-m(a)lists.trustedfirmware.org; Christopher Brand Subject: Re: [TF-M] CORE_TEST and the new build system Yes, it seems like the core tests slipped through conversion. I've already had a report of this and got a patch together but it needs some thorough testing since it affects the linking order. I'll notify here once the patch is submitted for review. Should be this morning. Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Christopher Brand via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 30 September 2020 23:45 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] CORE_TEST and the new build system It seems that docs/reference/services/core_test_services_integration_guide.rst hasn’t been updated to reflect the new build system (it says to build using ConfigCoreTest.cmake). That config isn’t mentioned in docs/getting_started/tfm_build_instruction.rst. So how do I build the CORE_TEST stuff with the new build system (I’m particularly interested in the IRQ test). Thanks, 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. -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

5 years, 1 month

1
0
0 0

-fshort-wchar

by Rønningstad, Øyvind

Hi guys. I'm curious why -fshort-wchar is enabled for ARMCLANG and GNUARM (not IAR, interestingly). This should have little or no impact since wchar_t is so rarely used, and causes incompatibility when I try to link my Zephyr app with TF-M libs. Øyvind

5 years, 1 month

1
0
0 0

Re: [TF-M] Following the TF-M build example

by Raef Coles

Would it be possible to know what commit hash of TF-M you are currently using Kevin? I had thought there was now some error handling in place for this but it's possible that it doesn't work as it should. Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Ken Liu via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 03 October 2020 14:37 To: tf-m(a)lists.trustedfirmware.org Cc: nd Subject: Re: [TF-M] Following the TF-M build example Hi, I assume you are building under windows, if that is true, add a -G"Unix Makefiles" in the command line would make it work as a quick fix, since cmake treat the default build system under windows as MSVC. We are trying to create a patch to enhance this part. BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Kilzer via TF-M Sent: Saturday, October 3, 2020 8:28 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Following the TF-M build example I’m following the first build example in docs\getting_started\tfm_build_instruction.rst, for the mps2/an521. cmake -S . -B cmake_build -DTFM_PLATFORM=mps2/an521 -DCMAKE_TOOLCHAIN_FILE=toolchain_GNUARM.cmake Building on Windows with gnu, it progresses pretty far then stops with the error shown below. Any suggestions? Kevin -- Configuring done CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: tfm_s_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:27 (target_add_scatter_file) CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: tfm_ns_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:40 (target_add_scatter_file) CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: bl2_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:63 (target_add_scatter_file) CMake Generate step failed. Build files cannot be regenerated correctly.

5 years, 1 month

1
0
0 0

Re: [TF-M] Following the TF-M build example

by Ken Liu

Hi, I assume you are building under windows, if that is true, add a -G"Unix Makefiles" in the command line would make it work as a quick fix, since cmake treat the default build system under windows as MSVC. We are trying to create a patch to enhance this part. BR /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Kilzer via TF-M Sent: Saturday, October 3, 2020 8:28 AM To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] Following the TF-M build example I'm following the first build example in docs\getting_started\tfm_build_instruction.rst, for the mps2/an521. cmake -S . -B cmake_build -DTFM_PLATFORM=mps2/an521 -DCMAKE_TOOLCHAIN_FILE=toolchain_GNUARM.cmake Building on Windows with gnu, it progresses pretty far then stops with the error shown below. Any suggestions? Kevin -- Configuring done CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: tfm_s_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:27 (target_add_scatter_file) CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: tfm_ns_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:40 (target_add_scatter_file) CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: bl2_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:63 (target_add_scatter_file) CMake Generate step failed. Build files cannot be regenerated correctly.

5 years, 1 month

1
0
0 0

Following the TF-M build example

by Kevin.Kilzer＠microchip.com

I'm following the first build example in docs\getting_started\tfm_build_instruction.rst, for the mps2/an521. cmake -S . -B cmake_build -DTFM_PLATFORM=mps2/an521 -DCMAKE_TOOLCHAIN_FILE=toolchain_GNUARM.cmake Building on Windows with gnu, it progresses pretty far then stops with the error shown below. Any suggestions? Kevin -- Configuring done CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: tfm_s_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:27 (target_add_scatter_file) CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: tfm_ns_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:40 (target_add_scatter_file) CMake Error at toolchain_GNUARM.cmake:114 (add_library): No SOURCES given to target: bl2_scatter Call Stack (most recent call first): platform/ext/target/mps2/an521/CMakeLists.txt:63 (target_add_scatter_file) CMake Generate step failed. Build files cannot be regenerated correctly.

5 years, 1 month

1
0
0 0

New TF-M Build doesn't track config changes

by Soby Mathew

Hi, With the new build system, TF-M downloads all dependant repositories to the BUILD folder as part of CMAKE configuration. CMake does provide `make clean` target to clean the build and rebuild but this doesn't track any config changes between the builds. Previously, the CMake workflow was to delete all contents in the BUILD folder before re-configuring for a new build but now this means the developer has to re-download all the dependant git repositories before the project can be build again. This can be a slow and cumbersome process for developers. Deleting the CMakecache.txt doesn't seem to solve the problem either. The most obvious solution is to move the cloned repositories outside the BUILD/ folder , so we can follow the previous workflow of deleting the BUILD folder before re-build. The sample test sequence to reproduce the problem is given below: /* Build secure regressions test suite */ $ make clean; cmake .. -DTFM_PLATFORM=mps2/an521 -DCMAKE_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DTEST_S=ON -DCMAKE_BUILD_TYPE=Debug; make install /* reconfigure and build PSA Crypto API test suite */ $ make clean; cmake .. -DTFM_PLATFORM=mps2/an521 -DCMAKE_TOOLCHAIN_FILE=../toolchain_GNUARM.cmake -DCMAKE_BUILD_TYPE=Debug -DTEST_PSA_API=CRYPTO; make install Built binary is still for regression test suite. There are multiple suggestions to solve the problem, One is to move the clone repositories outside the BUILD/ folder, or introduce a build target like `make cleanall` which does the equivalent of rm -rf !(lib) within the BUILD folder (i.e the build target will remove all folders except the lib folder which has the cloned repositories). Please let us know of your suggestions on this. Best Regards Soby Mathew

5 years, 1 month

1
0
0 0

Re: [TF-M] TF-M Technical Forum call – October 1

by Anton Komlev

Hi All, The agenda for the forum today: 1. New build system features, tricks and known issues. See you, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M Sent: 28 September 2020 11:39 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] TF-M Technical Forum call – October 1 Hello, The next Technical Forum is planned on Thursday, October 1 at 15:00-16:00 UTC (US 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

5 years, 1 month

1
0
0 0

Re: [TF-M] CORE_TEST and the new build system

by Raef Coles

Yes, it seems like the core tests slipped through conversion. I've already had a report of this and got a patch together but it needs some thorough testing since it affects the linking order. I'll notify here once the patch is submitted for review. Should be this morning. Raef ________________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Christopher Brand via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 30 September 2020 23:45 To: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] CORE_TEST and the new build system It seems that docs/reference/services/core_test_services_integration_guide.rst hasn’t been updated to reflect the new build system (it says to build using ConfigCoreTest.cmake). That config isn’t mentioned in docs/getting_started/tfm_build_instruction.rst. So how do I build the CORE_TEST stuff with the new build system (I’m particularly interested in the IRQ test). Thanks, 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.

5 years, 1 month

1
0
0 0

Re: [TF-M] Musca-B1 and new build system

by Tamas Ban

Hi Raymond, Thanks for reporting the issue! The observed behaviour has two reason: - In the new build system the default CMAKE_BUILD_TYPE=Release. In this case the logging is disabled in MCUboot to get smaller binary. You can set manualy to Debug in the command line to enable logging from bootloader * This commit 7d591a684b4abb0f61fbba8668dd6ea7b4b68698 introduced a crash in Musca S1/B1. Fix is ongoing. Tamas From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Raymond Ngun via TF-M Sent: 30 September 2020 17:44 To: David Hu via TF-M <tf-m(a)lists.trustedfirmware.org> Subject: [TF-M] Musca-B1 and new build system Hi all, I am attempting to build Musca-B1 with the latest in master but I'm not able to get it to run (nothing shows on the UART). At a minimum, the User Guide is out of date in terms of how the final hex is created. So, I have a couple questions. 1. Is the latest tested with Musca-B1? 2. Can I obtain some updated information on how to build and create an image for Musca-B1? Thank you, Ray 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.

5 years, 1 month

1
0
0 0

CORE_TEST and the new build system

by Christopher Brand

It seems that docs/reference/services/core_test_services_integration_guide.rst hasn't been updated to reflect the new build system (it says to build using ConfigCoreTest.cmake). That config isn't mentioned in docs/getting_started/tfm_build_instruction.rst. So how do I build the CORE_TEST stuff with the new build system (I'm particularly interested in the IRQ test). Thanks, 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.

5 years, 1 month

1
0
0 0

Musca-B1 and new build system

by Raymond Ngun

Hi all, I am attempting to build Musca-B1 with the latest in master but I'm not able to get it to run (nothing shows on the UART). At a minimum, the User Guide is out of date in terms of how the final hex is created. So, I have a couple questions. 1. Is the latest tested with Musca-B1? 2. Can I obtain some updated information on how to build and create an image for Musca-B1? Thank you, Ray 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.

5 years, 1 month

1
0
0 0

Re: [TF-M] Removal of MCUboot fork from TF-M

by Adrian Shaw

This is excellent work and great news for both projects. Well done. Best, Adrian ________________________________ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> on behalf of Tamas Ban via TF-M <tf-m(a)lists.trustedfirmware.org> Sent: 30 September 2020 11:13 To: tf-m(a)lists.trustedfirmware.org <tf-m(a)lists.trustedfirmware.org> Cc: nd <nd(a)arm.com> Subject: [TF-M] Removal of MCUboot fork from TF-M Hi, In the last few quarter TF-M team have worked on actively to upstream the TF-M related features from the forked MCUboot repo to the original repository. This activity has been finished recently and as a result the MCUboot fork has been removed from TF-M repo. Currently TF-M exclusively relies on MCUboot project as a secure bootloader. From now on all new development will be directly contributed to the upstream repo. List of feature which were upstreamed: * HW rollback protection * HW key integration * Data exchange between MCUboot and runtime firmware * RAM_LOAD boot mode * DIRECT_XIP boot mode BR, Tamas Ban

5 years, 1 month

1
0
0 0

Removal of MCUboot fork from TF-M

by Tamas Ban

Hi, In the last few quarter TF-M team have worked on actively to upstream the TF-M related features from the forked MCUboot repo to the original repository. This activity has been finished recently and as a result the MCUboot fork has been removed from TF-M repo. Currently TF-M exclusively relies on MCUboot project as a secure bootloader. From now on all new development will be directly contributed to the upstream repo. List of feature which were upstreamed: * HW rollback protection * HW key integration * Data exchange between MCUboot and runtime firmware * RAM_LOAD boot mode * DIRECT_XIP boot mode BR, Tamas Ban

5 years, 1 month

1
0
0 0

Using TF-M through ymodem to download tfm_s_enc_sign.bin---------STM32L562

by 徐鹏

Hello Jaouen, I have a development issue when running TFM download process on the STM32L562.Print a error log"[ERR] Image in the secondary slot is not valid!" when download tfm_s_enc_sign.bin.ALL other 3 bin（tfm_s_sign.bin，tfm_ns_sign.bin，tfm_ns_enc_sign.bin） download success. I follow the document UM2671 chapter 11.4 Download a new firmware image. The project is en.stm32cubel5_v1-3-0.zip，file：Projects\STM32L562E-DK\Applications\TFM Steps to reproduce: 1.run Projects\STM32L562E-DK\Applications\TFM\TFM_SBSFU_Boot\MDK-ARM\regression.bat to init device 2.build TFM_SBSFU_Boot application，TFM_Appli secure application，TFM_Appli non-secure application，Build TFM_Loader application 3.run Projects\STM32L562E-DK\Applications\TFM\TFM_SBSFU_Boot\MDK-ARM\TFM_UPDATE.bat to programing into STM32L5 internal and external Flash memory 4.success to run into app 5.press user button (blue) during board reset, the user enters local loader menu. 6.use ymodem to download tfm_s_enc_sign.bin to secure image 7.reset and then print error log "[ERR] Image in the secondary slot is not valid!" Reason： 1.hash verify not pass because after decrypt， the image not same with origin image.log as below： ===================================================== [INF] verify counter 0 1000000 1000000 [INF] counter 0 : ok [INF] hash256 : 54, cc, 2c, 4c, 97, b5, 55, 68, [INF] hash256 buf : cd, 76, a3, a1, cb, 1, 4d, bc, [ERR] Image in the secondary slot is not valid! ====================================================== Does anyone know what I39m doing wrong? Thanks in advance!

5 years, 1 month

1
0
0 0

Re: [TF-M] [RFC] The code review guideline

by Ken Liu

Hi, I would merge this one as it has been put there review for a while, thanks all the reviewers. This would provide a basic shape while we are creating new features, also could be viewed better after rendered. There would be many points can be updated later, let’s try to use it and see how it works – Create issues at https://developer.trustedfirmware.org/ and assign to me if there are, reply here is also workable. Thanks. /Ken From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M Sent: Tuesday, September 1, 2020 9:50 AM To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: [TF-M] [RFC] The code review guideline Hi, We are creating one document to describe the code review guidelines: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5372 The goal of this document is to introduce the source management level concepts to be followed while reviewing a code – which try to simplify the contribution (but burdens the reviewers? 😉). Difference to the `coding style`: * It focuses more on the source placement, interface definition and including, etc. As this document is keeping evolving in a period, the plan is we merge a simple version as start and adding more contents by new patches, so please give enough comments if you have, and don’t forget the concept: we want to make things rational and simple. Thanks. /Ken

5 years, 1 month

1
0
0 0

TF-M Technical Forum call – October 1

by Anton Komlev

Hello, The next Technical Forum is planned on Thursday, October 1 at 15:00-16:00 UTC (US 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

5 years, 1 month

1
0
0 0

Updated invitation: TF-M tech Forum @ Thu 15 Oct 2020 07:00 - 08:00 (BST) (tf-m@lists.trustedfirmware.org)

by Bill Fletcher

This event has been changed. 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 15 Oct 2020 07:00 – 08:00 United Kingdom Time Calendar: tf-m(a)lists.trustedfirmware.org Who: * Bill Fletcher- creator * Don Harbin * tf-m(a)lists.trustedfirmware.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=NWRmOTZydWZobWFnZ3RvM… 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

5 years, 1 month

1
0
0 0

Invitation: TF-M tech Forum @ Thu 15 Oct 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 15 Oct 2020 07:00 – 08:00 United Kingdom Time Calendar: tf-m(a)lists.trustedfirmware.org Who: * Bill Fletcher- organiser * Don Harbin * tf-m(a)lists.trustedfirmware.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=NWRmOTZydWZobWFnZ3RvM… 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

5 years, 1 month

1
0
0 0

Cancelled event with note: TF-M Tech Forum @ Thu 15 Oct 2020 16:00 - 17:00 (BST) (tf-m@lists.trustedfirmware.org)

by Bill Fletcher

This event has been cancelled with this note: "This will be rescheduled with the time corrected" 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 15 Oct 2020 16:00 – 17:00 United Kingdom Time Calendar: tf-m(a)lists.trustedfirmware.org Who: * Bill Fletcher- creator * Don Harbin * tf-m(a)lists.trustedfirmware.org 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

5 years, 1 month

1
0
0 0

Invitation: TF-M Tech forum @ Thu 1 Oct 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 1 Oct 2020 16:00 – 17:00 United Kingdom Time Calendar: tf-m(a)lists.trustedfirmware.org Who: * Bill Fletcher- creator * Don Harbin * tf-m(a)lists.trustedfirmware.org Event details: https://www.google.com/calendar/event?action=VIEW&eid=N29mbm1qN2prOXBxMDhpd… 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

5 years, 1 month

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

TF-M