xds510 connects with delfino F28335 but doesn't connect with c6713b or DM642

Bilal Ahmed

I have a c6713 based custom board and using XDS 510 USB and CCS 3.0. The board was working fine with only Processor and SDRAM stuffed. When Flash IC (S29AL032D) was stuffed, the reading of Manf. ID and Device ID was successful. Further code was added to erase the flash. Memory was viewed to see the erasing status. It was noted that the memory contents dont change for the sectors that were erased. I tried memory edit/fill options but writing to Flash wasn't successful.

We programmed/downloaded a code to DM 642 with the same emulator. After it, the emulator is neither connecting to DM 642 nor to C6713B. The same boards are working with XDS 560 PCI.

We tested c6713 based board with SDConfig utility, but Emulator Test ->JTAG scan chain test shows

"34 devices in JTAG scan chain"

"JTAG IR length of 54"

Actually only one device (c6713) is connected on the board and previously it was showing IR length of 46.

Now the Emulator is working with Delfino F28335 but doesn't connect with c6713b or DM642 based boards.

You are requested to look into the matter and provide needed help

Regards,

Bilal

over 11 years ago

Gautam Iyer over 11 years ago

Guru 192875 points

Hi Bilal,

I guess this post would help you:

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/139068.aspx

Regards,

Gautam

Bilal Ahmed over 11 years ago in reply to Gautam Iyer

Prodigy 175 points

Hi Gautam,

The post doesn't seem much supportive, as the emulator is connecting with delfino but not with 6713 or 642 boards. So, there is nothing yet which can explain this.

Also, why is Emulator Test showing multiple devices in JTAG Scan Chain?

Hope anybody gets to it more precisely.

Regards,

Bilal

desouza over 11 years ago in reply to Bilal Ahmed

TI__Guru**** 169864 points

Bilal,

It is very difficult to have a precise assessment on what may be happening, especially given the reason why you are getting so many devices in the scan chain, but I can guess two things:

- A DM642 misconfiguration on the EMU pins that is causing it to start in boundary scan mode (check this thread).

- A pull up and/or down resistor that is confusing the XDS510USB but not the XDS560PCI (which typically has stronger drivers at its end). In this case, can you take a look at section 6.3 of the XDS Target Connection Guide page.

One last thing it would be trying to reduce the JTAG clock speed of the XDS510USB and see if it gives more reliable results. Check this thread for details on how to do this.

Hope this helps,

Rafael

Code Composer Studio™︎

Code Composer Studio forum

xds510 connects with delfino F28335 but doesn't connect with c6713b or DM642