Simple enough.
But isn't the uCos init code assuming both that the timer is set correctly AND that it is set to the default?
I was thinking these assumptions could easily be checked, or that always explicitly writing to the desired (default) value
to the period registers would be OK, whether or not they really exist. With SOPC, the register space for the
timers has the same size regardless of options, so there is no risk of accessing the wrong register. This might
not be true for different HW, but init is expected to be custom anyway.
I don't think you would ever want a uCos app to run at timer interval different from what it thinks it is. Robustness?