Profile clock not available with C6414 hardware

Hi Raif,

Thanks for your post.

I agree with you, profile clock differs from different versions of CCS and also with Emulation drivers.

CCS3.3 allows us to profile functions, but CCS4.2 does not give any active confgurations hence cannot profile functions.

Also, the clock options only show up if the emulation driver is exposing events that can be counted (typically it is cycles).  If nothing is being exposed then the clock feature will not be available.

Please check with the datasheet and check whether it is a 32-bit clock or 64-bit clock and set the profiler clock to 32-bit/64-bit in CCS 3.3 or 5.4.(which ever version is used), because the profile clock over flows after 2^32 cycles, when i say profile clock, it is the no. of cycles that we see in the lower right corner after enabling Profile  -> Clock -> Enable.

Please check the below link for the usage of the profile clock in CCS

http://processors.wiki.ti.com/index.php/Profile_clock_in_CCS

Having CCSv5 problems? Check out the CCSv5 Troubleshooting Guide

Hi Sivaraj,

my problem is not that the CCS versions behave differently. The question is, why does one type of hardware work, while the other doesn't? And why does the hardware type only matter for the first target connection? Swapping the hardware afterwards makes no difference.

I forgot to mention: I tried the C6414T and C6415T DSPs with silicon revision 1.0 and 2.0. It makes no difference.

Could a miss-configuration of DSP pins cause this behaviour?

Thanks,
Ralf

Hi Raif,

Thanks for your post.

I do agree with your concern.

Actually, there are known design exceptions to functional specifications for both silicon revision 1.0 & 2.0 but for C641xT DSP platform. This could be the reason for the issue which you have posted here.

Please check the design exceptions to functional specifications in the datasheet link below for C641xT platforms:

http://www.ti.com/lit/er/sprz216j/sprz216j.pdf

Kindly refer Section 2 in the above link.

Thanks & regards,

Sivaraj K

Hi Sivaraj,

the only design exception I can think of which could affect this problem is "Power Sequencing - IO Before Core". But we already connected pin W25 to VSS like suggested in a new revision and it doesn't make any difference.

Thanks,
Ralf

Hi Raif,

Thanks for your post.

As per your above reply, there could be possibilities of hardware clocking issue. It works one way like, when you start with the working board, disconnenct and then connect the non-working board, it uses the clocking cycles of the previous hardware, so it works this way. Instead, if you start with the non-working board first, disconnect and then connect the working board, it doesn't syncronizes with proper clocking signal.

You have two option to sort out this issue:

1. You have diagnostic scan utility option available in CCS for the JTAG emulator used and Please run the diagnostic scan for all emulators which you have with the non-working board and try to find out, whether it malfunctions on any peripheral drivers and it throws error on the console. Also, please try the same steps with the working board and run the diagnostic scan inorder to confirm, all peripherals are working fine.

2. There are chances for the incorrect pin configuration on the JTAG emulator interfaced with the board or any wrong pin configuration on the peripherals. It seems like, it should be a clocking pin issue.

3. Also, we shall probe the clock signals through oscilloscope and check whether we have a valid clock signal at appropriate clock pins of C641xT device as well as all peripherals by referring the datasheet of TMS320C641xT family. I mean debugging at the hardware level through scope is needed for further investigation.

Please let us know on the progress you made for the above issue.

Thanks & regards,

Sivaraj K