Development kits in C2000

Hi,

Me neither can't find documentation about this kit. i wish to know what are its pros and cons in compare to the Experimenter's Kit.

br

Israel

Here's the document:

Also, here's the kit homepage:

Regards,

Gautam

Hi Israel,

FYI: All devices that have a eCAN or DCAN peripheral have the ability to communicate on a CAN network with minimal software intervention.
(you can get each device's peripheral set from each device family's datasheet)

For CAN to connect up to a proper network, the peripheral must be connected to an off-chip CAN transceiver. 
1) The eZDSP kits or the Peripheral Explorer kit (TMDSPREX28335) have a transceiver + its circuitry built into the PCB board.  Note that each of these kits come with and are designed to work a specific C2000 device - for example, the Peripheral Explorer kit is designed to work with the 'F28335.
2) For any of the Experimenter's kits you could, theoretically, solder/connect a transceiver onto the blank/prototyping areas of the board.  You could even utilize some of the schematics from the kits in (1).

Either option may be possible - depending on what device you are looking to use.


Thank you,
Brett

Hi Brett,

Thanks for the info.

i have some questions:

1)If i choose to communicate with the controller with the JTAG-USB connection,assuming i have a PC connected to the controller, what are its drawbacks against the CAN protocol? does the USB connection purpose is only for emulation, or i can use it also in real-time applications? i plan to use the "GUIcomposer" for making an interface on the computer. 

2) the Experimenter kit do have a USB with JTAG connection? in some of the pictures i see a USB plug but in others i don't. mabe there was an old version without it and in the current version it exists?

thanks,

Israel

Hi Israel,

1) In many of C2000's kits, we use a FT2232D or FT2232H to convert USB from a host PC to JTAG and also USB to UART/SCI.  That chip has two parallel paths and both can be utilized - and we often do in our kits.  JTAG should only be used for programming/debugging the device, but the UART/SCI channel could be used however you wish.  Another option would be just to put a 14-pin JTAG header on your final design, connect some external emulator (like an xds100v2) only when you need to program/debug, and put some cheaper version of the FT chip on your board that only has the USB-to-UART/SCI capability.

• CAN is a different type of interface and it has some advantages and some disadvantages when comparing to UART.  You can find a good comparisons between it (and others) across the web.
• If your end goal is only to interact with GuiComposer than I might recommend SCI/UART.  It is typically easier.

2) There are two version of the baseboard included with the Docking Station:

1. DIMM100 types (such as the TMDSDOCK28027) - an xds100v1 utilizing the FT2232D is on the baseboard.  No emulation logic is put on the controlCARD.
2. HSEC types (such as the TMDSDOCK28M36) - an xds100v2 utilizing the FT2232H is on the controlCARD itself (and a USB connector to interface with this chip is also on the cCARD).  No emulation logic is put on the Docking Station baseboard.

Hopefully this helps!


Thank you,
Brett

Yes. 
(FYI: that kit is of the DIMM100 type)

Hi Israel,

(based on your last post, I assume you are using the Peripheral Explorer kit - TMDSPREX28335)

There are several paths for potentially using the SCI of the Peripheral Explorer kit to communicate to something else (like a PC):

1. J12:  it interfaces as you describe - via RS232
2. USB:  first refer to the schematics for both the cCARD and the Peripheral Explorer baseboard.  If the baseboard's [M1]-J4 is populated and the cCARD's SW1 is open, the USB-to-SCI path is enabled (and contention-free).

Thank you,
Brett

Hi Brett,

yes currently i'm using the Peripheral Explorer kit - TMDSPREX28335.

i'm trying the second option you wrote. i populated J4 and opened SW1, i downloaded Hercules terminal, and trying to read a string i'm sending from the card (lab 9_1), but with no success.

i found out the USB is COM6, defined the setup in the terminal to match the card setup, but i don't see anything in the terminal.

maybe there is a problem to use the USB both to the CCS use for programming the card and debugging, and as a SCI input in the same time?

if there is a problem, programming the code into the FLASH, and using the USB only for power and for the SCI protocol will resolve the problem?

one more question: does the "TMDSDOCK28335 - Experimenter kit" can also communicate with the same way to the PC?

thanks,

Israel

Hi Israel,

My recommendation: start with a simpler goal to start, and build up your system in stages...

I'd recommend running the following example on the Peripheral Explorer board:
\controlSUITE\device_support\f2833x\v141\DSP2833x_examples_ccsv5\sci_echoback\

Description of the example is at the top of that project's main file.

Once this works, you'll have learned (or gained confidence in) the hardware using known good software.

(the Experimenter's Kit can interface to a PC via SCI/UART in the same general way - but will have its own particular jumper/switch settings to make it work)


Thank you,
Brett