This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Though I am currently being ignored by the powers that be (see this thread), I have another question.
I have the same debug task running on all three cores, and I managed to finally capture them with the MSA component without it crashing. What troubles me is that the timings are no where near accurate.
Timing the debug task explicitly (by just reading the DSP's tick count register), I know the task will execute for 11.1 ms, give or take a couple of micoseconds. The execution graph, though, shows the task only executing for 2 us. It's not a context switch because that's the ONLY task I have running. (My "Sync" task exits, the "Debug" runs and then exits followed by infinite "Idle".)
So two questions.
Why the great discrepancy?
Also, for core load balancing analysis purposes, exactly how synchronized is the timing among the core's? I mean, in the execution graph, are the tasks' start and stop time among the cores truly accurate?
(I'm attaching a .csv file of the session so you can load it yourself and see.)
Alex,
No worries, I will keep it here since it may help people find it when searching for similar issues.
Cheers,
Rafael