Hi @samet-san
Thank you for reaching out!
Let's investigate this issue together. I want understand better your background, how did you enabled the HAB? Using our Secure Provisioning Tool ? is your soruce code calling HAB APIs ( from a previously authenticated image by the bootROM) and then your are getting this error?
Diego
Thanks Diego.
This is my HAB Commands.
There are certificates and sign's with starts 0xD7 and 0xD8 tag. in the defined addresses.
(0xD8/0xD7 - size - version - certificate/sign)
I fused intermediate certificate hash. I made it by "nxpcrytpo rot calculate-hash --family rt117x -k certificate addres -o srk_fuses.bin. " command.
I didnt make anything else. I run it after make image with this parts.
How can I active HAB ? I dont know it ?
Hi @samet-san
I do apologize for the delayed response, I missed your reply.
The HAB event you report seem to indicate HAB_FAILURE, due to the reason of HAB_UNS_STATE (Unsuitable state ) and HAB_ENG_FAIL ( Engine failure).
To dive into errors I like to use the Appendix A: Interpreting HAB Event Data from Report_Event() API from the High Assurance Boot Version 4 Application Programming Interface Reference Manual contained in the CST( code signing tool) However, the manual does not dives into details, as we would like in this occasion, I apologize for this.
If HAB is enabled succesfully, you should not receive error events, and sometimes you can get warnings.
To enable HAB, we need to burn from 0xB00 to 0xB70 for the SRK and the 0x960 to enable HAB, as shown in the write scripts of the MCUXpresso Secure Provisioning Tool. Did you miss this fuse?
If you ping your RT1170 over USB (using the SPT or the blhost get-property command), can you see that the life cycle is set to close?
If you have found out something else in the meantine please let me know.
I appreciate your patience.
Diego