Hello,
I am trying to implement secure logging on the A-core (BSP43). The goal is to log security-related failures such as Secure Boot failures, Wi-Fi/TLS failures, etc.
Currently, I am attempting to log Secure Boot failures at the BL2 stage. My initial approach was to write these logs directly into NOR flash and encrypt them using HSE. However, I am running into the following limitations at the BL2 level on S32G:
Because of these constraints, I am unsure how or where such Secure Boot failure logs should be stored at BL2 so that they can later be accessed from Linux.
For Wi-Fi and TLS-related failures, I plan to use NetworkManager-based logging at the Linux level.
Could you please advise on a feasible approach for logging Secure Boot failures originating from BL2, or suggest a recommended mechanism for secure logging in this scenario?