• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 38 subscribers
  • Views 180 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.

Original question:

TIDA-010938: How to reduce the execution time for Interrupt ISR if ISR fre. 21.667KHZ.

TIDA-010938: TIDA-010938: 21.667Khz ISR is Taking More time in free running/release mode compared to Debugging mode

Arun C
Prodigy 10 points
Part Number: TIDA-010938
Other Parts Discussed in Thread: LAUNCHXL-F280039C,

Tool/software:

I'm Using LAUNCHXL-F280039C With TIDA-010938 Project (with LAB10 Selection). But The ISR Execution time in release mode is 23.2uS and debugging mode is 8.23uS for ref. attaching waveforms.

I'd tried different Optimization levels from 0-5 but no impact observed. Please help on this .


The ISR timing checked in TPGPIO24 pin waveforms just after Code running start button pressed
  

  • 0
    TI__Intellectual 865 points

    Hi Arun, 

    1. Just to clarify, by release mode you mean running from flash?

    2. Have any changes been made to the code?

    3. Typically I recommend running lab 1 with the launchpad, to see basic functionalities and remaining labs with the hardware, since we also run for fault conditions. When you are running with the launchpad and if you import the lab 10 debug file in to the expressions window, could you confirm that you see a fault in the system? Does the timing have an influence if you comment out the following function:

    stringINV_Fault_Read(); //Function to read faults

    Please let me know if this helps.

    Thanks & best regards,

    Veda