Remove log.sh/log.bat from code base:
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 15 2020
Jan 13 2020
Change for this issue had been merged
Jan 10 2020
Patch is uploaded to https://review.trustedfirmware.org/c/trusted-firmware-m/+/3107.
The root cause is:
- When building SPRTL, arch type is fetched from GNUARM cmake file since SPRTL CMake file is included with add_subdirectory() instead of include().
- The CM0+ arch type should be "armv6s-m". However, it is set to "armv6-m" in GNUARM cmake file, which stands for CM0. CM0 doesn't support SVC. Thus the build failed.
- Previously, the psa_client.c and` psa_service.c` were not in SPRTL folder. When building the both files, cpu type is fetched which is correct.
Patch had been merged.
All patches had been merged to the master branch.
Jan 9 2020
Jan 7 2020
Change for this issue had been merged as a hotfix
Change for this issue: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3051/
Jan 6 2020
Patch link:
Jan 4 2020
The problem is solved.
Jan 3 2020
Dec 31 2019
Dec 28 2019
Dec 27 2019
Dec 26 2019
Patch for the task:
https://review.trustedfirmware.org/c/trusted-firmware-m/+/2953/1
Dec 23 2019
Add PSA_DOOLBELL signal to assigned_signals
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2927/
Dec 20 2019
Bug spotted while creating test suite:
Add dependence deadlock check: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2924/
Align psa_wait() to PSA FF 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2380/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2402/
Align psa_close to psa ff 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2487/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2444/
Detect the current handling handle in psa_call
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2768/
Enhance the psa_call to process the invalid message
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2769/
Add an ipc test for psa_call
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2818/
Align psa_version to PSA FF 1.0.0
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2920/
As the PSA FF 1.0.0 mentioned in 3.5.2:
Add a doc about how to add a secure partition: https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2921/
Dec 19 2019
Dec 18 2019
Keep this task here since there would be another update.
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 17 2019
Patch had been merged to the master branch.
Dec 16 2019
Dec 14 2019
Related reviews:
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2814/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2815/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2816/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2817/
- https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3046/
How can we add name? To do it we have to follow best write my essay sites where we are just waiting for those things where we just want to take from description and all which we need. So here are some simple method which tell you to add.
Dec 13 2019
Dec 12 2019
patches to implement panic-related functions:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2779/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2780/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2781/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2782/
Dec 11 2019
Dec 6 2019
Related changes:
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2679/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2742/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/2954/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3139/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3140/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3141/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3142/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3143/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3144/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3145/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3146/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3147/
https://review.trustedfirmware.org/#/c/trusted-firmware-m/+/3148/
Patch had been merged into the master branch.
The topic of the patches for this:
https://review.trustedfirmware.org/q/topic:%22out_of_tree_build%22+(status:open%20OR%20status:merged)
Dec 5 2019
Snapcraft distributes builds for the latest stable versions of CMake: https://snapcraft.io/cmake
Perhaps consider recommended it be installed through that? On Ubuntu it is as simple as sudo snap install cmake --classic.
Changes for this issue had been merged.
Dec 4 2019
Snapcraft distributes builds for the latest stable versions of CMake: https://snapcraft.io/cmake