Partial fix for timing of initial loop in Control module

Instead of jumping into the middle of the loop and trying to get the
timing right for the first loop, the code now falls through to the
WAITCNT at the beginning of the loop, and makes sure that the cog is
synchronized to the hub. Now at least the code doesn't freeze up when
it's set to 80 cycles and all control cog loops should have the exact
same timing if the cycle time is a multiple of 16, but I still have to
set up my logic analyzer to find out why I'm getting completely wrong
trace data at 80 cycles, while at 88 cycles, everything appears to work
as expected...