Thanks.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mar 18 2019
Mar 17 2019
@KenLSoft Yes, our platform (LPC55S69 by NXP) does defined __FPU_PRESENT=1U.
Mar 15 2019
@mikisch81
A short question, has your platform defined __FPU_PRESENT=1?
Mar 14 2019
Patches for the fixing:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/713/
Mar 13 2019
i can confirm that the patch is working on mbed-os with NXP LPC55S69
Patches for the fixing:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/712
No. T95 needs deeper investigation to check what cmake version the fix supports and if all aspects are addressed. Response files not only affect the linker but the archiver too.
There was an important bugfix for response file handling merged into cmake 3.9 so we might need to drop support for anything below 3.10.
Does it mean that patches mentioned in T95 could be merged?
The response file problem is another ticket. See https://developer.trustedfirmware.org/T95
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[2]: *** [app/secure_fw/CMakeFiles/tfm_s.dir/build.make:167: app/secure_fw/tfm_s.axf] Error 1 make.exe[1]: *** [CMakeFiles/Makefile2:252: app/secure_fw/CMakeFiles/tfm_s.dir/all] Error 2 make.exe: *** [Makefile:118: all] Error 2
and what error do you get?
Hi,
I am using ARMCLANG build on AN521, with latest master branch:
https://git.trustedfirmware.org/trusted-firmware-m.git/commit/?h=refs/heads/master&id=807fedbb8070b6d735e1c9e2103e6c1ea632fe8c
The patch is created, do the test now. Expect to publish it soon for review.
Thanks.
In my test environment I could not re-create any failure. Can you please provide more details about your case?
Hi Gyuri,
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?
Thanks.
Mar 12 2019
In T273#3082, @mikisch81 wrote:Can you elaborate on the root cause?
Mar 11 2019
We are currently pre-occupied with the 5.12 release, you can look at Mbed-os PR#10027 to see how we solved this issue.
Can you elaborate on the root cause?
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!
Hi @mikisch81,
Since you have found the root cause, can you provide a fix for that? You can push to branch feature-ipc.
Thanks.
Mar 10 2019
Inside the svc_handler if you check LR, which holds EXC_RETURN.
We are experiencing this issue on the NXP LPC55S69 MCU, which is Cortex-M33-FE core.
Mar 7 2019
Related changes:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/700/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/701/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/685/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/702/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/703/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/704/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/705/
Mar 5 2019
Fix for this is provided with https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/635/
Thanks.
Mar 4 2019
Concerned patches are:
The following changes are further created for this issue:
Patches for this ticket: https://review.trustedfirmware.org/c/trusted-firmware-m/+/669
Could you create a new Task issue for it?
Mar 3 2019
Hi all,
Mar 1 2019
Issue resolved by https://developer.trustedfirmware.org/T192
So there are two issues:
- The first issue should have been fixed in the above two patches.
- The second issue had been fixed in this patch: https://review.trustedfirmware.org/c/trusted-firmware-m/+/612. This patch had been merged into "feature-ipc" branch on Feb 12. So, please update your to align with the newest code version.
Feb 28 2019
We checked both patches, and they do not seem to fix the issue
After extensive testing no blocking issues could be identified and this effort turned to be a documentation update. See https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/661/
All mentioned cmake versions work fine win the build-system..
Feb 27 2019
Add another patch to fix this problem in GCC: https://review.trustedfirmware.org/c/trusted-firmware-m/+/666/1
Fix it on this patch: https://review.trustedfirmware.org/c/trusted-firmware-m/+/662/1. Please check it on your board.
Feb 26 2019
Feb 25 2019
Feb 24 2019
- from my latest debug session i found that psa_wait returns the correct signals, but by the time psa_get tries to handle them the signals shut down and then psa_get will go into panic
- client sends a string to SP1, SP1 doubles the string and calls SP2, SP2 should reverse the string and return it to SP1 which will return it to client.
- i dont know
I can verify that https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/653/ works on our code.
Feb 22 2019
Hello, this bug had been fixed in this patch: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/653/
Feb 21 2019
Hi Oren,
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?
Hi Oren,
For PSA related ticket please add me as subscriber. Thanks.
Feb 20 2019
The change which fixes this issue is available here: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/650/
Feb 19 2019
Related change:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/552/
Feb 18 2019
Update the API version number to 1.0-beta:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/641/
The change for this issue has been merged.
The change for this issue have been merged.
Validated and merged. Please help to close this ticket.
Validated and merged.
Can you help to close this item? Thanks.