Hi,

During the level3 prototyping, we found using a unified sct/ld/file would be hard because we are trying to cover platform-specific setting in ONE place.

The biggest concern of preventing spreading the LD is: if there are COMMON changes then every platform source needs to be updated.

I believe the COMMON change is the arrangement of ARoT and PRoT, those platform-specific things such as CODE_SRAM and MPU alignment issue should not be covered inside the common sct/ld/icf.

Not sure if all these format support #include but as we are using a template so it should be possible to put COMMON settings inside a COMMON template and let platform to contain these common part and then add the specific settings.

I have a rough idea (see above) and need more investigation, request for ideas/concerns about this part.

Thanks.

/Ken

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Shawn Shan via TF-M
Sent: Wednesday, August 5, 2020 1:27 PM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] Proposal to separate SCT/LD into each platform folder

Hi all,

There are many differences in linker scripts between each platform. Using a common_s.sct/ld makes it too complicated.

And at the same time, in order to achieve isolation level 3, the position of the sessions in scatter and linker script file needs to be adjusted.

The common linker scripts would be more complicated with isolation L3.

So I would like to propose to have dedicated linker scripts for platforms with enough differential arrangements.

What’s your opinion on this?

Best regards,

Shawn