Hello everybody ,
do you have exact PN of the 168 connector present on the experimenter kit ?
about schematics in latest Controlsuite there is and indication of "edge pinout not fixed ... "
do have any newer documentation ?
thank you
bye
Carlo
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hello everybody ,
do you have exact PN of the 168 connector present on the experimenter kit ?
about schematics in latest Controlsuite there is and indication of "edge pinout not fixed ... "
do have any newer documentation ?
thank you
bye
Carlo
Hi everybody
please any news ?
thank you
bye
Carlo
Carlo,
Attached is the most recent version of the 168-pin docking station. Unfortunately, this set of docking stations did not match up with the DIM168 Delfino controlCARD; particularly, the issue was with pin 107. This pin/trace will need to be cut for the board to work.
Thank you,
Brett
Brett,
The schematics you have attached show a DIMM168 USB experimenters board using an FT2232D (I'm assuming this is used to implement XDS100 emulation). I thought the the 168-pin docking station didn't come with the USB emulator because they "require an external JTAG emulator to keep up with the C2834x’s high performance". Are the drawings you attached for a new version that is not released yet? Can the FT2232H shown in this schematic (or the FT2232D used on the other USB docking stations) be used to successfully implement an XDS100 emulator in combination with the TMDXCNCD28346-168 control card following this procedure. It would be nice to use built in USB emulation for a project I'm working on.
Thanks,
Jon
Jonathon,
About 2-6 months ago we released a new revision of the DIM168 Experimenter's board which works in conjunction with the C2834x DIM168 controlCARD. This was done so that the controlCARD could work with an onboard xds100v2 emulator. The xds100v2 emulator is a step-up from the earlier xds100v1 emulator (which we've been using on many C2000 kits) and has a faster data rate which would make the debugging process more workable.
Most of the other controlCARD's Experimenter Kits come with a board which has an onboard xds100v1 emulator. The procedure you linked gives the process to get the xds100v1 emulator working. The process for xds100v2 is similar but uses a different .ept file.
The xds100v1 (FT2232D) or xds100v2 (FT2232H) can be used with the C2834x devices although I would recommend using the xds100v2 because of the reasons mentioned above.
See the following wiki article for more information:
http://processors.wiki.ti.com/index.php/XDS100
Thank you,
Brett
Brett,
I have a couple more questions about the integration of the XDS100v2 with the DIM168 control card.
1. The DIM168 USB schematics you attached do not include the CPLD from the XDS100v2 reference design (from the Wiki page you linked to). If I were to build my own board to interface to the control card which design should I follow (with or without the CPLD)?
2. Would the .ept file needed to program the device be different than the one included with the XDS100v2 reference design if I omitted the CPLD?
On a side note, I thought is was awesome that the XDS100v2 reference design is provided as a Kicad project. It would be even more awesome if the hardware development files in controlSUITE followed the same format. ; )
Thanks,
Jon
Jonathon,
To be honest I'm not really an expert in the xds100v2 hardware. I believe the CPLD was added as a minor revision to the original xds100v2 design in order to support adaptive clocking. Which I believe is needed to fully support emulation on ARM parts that TI has. If you want to be safe (which may be the best option), you can certainly go with the full xds100v2 design from the wiki site and do well.
In-house we've used the DIM168's xds100v2 design and things have worked with C2000 devices, so you can also use that as well.
Thank you,
Brett
Jon,
1 - This choice depends on what you're trying to do. You do not need the CPLD for the basic functions but as Brett mentioned, the CPLD is useful when you want to add features and/or robustness to the circuit. If cost and board real estate is not an issue, I would put it on there for future flexibility.
2- I attached the xds100v2.ept we use internally.
http://e2e.ti.com/cfs-file.ashx/__key/CommunityServer-Discussions-Components-Files/171/6431.XDS100v2.ept
Regards,
Alex