problem with DSK6455/EVM6455 and CCS 3.3

Amit said:

1. Can we use 6455 and CCS 3.3 using the embedded JTAG emulator or External JTAG emulator?

Yes, both methods work under CCS 3.3.

Amit said:

2. If yes, we were able to execute a program on 6455 using external JTAG emulator and CCS 3.3, but if we had to use the clock() to perform profiling, it returns 0 cycles, even after enabling the clock using the profile tab in the CCS

Which clock are you referring to?  Are you actually talking about an API or the clock that is built into the IDE?

 

Brad, I think Amit means at CCS Profile->Clock - you can Enable and View.

Amit, with the full version of CCS (not the one that comes with the DSK) you can connect both ways as Brad said. I just tested the clock with xds510 and it worked....

Mariana said:

 

Brad, I think Amit means at CCS Profile->Clock - you can Enable and View.

Yes, as Mariana mentioned CCS Profile->Clock is being enabled, and I am measuring profiling using the clock() API. I get the count as zero.

So, If i update my CCS 3.3, this problem should get solved?

 

When you go to Profile -> Clock you need to do "enable" (as you've already done) and "view" which it sounds like you have not done.  You'll then see a little "stop watch" appear at the bottom right corner of the screen.  It will count CPU cycles.  By double-clicking on it you can reset it.

I found this note in the compiler guide about the clock() API:

spru187n said:

The clock function works with the stand-alone simulator (load6x). Used in the load6x environment, clock() returns a cycle accurate count. The clock function returns -1 when used with the HLL debugger.

If you're looking to use an API, then you might want to try CLK_gethtime() from BIOS.  It utilizes a piece of hardware inside the 64x+ Megamodule called the Time Stamp Counter (TSC) which is a free-running counter that operates at CPU/1 frequency.

You shouldn't need to update to CCS 3.3 to get this functionality, though there have been a lot of IDE fixes in CCS 3.3 so I would recommend it regardless.

Brad

Amit said:

2. If yes, we were able to execute a program on 6455 using external JTAG emulator and CCS 3.3, but if we had to use the clock() to perform profiling, it returns 0 cycles, even after enabling the clock using the profile tab in the CCS

He is referring to a function which I believe is inside the RTS. I have seen requests about using clock() previously, and I believe this is a function that one must build specifically for that system based on device clock speed, etc. This implementation would likely use the CLK_gethtime() function Brad has mentioned and would turn that function's result into seconds. I do not believe that clock() does anything in its current, out-of-box state.

*edit* I added a little bit of text for clarity.