Update glossary: https://review.trustedfirmware.org/c/trusted-firmware-m/+/4139/
Core HAL design: https://review.trustedfirmware.org/c/trusted-firmware-m/+/4076/
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
May 22 2020
May 22 2020
• pefeced347 added a comment to T398: Initial support for IAR Embedded Workbench for Arm tool chain.
May 20 2020
May 20 2020
May 18 2020
May 18 2020
May 15 2020
May 15 2020
The memory limit issue could also be fixed by:
As I saw the memory limit issue also present in the non-secure scatter files.
May 14 2020
May 14 2020
May 13 2020
May 13 2020
May 11 2020
May 11 2020
May 7 2020
May 7 2020
davidhuziji added a project to T744: Improve secure function entry point of Library model: Trusted Firmware M.
davidhuziji triaged T743: Mbed-crypto persistent key builds fail with GNUARM when Protected Storage is disabled as High priority.
May 6 2020
May 6 2020
May 5 2020
May 5 2020
Have just pushed the IAR support for this.
May 4 2020
May 4 2020
Once this gets merged I’ll provide a patch to allow building with IAR.
May 3 2020
May 3 2020
For the patch above, see: https://review.trustedfirmware.org/c/trusted-firmware-m/+/4018
Apr 30 2020
Apr 30 2020
The attached patch should resolve the issues, but I'll get these fixes merged in ASAP.
This seems to be the offending commit, but I'm not sure how this was missed when I did the test builds pre-merge:
Looks like 8e65396a causes build failures for this.
Apr 29 2020
Apr 29 2020
Since the change referred to in the original issue (https://review.trustedfirmware.org/c/trusted-firmware-m/+/1123) has been abandoned with an alternative added to the comments for that review, I am closing this thread.
I suggest that considering the time elapsed since the last comment to open a new issue and refer back to this if there are related comments on the present state of the project.
The aforementioned fix was merged on 26 July, 2019. Closing this issue.
Apr 27 2020
Apr 27 2020
Apr 23 2020
Apr 23 2020
Sherryzhang2 added a project to T679: Fix Non-Secure stacks over-allocated issue: Trusted Firmware M.
Sherryzhang2 updated the task description for T718: The actual MSP stack size is 0 on AN539 nonsecure and the MSP stack is over-allocated in sct/ld file.
Sherryzhang2 renamed T718: The actual MSP stack size is 0 on AN539 nonsecure and the MSP stack is over-allocated in sct/ld file from The actual MSP stack size is 0 on AN539 nonsecure to The actual MSP stack size is 0 on AN539 nonsecure and the MSP stack is over-allocated in sct/ld file.
Apr 22 2020
Apr 22 2020
davidhuziji updated subscribers of T717: Conflict in task notification in NS mailbox in dual-cpu TF-M.
Apr 20 2020
Apr 20 2020
Fix has been merged
Apr 14 2020
Apr 14 2020
Apr 13 2020
Apr 13 2020
kevin-peng-hao added a comment to T689: Add some logs printing in NS to indicate the whole system has booted up.
Patch merged. Close it.
Apr 10 2020
Apr 10 2020
I think this item is covered by other ongoing tasks, so close it.
Apr 8 2020
Apr 8 2020
Apr 6 2020
Apr 6 2020
Please note, this has NOT been tested with ARMCLANG, only with GNUARM. Further testing and work is required for ARMCLANG support.
Apr 2 2020
Apr 2 2020
matetothpal triaged T704: Build: Verify that __thumb2__ define is present when CPU architecture is properly set as Low priority.
kevin-peng-hao renamed T644: Build system: clean up, minor refines and corner case fixes from Build system: clean up and minor refines to Build system: clean up, minor refines and corner case fixes.
Mar 30 2020
Mar 30 2020
soby-mathew added a comment to T694: Boot up fails if there is unexpected data in flash on Musca-A2.
Internal ref: https://jira.arm.com/browse/IOTPSW-2914
Mar 30 2020, 10:03 AM · Restricted Project
soby-mathew added a comment to T693: Using test NV counters causes protected storage to be invalid after reboot.
Internal ref : https://jira.arm.com/browse/IOTPSW-2861
Mar 30 2020, 9:51 AM · Restricted Project
Internal ref : https://jira.arm.com/browse/IOTPSW-2826
soby-mathew added a comment to T696: After PSA Arch FF test failure, Musca-B1 boot fails when SST/ITS are using Flash .
Internal ref: https://jira.arm.com/browse/IOTPSW-2801
Internal ref: https://jira.arm.com/browse/IOTPSW-2817
Mar 27 2020
Mar 27 2020
Mar 26 2020
Mar 26 2020
This causes random failure in PSA Arch ITS and PSA Arch PS tests.
See related Musca-A2 issue here : https://developer.trustedfirmware.org/T694
soby-mathew added a comment to T694: Boot up fails if there is unexpected data in flash on Musca-A2.
We would need to support versioning of SST FS data and also have mechanisms to detect if the flash is clean or in consistent state.
Mar 26 2020, 3:29 PM · Restricted Project
Mar 26 2020, 3:28 PM · Restricted Project
soby-mathew updated the task description for T693: Using test NV counters causes protected storage to be invalid after reboot.
Mar 26 2020, 9:33 AM · Restricted Project
soby-mathew updated the task description for T693: Using test NV counters causes protected storage to be invalid after reboot.
Mar 26 2020, 9:32 AM · Restricted Project
soby-mathew added a comment to T693: Using test NV counters causes protected storage to be invalid after reboot.
Internal ref : https://jira.arm.com/browse/IOTPSW-2808
Mar 26 2020, 9:30 AM · Restricted Project
soby-mathew added a comment to T693: Using test NV counters causes protected storage to be invalid after reboot.
This issue is also seen on Musca-A board.
Mar 26 2020, 9:29 AM · Restricted Project
soby-mathew created T693: Using test NV counters causes protected storage to be invalid after reboot.
Mar 26 2020, 9:24 AM · Restricted Project
Mar 25 2020
Mar 25 2020
soby-mathew added a comment to T692: AN521 FVP soft reset via AIRCR does not reset MPC / PPC / MPU during PSA FF test.
This is an issue on FVP. It will case the system cannot boot up after a warm reset. So as a workaround, we have to skip BL2 when testing.
soby-mathew added a comment to T692: AN521 FVP soft reset via AIRCR does not reset MPC / PPC / MPU during PSA FF test.
The output hangs at this point :
Trying ::1... Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. [INF] Starting bootloader [INF] Image 0: version=0.0.0+5, magic= good, image_ok=0x3 [INF] Image 1: No valid image [INF] Booting image from the primary slot [INF] Bootloader chainload address offset: 0x80000 [INF] Jumping to the first image slot [Sec Thread] Secure image initializing! TFM level is: 0x00000001 [Sec Thread] Jumping to non-secure code...
This is a known limitation of CC-312 and hence will not be fixed in TF-M code.
Update from Tamas