I got a C2000 Piccolo from Maker Faire for over a month, still don't know how to use it.

If you download the ControlSuite software, there should be lots of examples and help to get you started.  It is a free package from TI and I usually go there first to find a "blinking LED" project for my particular processor.

The QSG that comes with the kit mentions to download controlSUITE from

www.ti.com/c2000-launchpad

and follow the instructions.

The wiki is also a good site (and we need to link to it more easily from the URL above)

http://processors.wiki.ti.com/index.php/C2000_LaunchPad#C2000_LaunchPad_.28LAUNCHXL-F28027.29_Resources

there is also the www.ti.com/launchpad site, which has a C2000 sub-site

http://www.ti.com/ww/en/launchpad/c2000_head.html

Thanks all for the quick reply.

I prefer to have a easy interface like Arduino. I will wait for 2 weeks then.

My plan is to upgrade an old system which is using TMS320C32. The system is really simple but complicated due to limited resource 10 years ago.

The Code Composer has so many version and only one version works for this chip. Is there a forum of how to debug TMS320C32? Not many support for this old chip and when I tried to read variable from the Emulator, it gave me wrong value sometimes... >_<

PS. If there is any code migration technique, please let me know. Cheers

Andy,

Given the age of the part, I don't think there will be any migration information available.  Can you give me some information on what the C32 is interfacing to and what it is doing?  I can point you in the right direction if I have a little more information on the application and its needs.

Regards,

Hi,

I'm new to TI DSP, I'm a FPGA engineer, know simple MCU coding.

1. Every time when I make a new program for C32, I need to paste the boot loader from previous binary file to the top of the new binary file before I upload the whole thing to a flash. Where is that boot loader comes from? Can I read what that binary boot loader says? If it is a generic one, it should be good (Like an Ardunio bootloader). If it is a custom-made one, I will be in trouble (How can a human read a binary bootloader?)

2. When I use the Emulator (SEED-XDSpp), it seems like the C32 has to have the same image in the flash in order to make debugging work. And it took over 10 mins for the emulator to upload the image file. Is it the case or I did something wrong? Any tutorial of using emulator? (I can't find a new emulator anymore, I don't mind to buy an emulator from TI)

3. How to calculate the timing? The original code has a long piece of code inside the interrupt routine. It is a periodic interrupt and the original designer didn't check the timing I guess. Then, other engineers started adding it longer and longer. I'm afraid the interrupt routine timing is longer than one period of interrupt.

It will be great if you can give me some hints about these questions. Thanks

Andy,

1. Without the source information for the bootloader it will be very hard to know how it works.  I don't think anyone around here is familiar with this part or its associated tools.
2. That makes sense that the image must be programmed in flash and the IDE in order to make debugging work.  This is how our current software and devices work.  10 minutes to program the device does seem like a long time.  I honestly don't know how long it should take on this device though.  I don't think our current emulators support this device.
3. If you can modify the code, I would use a GPIO to monitor the interrupt timing.  You can set a GPIO high at the beginning and low at the end of the interrupt and then monitor the GPIO with a scope.

Hi,

Is there a next generation of TMS320C32? Migrate a system to next chip is always a headache.

I assume the bootloader is just a generic one but how did the original engineer create it though? Is it in CCS 4.0? If I can create one, may be I can do the bit compare to be sure it is a generic one.

Yes, for the interrupt timing, GPIO or LED blink is the last resource I can use. Some engineers put printf in the interrupt subroutine code and messed up the timing. Is there a work around method to put the printf to a buffer? (Like DMA and stuff? I prefer if there is a library)

It will be great if you know any know has used TMS320C32 or Code Composer 3.0/4.0 before. It is not easy to get information on the website. Thanks

So I looked in the datasheet and it looks like there is some kind of bootloader present on the device.  The bootloader is only there to copy program code from the external memory interface into RAM before the application starts executing.  The header that you have to append is probably code that the bootloader needs in order to identify what to copy.  This is probably specific to your particular board.  I can't easily find any internal information on this device, so my best advice is to read through the documentation available on the product page:

http://www.ti.com/product/tms320c32

Our current run time support library does support redirection of printf to a buffer, but I'm not sure about the code for that device.  If you can find a compiler guide for that device, the information on redirecting stdout would be there.

I understand this device is difficult to work with, but I'm afraid we won't be able to provide you with much help on this device because of its age.

