- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I have a TC265 B-Step on a custom board with the debug interface lock enabled in the UCB.
I am able to connect to the microntroller with the correct password using the Memtool in combination with the miniWiggler 2.0 and DAS V7.1.8 64 bit. However, if I deinstall this version of DAS and install DAS V7.3.7 64bit, I am not able to connect and unlock the debug interface anymore. But normal connect on TC265 B-Step devices with unlocked debug interfaces still works.
Is this a bug of the current version of DAS? Or am I missing some configuration?
Any help is much appreciated, since I would like to use the current version of DAS.
Best regards,
FxK
- Labels:
-
AURIX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
Did you get any error message from the tool when you faced the issue ? Could you please check the hints mentioned in the Tool release notes and see if everything is followed.
Regards,
Prudhvi.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Prudhvi,
when connecting to a debug protected device, I get the following error message:
Message from component 'IMTMemtool' :
Can't connect to Target
Message from component 'Controller0.Core0.Tc2CoreTargIntf' :
Can't connect target !
Message from component 'Controller0.Core0.Tc2CoreTargIntf' :
Can't connect target device via DAS !
I double checked the hints in the release notes you linked, but I did not find any problem.
Best regards,
FxK