Page MenuHomePhabricator

ioannisg (Ioannis Glaropoulos)
User

Projects

User does not belong to any projects.

User Details

User Since
Oct 8 2020, 1:38 PM (36 w, 2 d)

Recent Activity

Thu, Jun 3

ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

As you know, for secure and non-secure side are closely related in TF-M. In latest TF-M v1.3 release, FP support (in secure side either non-secure side) are not official announced, so the problem you reported is not a TF-M bug.

Thu, Jun 3, 8:05 AM · Trusted Firmware M

Tue, Jun 1

ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

Hi Feder,
Honestly, I've only faced this issue when doing some advance scheduling manipulations on the Non-Secure side (modifying LSPACT, FPCA, etc.), so not in mainline TF-M/RTOS use-cases. Please disregard it for now.

Tue, Jun 1, 12:08 PM · Trusted Firmware M

Mon, May 31

ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

Any updates here, Feder?

Mon, May 31, 9:15 AM · Trusted Firmware M

Thu, May 27

ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

However, this is only a partial solution. That is because a Secure thread re-scheduling will clear the .FPCA flag, but leave the LSPACT set, meaning that a NS IRQ with FP instructions will trigger again an FP stacking. But this FP stacking will be done on the memory where FPCAR is pointing at, and FPCAR is only updated in exception entry, if .FPCA is set. As a result, it does not seem that you avoid a stack corruption.

Thu, May 27, 8:06 AM · Trusted Firmware M
ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

Hi Feder, correct; setting CPACR_S solves the problem of Secure No-Coprocessor Usage Fault.

Thu, May 27, 7:36 AM · Trusted Firmware M

Wed, May 26

ioannisg assigned T926: log: UART drivers and libraries are compiled in when log level is set to "silence" to Anton-TF.

Anton, could you please, suggest an assignee for this one? Thanks!

Wed, May 26, 1:20 PM
ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

Hi Feder,

Wed, May 26, 10:42 AM · Trusted Firmware M

May 18 2021

ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

I tried this on my side on STM32L562e_dk board with TF-M repo: enable "-mfloat-abi=softfp" in NS side and use TF-M default "-mfloat-abi=soft" option, and changed FP registers in non-secure thread first, then do PSA call. When system is in secure thread mode, no crash found even FPCCR_S.LSPACT = 1.

May 18 2021, 8:50 AM · Trusted Firmware M
ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

Do you have FP instruction in secure thread? If there is no FP instruction, the processor will not stack FP registers even LSPACT flag is set.
I tried this on my side on STM32L562e_dk board with TF-M repo: enable "-mfloat-abi=softfp" in NS side and use TF-M default "-mfloat-abi=soft" option, and changed FP registers in non-secure thread first, then do PSA call. When system is in secure thread mode, no crash found even FPCCR_S.LSPACT = 1.

May 18 2021, 8:45 AM · Trusted Firmware M

May 13 2021

ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

TF-M currently support "-mfloat-abi=soft" as default, but doesn't support the setting in Zephyr "-mfloat-abi=softfp". Because they are totally different things.

May 13 2021, 5:56 PM · Trusted Firmware M
ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

Yes, it crashes even without Lazy Stacking. It is a bit more deterministic as is. It crashes in the first secure exception entry, after the transition to secure domain from non-secure.

May 13 2021, 8:26 AM · Trusted Firmware M
ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

But for Zephyr, are you using soft FP or hardware FP?

May 13 2021, 8:12 AM · Trusted Firmware M

May 12 2021

ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

Hi Feder,

May 12 2021, 12:36 PM · Trusted Firmware M

May 3 2021

ioannisg triaged T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU as High priority.

Setting this to High for now - but feel free to re-triage this was not appropriate.

May 3 2021, 8:21 AM · Trusted Firmware M
ioannisg added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

Hi Feder,

May 3 2021, 8:04 AM · Trusted Firmware M

Apr 27 2021

ioannisg created T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.
Apr 27 2021, 9:12 AM · Trusted Firmware M