BR,

Hi all,

I'm a electrical engineer with interest in motor control and power electronics.

I bought the dual motor control development kit with C2000 and c28035/piccolo to learn more about how a actual frequency converter actually works and try do experiment with sensorless control

However, the "getting starting"-support was very insufficient for people like me who are new to MCU programming. Also the sample project was made for CCS 3 and did not work with CCS34 which was included. I worked for hours to clear build errors, but for each new fault clearance I received a dozen more.

By coindidence i found crosshairs' package with gui and CCS filed for ccs4, but i still have some problems getting a error free build.

Is there any working samples for CCS4 which I can use to learn how to "play around with" a real project? Blinking lights or running motors, i dont care - all i want is a sense of getting something to work.

Hi Yngve,

Exactly which kit did you buy?  Could you provide a link to it?

CCS 3 is a very old version...we are currently at CCS v5.5 with version 6 due to come out soon.  I wonder if there is a newer version of the example software available for CCS5.  Have you downloaded controlSUITE?  There are lots of example projects there that should just work.

Trey German said:

Hi Yngve,

Exactly which kit did you buy?  Could you provide a link to it?

CCS 3 is a very old version...we are currently at CCS v5.5 with version 6 due to come out soon.  I wonder if there is a newer version of the example software available for CCS5.  Have you downloaded controlSUITE?  There are lots of example projects there that should just work.

Hello Trey!

I bought this kit: http://www.ti.com/tool/TMDS2MTRPFCKIT

The samples were CCS3.3, the included CCS was 4.2.1 (and no instructions on how to register, so i'm running eval version with 20 days left).

I have downloaded the controlSUITE, but I did not find samples spesific to Piccolo F28035. However, at crosshairs homepage there is a TSP for the TMDS2MTRPFCKIT written for CCS4 (Link: http://crosshairsembedded.com/TMDS2MTRPFCKIT)

Luckily, a former employee of Crosshairs is working across the hall at my office (this is actually an insane coindidence, and i didnt know that TI had a deal going on with crosshairs until after I received the kit and did a google search for better documentation than what was included).

Ok, so first off make sure you have the latest version of controlSUITE which can be downloaded from here:

ti.com/controlsuite

Second, go ahead and download CCSv5 from here:

http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_5_Downloads

You can license it with the XDS100 option which will give you an unlimited unlocked copy of CCS.  After you install it if you need help/more details setting that up let me know.

Once you've downloaded and installed controlSUITE, you can import the project(s) found in c:\ti\controlsuite\development_kits\LVMultiAxis+PfcKit_v1.4

and they should build.  If they don't let me know and I'll alert the appropriate parties to get this fixed.

OK, thanks Trey.

I'll keep you posted

Trey German said:

Ok, so first off make sure you have the latest version of controlSUITE which can be downloaded from here:

ti.com/controlsuite

Second, go ahead and download CCSv5 from here:

http://processors.wiki.ti.com/index.php/Download_CCS#Code_Composer_Studio_Version_5_Downloads

You can license it with the XDS100 option which will give you an unlimited unlocked copy of CCS.  After you install it if you need help/more details setting that up let me know.

Once you've downloaded and installed controlSUITE, you can import the project(s) found in c:\ti\controlsuite\development_kits\LVMultiAxis+PfcKit_v1.4

and they should build.  If they don't let me know and I'll alert the appropriate parties to get this fixed.

OK,

That actually worked out perfectly. Thanks for letting me know :)

Now you (TI) only have to add this information inside the boxes (either on a big yellow note or an actual update on the disk).

I apologize the bring-up was not as smooth as it should be.  I'll provide your feedback to the appropriate team.

Trey German said:

I apologize the bring-up was not as smooth as it should be.  I'll provide your feedback to the appropriate team.

I like to think that if it all were plug and play, I wouldnt have learned anything about all the things I've been through the last days :)

Hi,

I wonder if the TI version of Arduino IDE is ready?

I really need to port the old code from TMS320C32 to a new chip.

Thanks,

Andy

Andy,

Its almost ready.  We've released 3 internal alpha builds and will be doing an external beta release in December.  Look for it on the energia website energia.nu

Any update with the arduino look alike software? Thanks.

Yes, I'm actually working on the release now. It should be released next Thursday and will be a public beta. We've worked out a lot of bugs over the past month but I want to get some more feedback before we go to a GA release.

BR,