Thanks for your inputs.

I am seeking if boot data is used for a specific service only – if that is true, this boot data actually can be bound to the specific services, and other could request boot data related services by API.

/Ken

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Michel JAOUEN via TF-M
Sent: Tuesday, February 9, 2021 8:53 PM
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: Re: [TF-M] Boot data usage

Hello,

On STM platform, The boot data is also used to pass specific information to user different from attestation.

For this support a specific  Major is used. The actual implementation available in ST cube needs to be reworked so that each platform can  customize it (Major value, and table checking access control on tfm core)

Best regards

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Tamas Ban via TF-M
Sent: mardi 9 février 2021 11:52
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: Re: [TF-M] Boot data usage

Hi Ken,

AFAIK current implementation of FWU partition also relies on shared data received from bootloader.

Tamas

From: TF-M <tf-m-bounces@lists.trustedfirmware.org> On Behalf Of Ken Liu via TF-M
Sent: 2021. február 9., kedd 10:47
To: tf-m@lists.trustedfirmware.org
Cc: nd <nd@arm.com>
Subject: [TF-M] Boot data usage

Hi,

Wondered if someone is expanding the boot data usage, as the default user is attestation only.

Please provide your case if you are expanding boot data usage.

Thanks!

/Ken