LP-AM263P: Unable to flash the hs images due to timeout in the hsmgetversion example

Hi Srinivas,

Let me try to reproduce this early next week and get back to you.

Meanwhile could you please try using Uniflash tool?

Hello Nilabh Anand , 

Any update on this ? 

I tried via Uniflashing tool for normal images but is it the same for HS images ? Becuase for HS images also there are uart sbl hs image and then phy tuning and ospi sbl hs image. But in Uniflash I dont see a place to flash uart hs, so I flashed only ospi sbl hs image. But the device doesn't print anything. 

Also are you using AM263Px-LP or AM263Px-CC.

I see LP in thread title and in the cfg file, looks like you are using CC

Also did you convert the device to HSSE, by programming the keys and are you using the same keys for encryption?

Using same keys, No key related thing done other than the steps followed from hsm getversion example.

Is there something I miss there ?

I am using CC. I created this ticket from another thread so it had automatically created the name LP. 

I tried it on my side, I do not see this issue.

There are a few follow up questions:

1. Which AM263P-LP board revision are you using?

2. Which MCU PLUS SDK version are you using?(The version from which you are using the SBL and uart uniflash flasher)

3. Which open ssl version do you have on your PC?

3. OpenSSL 3.5.1 1 Jul 2025 (Library: OpenSSL 3.5.1 1 Jul 2025)

2. MCU SDK -> mcu_plus_sdk_am263px_10_02_00_15

1. AM263P4 -> ZCZ-C

TIFS: tifs_am263px_10_02_00_01

Nilabh Anand said:

1. Which AM263P-LP board revision are you using?

I meant the Rev-A, Rev-B, this might be written on your cc-board

XAM263P4ACOMF is written ? 

Nilabh Anand : Any update ? 

Hi Srinivas,

Just to reconfirm, you device is in HSSE which is coverted from HS-FS to HS-SE using TI OTP KW tool using the same keys TI provided as part of package?

Did you rebuild the TIFS firmware in the TIFS SDK and did this hsmRtImg.h file get reflected in the mcu_plus_sdk folder?

The sbl_uart should pick up this updated HSM header file, so this step is crucial. 

If you have pointed to the mcu_plus_sdk path in import.mak file of TIFS SDK, this should happen upon building the TIFS firmware.

Can you confirm the above?

Thanks and Regards,

Nikhil Dasan

Hi Srinivas,

I am unable to reproduce the issue. Please use below and try on your setup:

SBL:

/cfs-file/__key/communityserver-discussions-components-files/908/sbl_5F00_ospi_5F00_multicore_5F00_elf.release.hs.tiimage

UART Uniflash:

/cfs-file/__key/communityserver-discussions-components-files/908/sbl_5F00_uart_5F00_uniflash.release.hs.tiimage

Application:

/cfs-file/__key/communityserver-discussions-components-files/908/hello_5F00_world.release.mcelf.hs

If this also does not work, then I am suspecting something went wrong in OTP programming.

I am using the latest SDK: 10.02.0015

Let me know your feedback

Hello Nilabh, I am getting this error with the custom flash loader enabled. If I don't enable i am getting stuck during the flashing of SBL itself

Hello Rijohn Pius  and Nilabh Anand ,

I tried with uniflash tool v9.2 and I am able to boot the system properly. Thanks a lot