AM263P4-Q1: Regarding the "[HSM_CLIENT] Timeout exception”

Hi Atsuki san,

Which TIFS version are you using along with SDK 11.0 ?

Also, which memory regions are you trying to firewall which are giving a timeout?

Thanks and Regards,
Aditya Singal

To check the TIFS version, we tried to obtain it using HsmClient_getVersion(), but SystemP_TIMEOUT is returned, and we are unable to get the version.

Is there any other way to check the TIFS version?

Also, if there is a possibility that the HSM is not starting up or operating properly in the first place, could you please advise us on the procedure to check the operating status of the HSM?

The memory regions we are trying to firewall are the OCSRAM (Bank0 to Bank3) and the FLASH region.

Requested response date: October 2, 2026

Hi,

From the above explanation, it looks like the device has not booted the HSM firmware as none of the services are being acknowledged.

What is the status of the loadHSMFirmware API in your bootloader? Did you get the boot notify from HSM there?

Thanks and Regards,

Nikhil Dasan

Hi Nikhil

HsmClient_loadHSMRtFirmware(), which is called from Bootloader_socLoadHsmRtFw() in the bootloader, returns SystemP_SUCCESS.
Within HsmClient_loadHSMRtFirmware(), the following code waits for a boot notification from the HSM. Since the subsequent processing continues successfully, we believe that the HSM boot notification has been received and that the HSM firmware has started correctly.

status = HsmClient_waitForBootNotify(NotifyClient, SystemP_WAIT_FOREVER);

Could you please advise if there are any other points that we should check?

Requested response date: October 6, 2026

Hi,

Are you running this on HS-SE device? 

If yes, then you can open the debug for HSM core and check what is happening there.

If it is HS-FS, then this is not possible as JTAG is locked for M4.
If that is the case, can you share the screenshot of the log from your end and the code that you are running?

Thanks and Regards,

Nikhil Dasan

Hi Nikhil

The following is the log output captured when HsmClient_getVersion() was executed in the environment prior to the migration to SDK 11.0.
Based on this result, we understand that the application was running on an HS-FS device.

We would also like to provide one additional clarification.
Although we are currently migrating to SDK 11.0, the SDK versions on which the original images are based are as follows:

- Loader image: Based on SDK 10.0
- Application image: Based on SDK 9.02

We will share the screenshot of the log captured when the issue occurred, along with the relevant code, via email.
We would appreciate your cooperation in analyzing this issue.

Requested response date: October 12, 2026

Sure, awaiting your package over mail. 

Meanwhile, in the screenshot, I see that the version used for HSMRT is 10.0. Are you migrating to 11.0 keeping hsmrt of 10.0? 
Please use the hsmrt of 11.0 as well

Thanks and Regards,

Nikhil Dasan

Hi Nikhil

We have requested that the log screenshots and related code be sent to you.
If you have not received them yet, please let us know.

Also, we would appreciate it if you could let us know when you expect to be able to share the analysis results.

> Meanwhile, in the screenshot, I see that the version used for HSMRT is 10.0. Are you migrating to 11.0 keeping hsmrt of 10.0?

This screenshot was taken in the pre-migration environment.
In the post-migration environment, HSMRT version 11.0 is being used.

Currently, in this post-migration environment, the HSM-related APIs are returning SystemP_TIMEOUT, and we are also unable to retrieve the HSMRT version information.

Requested response date: October 19, 2026

Imada

Hi Imada-san,

I've received the package. Let me check and get back to you.

Thanks and Regards,

Nikhil Dasan