AM2634: AM2634 HSM core debugging

Jaka Jemec

Part Number: AM2634
Other Parts Discussed in Thread: AWR2944, AM2732, LP-AM263,

Hi, I would like to establish debug connection on HSM CM4 core using our debug tool (iSystem). We got " AM263x Security Hardware Addendum" and I tried to do the steps described there. Somehow no address related to HSM can't be accessed. On others, a bit similar devices like AWR2944 and AM2732 writing to HSM_CTRL_LOCK0_KICK0 and HSM_CTRL_LOCK0_KICK1 registers were required and then releasing the HSM core by writing to HSM_CTRL_HSM_CM4_CFG register. But this can't be done here on AM263x, since all HSM_CTRL memory region starting from 0x47000000 can't be accessed.
Do you have any suggestions on what we should do?

Thank you,
Jaka

over 2 years ago

0 Aakash Kedia over 2 years ago

TI__Mastermind 26145 points

Hi Jaka Jemec,

Do you have a GP device or a HS device ? If its a HS device, is this HS-FS device or HS-SE device ?

To get this information use the following FAQ - https://e2e.ti.com/support/microcontrollers/arm-based-microcontrollers-group/arm-based-microcontrollers/f/arm-based-microcontrollers-forum/1170785/faq-mcu-plus-sdk-am243x-how-to-identify-if-the-device-is-gp-device-or-hs-device

Best Regards,
Aakash

0 Jaka Jemec over 2 years ago in reply to Aakash Kedia

Prodigy 115 points

Is there any other chance to check if the device is GP or a HS, perhaps by reading any register or ROM area? UART communication that you described isn't possible, because we had to modify our LP-AM263 board and solder on a Cortex 10-Pin debug connector and disassembled some on-board debugger related components (U25, U26, U27) so it doesn't interfering while we want to communicate with AM2634 chip via JTAG/SWD.

0 Aakash Kedia over 2 years ago in reply to Jaka Jemec

TI__Mastermind 26145 points

Hi Jaka Jemec,

In the CSL_TOP_CTRL_U_BASE (0x30E0000U) - there is a EFUSE_DEVICE_TYPE register at 0x220 offset.

These are the values -

Hope it helps.

Best Regards,
Aakash

0 Jaka Jemec over 2 years ago in reply to Aakash Kedia

Prodigy 115 points

Hi Aakash Kedia, I found the register that you mentioned in reference manual, but it is on different address.

The value of that register is 0x000000AA, probably that means the device typ is HS-FS. The address you mentioned (0x30E0000U + 0x220) can't be read.

0 Aakash Kedia over 2 years ago in reply to Jaka Jemec

TI__Mastermind 26145 points

Hi Jaka Jemec,

I am a bit confused. Are you working on AM263x or AM273x ?

For AM263x, there is no GP part so the device is always shipped in HS-FS mode. If the device is HS-FS mode, the debug for HSM sub-system is always closed.

Best Regards,
Aakash

0 Jaka Jemec over 2 years ago in reply to Aakash Kedia

Prodigy 115 points

Hi,

I am working on AM263x where I would like to debug HSM_CM4 core. To me it looks pretty similar as on AM273x, where we are able to normally debug this HSM core.
So from your answer I assume we can't debug it, since the mode is HS-FS. We are unable to read any of HSM registers.

Best regards,
Jaka

+1 Aakash Kedia over 2 years ago in reply to Jaka Jemec

TI__Mastermind 26145 points

Hi Jaka Jemec,

That is the correct understanding. HSM Debug for HS-FS devices is not supported by TI.

If you intend to debug HSM for development, one method would be to convert the device to HS-SE device and use TIFS-MCU Firmware to open the debug of HS-SE devices. But that is one complicated way to do it. You can request for EMU parts if HSM Firmware development is not your intent.

Best Regards,
Aakash

Arm-based microcontrollers

Arm-based microcontrollers forum

AM2634: AM2634 HSM core debugging