• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 374 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

ccs5.5 pro trace bug

si cheng
Expert 2685 points

hello:

I baught a XDS560V2 PRO trace receiver from TI estore, I use it to trace data from C6678 EVM board.I set the receiver buffer size to 1GB,and when the buffer is full, it will show the trace info on the CCS. Because the trace buffer is too large, it need several hours to get all the info on to the CCS. I  find that several hours later, the CCS trace have bug,please see the picture:

Q1： the Update Progress become to negative number，and yesterday，I have a another trace, the  Update Progress become to 148%,more  than 100%，when this bug happens, it will not updata the info from trace buffer to CCS. I am not sure whether this is a bug of CCS5.5 or not, if it's ,how can I solve this problem, because I need the trace info. If ccs get the trace info onto it last for several hours, this problem will occur.

Q2：another question , if I get the inclusive percent info， the top-level function maybe 100% or closest to it,

but actually，it's not， no one function's  inclusive percent info more than 20% in my project. The trace range I used is start and stop at address.

Q3: In the receiver/transport settings, I set the Num of pins is 17,default is 10, I am not clear if this have a influence, what 's the Num of pins used for?

Best Regards,

Si

  • 0
    TI__Guru**** 168297 points

    Si,

    Q1: The display issue should not happen, therefore it is probably a bug on the screen caused by the volume of data coming from the Trace pod. Unfortunately there will be no more bug fixes for CCSv5, therefore I imagine if this was improved in CCSv6 (released yesterday). You can install it in a separate directory and use it to debug the board.

    Q2: If I recall correctly, there was a problem with either the inclusive or the exclusive percent information in v5.5, but I can't retrieve the exact bug number. I recall that v6 has several improvements to that, therefore it may be worth trying with it as well.

    Q3: The number of pins sets the amount of pins used to transfer the data between thee device and the Trace pod. Therefore, it has a direct influence on the speed of the data transfer, but not all devices have the complete number of pins. It should not influence in the behavior you are seeing.

    Regarding the time that it takes to process and display the data, this is an intrinsic characteristic of the Trace buffer. Since the data is collected and stored in compressed form to do post-processing in CCS, the time to finish this is significant. I personally was never able to retrieve successfully more than 8MB of Trace buffer data, and even still it took several hours of data transfer and processing. Therefore, I strongly suggest you reduce your trace collection buffer and adjust the start and stop points carefully to get a narrower snapshot of the code execution.

    Hope this helps,

    Rafael