Forums

TI CCS question

Started by Kesh June 3, 2004
Hi all,

I'm getting used to the TI C6701 EVM & CCS IDE (coming from ADI EZKIT 
background) and trying to figure out what's going on with CCS. I have 
few questions, and if anyone can answer'em, I'd greatly appreciate it!!

I've noticed the CCS takes up close to 100% of CPU time when the DSP is 
running. Is this because of the CCS/CPU emulating the DSP?

Is there any setting where I can turn off this emulation or whatever 
causing the high CPU usage? We're trying to do data acquisition at the 
same time the DSP is running (on the same PC). CCS taking up all CPU 
time concerns us as it may cause the DAQ to drop some samples.

Would using a hardware emulator, XDS510/560, help reducing the CPU load?

Finally, does TI EVM have any monitor program a la EZ-KIT? I don't see 
any EEPROM on the EVM, so I'm guessing it doesn't.

Thanks!!
Kesh Ikuma
Hello Kesh,

> I've noticed the CCS takes up close to 100% of CPU time when the DSP is > running. Is this because of the CCS/CPU emulating the DSP?
No. May you have a LED somewhere on the DSK that you can toggle. That will prove that it's real.
> Is there any setting where I can turn off this emulation or whatever > causing the high CPU usage?
I don't know.
> Would using a hardware emulator, XDS510/560, help reducing the CPU load?
XDS510 I think will not change CPU usage. XDS560 I think does. - But no guarantee
> Finally, does TI EVM have any monitor program a la EZ-KIT? I don't see > any EEPROM on the EVM, so I'm guessing it doesn't.
Monitor program ? You can have Memory Windows, Scope screens and by using "Probe Points" you can decide when in your program they should be updated. "Debug -> Probe Points" (first right click in code to toggle Probe Point) Good luck, Wolfgang
Wolfgang wrote:
>>I've noticed the CCS takes up close to 100% of CPU time when the DSP is >>running. Is this because of the CCS/CPU emulating the DSP? > > > No. May you have a LED somewhere on the DSK that you can toggle. > That will prove that it's real.
I do know the programming is running on the DSP (I'm running codec I/O). Maybe I wasn't too clear. I would like to know if the CPU is busy because it is keeping up with what the DSP is doing. My understanding of "emulation" is for another processor (in this case, the CPU) mimic/monitor the DSP. Anyone please correct me if I'm wrong.
>>Would using a hardware emulator, XDS510/560, help reducing the CPU load? > XDS560 I think does. - But no guarantee
Is there anyone out here who can confirm this?!?! Thanks!! Kesh
"Kesh" <tikuma@hotmail.com> wrote in message
news:c9pu6v$6o6$1@solaris.cc.vt.edu...
> Wolfgang wrote: > I do know the programming is running on the DSP (I'm running codec I/O). > Maybe I wasn't too clear. I would like to know if the CPU is busy > because it is keeping up with what the DSP is doing. My understanding of > "emulation" is for another processor (in this case, the CPU) > mimic/monitor the DSP. Anyone please correct me if I'm wrong.
When you configure CCS (via the cc_setup.exe program) as a SIMULATOR then all the DSP functionality is mimicked by your computer. In this case you should expect CCS to use as much CPU as possible to crank through your program. When you configure CCS for EMULATION then CCS will compile, link, and download your code to the DSP. When you hit Debug -> Run it starts the DSP running the code you downloaded. This requires practically zero processing by the computer. There are a few ways to know whether you're doing simulation or emulation. An easy way to tell is to close CCS, unplug your board, and then restart CCS. If you have CCS configured to do emulation (i.e. run code on the DSP) then it will not open unless the board is powered up and connected. If you get some kind of error message when you try opening CCS with the board powered off then you probably have CCS configured for emulation. The way to check this with more certainty would be open cc_setup.exe and see which configuration you're using.
> >>Would using a hardware emulator, XDS510/560, help reducing the CPU load? > > XDS560 I think does. - But no guarantee > > Is there anyone out here who can confirm this?!?!
What board are you using? The Spectrum Digital DSK boards all have the emulation hardware right on the board. This allows you to plug your USB cable directly into the board rather than use a $2000 XDS510 emulator. Either way should give you the same result. Both do hardware emulation. It sounds to me like you have CCS configured as a simulator. Brad
Brad,

Thanks for the reply. We're 100% sure the program is running on the DSP 
as we're doing audio I/O. And the developm't board is TI C6701 EVM.

> When you configure CCS for EMULATION then CCS will compile, link, and > download your code to the DSP. When you hit Debug -> Run it starts the DSP > running the code you downloaded. This requires practically zero processing > by the computer.
The CPU does zero processing while the DSP is running, but yet Windows XP Task Manager still reports 99% usage by cc_app.exe?? Does this mean that the cc_app.exe takes up the CPU time for no real reason? Kesh
> I've noticed the CCS takes up close to 100% of CPU time when the DSP is > running. Is this because of the CCS/CPU emulating the DSP?
I disabled RTDX and turnded off "Real Time Analysys" and "All Trace Event Classes" in my CDB file Global Settings section. That helps a lot on my PC, but some PCs dont have a problem with it. I use Norton Antivirus instead of McAffee. McAffee was unuseable with CCS on one of my PCs.
>Is there any setting where I can turn off this emulation or whatever >causing the high CPU usage? We're trying to do data acquisition
you can also try a Debug:RunFree so the PC doesnt try to talk to the emulator.
>Would using a hardware emulator, XDS510/560, help reducing the CPU
load? I am using an XDS510-pp-plus (parallell port), doesnt seel to help, maybe the USB version would have less overhead.
> Finally, does TI EVM have any monitor program a la EZ-KIT? I don't see > any EEPROM on the EVM, so I'm guessing it doesn't.
I know of no monitoring programs except the stuff that happens in DSP BIOS. -howy zaxcom engineer