Tue, Jun 11
Mon, Jun 3
Thanks, guys. I think this issue could be closed. Only one test patch is not merged.
Wed, May 29
May 23 2019
May 5 2019
The patch is here:
Apr 30 2019
Apr 28 2019
A new patch has been provided, to avoid set response file as default:
Apr 24 2019
This problem is not the one NXP reported. This is the models conflict in regression tests. Summer is doing a task and trying to fix this.
Apr 19 2019
Apr 18 2019
Apr 16 2019
Apr 12 2019
This issue is related to a further design change of retrieve NS parameters; let me down the priority for it and keep it here as a reminder.
Apr 9 2019
Mar 30 2019
Mar 28 2019
After Jinja2 is merged, there is a template for GCC and ARMCLANG. Close this task.
Mar 27 2019
Mar 26 2019
Mar 25 2019
Mar 21 2019
Mar 18 2019
Tried latest merged master branch on MUSCA_A and IPC works fine. Mark this task as resolved.
Mar 15 2019
A short question, has your platform defined __FPU_PRESENT=1?
Mar 14 2019
Mar 13 2019
Patches for the fixing:
Does it mean that patches mentioned in T95 could be merged?
Fatal error: L6002U: Could not open file @CMakeFiles/tfm_s.dir/objects1.rsp: No such file or directory Finished: 0 information, 0 warning, 0 error and 1 fatal error messages. make.exe: *** [app/secure_fw/CMakeFiles/tfm_s.dir/build.make:167: app/secure_fw/tfm_s.axf] Error 1 make.exe: *** [CMakeFiles/Makefile2:252: app/secure_fw/CMakeFiles/tfm_s.dir/all] Error 2 make.exe: *** [Makefile:118: all] Error 2
I am using ARMCLANG build on AN521, with latest master branch:
The patch is created, do the test now. Expect to publish it soon for review.
I saw the document update patch, but cmake 3.10 still fails in my side. Which means the document is updated first before cmake change?
Mar 12 2019
Mar 11 2019
Hi @mikisch81 ,
We have spotted this issue, and now thinking the best solution for it. Please ping me if you have any updates for this task, thanks!
Since you have found the root cause, can you provide a fix for that? You can push to branch feature-ipc.
Mar 1 2019
Feb 21 2019
I read the test code and got some questions:
- There are two partitions involved, can you tell which psa_wait returned wrong signal code and show me the debug message (I noticed SP2 would print out something if psa_wait returned error message)? It would be nice if you can tell the line number in the source you shared.
- It looks like the case is: client -> SP1 -> SP2, three roles get involved in testing, is that true? Or there are more roles?
- I can not find TF-M adapter layer in cloned source of mbed-os, is the code showed as same as the working version on your local?
For PSA related ticket please add me as subscriber. Thanks.
Feb 19 2019
Feb 18 2019
Validated and merged. Please help to close this ticket.
Validated and merged.
Can you help to close this item? Thanks.
Feb 12 2019
That's a quick fix for removing the blocker. After T244 is solved this patch maybe not relevant, the purpose is no affecting API user behaviour (no workarounds) even the connection handle allocation mechanism is changed. Since mechanism changing may not happen soon, let's apply this one first.
Feb 1 2019
Jan 31 2019
Thanks for submitting. We will investigate it and try to find out a plan.
Jan 29 2019
This line is for extracting NSPE invec/outvec from invec due to parameters number limitation. The anti-TOCTOU is added in line: 177 now working for secure partitions.
Jan 28 2019
Thanks, Alexander, currently we copy into a local buffer and then moved to the message instead of moving to message directly due to message buffer allocation limitation (https://developer.trustedfirmware.org/T195)
Jan 24 2019
Jan 23 2019
Jan 22 2019
Task moved to :https://developer.trustedfirmware.org/T185
Jan 11 2019
No problem to handle this task, since it is needed eventually. Current no duplicated item for this, the only thing is if there is a bigger task would cover this item.
Dec 27 2018
Version 3.7 won't report the issue in my side.
Dec 26 2018
Gerrit review items: