Hi Taehoon Kim,

We seem to experience an issue with the mailing list where messages are not properly dispatched. I reproduced your initial email sent Dec 18th 2025 below and Cced relevant folks just in case.

Regards,

Olivier.

____________________________________________________________

Hello, I'm firmware developer for RD-V3-R1 chipset.

I have developed our firmware based on Neoverse Reference Platform RD-INFRA-2025.07.03, but I have also kept an eye on the code to ensure we remain in step with the latest release. 

While inquiring on the TF-M forum to update the TF-M code, I also developed a query regarding the TF-A section.

Re: Several Questions related to RSE Provisioning - TF-M - lists.trustedfirmware.org

This link includes that RSE API codes are removed in the SotA TF-A codes.

I check this in the TF-A commit.

https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/46314

I was already aware that this API was not used outside of test code. However, I would like to know the reason why that code was removed, beyond the simple fact that it was not being used. Is it possible that Chain-of-Trust is established in whole firmware stack from RSE ROM to AP BL33 bootloader, without RSE assist? If possible, what does TF-A rely upon as the basis for trust in establishing the Root of Trust? 

Our team believed that CoT was established on the premise of the RSE API, and was therefore designing to ensure the trustworthiness of the entire firmware using that code. However, we recognise that to use the latest version of the code, we must abandon that belief and design in a different manner. Before the new version of RD-INFRA is released, we intend to resolve this internally as a team.

Should you feel the scope of the question extends beyond what is typically addressed in the forum, please do not hesitate to let us know.

Thank you for reading this mail.

Best Regard,

Taehoon Kim