HSM lock

Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

cross mob
User16819
Level 1
Level 1
Hi everyone,

I have problem after flashing HSM from examples on TC297 devkit board:
1. flashed BootBasic - (i used percompiled file from example)
2. flashed HsmDemo (i compiled it with HIGHTEC ARM toolchain)
3. flashed ProconHsmCotp for configuration UCB

I checked code in memory on every step, everything flashed. I flashed it with memtool, convert ELF file to HEX with objcopy -O ihex file.elf file.hex

After restart i cann't connect to HSM. Also i have red led ESR0 (RESET state) What does it mean?

I try check board with DAS device scanner, it sees board, but i have strange status "DAS Error: DEVICE_LOCKED". But i don't set any protection, just flashed examples HSM. Why have i this error?

3741.attach


Give me any advice.
0 Likes
6 Replies
User13290
Level 5
Level 5
First like received First solution authored

Hi Yuriy,

This is probably caused by the same issue as discussed here. In essense you may have inadvertently bricked your device, without the possibility of restoring it to normal.

Best regards,

Henk-Piet Glas

Principal Technical Specialist
Embedded Software

0 Likes
User16819
Level 1
Level 1
Henk-Piet Glas

But I checked exist bootloader before activation UCB. Also code ProconHsmCotp checks first addresses 0x20005000. If code HsmDemo throw some exception in during boot HSM, will it lock device? I just want understand problem. I used examples from infineon and followed instructions. But i used other compiler HIGHTEC and Memtool for flashing. Can be it cause?
0 Likes
User13290
Level 5
Level 5
First like received First solution authored

Hi Yuriy,

Sorry, there's nothing more that I can add other than what I said. If your device is inaccessibly after enabling HSM, then to all intends and purposes it is most likely bricked. You can ask for a 2nd opinion from your Infineon representative. Perhaps there are ways to backtrace the cause that I do not know of. But as soon as the debug interface is taken out of the loop you're pretty much lost as to what it may have been.

Best regards,

Henk-Piet Glas

Principal Technical Specialist
Embedded Software

0 Likes
User16819
Level 1
Level 1
i have already ordered new device, but if i do same steps, result will be same (brick a device). I want understand what i did wrong with flashing or compilation.
0 Likes
User13290
Level 5
Level 5
First like received First solution authored

Hi Yuriy,

I personally cannot help you with that. Maybe someone else on this forum can.

Best regards,

Henk-Piet Glas

Principal Technical Specialist
Embedded Software

0 Likes
User13290
Level 5
Level 5
First like received First solution authored

Hi Yuriy,

I can give you one advice though. You need a professional debugger that supports HSM in terms of HLL debugging and HSM specific SFR definitions. Without such a tool the odds are against you. You really need a professional debugger. In that case not only do you have the aforementioned features, you also have an interface that allows you to enable/disable HSM with the flick of a switch, as well as defining the bootsector that BootBasic is booting HsmDemo from. That's really what you need as a first time user. Note that for HSM integration of this kind the debugger vendor will first have to ask NDA permissions from Infineon. So it's not provided out of the box. You're not the only one by the way. I've managed to brick two boards myself for the very same reason (I know for sure I corrupted my UCB's).

Best regards,

Henk-Piet Glas

Principal Technical Specialist
Embedded Software