The reason could be:
The start of emulation on TriCore DAP. Trigger is set to the positive edge on RESET. After reset DAP communication goes via two lines (DAP0 and DAP1). It switches to 3 pin mode if DAP Wide is selected. DAP protocol is a message based protocol. Debugger sends command (telegram) and ECU answers to command at the same line.
Zoomed recording when reset is released.
Zoomed recording when first DAP telegram is sent. First telegram is SYNC telegram where ECU answer with 0xAAAAAAAA (See the 10101010101010101 stream).
(In most cases that is the pin 40 on ST1 connector). Bent pin disables connection between the debugger and the Target or causes a short-circuit with the pin 38 which is usually most of the time low.
winIDEA is using a FLASH monitor which is used to program FLASH during download operation. Debugger first initializes part of the target RAM where monitor will be placed, then downloads monitor and execute it. If external watchdog is triggered it causes CPU to reset which invalidates RAM and flash monitor stops working and hence error message displayed by the debugger. Refer to the topic Active Watchdog issues.
Check which Debug Mode (Standard, Wide) is supported.
It is recommended to connect the TRST' pin:
Signal TRST’ (previously DAPEN) is used to select either DAP or JTAG on power on reset. It is important which logic level is present on the TRST' pin during power on reset sequence: if logic 0 - JTAG is selected; if logic 1 - DAP is selected.
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.