June 2020 - TF-M - lists.trustedfirmware.org

by Kumar Gala

Zephyr uses DT as a means to describe the hardware to the system for things like register address, irq numbers, etc. Instead of the typical runtime usage, it generates code to be used at build time for Cortex-M (and other) devices to address the size cost concern. On the KConfig side Zephyr uses a python implementation of the KConfig parser to allow portability across host build systems. - k > On Jun 12, 2020, at 4:35 AM, Gyorgy Szing via TF-M <tf-m(a)lists.trustedfirmware.org> wrote: > > Hi, > > Just some minor additions. In the TF-M build system Kconfig will most likely generate input for cmake scripts, so the compiler may not have a connection to it. > > The original intention with DT is capturing configuration data to allow hardware independent binaries (for defining base address of peripherals, boot information, etc..), and is mostly parsed runtime. In the Cortex-M space this might be a bit out-of scope. Most likely it will be used as a “standard” language to define “retargeting” information, and a tool will be developed which runs compile time and which allows access to the retargeting data for cmake. Something like CMSIS zone, but closer to established open-source technologies. > In multicore systems having bot Cortex-A and M core DT would allow having a consistent solution for both A and M firmware. This is also a reason why cmake is a better build solution for TF-M than CMSIS Build. > > /George > > From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M > Sent: 12 June 2020 11:16 > To: Thomas Törnblom <thomas.tornblom(a)iar.com>; tf-m(a)lists.trustedfirmware.org > Cc: nd <nd(a)arm.com> > Subject: Re: [TF-M] CMake flags > > Hi Thomas, > > DT is another very attractive topic. TF-M currently doesn’t include any DT support. > So maybe there is mixed preprocessing of DT and Kconfig in Zephyr, but Kconfig can be parsed without any compiler. > > Best regards, > Hu Ziji > > From: Thomas Törnblom <thomas.tornblom(a)iar.com> > Sent: Friday, June 12, 2020 5:09 PM > To: David Hu <David.Hu(a)arm.com>; tf-m(a)lists.trustedfirmware.org > Cc: nd <nd(a)arm.com> > Subject: Re: [TF-M] CMake flags > > Perhaps I'm mixing dts and Kconfig up. > > In Zephyr, dtc is used to generate output that is run through the gcc preprocessor in assembly mode. > > The output from dtc looks like: > --- > /dts-v1/; > > / { > ï¿½ï¿½ï¿½ #address-cells = < 0x1 >; > ï¿½ï¿½ï¿½ #size-cells = < 0x1 >; > ï¿½ï¿½ï¿½ model = "STMicroelectronics STM32F746G DISCOVERY board"; > ï¿½ï¿½ï¿½ compatible = "st,stm32f746g-disco", "st,stm32f746"; > ï¿½ï¿½ï¿½ chosen { > ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,console = &usart1; > ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,shell-uart = &usart1; > ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,sram = &sram0; > ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,flash = &flash0; > ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,dtcm = &dtcm; > ï¿½ï¿½ï¿½ }; > ... > --- > > Our preprocessor can not be run in assembler mode and it pukes on the "#address-cells" type elements in the file. > > If this is not what Kconfig is about, then please ignore my comments. > > Thomas > > Den 2020-06-12 kl. 09:43, skrev David Hu: > Hi Thomas, > ï¿½ > Iï¿½ve not met such a problem yet. Could you please give more details about the portability issues in Kconfig? > In our PoC, it firstly parses the Kconfig files and then convert the output Kconfig options into CMake flags. Thus the whole process is not related to any compiler. > I checked Zephyr previously. It looks like Zephyr has the similar idea as our PoC does. > ï¿½ > Best regards, > Hu Ziji > ï¿½ > From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Tï¿½rnblom via TF-M > Sent: Friday, June 12, 2020 3:36 PM > To: tf-m(a)lists.trustedfirmware.org > Subject: Re: [TF-M] CMake flags > ï¿½ > Introducing a dependency on Kconfig may cause portability issues with some toolchains (IAR for instance) > > I am working on adding support for the IAR toolchain to Zephyr, and Kconfig is one of the issues I've run into. > > At least in Zephyr, the output from Kconfig is run through the C preprocessor and this causes issues with the IAR preprocessor so for now I use gcc for this step. > > Thomas > > Den 2020-06-12 kl. 07:32, skrev David Hu via TF-M: > Hi Adrian, > ï¿½ > Actually we have been investigating configuration alternatives and making some prototypes of Kconfig. > ï¿½ > Kconfig can bring some advantages: > • It can setup configuration and check dependency before CMake starts and therefore it can help CMake simplify dealing with the mutual dependencies. For example, if CPU and arch options can be configured in Kconfig, CMake can avoid the workaround to re-configure compiler after parsing platform files. > • Kconfig can collect together the options which are distributed in various CMake files. Developers can more easily understand the options and their dependencies, compared with searching them all around the build system. > ï¿½ > But Kconfig may not cover all the flags in command line. Flags such as compiler selections, build type and project config file, may vary in each build. It can be inconvenient to put them into Kconfig. > ï¿½ > Best regards, > Hu Ziji > ï¿½ > From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Adrian Shaw via TF-M > Sent: Friday, June 12, 2020 12:24 AM > To: Raef Coles <Raef.Coles(a)arm.com> > Cc: tf-m(a)lists.trustedfirmware.org > Subject: [TF-M] CMake flags > ï¿½ > Hi Raef. Thanks for the presentation today. > ï¿½ > If I remember correctly, TF-M's CMake has quite a lot of command line flags now (the ones that are set with -D). And I think this will grow in the future as more options are needed. > ï¿½ > From a command line point of view, this is kind of annoying because the commands end up being quite long. Do you guys think something like Kconfig could help? > ï¿½ > Adrian > ï¿½ > > ï¿½ > -- > > 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 Website: www.iar.com > Twitter: www.twitter.com/iarsystems > > -- > > 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 Website: www.iar.com > Twitter: www.twitter.com/iarsystems > -- > TF-M mailing list > TF-M(a)lists.trustedfirmware.org > https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 6 months

