Categories

{{ selectedCategory.name }}

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!

Arm Cortex S32K3xx: Debug password and endianness

14-Mar-2024

While using winIDEA you encounter an error related to debug password configuration, e.g. Debug access failed.


Possible solutions

Verify endianness

It's possible that the endianness of the provided password is incorrect. For example, if you programmed the password into UTEST as 0x00, 0x01, 0x02, 0x03, 0x04, 0x05, 0x06, 0x07,... the correct password is 0x03020100, 0x07060504,... and not 0x00010203, 0x04050607,...

1. Check how you programmed the password into UTEST, using the winIDEA Memory window, with the display unit size set to 1 byte. Adjust the endianness in the GUI.

2. Enable (27) EVE log via Help / Support / Log, then start the debug session. If a valid device IDCODE is read, but the password is not accepted (timeout) then the provided password is incorrect. 


Device lifecycle considerations

1. Investigate whether the device has undergone any changes in its life-cycle, such as configuration bit settings or changes to the debug port.

2. Refer to the device's documentation and check if specific configuration bits or life-cycle stages can close or disable the debug port, even if the correct keys or passwords are known.


More resources in winIDEA Help

Was this answer helpful?

Sorry this article didn't answer your question, we'd love to hear how we can improve it.
Note: This form won't submit a case. We'll just use it to make this article better.

Similar topics

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No similar topics found!

Other topics in the same category

{{ topic.Title }} {{ topic.Ddate | formatDate }}

{{ topic.Content }}

No topics found!