2
\$\begingroup\$

I have a EK-TM4C123GXL LaunchPad includes TM4C123GH6PM. I want to debug that with BLACKHAWK XDS200 or BLACKHAWK USB100v2.

I am using CCS v11.xx and Uniflash programs. My connections are like that;

Debuggers JTAG 5 pins(TMS,TCK,TDI,TDO,nTRST) goes to Boards 5 pins correctly. Debuggers GND goes to Boards GND. Debuggers TVD pin goes to Boards 3.3V. Boards EXT DBG pin goes to GND like datasheet. Supply switch states is "DEVICE"

Debuggers seen by programs easily, There is not any problem.

Boards voltages are correct.

But Even though I am sure of every connection, I still get the -183 (broken cable) error. Debugger can not see processor and can not debug it.

I tried with 2 different similar boards but results is same. Moreover I can debug with internal debug interface without any problems.

Considering all this, what could be the problem?

I drop the photos example.

enter image description here

enter image description here

I have 2 more questions

  1. I searched for driver software for debuggers, but I think the drivers are loaded together with CCS (I am using v11.2). Do I need to load another software/driver?
  2. Should the EXT DBG pin be pulled to GND when programming the board with a debugger or when using the board as a debugger?
\$\endgroup\$
1
  • 1
    \$\begingroup\$ Why all the SHOUTING in the question title? Please fix. \$\endgroup\$ Commented May 5 at 18:31

2 Answers 2

Reset to default
3
\$\begingroup\$

Edit

Should the EXT DBG pin be pulled to GND when programming the board with a debugger or when using the board as a debugger?

Good catch.

It's documented here: SPMA075 - Using TM4C12x Devices Over JTAG Interface

Specifically in chapter 4.5 "Using an External Standalone Debug Probe With EK-TM4C123GXL".

Since there is no standard header available, the header needs to be wired to the external debug probe as shown in Figure 10. The following steps must be followed for correct operation.

  1. Connect the header pin EXTDBG to GND on the EK-TM4C123GXL. This is required so that when the board is powered up, the ICDI detects a logic-low level and tri-state the JTAG pins allowing external debug probe to drive the signal.
  2. Connect the header pin GND to GND on the debug probe
  3. Connect the header pin TCK to TCK on the debug probe
  4. Connect the header pin TMS to TMS on the debug probe
  5. Connect the header pin TDI to TDI on the debug probe
  6. Connect the header pin TDO to TDO on the debug probe
  7. Connect the header pin RST_N to reset on the debug probe
  8. Make sure that the power selector is moved to DEVICE side
  9. Connect the USB cable on the USB device connector

I searched for driver software for debuggers, but I think the drivers are loaded together with CCS (I am using v11.2). Do I need to load another software/driver?

Installing CCS is sufficient. But during the installation process you specifically have to select Blackhawk and SEGGER drivers, if needed. At least for some older versions of CCS.

\$\endgroup\$
4
  • \$\begingroup\$ I tried to program a tm4c123 board with another tm4c123 board and it was successful. The switch on the board I used as a debugger was in the "DEBUG" position and the H24 and H25 jumpers were not plugged. On the other hand, the switch on the programmed board was in the "DEVICE" position and the jumper was plugged. Only 4 jtag lines were connected (TMS, TDI, TDO, TCK). The EXT DBG pin was empty on both boards. I think the problem here seems to be related to the XDS Debugger. But unfortunately, I have to use debuggers such as XDS200 or XDS100v2 in my project. \$\endgroup\$ Commented May 7 at 7:27
  • 1
    \$\begingroup\$ I can (slightly) understand if you want to use the XDS200 because of the better performance. But the XDS100v2 is no better than the integrated ICDI. Why don't you simply use the ICDI while working on this EK? \$\endgroup\$ Commented May 7 at 7:59
  • 1
    \$\begingroup\$ One advantage of the ICDI is that you can more easily unlock a 'code security' locked MCU using LM Flash. \$\endgroup\$ Commented May 7 at 8:03
  • \$\begingroup\$ Actually, the main purpose is not to program the processor. It is to prove that code can be transferred to this board with JTAG using a debugger in a test setup. We resorted to this method because this was what our customer wanted. \$\endgroup\$ Commented May 7 at 8:49
1
\$\begingroup\$

I solved the problem.

I said that I tried every combination and checked all the connections. Today I accidentally solved the problem. The situation is as follows; In the pin documents, pin number 4 (14 pin TI header) is seen as TDIS and this pin is specified as GND in the TI document. In the pinout document of the 14 pin TI connector, pins 8, 10 and 12 are also shown as GND along with number 4. I tried by sharing the GND of the board and the GND of the debugger with these pins. I thought that this pin was connected to GND within the debugger, but it turned out that I had to connect it externally.

Connecting this pin to GND solved my problem.

In order to help those who do a similar debugging process; EXT DBG and TDIS pins should definitely be connected to GND.

Thank you for helps, it was so useful.

\$\endgroup\$

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.