1
0
0 0

Re: [TF-M] CMake flags

by Rønningstad, Øyvind

Note that Zephyr has a Cmake function that does this exact thing, if you're interested: https://github.com/zephyrproject-rtos/zephyr/blob/master/cmake/extensions.c… Øyvind Rønningstad -----Original Message----- From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: Friday, June 12, 2020 11:45 To: Raef Coles <Raef.Coles(a)arm.com>; Gyorgy Szing <Gyorgy.Szing(a)arm.com>; Adrian Shaw <Adrian.Shaw(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] CMake flags Hi Raef, My current prototype is to parse the options from Kconfig output file and "inject" them into CMake (by set()) in a CMake file running at the beginning of build process. Kconfig generation is an optional step before build starts, only if you request to change the configuration. Otherwise, build just starts with previous Kconfig output config as normal. Best regards, Hu Ziji -----Original Message----- From: Raef Coles <Raef.Coles(a)arm.com> Sent: Friday, June 12, 2020 5:34 PM To: Gyorgy Szing <Gyorgy.Szing(a)arm.com>; David Hu <David.Hu(a)arm.com>; Adrian Shaw <Adrian.Shaw(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: CMake flags I think I'd advocate for using a workflow of generating a cfg.cmake file from the kconfig, instead of a txt file with an associated cmake parser. I think it'd be advantageous to not have a parser for an arbitrary config file format in the cmake, since the cmake set(CACHE) statements are already fairly user-readable. It would be different if we could only generate something less readable from the kconfig (i.e. xml/json). It would be ideal if we could generate the statements such that: set(<variable_name> <default_option> CACHE <TYPE> "<docstring> (<valid_option> | <valid_option> | ...)" I'm not sure if we can do this in Kconfig, but it seems plausible, and imo is the ideal solution since it gives the user of later editing the cmake config (even using a cache editor like ccmake) while documenting which choices are sane. Raef ________________________________________ From: Gyorgy Szing <Gyorgy.Szing(a)arm.com> Sent: 12 June 2020 06:56 To: David Hu; Adrian Shaw; Raef Coles; tf-m(a)lists.trustedfirmware.org Cc: nd; nd Subject: RE: CMake flags Hi, This requirement could be addressed with a user specific metadata file which is processed by the build-system. Implementation wise the easiest would be to include a file like UserCfg.cmake. This file could contain set(<option> CACHE <STRING|BOOL|PATH> "") commands to set the option variables. User experience wise a text file parsed by cmake scripts would be the best. Such a file could contain variable=value lines. Longer term when Kconfig support is ready, it could cover these options too. Running Kconfig is a an act done less often, and most of the times, the user is expected to save the Kconfig input and output files. Most of the time the build-system would just use the pre-generated config. I imagine a workflow similar to the one used by the Linux Kernel. Just my two cent's though. /George From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: 12 June 2020 07:33 To: Adrian Shaw <Adrian.Shaw(a)arm.com>; Raef Coles <Raef.Coles(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] CMake flags Hi Adrian, Actually we have been investigating configuration alternatives and making some prototypes of Kconfig. Kconfig can bring some advantages: * It can setup configuration and check dependency before CMake starts and therefore it can help CMake simplify dealing with the mutual dependencies. For example, if CPU and arch options can be configured in Kconfig, CMake can avoid the workaround to re-configure compiler after parsing platform files. * Kconfig can collect together the options which are distributed in various CMake files. Developers can more easily understand the options and their dependencies, compared with searching them all around the build system. But Kconfig may not cover all the flags in command line. Flags such as compiler selections, build type and project config file, may vary in each build. It can be inconvenient to put them into Kconfig. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Adrian Shaw via TF-M Sent: Friday, June 12, 2020 12:24 AM To: Raef Coles <Raef.Coles(a)arm.com<mailto:Raef.Coles@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] CMake flags Hi Raef. Thanks for the presentation today. If I remember correctly, TF-M's CMake has quite a lot of command line flags now (the ones that are set with -D). And I think this will grow in the future as more options are needed. From a command line point of view, this is kind of annoying because the commands end up being quite long. Do you guys think something like Kconfig could help? Adrian -- TF-M mailing list TF-M(a)lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m

