Background
On an i.MXRT1064 SoC that was running a secondary bootloader with debugger attached, a call was made to the HAB API entry function - the status returned by the call indicated HAB failure. A call was then made to HAB API function report_event, to see what (if any) audit events were logged; after calling report_event, the event log buffer did contain event data. The event log data began with:
[0] 0xdb //Tag: 0xDB = Event
[1] 0x00 //Event data length MSB
[2] 0x2c //Event data length LSB - overall data
[3] 0x43 //Major version = 4, minor version = 3
[4] 0x33 //STS: HAB_FAILURE
[5] 0x30 //RSN: HAB_ENG_FAIL
[6] 0xe1 //CTX: HAB_CTX_ENTRY
[7] 0x1e //ENG: HAB_ENG_SNVS
The data at index 7 appear to indicate an issue with the secure non-volatile storage (SNVS) engine.
Questions
- Are there common reasons execution of HAB API entry may return a status of HAB failure? Especially as concern SNVS?
- Is there standard setup required to successfully run HAB API entry, such as enabling particular clocks, setting configuration in control registers, clearing particular flags, etc.?
- Example code which demonstrates use of HAB API calls from a secondary bootloader on an i.MXRT platform would be helpful - is there any available?
Thank you and best regards
