ULINK: Startup Problems with Infineon OCDS on XC16X

Information in this article applies to:

• ULINK USB-JTAG Adapter
• ULINK2 USB-JTAG Adapter

QUESTION

We have a problem with OCDS debugging on a new board using XC167. 

The board is straightforward; we are setting the XC167 in single-chip mode with /EA==1 (no pull-down). When I try to connect with OCDS, µVision replies that it cannot detect the hardware and displays a message box:

Error: Target DLL has been cancelled.
Debugger aborted!

If the board is not powered, or in bootstrap mode (using the /RD pull down), µVision shows the correct error message.

Do you have any idea on the mistake?

ANSWER

There are a couple of potential issues that need to be taken care of when using OCDS. Check the following:

1. XTAL frequency: we have seen that XTAL is a critical point. Use for starting an 8MHz XTAL as on the Infineon board.
2. RESET logic: sometimes an off-chip reset logic causes problems. You should remove a capacitor on the reset input for testing.
3. +5V power supply: The OCDS pin 2 (VCC) should be connected to +5V. ULINK has an internal jumper that should be in EXT position so that the drivers are using 5V. We have seen that 3.3V (which is the internal ULINK voltage) sometimes creates problems with external logic.

MORE INFORMATION

• Application Note 163: Programming the Infineon XC16x / ST Super10 Devices
• Refer to Target Connectors in the ULINK User's Guide.

SEE ALSO

• ULINK: Connection Issues With Ulink and XC161 AC Step
• ULINK: OCDS: Program Counter moves to Incorrect Values
• ULINK: XC16X OCDS Interface does not work

ULINK: XC16X OCDS Interface does not work

Last Reviewed: Tuesday, January 5, 2021