4 years, 6 months

1
0
0 0

Re: [TF-M] CMake flags

by Gyorgy Szing

Hi, This requirement could be addressed with a user specific metadata file which is processed by the build-system. Implementation wise the easiest would be to include a file like UserCfg.cmake. This file could contain set(<option> CACHE <STRING|BOOL|PATH> "") commands to set the option variables. User experience wise a text file parsed by cmake scripts would be the best. Such a file could contain variable=value lines. Longer term when Kconfig support is ready, it could cover these options too. Running Kconfig is a an act done less often, and most of the times, the user is expected to save the Kconfig input and output files. Most of the time the build-system would just use the pre-generated config. I imagine a workflow similar to the one used by the Linux Kernel. Just my two cent's though. /George From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: 12 June 2020 07:33 To: Adrian Shaw <Adrian.Shaw(a)arm.com>; Raef Coles <Raef.Coles(a)arm.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] CMake flags Hi Adrian, Actually we have been investigating configuration alternatives and making some prototypes of Kconfig. Kconfig can bring some advantages: * It can setup configuration and check dependency before CMake starts and therefore it can help CMake simplify dealing with the mutual dependencies. For example, if CPU and arch options can be configured in Kconfig, CMake can avoid the workaround to re-configure compiler after parsing platform files. * Kconfig can collect together the options which are distributed in various CMake files. Developers can more easily understand the options and their dependencies, compared with searching them all around the build system. But Kconfig may not cover all the flags in command line. Flags such as compiler selections, build type and project config file, may vary in each build. It can be inconvenient to put them into Kconfig. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Adrian Shaw via TF-M Sent: Friday, June 12, 2020 12:24 AM To: Raef Coles <Raef.Coles(a)arm.com<mailto:Raef.Coles@arm.com>> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] CMake flags Hi Raef. Thanks for the presentation today. If I remember correctly, TF-M's CMake has quite a lot of command line flags now (the ones that are set with -D). And I think this will grow in the future as more options are needed. >From a command line point of view, this is kind of annoying because the commands end up being quite long. Do you guys think something like Kconfig could help? Adrian

4 years, 6 months

3
3
0 0

Re: [TF-M] CMake flags

by Gyorgy Szing

