Hello Jorge,
the tests were done with an SCU firmware derived from version 1.15.0 of the porting kit and a U-Boot derived from tag rel_imx_5.4.70_2.3.2.
The AHAB container was loaded at address 0x98000000. I've changed the flags at offset 4 to cause authentication errors. The original flags byte was 0x02 for verification with OEM SRK 0. Using 0x00 (= unsigned container) instead resulted in
=> auth_cntr 0x98000000;ahab_status
Authenticate OS container at 0x98000000
sc_seco_authenticate: res:3
Authenticate container hdr failed, return -22
Lifecycle: 0x0080, OEM closed
SECO Event[0] = 0x0087F729
CMD = AHAB_AUTH_CONTAINER_REQ (0x87)
IND = Unknown Indicator (0xF7)
sc_seco_get_event: idx: 1, res:3
Using 0x12 (signed with OEM SRK 1) resulted in
=> auth_cntr 0x98000000;ahab_status
Authenticate OS container at 0x98000000
sc_seco_authenticate: res:11
Authenticate container hdr failed, return -5
sc_seco_authenticate: res:11
Error: release container failed!
Lifecycle: 0x0080, OEM closed
SECO Event[0] = 0x0087F029
CMD = AHAB_AUTH_CONTAINER_REQ (0x87)
IND = AHAB_BAD_SIGNATURE_IND (0xF0)
SECO Event[1] = 0x00890029 sc_seco_get_event: idx: 2, res:3
In a third test I changed an unimportand bit at the beginning of the kernel image. The result was
=> auth_cntr 0x98000000
Authenticate OS container at 0x98000000
sc_seco_authenticate: res:11
Authenticate img 0 failed, return -5
=> ahab_status
Lifecycle: 0x0080, OEM closed
SECO Event[0] = 0x0088F129
CMD = AHAB_VERIFY_IMAGE_REQ (0x88)
IND = AHAB_BAD_HASH_IND (0xF1)
sc_seco_get_event: idx: 1, res:3
In all three cases I proceeded to boot into Linux. Linux was still able to decrypt CAAM blobs that were created when booting without SECO events in OEM closed lifecycle. The CSTA register in Linux' CAAM job ring had the value 0x106, which tells me that the SSM was still in secure state.
Best regards,
Daniel