User Details
- User Since
- May 23 2018, 7:22 AM (97 w, 3 d)
Feb 13 2020
Feb 12 2020
Hi Andrej,
Hi Andrej,
I have updated patch and test with FP enabled in my side and it works. Can you take a try on your side?
Thanks.
Feb 11 2020
Thanks. I just found the patch missed something, I will re-create a patch to update that.
Feb 10 2020
Feb 6 2020
Patch created:
Feb 3 2020
Thanks for your input, that helps much. I will create fixes when I back to office.
Feb 1 2020
BTW, can you update other tfm_arch_*.h as well?
We can help verify the changes not covered in your side.
Hi Andrey,
Jan 31 2020
More hints for you:
Sorry for the late response and thanks for the findings. Could you share your image binary so that I could take a try? I got a board but not set up the environment yet.
Jan 25 2020
Looks like this was caused by the push operation, and it was caused by accessing an address out of ARM_LIB_STACK.
Jan 22 2020
Jan 19 2020
Hi Andrei,
Jan 16 2020
Jan 15 2020
Jan 13 2020
Remove log.sh/log.bat from code base:
Jan 9 2020
Jan 7 2020
Jan 3 2020
Dec 31 2019
Dec 30 2019
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2489
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2955
Dec 27 2019
Dec 20 2019
As the PSA FF 1.0.0 mentioned in 3.5.2:
Dec 18 2019
Keep this task here since there would be another update.
Now the parameter packing method is changed and this problem is not there.
Check the patch:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2445
Now one handle could only have one message body, and this message body is allocated while handle is created. So there is no resource allocation issue for the message (we do have this problem for handle but this ticket is not the case). Close this task as done.
Dec 16 2019
The plan is:
- Will use customized implementation of 'printf' to avoid reference low-level APIs and __stdout.
- This 'printf' will call USART directly.
- SVC printf will be removed. No log output under SVC mode.
Dec 13 2019
Attach the diagram.
Nov 14 2019
For 'Cooperative Scheduling Rules':
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2466
Well. So the first step we are creating patches to add power/wait; after this we plan to purge the SVC calling to uart driver.
Nov 12 2019
TFM is involving a self-implemented printf, which means the existing solution is not applicable for re-targeting toolchain provided printf into putc/write.
So this can be a solution:
Nov 11 2019
Thanks. The even recorder looks quite keil specific. Hmmm, let's try to find some other way.
Oct 8 2019
Hi Robert,
Shall we involve mbed-crypto people for this topic?
Sep 18 2019
Patch created:
Mark this task as resolved since IPC is available.
Sep 3 2019
I think the mechanism is changed during this patch:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/1744
Done by David Hu's patch:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/1734
Aug 29 2019
Aug 27 2019
Started progress on it, investigating the effect.
Aug 19 2019
Aug 17 2019
Aug 15 2019
Aug 1 2019
Patch for master branch updated:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/1686
Jul 29 2019
You can do it in feature-ipc branch first. I will take a look if I could cherry-pick it back to master, or I will wait for a merge from the feature-ipc branch.
I think these changes are covered by:
I will start a series of patches for this issue. Check mailing list for details.
Hi David, since you are changing the memory checking related topics, can you help to do this task as well?
Resolve the changes since no response. We can re-open it if there are still concerns.
Jul 18 2019
Append a tiny patch to update the document path:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/1591
Jul 15 2019
Jul 9 2019
Another (final) patch:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/1487
Jul 3 2019
Thanks, that is helpful. Will let you know after the feature is created.
Hi Kevin,
Can you help to take a look?
-Ken
Hi Qixiang,
Can you help to :
- provide the version customer are using
- provide the solution you have created?