I am running SDK version 11_00_00_19 and TIFS version 11_00_00_01 and have flashed my keys to my board and converted it to HS_SE mode and can validate that the hashes of the keys on the board are what is expected.
I have been able to flash and run multiple different applications - all of the AES provided examples from the SDK in addition an application I wrote seperatly.
A few weeks ago I was working on an AM263P board and was able to write and execute code that called upon the proc_auth_boot hsm client to validate an image and it executed correctly. I just started over with a new AM263PX board and have been able to execute everything but any HSM_Client Calls.
Calling proc_auth_boot (HsmClient_procAuthBoot) fails with the [HSM_CLIENT] Proc_Auth_Boot request NACKed by HSM server error but I can validate that is is reading the certificate and image in flash correctly before that call is made.
Also running an SBL that disables the HSM debug firewall with the certificate generated for my board returns this error:
[HSM_CLIENT] OpenDbgFirewall request NACKed by HSM server
Starting OSPI Bootloader ...
SBL failed!!
In addition - running the hsm_services example executed correctly without any issues.
Is there anything I should look into specifically to resolve this problem or is there something I am overlooking?