TM4C1233C3PM: Error -1170

Hi,

  Please start with this troubleshooting guide to see if it will lead you to the cause of the problem. 

https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html#cable-break

Hi Charles,

Good Day. Actually, I already send that link to the customer prior to posting his query here in the forum. He already follows the instructions on the link to fix the error -1170 but he is still encountering the same error. Can you help the customer to fix the error? Thank you very much.

Best Regards,

Ray Vincent

Ray Vincent Aranzaso said:

I use a custom board with TM4C1233 and a stand-alone XDS560v2 System Trace. The JTAG probe is working ok, I tested it on TMS320F28069. TM4C1233 is ok too, I can program it with an ICDI programmer. The harness is ok too because it passes the connection test. They should be something in the settings.

To confirm:

TM4C1233 + XDS560v2 = Connection test passes but error -1170 occurs

This error is typically caused by the device being in a bad state or some board hardware failure. But the customer also mentioned that there is no issue connecting to the same target with an ICDI probe. They also mentioned that the XDS560v2 works find with an F28069.

Hence it could be a configuration issue. One thing to try is lowering the TCLK value:

https://www.youtube.com/watch?v=mKxaztkCsYw

I can also see if I can successfully connect to one of my Tiva devices with my XDS560v2. What is the vendor of the customer's XDS560v2?

Thanks

ki

Hi Ki,

Good Day. Lowering TCLK didn't help, the customer tried even 100kHz. No hardware issues, he also tried to flash the chip with XDS110 and it works. The vendor is Blackhawk. Here is the output log from the Blackhawk configuration utility:

CMD: dtc_conf get bh560v2u 0
addrConf=:55756
addrIo=:55755
boardRev=2
dtcName=none
epkRev=5.0.573.0
fpgaRev=1.54
ipAddress=none
ipBroadcast=none
ipClient=none
ipConfig=dhcp
ipGateway=none
ipHwaddress=none
ipLeasehours=none
ipLeasetime=none
ipMtu=none
ipNetmask=none
ipNetwork=none
ipPointopoint=none
productClass=XDS560V2
productName=Blackhawk XDS560v2 System Trace
safeMode=false
serialNum=00:0F:D2:02:09:EE
swBuildTime=Mar 30 2012 17:37:41
swRev=5.0.573.0
time=none
vendorName=Blackhawk

Best Regards,

Ray Vincent

I'm not sure what else to suggest. I'll see if I can get by Blackhawk XDS560v2 to connect to a TM4C device tomorrow

I was able to use my Blackhawk XDS560v2 to connect to my TM4C1294NCPDT LaunchPad. I also had no issues download/flashing a program.

Ray Vincent Aranzaso said:

It passes the connection test but when I try to flash it CCS returns the error "Error connecting to the target: (Error -1170 @ 0x0)

Is the issue only when the customer tries flashing the program? Connecting to the target via CCS debug session is fine?

Hi Ki,

Good Day. The debug doesn't work either. He had TM4C1294NCPDT LaunchPad. Can you provide some example projects for the LaunchPad with some instructions on how you connected Blackhawk to the board? Thank you very much.

Best Regards,

Ray Vincent

Ray Vincent Aranzaso said:

He had TM4C1294NCPDT LaunchPad. Can you provide some example projects for the LaunchPad with some instructions on how you connected Blackhawk to the board?

I simply connected my Blackhawk XDS560v2 to the 10-pin ARM JTAG header on U6.

See section 2.3.2 of the launchpad user's guide for more details: https://www.ti.com/lit/ug/spmu365c/spmu365c.pdf

Note that to connect my XDS560v2, I had to use some adaptors to go from MIPI-60 to 10-pin ARM.

Once the connection was complete, I simply create a target configuration for Blackhawk XDS560v2 and TM4C1294NCPDT. Then I was able to launch a debug session and connect to the target.

Hi Ki,

Good Day. 

Ray Vincent Aranzaso said:

Unfortunately, he doesn't have a MIPI-60 to 10-pin adapter. He found it here www.blackhawk-dsp.com/.../12209.html. Are you using this one? Is there anything cheaper?

I actually needed two adaptors. I am using the 20-pin cTI to 10-pin ARM that you mentioned, along with a MIPI-60 to 20-pin cTI: https://www.blackhawk-dsp.com/store/12188.html

Unfortunately these adaptors are pretty pricey these days. Many people who have the tools just try to mod one themselves.

Ray Vincent Aranzaso said:

And he still doesn't understand why he can connect to the MCU with XDS110 and cannot with Blackhawk XDS560v2

I do not understand either. It could be something as minor as one debug probe having a better tolerance for noise on a particular board than another.

One thing for the customer to try is to see if the same XDS560v2 fails on another TM4C1233 target. Also if the customer has another XDS based probe (like 100/110/200), see if that works on the board with the issue.

Thanks

ki

Hi Ki,

Good Day. He'd tried to connect with Blackhawk XDS560v2 to 2 custom boards. One board has TM4C1233H6PM, the second board has TM4C123GH6PM. It doesn't work on both boards. He's got XDS200 and it works OK with TM4C1233H6PM, he didn't try it with TM4C123GH6PM, but it should work too. He should receive 20-pin cTI to 10-pin tonight or tomorrow. He will let us know once he receives it.

Best Regards,

Ray Vincent

Hi Ki,

Good Day. He tested Blackhawk XDS560v2 on TM4C129ENCPDT via J6 and it works. Now he needs to understand why it doesn't work with TM4C123. Could it be because it is the 123 series and it works with the 129 series only? Or pull up and pull down resistors on JTAG? The custom board and launchpad have different configurations. I attached pictures of the JTAG connection of the custom board.

Best Regards,

Ray Vincent

Ray Vincent Aranzaso said:

Now he needs to understand why it doesn't work with TM4C123. Could it be because it is the 123 series and it works with the 129 series only

XDS560v2 technically supports TM4C123 and TM4C129.  I assume the TM4C1233 board is a custom board. It is likely something specific to the custom board design that the XDS560v2 is sensitive to. 

It is interesting that the XDS200 does work because the XDS560v2 and XDS200 does share some similarities with both hardware and software implementation.

Ray Vincent Aranzaso said:

Or pull up and pull down resistors on JTAG? The custom board and launchpad have different configurations. I attached pictures of the JTAG connection of the custom board.

I can't comment much on the schematics as it is beyond my expertise. I will bring this thread to the device experts for more suggestions.

Thanks

ki