null should do nothing for 2 steps (nop behavior)
RodrigoDornelles opened this issue · 0 comments
RodrigoDornelles commented
Please Describe The Problem To Be Solved
It is common between processors, to work with device synchronization, to ignore 2 cycles (in this case it would be two calls to driver_interrupt
) before running again.
Suggest A Solution
In order not to add any ram usage or increase complexity, it can be worked on in the state machine.
case FSM_3BC_WAITING_NOP:
app->state = FSM_3BC_RUNNING;
return true;