• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 82 subscribers
  • Views 823 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

CCS/TMS320F28377D: The different between run and step run in the ccs

shook xu
Intellectual 745 points

Part Number: TMS320F28377D

Tool/software: Code Composer Studio

hi！

I debug the same program . but when i run this program in the run ,half run ,step run the time is different. why?

in the run case the time is 214 cycle，step run is 160 cycle, the other is 184 cycle , why there is so much different？

regards

shook

  • 0
    TI__Mastermind 27200 points
    Shook,

    The difference between cycles counts is because the debugger flushes the CPU pipeline each time it reaches a break-point. If you experiment by changing the loop length, and measuring the run and single step cycle counts, you'll find the difference is linearly proportional to loop length.

    The cycle count measure using run is the actual time taken by the loop and should closely match what you see at GPIO104.

    Regards,

    Richard
  • 0 in reply to Richard Poley
    Intellectual 745 points
    hi
    Richard
    thank you for your answer
    the reason of the different is because the CPU pipeline write-read protection. in the step run mode the pipeline can't test the pipeline conflicts because the pipeline was flushed every step run. In the run mode we can test the pipeline protection
    is right?
    regards
    shook
  • 0 in reply to shook xu
    TI__Mastermind 27200 points

    Shook,

    That could be one reason, yes.

    Regards,

    Richard