- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
i would like to ask for help regarding debug interface lock (software implementation) on Aurix litekit 275 .
Debug lock was implemented according to AP32389 application note. Debug interface is locked successfully, however we can not unlock it. We were using memtool.
I would like to ask for help regarding unlocking device what should i try to unlock it. I read almost all forum topics regarding similar issue.
Also is there any known issues when implementing interface lock with code and unlocking it with memtool?
Error code i receive.
Any kind of advise, response would be appreciated.
Regards,
Jan
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Please see the section "3.2 Unlock using the Infineon Memtool/PLS UDE Memtool" in the AppNote available in the link and let us know if the issue is still not resolved.
Regards,
Prudhvi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Please see the section "3.2 Unlock using the Infineon Memtool/PLS UDE Memtool" in the AppNote available in the link and let us know if the issue is still not resolved.
Regards,
Prudhvi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
thanks for the answer. As far as i know, unlocking debug interface with miniwrigler debuger and mem tool is not possible (it was possible in the past ). I contacted support PLS regarding this problem, they said that for debug interface lock we should use PLS instead of miniwrigler.