Hi Bohdan,

Could you share a bit more info on the issue with BL2 variable?

As you know, TF-M uses MCUBoot from a separate repo also. Believe it’s not difficult to build TF-M without BL2 but not sure what is your problem exactly.

True, the build system is a bit complicated, but on positive side– that is the simplified version. It was discussed on the tech forum twice, first on 11.06.2020 and second on 01.10.2020. By some reason, materials from the 2^nd session are not available so I attached the slides here.

We can touch the topic on the forum tomorrow, if you wish.

Hope that helps,

Anton

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Bohdan Hunko via TF-M
Sent: Tuesday, September 28, 2021 11:44 AM
To: tf-m@lists.trustedfirmware.org
Cc: Kostiantyn.Tkachov@infineon.com; Roman.Mazurak@infineon.com; Hennadiy.Kytsun@infineon.com
Subject: [TF-M] Enablement of external bl2 builds

Hi everyone,

When adding support for new platform we ran into an issue with BL2 variable.

In our architecture we have Bootloader based on MCUboot (aka BL2) but we are not planning to build it with TF-M.

Bootloader would be separate repo and be built separately.

So we need the way to build TF-M with FWU service and shared data definitions when BL2=OFF.

I was trying to add support for this but was not able to do this because build structure is quite complicated.

Does anyone have ideas or suggestions about the way we can implement this feature?

Best regards,

Bohdan Hunko

Cypress Semiconductor Ukraine

Engineer

CSUKR CSS ICW SW FW

Mobile: +38099 50 19 714
Bohdan.Hunko@infineon.com