Status update

Change for this issue had been merged.

Change for this issue: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4743

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4730

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

Hi Ryan,

Hi Varun,
Yes, both are possible, but if I understand you correctly, they are out of scope for the Phase 2 project.

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?

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.

use different 'inc' file and int function for different models.
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4629/1
move spm header files to spm folder:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4630/3

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4630/1

Other commits which enables certain TF-M related features with upstream MCUboot v1.6:

Looks like TSP for imx8mm platform is not yet supported. Error indicates that TSP platform makefile
is absent in the platform directory <./plat/imx/imx8m/imx8mm/ >.

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4571
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4572
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4573

This patch fixes the issue https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4533

One more patch for this for new platform: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4562

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4548

patches link:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4545
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4546
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4547
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4644
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5229

Patch is ready:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4544

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/4535

More patch:
https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/4513

A new mechanism for these libc API is under development, see this:

Curious, noted is printf to be redesigned. What about malloc, calloc, and other libc functions that currently rely on a common RW section. That is the App RoT won't have access (and shouldn't have access) to say a common heap through libc. Has this been considered?