CCS/MSP430F5529: DriverLib Bug

PS. It looks wrong in Timer_A_initUpMode and Timer_A_initUpDownMode too but it's in the right place for Timer_A_initContinuousMode()

Hi Matt,

Are you suggesting that for Timer_A_initUpMode(), the correct sequence should be:

-------------------------------------------------------

HWREG16(baseAddress + OFS_TAxCCR0) = param->timerPeriod;

if (param->startTimer) {
HWREG16(baseAddress + OFS_TAxCTL) |= TIMER_A_UP_MODE;
}

-------------------------------------------------------

because of the note "Modifying Timer_A registers" in section 17.2.1 of the User's Guide (https://www.ti.com/lit/pdf/slau208)?

Srinivas

Yes, but also imagine where you ask the timer to fire an interrupt in 100 uS. And then you take the interrupt and stop the timer. And then later you ask the timer to fire an interrupt in 100 mS. But as you start the timer, a 100uS ISR runs and immediately upon that ISR completing the old timer setting of 100uS fires even though you expected a 100mS interrupt. That is able to happen because you started the counter before you loaded the new value.

For much the same reason, it should also follow the CCIE setting, to avoid stray interrupts.