• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 38 subscribers
  • Views 217 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.

TIDA-010054: Questions about TIDA-010054 source code

Johnny Chen
Expert 4920 points
Part Number: TIDA-010054

Tool/software:

Hi Champ,

I am asking for my customer.

They are evaluating TIDA-010054, and have few questions about the source code.

(1). Entering ISR, there are having counters (isr1Ticker++ / isr2Ticker++) added up in ISR1 and *in ISR2, any specific use for the counters ? any purpose for the two counters ?

(2). There is GPIO redefined. Debugging and Relay control are in conflict with GPIO58 but it's not used, is there any consideration that remains / keeps in the source code ? any use / design concern for that ?

(3). What are the A0-A3, B0-B3, C0-C3 tasks switching modes and uses in main.c file ?

(4). The command slow start mode in ISR2, is there a flowchart to illustrate ? Contains the feedback using IDFM for moving average and mapping process.

Thanks and regards,

Johnny

  • 0
    TI__Expert 4400 points

    Hi Johnny,

    Thanks for reaching out. Fin my answers below:


    (1) These ISR tickers are used to monitor the ISR execution. ISR1 is executed at 100kHz and ISR2 is executed at 10kHz, so isrTicker1 should be 10x isrTicker2. Its just to monitor if ISRs are executed at the expected rates.

    (2) GPIO 58 is only used for the relay control. The XBAR configuration is not needed.  I think it is a relic form a previous version. 

    (3) These tasks are lower priority task which are executed when there is no ISR pending. After initialization in the main the first jump is to  (*Alpha_state-Ptr)() which is task A0. If the timer is not overflown yet , all the A tasks are executed In our case we have only task A1. If the timer has overflown we change Alpha_STate_Ptr = B0 and in the next interval all the B tasks are done in that case we have B1 , B2 and B3. If the B task timer has overflown we jump back to A tasks. C tasks are not used in this example.

    (4) I am not sure to which part of ISR 2 you are referring to. In general all the references for the control loops are slewed here, avoiding sudden jumps in  the control loop references, which helps with stability.

    Best regards,

    Andreas