Hello support Team,
Our project is based on the software architecture of the example TI "« \CapTIvateDesignCenter\example_projects\CaptivateDesignCenterWorkspace\TI_Examples\FR2676_CAPTIVATE-BSWP »".
- The configuration chosen in the "CaptivateDesignCenter" is "I2C_Bluck" in the "Communication interface" tab.
- We have configured the Timer A3 setting as follows: P4.5 associated to TA3.2 en PWM mode (perio fixed by TA3CCR0 ), and P4.6 associated to TA3.1 en PWM mode also (perio fixed by TA3CCR0 ).
- Notice that Timer2 has the same configuration.
During the execution of the code, we notice unexpected behavior of Timer 3. In fact,in debug mode, its settings (TA3CTL, expected: 0x0111 like TA2, found 0x0131!)
Is modified and its initial configuration is lost with each passage of the function CAPT_appHandler () which is in the while (1) loop of the main ( as follow ) :
Questions
* Is the “CAPT_appHandler ()” responsible for this change?
* How can we ensure that our Timer 3 configuration is not lost and remains frozen?
Thanks for your response