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

cross mob
daco_2225886
Level 1
Level 1
5 sign-ins First reply posted First like given

Hello,

 

We are using MiniWiggler 3 to debug a TC367D with Aurix Development Studio 1.8.0.

We are facing an issue when we make a SoftwareResetRequest with API IfxCpu_triggerSwReset.

In this case we lose the debug connection and are not able anymore to debug the software after the reset.

Could you please tell us if there is something special to do not to lose the debugger after the SoftwareResetRequest.

 

Thanks for your help.

Damien

 

 

0 Likes
1 Solution
Di_W
Moderator
Moderator
Moderator
1000 replies posted 250 solutions authored 100 likes received

Understood. This will be reported to the team to check if have better solution.

View solution in original post

3 Replies
Di_W
Moderator
Moderator
Moderator
1000 replies posted 250 solutions authored 100 likes received

For this scenario, the debugger will stop. Maybe you can use GPIO or UART for outputting critical info.

0 Likes
daco_2225886
Level 1
Level 1
5 sign-ins First reply posted First like given

This sounds bad then.

What solution do you propose then to be able to debug this case?

Because it seems that the issue comes from the init phase (or at early level)  so my CAN communication (and I guess UART) are not yet working.

It is quite common thing that the debugger is not lost after a software reset, this is possible for example for ARM MCU and IAR debugger for exemple.

I guess there should be also a way to debug this case for TC37x right?

The problem comes from the MiniWiggler, the DAS, the MCU or AURIX Dev Studio?

0 Likes
Di_W
Moderator
Moderator
Moderator
1000 replies posted 250 solutions authored 100 likes received

Understood. This will be reported to the team to check if have better solution.