Details
Description
rcX V2.0 automatically started the cyclic timer during rX_TimCreateCycle. rcX V2.1 creates the timer internally in stopped mode and the user needs to activate it using rX_TimSetTimer.
This is an API incompatibility which should be fixed.
NOTE: Starting it manually also does not work, as it causes a data abort.
Known Workaround (sequence):
- Use a normal timer (rX_TimCreateTimer) with a callback.
- The the task waiting that should be waiting on a cycle into wait (e.g. by letting it wait on an event/semaphore)
- Let the callback wake up the waiting tasks (e.g. Signal event/semaphore)