Fri, Jul 10
Thu, Jul 9
Wed, Jul 8
This problem has been fixed for quite a while, close it.
This issue has the same underlying cause as T696 so closing as duplicate.
Tue, Jul 7
There is an issue with Musca-B1 QSPI flash that causes this failure. The fix is under investigation.
This is an issue with the way the tests are done:
Fri, Jul 3
Thu, Jul 2
split the core part into small patches for easier review:
Wed, Jul 1
Tue, Jun 30
Secure Partition HAL patches:
Mon, Jun 29
Pursuing Jose's early work through Google gerrit interface.
We'll provide more design details in the shared SPM doc.
Fri, Jun 26
Thu, Jun 25
Change for this issue had been merged.
Change for this issue: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4743
Wed, Jun 24
Tue, Jun 23
Thanks for your comments and clarification. I should have updated this ticket with the information provided in the mail list, in order to keep them in sync.
/home/lm/work/gcc-linaro-7.5.0-2019.12-x86_64_aarch64-linux-gnu/bin/aarch64-linux-gnu-ld: invalid origin for memory region RAM
Makefile:721: recipe for target 'build/imx8mm/release/bl32/bl32.elf' failed
make: *** [build/imx8mm/release/bl32/bl32.elf] Error 1
Mon, Jun 22
Yes, both are possible, but if I understand you correctly, they are out of scope for the Phase 2 project.
Sun, Jun 21
Hi, for the static analysis checks, is it possible to update/increase the rules per platform? Also, is it possible to introduce more scanners for a platform?
Fri, Jun 19
Thank you for your reply.
I noticed this as well, and I was on the verge of submitting a patch until I looked into it further and decided that the current default is justifiable.