Intermittent XDS100v2 emulator Error -1135 with custom F28069 target

Gordon,

I'm going to move this to the Code Composer forum because I suspect an issue between the CCS driver and your emulator.  We'll see if they have anything to add.

Could you upload the portion of the schematic that goes between the emulation header and the chip though?  I can then see if anything is wrong there.


Thank you,
Brett

Please see attached file which contains the portion of the schematic with the Jtag header to F28069 interface.

Regards,

Gordon

4213.PortionOfCustomF28069Schematic.pdf

Gordon,

I don't see any changes to suggest hardware-wise.

I again think that the issue may be driver related. 


Thank you,
Brett

Hello Brett,

I have questions related to JTAG 14-pins connection.

I see that XDS100 emulator with 14-pins has this pins connection based on http://www.blackhawk-dsp.com/jtag.aspx

And based on XDSv2 schematic:

And in Gordon's schematic, it was:

But in TMDSHVMTRINSPIN, it was:

And in another schematic (experimenter kit), I saw that pin 13 and pin 14 were connected to EMU0 and EMU1.

I think XDS100 doesn't use EMU0 and EMU1. So should I pull them up like Gordon't way or just let the pins NC?

Which one that the best connection for TMDSEMU100v2U-14T in this case?

Also, should I leave pin 6 to be NC? Or in Gordon's case, it was connected to GND. Is it OK?

Thanks in advanced.

Best regards,

Maria

Maria,

Sorry for the late response.

Pin6: Pin 6 of the 2x7 header should be cut.  Because of this, it doesn't actually matter how it is connected schematic-wise.

Pin13&14: On Piccolo devices, having NC should be adequate (because there is no EMU0/EMU1 connection on the chip itself).  On many other devices, EMU0/EMU1 is used and should have a pull-up.


Thank you,
Brett

Brett:

I still don't know what Error code -1135 means. DbgJtag only lists the messages associated with errors -1 to -999.

Also, regarding having up-to-date drivers, are you referring to FTDI drivers which are bundled with CCS 5.5? 

And do you have an explanation for why there is no issue with XDS100v2 built into Piccolo ControlStick F28069, but there is an issue with a separate XDS100v2 emulator when used with our custom board. The XDS100v2 device driver is the same for both target configurations.

Gord

Gord,

From what I have seen Error -1135 is a fairly generic error staying that connectivity was lost.  I haven't ever seen a good description of Error -1135 myself.

From my understanding, the most-up-date driver should be installed with CCS5.5.

The people who would be best able to answer your questions are in this forum (however, often if a TIer is responding other TIers may not pick up the post).  I might recommend reposting these new questions directly to this forum (CCS).  Feel free to link to this thread in your new thread.


Thank you,
Brett

Hello Brett,

Thanks a lot for the answer.

Brett Larimore said:

Pin13&14: On Piccolo devices, having NC should be adequate

In this case Gordon uses piccolo, but in his schematic, he pulled-up these pin 13&14, will it influence the emulating process or not?

For Gordon, hope you can solve your problem soon.

Do you have another TI board (not your custom board) to try with XDS100v2 emulator that you have?

Best regards,

Maria

Maria,

From my understanding, having pull-ups on pin 13 & 14 shouldn't change the way the emulator operates on Piccolo devices.


Thank you,
Brett