The PeriodicTask currently occupies one of the Timers (TIMER32_0_BASE) to notify itself.
So when a second periodicTask is created, it will take that timer and assign it to itself. (deregistering the first PeriodicTask).
Possible solution is to have a separate interrupt handler that holds a list of periodic tasks to notify all of them, instead of having the PeriodicTask notify itself.
The PeriodicTask currently occupies one of the Timers (TIMER32_0_BASE) to notify itself. So when a second periodicTask is created, it will take that timer and assign it to itself. (deregistering the first PeriodicTask).
Possible solution is to have a separate interrupt handler that holds a list of periodic tasks to notify all of them, instead of having the PeriodicTask notify itself.