Hi all,
The design document is merged as planned.
Thanks a lot for your review! Any further comment or suggestion is always comment. 😊
Best regards,
Hu Ziji
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of David Hu via TF-M
Sent: Monday, February 1, 2021 4:01 PM
To: tf-m(a)lists.trustedfirmware.org
Cc: nd <nd(a)arm.com>
Subject: [TF-M] Ask for final review on physical attack mitigation design
Hi all,
I’d like to merge the design document of physical attack mitigation in TF-M this week if no further comment.
May I ask you to take another look at the following document patch?
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7476
Best regards,
Hu Ziji
This patch was generated by git command automatically:
$ git add --renormalize .
It does change any contents of the files, except the line-endings in the repository.
Your existing local working tree should not be affected when you pick up it or later when it's merged.
The only file maintained manually is the .gitattributes
Best Regards,
Kevin
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Kevin Peng via TF-M
Sent: Friday, February 5, 2021 9:53 AM
To: tf-m(a)lists.trustedfirmware.org
Cc: nd <nd(a)arm.com>
Subject: [TF-M] TF-M git repo normalization
Hi all,
Following the git normalization topic of the tech forum yesterday, I checked TF-M.
It has not been enabled the git normalization feature.
I've made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283> to make this happen.
Please check out or rebase your work upon this patch to see any issues.
Your existing working tree should not be affected regarding the line-endings.
What is the normalization?
To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other.
Reference: https://git-scm.com/docs/gitattributes
Best Regards,
Kevin
Hi all,
Following the git normalization topic of the tech forum yesterday, I checked TF-M.
It has not been enabled the git normalization feature.
I've made a patch<https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8283> to make this happen.
Please check out or rebase your work upon this patch to see any issues.
Your existing working tree should not be affected regarding the line-endings.
What is the normalization?
To be simple, different developers on different Host OS can have different line-endings in their local working tree and do not need to worry about interference with each other.
Reference: https://git-scm.com/docs/gitattributes
Best Regards,
Kevin
Hi,
Looks like we have an empty agenda for tomorrow's forum. Let's use the time for the free discussion on any TF-M topic. Please raise questions / issues / improvements worth to be discussed within the community.
See you,
Anton
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Anton Komlev via TF-M
Sent: 28 January 2021 13:29
To: tf-m(a)lists.trustedfirmware.org
Cc: nd <nd(a)arm.com>
Subject: [TF-M] Technical Forum call - February 4
Hello,
The next Technical Forum is planned on Thursday, Feb 4 at 7:00-8:00 UTC (Asia 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
Hi Thomas,
Sorry about that. I have reproduced the issue on AN521 by copying over the lpcxpresso55s69 storage config. I'll investigate a fix on that platform, but will need you to verify it for me afterwards as I don't have that platform.
Kind regards,
Jamie
From: TF-M <tf-m-bounces(a)lists.trustedfirmware.org> On Behalf Of Thomas Törnblom via TF-M
Sent: 03 February 2021 13:30
To: tf-m(a)lists.trustedfirmware.org
Subject: Re: [TF-M] NXP lpcxpresso55s69 appears broken
Looks like this is the commit that breaks the nxp/lpcxpresso55s69 support:
---
PS C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m> git bisect good
6a3946aa017fa4da3953a825991f8ce755114637 is the first bad commit
commit 6a3946aa017fa4da3953a825991f8ce755114637
Author: Jamie Fox <jamie.fox(a)arm.com><mailto:jamie.fox@arm.com>
Date: Mon Dec 7 21:50:31 2020 +0000
Platform: TF-M ITS and PS HAL
...
---
Den 2021-02-03 kl. 13:54, skrev Thomas Törnblom via TF-M:
I have just fixed an IAR linking issue for the nxp/lpcxpresso55s69, see https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8251
I tried using the current sources, but it seems that there is some issues causing the board to run into a hard fault when built with GNUARM.
Not sure what commit caused the breakage.
Cheers,
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>
--
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>
Hi Jamie,
I’ll be happy to test here as well if you add me to the change request.
Best regards,
Kevin
On Wed, 3 Feb 2021 at 16:10, Jamie Fox via TF-M <
tf-m(a)lists.trustedfirmware.org> wrote:
> Hi Thomas,
>
>
>
> Sorry about that. I have reproduced the issue on AN521 by copying over the
> lpcxpresso55s69 storage config. I’ll investigate a fix on that platform,
> but will need you to verify it for me afterwards as I don’t have that
> platform.
>
>
>
> Kind regards,
>
> Jamie
>
>
>
> *From:* TF-M <tf-m-bounces(a)lists.trustedfirmware.org> *On Behalf Of *Thomas
> Törnblom via TF-M
> *Sent:* 03 February 2021 13:30
> *To:* tf-m(a)lists.trustedfirmware.org
> *Subject:* Re: [TF-M] NXP lpcxpresso55s69 appears broken
>
>
>
> Looks like this is the commit that breaks the nxp/lpcxpresso55s69 support:
> ---
> PS C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m> git bisect good
> 6a3946aa017fa4da3953a825991f8ce755114637 is the first bad commit
> commit 6a3946aa017fa4da3953a825991f8ce755114637
> Author: Jamie Fox <jamie.fox(a)arm.com> <jamie.fox(a)arm.com>
> Date: Mon Dec 7 21:50:31 2020 +0000
>
> Platform: TF-M ITS and PS HAL
> ...
> ---
>
> Den 2021-02-03 kl. 13:54, skrev Thomas Törnblom via TF-M:
>
> I have just fixed an IAR linking issue for the nxp/lpcxpresso55s69, see
> https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8251
>
> I tried using the current sources, but it seems that there is some issues
> causing the board to run into a hard fault when built with GNUARM.
>
> Not sure what commit caused the breakage.
>
> Cheers,
> 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 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
>
Looks like this is the commit that breaks the nxp/lpcxpresso55s69 support:
---
PS C:\Users\thomasto\Projects\tf-m4\trusted-firmware-m> git bisect good
6a3946aa017fa4da3953a825991f8ce755114637 is the first bad commit
commit 6a3946aa017fa4da3953a825991f8ce755114637
Author: Jamie Fox <jamie.fox(a)arm.com>
Date: Mon Dec 7 21:50:31 2020 +0000
Platform: TF-M ITS and PS HAL
...
---
Den 2021-02-03 kl. 13:54, skrev Thomas Törnblom via TF-M:
> I have just fixed an IAR linking issue for the nxp/lpcxpresso55s69,
> see https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8251
>
> I tried using the current sources, but it seems that there is some
> issues causing the board to run into a hard fault when built with GNUARM.
>
> Not sure what commit caused the breakage.
>
> Cheers,
> 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>
>
--
*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>
I have just fixed an IAR linking issue for the nxp/lpcxpresso55s69, see
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/8251
I tried using the current sources, but it seems that there is some
issues causing the board to run into a hard fault when built with GNUARM.
Not sure what commit caused the breakage.
Cheers,
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>
Hi all,
I'd like to merge the design document of physical attack mitigation in TF-M this week if no further comment.
May I ask you to take another look at the following document patch?
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7476
Best regards,
Hu Ziji
Oyvind,
Thanks for putting this together. Looks quite useful, and saves some
monotony debugging.
I put together a similar script but as a Python function for GDB:
https://gist.github.com/microbuilder/1677a27e4566a28b36a79f954f1dede6 ...
having this in C, however, means you don't need to have a Python-enabled
version of GDB.
Best regards,
Kevin
On Fri, 29 Jan 2021 at 11:33, Rønningstad, Øyvind via TF-M <
tf-m(a)lists.trustedfirmware.org> wrote:
> Hi everyone
>
> I wanted to make it easier to debug HardFaults/BusFaults/SecureFaults in
> TFM, since I’ve gotten quite a few of them while adding the nrf platforms.
>
> I have created a proposal in
> https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/7891 and
> would like to get some comments on the general idea.
>
> The proposal gathers a number of different values, especially the ones
> that are harder to retrieve in a debugger, like the fault status registers
> in SCB.
>
> The values are placed in memory so they can be inspected in a debugger,
> and if built with -DTFM_SPM_LOG_LEVEL=TFM_SPM_LOG_LEVEL_DEBUG they are also
> printed.
>
> Here is an example of the printout:
>
> FATAL ERROR: HardFault
>
> Here is some context for the exception:
>
> EXC_RETURN (LR): 0xFFFFFFBD
>
> Exception came from non-secure FW in thread mode.
>
> MSP(_S): 0x200007F8
>
> PSP(_S): 0x20000F28
>
> Exception frame at: 0x200176D8
>
> R0: 0x0000003E
>
> R1: 0x00000001
>
> R2: 0x00000001
>
> R3: 0xFFFFFFFF
>
> R12: 0x00000000
>
> LR: 0x00050623
>
> PC: 0x00050626
>
> CFSR: 0x00000000
>
> BFAR: Not Valid
>
> MMFAR: Not Valid
>
> HFSR: 0x40000000
>
> SFSR: 0x00000000
>
> SFAR: Not Valid
>
>
>
> BR, Øyvind Rønningstad
> --
> TF-M mailing list
> TF-M(a)lists.trustedfirmware.org
> https://lists.trustedfirmware.org/mailman/listinfo/tf-m
>
