- User Since
- Jun 11 2018, 8:53 AM (174 w, 5 d)
Thu, Sep 23
The 1.4.x branch is only intended for security fixes.
Sat, Sep 18
I think you're right.
The Secure PendSV is masked by NSPE, although it has the same priority value 0x80.
It has to have a lower value to preempt the NSPE, having an equal priority value does not work.
Fri, Sep 17
Aug 3 2021
If it's an RTX issue, then please contact RTX people. Thanks very much.
Jul 29 2021
I think it's not the priority issue.
I'm testing with:
- The NS is bare metal (is that the terminology? Only a main function, NO RTOS)
- The NS calls test_app(NULL) directly - some RTOS dependencies have been removed such as the PS test suites and the tfm_ns_interface implementations.
- Before the test_app was called, I set the BASEPRI_NS to 32 using the debugger
Jul 28 2021
Hi @ioannisg , my understanding is the same as yours.
In theory, there should be any issues.
May I ask which service were you connecting to and got the invalid handle?
And could you provide more information on how the IRQs are locked? I have not ever used the BASEPRI_NS.
Any other information like the version of TF-M you are integrating and build configurations would also help.
Jul 20 2021
OK, could you take this issue, @adeaarm ?
Jul 19 2021
Thanks Antonio for the information.
Since this is not a TF-M issue, suggest closing it.
Dec 23 2020
Apparently, the patch didn't work for GCC. Sorry about that.
It has been reverted for the time being:
Oct 28 2020
Oct 13 2020
Sep 9 2020
Several preparation patches including scatter file adjustments.
Aug 27 2020
Jul 27 2020
Jul 24 2020
Jul 10 2020
Jun 11 2020
Jun 9 2020
Jun 4 2020
Patches for tf-m-tests:
May 29 2020
Apr 13 2020
Patch merged. Close it.
Apr 10 2020
Apr 2 2020
Mar 27 2020
Mar 19 2020
Mar 5 2020
Patch for addressing the ticket:
Mar 3 2020
Patch made to fix:
Feb 14 2020
It's configured in CommonConfig.cmake, line #321.
The name is CONFIG_TFM_ENABLE_CTX_MGMT.
Feb 13 2020
Hi Reinhard, FYI the patches have been merged.
Jan 22 2020
Jan 16 2020
Jan 9 2020
Jan 8 2020
There are some patches for conditional build for secure context management APIs:
Dec 26 2019
Patch for the task:
The patch is merged, so close it.
Patches are merged, so close it.
Dec 20 2019
Dec 6 2019
Patches for this ticket:
The patch for address this: https://review.trustedfirmware.org/c/trusted-firmware-m/+/2738/
The topic of the patches for this:
Nov 29 2019
Sure, I've worked out some patches and are testing and refining them, will submit them for review if no issues found.
Nov 22 2019
Nov 21 2019
Patches for the ticket:
Oct 23 2019
Oct 22 2019
The patch to address this task:
Oct 21 2019
Oct 9 2019
Aug 13 2019
Aug 2 2019
Patches for additional refactoring:
Hi @qixiang , the problem is right about memory, I don't think we have enough space to support debug options for crypto on both platforms.
If you agree, can we close it as "won't fix". Thanks.
Jun 26 2019
May 27 2019
May 17 2019
May 8 2019
May 7 2019
Apr 25 2019
First, correct the testing result: it's the NS interface tests are failing. Partition index 0 is just the NS world and it is not allowed the "start_partition".
Apr 19 2019
Apr 4 2019
Mar 13 2019
Mar 4 2019
Patches for this ticket: https://review.trustedfirmware.org/c/trusted-firmware-m/+/669
Feb 26 2019
Feb 14 2019
This task is addressed by the following commits: