Hello there,
We are trying to implement a lock/unlock mechanism on the main debug port of the AURIX TC277P controller using the 32-byte password that is written into the UCB_DBG register of the controller. However, when testing our code we got locked out of the board.
We used the following 32 byte password for locking the debug port:
0x1d1d2fdd, 0xc5c455fc, 0xb3ffa197, 0xb5624715, 0x1c67c968, 0xec4e44ac, 0x84a61235, 0x0f9c11a7
For locking, we wrote the following data to the UCB_DBG register 8-bytes at a time in the same order as it appears in the table below starting from the address - 0xAF101400(of UCB_DBG) using the code from page no 34 and 35 from the infineon application note attached with this post - AP32389_TC2xx_Debug_Protection_with_HSM_V1.2.pdf
| Sr |
Description |
Value we wrote |
Size(Bytes) |
Significance in UCB_DBG Register |
| 1 |
PROCONDBG bits |
0x00000003 |
4 |
We intend to lock the debug port by writing value 0x3 to PROCONDBG bits |
| 2 |
Copy of PROCONDBG bits |
0x00000003 |
4 |
Value must be the same as that in PROCONDBG bits |
| 3 |
Password |
0x1d1d2fdd, 0xc5c455fc, 0xb3ffa197,
0xb5624715, 0x1c67c968, 0xec4e44ac,
0x84a61235, 0x0f9c11a7
|
32 |
Value of the password to be used to lock the debug port |
| 4 |
Copy of Password |
0x1d1d2fdd, 0xc5c455fc, 0xb3ffa197,
0xb5624715, 0x1c67c968, 0xec4e44ac,
0x84a61235, 0x0f9c11a7
|
32 |
Copy of the value of the password to be used to lock the debug port |
| 5 |
Confirmation Code |
|
4 |
Confirmation for updating password lock |
| 6 |
Copy of Confirmation Code |
|
4 |
Copy of the confirmation code |
We are using the UDE 2021 debugger to debug our code and thus to unlock the debug port, we used the UI provided by UDE and tried entering the same password given above, but it does not unlock the debug port. We are also trying to communicate with the controller using CAN interface, but the controller is not responding to any external communications - CAN or otherwise, at all and is completely unresponsive since executing the Locking sequence described above.
Any help we can get in unlocking this controller and recovering it as a whole and/or understanding how to properly lock/unlock the debug port properly would be greatly appreciated as we've been stuck with this issue for several days now.
I have also attached the error message we get when trying to unlock the debug port using the password from UDE debugger for reference (Error_Msg_UDE2021.png)