Hi, Just some minor additions. In the TF-M build system Kconfig will most likely generate input for cmake scripts, so the compiler may not have a connection to it. The original intention with DT is capturing configuration data to allow hardware independent binaries (for defining base address of peripherals, boot information, etc..), and is mostly parsed runtime. In the Cortex-M space this might be a bit out-of scope. Most likely it will be used as a "standard" language to define "retargeting" information, and a tool will be developed which runs compile time and which allows access to the retargeting data for cmake. Something like CMSIS zone, but closer to established open-source technologies. In multicore systems having bot Cortex-A and M core DT would allow having a consistent solution for both A and M firmware. This is also a reason why cmake is a better build solution for TF-M than CMSIS Build. /George From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M Sent: 12 June 2020 11:16 To: Thomas Törnblom <thomas.tornblom(a)iar.com>; tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] CMake flags Hi Thomas, DT is another very attractive topic. TF-M currently doesn't include any DT support. So maybe there is mixed preprocessing of DT and Kconfig in Zephyr, but Kconfig can be parsed without any compiler. Best regards, Hu Ziji From: Thomas Törnblom <thomas.tornblom(a)iar.com<mailto:thomas.tornblom@iar.com>> Sent: Friday, June 12, 2020 5:09 PM To: David Hu <David.Hu(a)arm.com<mailto:David.Hu@arm.com>>; tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] CMake flags Perhaps I'm mixing dts and Kconfig up. In Zephyr, dtc is used to generate output that is run through the gcc preprocessor in assembly mode. The output from dtc looks like: --- /dts-v1/; / { ï¿½ï¿½ï¿½ #address-cells = < 0x1 >; ï¿½ï¿½ï¿½ #size-cells = < 0x1 >; ï¿½ï¿½ï¿½ model = "STMicroelectronics STM32F746G DISCOVERY board"; ï¿½ï¿½ï¿½ compatible = "st,stm32f746g-disco", "st,stm32f746"; ï¿½ï¿½ï¿½ chosen { ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,console = &usart1; ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,shell-uart = &usart1; ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,sram = &sram0; ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,flash = &flash0; ï¿½ï¿½ï¿½ ï¿½ï¿½ï¿½ zephyr,dtcm = &dtcm; ï¿½ï¿½ï¿½ }; ... --- Our preprocessor can not be run in assembler mode and it pukes on the "#address-cells" type elements in the file. If this is not what Kconfig is about, then please ignore my comments. Thomas Den 2020-06-12 kl. 09:43, skrev David Hu: Hi Thomas, ï¿½ Iï¿½ve not met such a problem yet. Could you please give more details about the portability issues in Kconfig? In our PoC, it firstly parses the Kconfig files and then convert the output Kconfig options into CMake flags. Thus the whole process is not related to any compiler. I checked Zephyr previously. It looks like Zephyr has the similar idea as our PoC does. ï¿½ Best regards, Hu Ziji ï¿½ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org><mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Thomas Tï¿½rnblom via TF-M Sent: Friday, June 12, 2020 3:36 PM To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: Re: [TF-M] CMake flags ï¿½ Introducing a dependency on Kconfig may cause portability issues with some toolchains (IAR for instance) I am working on adding support for the IAR toolchain to Zephyr, and Kconfig is one of the issues I've run into. At least in Zephyr, the output from Kconfig is run through the C preprocessor and this causes issues with the IAR preprocessor so for now I use gcc for this step. Thomas Den 2020-06-12 kl. 07:32, skrev David Hu via TF-M: Hi Adrian, ï¿½ Actually we have been investigating configuration alternatives and making some prototypes of Kconfig. ï¿½ Kconfig can bring some advantages: * It can setup configuration and check dependency before CMake starts and therefore it can help CMake simplify dealing with the mutual dependencies. For example, if CPU and arch options can be configured in Kconfig, CMake can avoid the workaround to re-configure compiler after parsing platform files. * Kconfig can collect together the options which are distributed in various CMake files. Developers can more easily understand the options and their dependencies, compared with searching them all around the build system. ï¿½ But Kconfig may not cover all the flags in command line. Flags such as compiler selections, build type and project config file, may vary in each build. It can be inconvenient to put them into Kconfig. ï¿½ Best regards, Hu Ziji ï¿½ From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org><mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Adrian Shaw via TF-M Sent: Friday, June 12, 2020 12:24 AM To: Raef Coles <Raef.Coles(a)arm.com><mailto:Raef.Coles@arm.com> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] CMake flags ï¿½ Hi Raef. Thanks for the presentation today. ï¿½ If I remember correctly, TF-M's CMake has quite a lot of command line flags now (the ones that are set with -D). And I think this will grow in the future as more options are needed. ï¿½ >From a command line point of view, this is kind of annoying because the commands end up being quite long. Do you guys think something like Kconfig could help? ï¿½ Adrian ï¿½ ï¿½ -- 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> -- 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, 6 months

1
0
0 0

Re: [TF-M] CMake flags

by David Hu

Hi Thomas, I've not met such a problem yet. Could you please give more details about the portability issues in Kconfig? In our PoC, it firstly parses the Kconfig files and then convert the output Kconfig options into CMake flags. Thus the whole process is not related to any compiler. I checked Zephyr previously. It looks like Zephyr has the similar idea as our PoC does. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M Sent: Friday, June 12, 2020 3:36 PM To: tf-m(a)lists.trustedfirmware.org Subject: Re: [TF-M] CMake flags Introducing a dependency on Kconfig may cause portability issues with some toolchains (IAR for instance) I am working on adding support for the IAR toolchain to Zephyr, and Kconfig is one of the issues I've run into. At least in Zephyr, the output from Kconfig is run through the C preprocessor and this causes issues with the IAR preprocessor so for now I use gcc for this step. Thomas Den 2020-06-12 kl. 07:32, skrev David Hu via TF-M: Hi Adrian, Actually we have been investigating configuration alternatives and making some prototypes of Kconfig. Kconfig can bring some advantages: * It can setup configuration and check dependency before CMake starts and therefore it can help CMake simplify dealing with the mutual dependencies. For example, if CPU and arch options can be configured in Kconfig, CMake can avoid the workaround to re-configure compiler after parsing platform files. * Kconfig can collect together the options which are distributed in various CMake files. Developers can more easily understand the options and their dependencies, compared with searching them all around the build system. But Kconfig may not cover all the flags in command line. Flags such as compiler selections, build type and project config file, may vary in each build. It can be inconvenient to put them into Kconfig. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org><mailto:tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Adrian Shaw via TF-M Sent: Friday, June 12, 2020 12:24 AM To: Raef Coles <Raef.Coles(a)arm.com><mailto:Raef.Coles@arm.com> Cc: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Subject: [TF-M] CMake flags Hi Raef. Thanks for the presentation today. If I remember correctly, TF-M's CMake has quite a lot of command line flags now (the ones that are set with -D). And I think this will grow in the future as more options are needed. >From a command line point of view, this is kind of annoying because the commands end up being quite long. Do you guys think something like Kconfig could help? Adrian -- 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, 6 months

2
2
0 0

Re: [TF-M] CMake flags

by Thomas Törnblom

Introducing a dependency on Kconfig may cause portability issues with some toolchains (IAR for instance) I am working on adding support for the IAR toolchain to Zephyr, and Kconfig is one of the issues I've run into. At least in Zephyr, the output from Kconfig is run through the C preprocessor and this causes issues with the IAR preprocessor so for now I use gcc for this step. Thomas Den 2020-06-12 kl. 07:32, skrev David Hu via TF-M: > > Hi Adrian, > > Actually we have been investigating configuration alternatives and > making some prototypes of Kconfig. > > Kconfig can bring some advantages: > > * It can setup configuration and check dependency before CMake > starts and therefore it can help CMake simplify dealing with the > mutual dependencies. For example, if CPU and arch options can be > configured in Kconfig, CMake can avoid the workaround to > re-configure compiler after parsing platform files. > * Kconfig can collect together the options which are distributed in > various CMake files. Developers can more easily understand the > options and their dependencies, compared with searching them all > around the build system. > > But Kconfig may not cover all the flags in command line. Flags such as > compiler selections, build type and project config file, may vary in > each build. It can be inconvenient to put them into Kconfig. > > Best regards, > > Hu Ziji > > *From:* TF-M <tf-m-bounces(a)lists.trustedfirmware.org> *On Behalf Of > *Adrian Shaw via TF-M > *Sent:* Friday, June 12, 2020 12:24 AM > *To:* Raef Coles <Raef.Coles(a)arm.com> > *Cc:* tf-m(a)lists.trustedfirmware.org > *Subject:* [TF-M] CMake flags > > Hi Raef. Thanks for the presentation today. > > If I remember correctly, TF-M's CMake has quite a lot of command line > flags now (the ones that are set with -D). And I think this will grow > in the future as more options are needed. > > From a command line point of view, this is kind of annoying because > the commands end up being quite long. Do you guys think something like > Kconfig could help? > > Adrian > > -- *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, 6 months

1
0
0 0

Re: [TF-M] CMake flags

by David Hu

Hi Adrian, Actually we have been investigating configuration alternatives and making some prototypes of Kconfig. Kconfig can bring some advantages: * It can setup configuration and check dependency before CMake starts and therefore it can help CMake simplify dealing with the mutual dependencies. For example, if CPU and arch options can be configured in Kconfig, CMake can avoid the workaround to re-configure compiler after parsing platform files. * Kconfig can collect together the options which are distributed in various CMake files. Developers can more easily understand the options and their dependencies, compared with searching them all around the build system. But Kconfig may not cover all the flags in command line. Flags such as compiler selections, build type and project config file, may vary in each build. It can be inconvenient to put them into Kconfig. Best regards, Hu Ziji From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Adrian Shaw via TF-M Sent: Friday, June 12, 2020 12:24 AM To: Raef Coles <Raef.Coles(a)arm.com> Cc: tf-m(a)lists.trustedfirmware.org Subject: [TF-M] CMake flags Hi Raef. Thanks for the presentation today. If I remember correctly, TF-M's CMake has quite a lot of command line flags now (the ones that are set with -D). And I think this will grow in the future as more options are needed. >From a command line point of view, this is kind of annoying because the commands end up being quite long. Do you guys think something like Kconfig could help? Adrian

4 years, 6 months

1
0
0 0

CMake flags

by Adrian Shaw

Hi Raef. Thanks for the presentation today. If I remember correctly, TF-M's CMake has quite a lot of command line flags now (the ones that are set with -D). And I think this will grow in the future as more options are needed. >From a command line point of view, this is kind of annoying because the commands end up being quite long. Do you guys think something like Kconfig could help? Adrian

4 years, 6 months

1
0
0 0

Re: [TF-M] TF-M Technical Forum call - June 11

by Anton Komlev

Hello, Agenda for today's Tech forum: 1. Ongoing MCUboot alignment update. 2. Build system improvements. Code sharing between bootloader and runtime firmware will be presented on the next call. Best regards, Anton From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Vincze via TF-M Sent: 05 June 2020 13:03 To: tf-m(a)lists.trustedfirmware.org Cc: nd <nd(a)arm.com> Subject: Re: [TF-M] TF-M Technical Forum call - June 11 Hi, I also would like to give a brief update on the status of the ongoing MCUboot alignment work. David V From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org<mailto:tf-m-bounces@lists.trustedfirmware.org>> On Behalf Of Tamas Ban via TF-M Sent: 05 June 2020 11:23 To: tf-m(a)lists.trustedfirmware.org<mailto:tf-m@lists.trustedfirmware.org> Cc: nd <nd(a)arm.com<mailto:nd@arm.com>> Subject: Re: [TF-M] TF-M Technical Forum call - June 11 Hi Anton, I would like to give a short presentation about crypto code sharing between bootloader and runtime firmware(SPE). Tamas 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: 03 June 2020 21:21 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] TF-M Technical Forum call - June 11 Hello, The next Technical Forum is planned on Thursday, June 11 at 15:00-16:00 UTC (US time zone). Please reply on this email with your proposals for agenda topics. Here are some local time examples: Location Local Time Time Zone UTC Offset Vancouver<https://www.timeanddate.com/worldclock/canada/vancouver> (Canada - British Columbia) Thursday, 11 June 2020, 08:00:00 PDT<https://www.timeanddate.com/time/zones/pdt> UTC-7 hours Chicago<https://www.timeanddate.com/worldclock/usa/chicago> (USA - Illinois) Thursday, 11 June 2020, 10:00:00 CDT<https://www.timeanddate.com/time/zones/cdt> UTC-5 hours Cambridge<https://www.timeanddate.com/worldclock/uk/cambridge> (United Kingdom - England) Thursday, 11 June 2020, 16:00:00 BST<https://www.timeanddate.com/time/zones/bst> UTC+1 hour Shanghai<https://www.timeanddate.com/worldclock/china/shanghai> (China - Shanghai Municipality) Thursday, 11 June 2020, 23:00:00 CST<https://www.timeanddate.com/time/zones/cst-china> UTC+8 hours Corresponding UTC (GMT) Thursday, 11 June 2020, 15:00:00<https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200611T1500> Best regards, Anton Komlev

4 years, 6 months

1
0
0 0

TF-M v1.1 - Heads up

by Shebu Varghese Kuriakose

Hi All, Just a heads up that TF-Mv1.1 tag is planned for middle to end of July. Code freeze of TF-M master is aimed around end of June to allow enough time for testing. Similar to TF-Mv1.0 and previous tags, v1.1 will include all TF-M changes in TF-M master available till code freeze in end of June. Availability of the tag will be notified via. this mailing list. Thanks, Shebu Technology Manager-TF-M, Arm Ltd.

4 years, 6 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

TF-M June 2020