Hello,
We found an issue with the background task in CLA. In our setup we have one EPWM triggered CLA Task (Task 1) and one SW Triggered Task (CLA Task 2) working in parallel with a Background Task continuously running (at 10kHz). CLA Load was checked and is under 50%.
When the background task is interrupted by a SW Triggered CLA task (via CLA_forceTasks API call)
the background task’s context is lost and data is corrupted. However if it is interrupted by a CLA Task triggered by e.g. EPWM it will store it’s context
correctly and behave as expected.
