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.

TMS320C2834x motor control EVM?

Other Parts Discussed in Thread: TMS320C28342, DRV8412, CONTROLSUITE, TMDSCNCD28069ISO

Hi everyone!

A customer of mine wants to commit to either the Delfino TMS320C28342, 28344, or 28346 but would like to first evaluate it through a motor control application.Their old design is currently using a Piccolo part although they want to use this specific Delfino product line in their next-gen device mainly because of its speed (300 MHz.).

I did some research and I am aware of the C28346 controlCARD that fits a DIM168 slot along with the experimenter kit available. How would the customer be able to implement the C28346 experimenter kit with motor control? Is there a simple solution here that the experimenter kit could interface with to provide motor control for this specific controlCARD?

If not, I think our only option here would be to drop in a slower, 200 MHZ C28343 (DIM100) controlCARD into an EVM such as the DRV8412 or TMDSHVMTRPFCKIT. The only problem here after reading a few E2E posts is that (1) the controlCARD pinouts might not exactly match those on the EVM schematic and (2) that there will be some porting effort involved with the motor control examples in controlSUITE for this EVM.

What do you guys think?

Thanks for your support,

Sean

  • Sean,

    couple things...

    1. We just announced brand new F2837xD series, with even more performance than the 300 MHz C2834x series.  Highly recommend they take a look a this new family first, it's a superior product.  We don't have any application kits avaialble yet for this family, but it could be plugged in to a kit like TMDSHVMTRPFCKIT (which has projects for F28335) and could run in pretty short time.

    2. Considering you would just be running a single motor, and maybe PFC, on one of these kits, it really doesn't matter if you test the 150 MHz F283x or a 200-300 MHz C283x.  Both of them will give identical performance out of RAM for a real time control loop.  So if they are set on C283x I would just start evaluation with the F283x, and as mentioned we have the high voltage TMDSHVMTRPFCKIT with some examples.  If they are doing low voltage, they may want to look at using the 90 MHz F28069 instead, as we have several projects on the low voltage kits like DRV8301-HC-C2-KIT and DRV8312-C2-KIT (these ship with F28035, would have to use TMDSCNCD28069ISO for the F28069).  The CPU performance and SW would completely port up to a C283x.

     

  • Gautam & Chris,

     

    This is awesome. Thanks for your quick responses here guys.

     

    Chris, in (1) you were saying that our new dual core Delfino's can be plugged into the TMDSHVMTRPFCKIT and run the F28335 SW examples. Why does the customer NOT need to port these examples over to the F2837D?

    Also, I'm assuming if these guys wanted to also test C28343 processor performance/functionality (benchmarking comparison), would there be any obstacles to doing this on the high voltage kit referenced above (in comparison to say an experimenter kit)? For example, I didn't see the possibility of an external JTAG emulator on the website for the TMDSHVMTRPFCKIT.

    If these guys wanted to still test the C28343 on the kit above(kill two birds with one stone since only one EVM would have to be bought), can the onboard emulator here keep up with a C2843x part or only F28335 and F2837D parts ?

    I will definitely push these guys towards the TMDSHVMTRPFCKIT with the F283x. However, I feel that they will still want to compare the C283x processor only against their old Piccolo device and in this case I am just trying to prevent them from having to buy two EVM's and two controlCARDs :)

    Thanks,

    Sean

  • "Chris, in (1) you were saying that our new dual core Delfino's can be plugged into the TMDSHVMTRPFCKIT and run the F28335 SW examples. Why does the customer NOT need to port these examples over to the F2837D?"

    There will be some minor porting for the memory map, checking I/O mapping, things like that. But in general all the core code should run as-is.

    "For example, I didn't see the possibility of an external JTAG emulator on the website for the TMDSHVMTRPFCKIT."

    This kit has on-board XDS100 isolated emulation and a 14-pin JTAG header for external emulation.

    "I feel that they will still want to compare the C283x processor only against their old Piccolo device and in this case I am just trying to prevent them from having to buy two EVM's and two controlCARDs :)"

    If they are already familiar with Piccolo then they can even extrapolate the benchmarking of running Piccolo from RAM to the C283x from RAM. There will be a direct correlation between the two based on clock rates as RAM all runs full speed with no wait states.

    Good luck