Thank you for continued investigation. The memory allocation with extra code added to CLA Task 2 is shown below: Regarding the extra code please note the following points: 1- Task2 which contains extra code still works fine in all cases. If Task1 is called alone then this task also generates the expected outputs and works fine. Only when both the tasks are called together (we are using software triggers to force CLA tasks) then we observe that Task1 does not update its outputs but Task 2 updated the outputs correctly. Task 1 is however getting executed as we have profiled it and discussed in the start of the thread. 2- The extra code does not include any additions in CPU to CLA or CLA to CPU message RAMs. It is simply a logic to gradually ramp up the battery current value from initial set point to a new set point (to avoid some over shoots) so the only effect that it can have could be addition of some more local variables in Task 2 and some additional code size. We suspect that it could be some memory leakage issue or some kind of optimizations by compiler. Can you provide some guide lines to systematically debug this issue?. We have not used any background CLA task and are not much aware of its use case. Please let us know if it is recommended to use it. If any additional info is required then please let me know. If you still think that the actual code can be helpful then please let me know and I will share the complete source files for CLA Task 2 for both cases.
↧