TMS320F28379D: CCS GUI Crashing with fast GEL Script Output

Forgot to metion: I plan to take the output file to matlab and plot/analyze my data there. I've the sample time between each entry (0.1 ms) so it'll be easy.   

Pedro Paulo said:

Initial Approach:

I successfully plotted the variable data using the GUI Composer graph, but the refresh rate didn't help me. Adjusting the refresh rate through the $refresh_interval variable (as documented in [1]) proved ineffective.

The link you referenced is very old and I believe it was for an older GC version that is not supported anymore. I am confirming this.

Pedro Paulo said:

Alternative Approach:

I attempted to print the variable data to the console standard output and then redirect it to a file using a GEL script, as suggested in [2].

While this method yielded the desired results, the rapid output of the script (I reduced the GEL_SetTiumer() argument to 0.1 milliseconds) caused the CCS GUI to crash.

While did you mean 100 milliseconds? In any case CCS should not crash. Can you generate a debug server log while reproducing the crash and zip the log and attach it to this thread? Also attach a crash dump file.

For more information on both, please see:

https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

Pedro Paulo said:

My Query:

To avoid further GUI crashes, is there a way to disable/hide the console output generated by the GEL script? I belived that that's what caused the crash.

Is my current approach inefficient or unnecessary? Please offer any alternative suggestions or insights.

Thank you!

instead of printing the value to the console, perhaps you can try buffering the value to target memory somewhere? That may be more efficient.

Thanks

ki

Also, what version of GC are you using?

Ki said:

While did you mean 100 milliseconds?

Nope, 0.1 milliseconds. Here's the debug.log. Also,  CCS stops responding after I start the script. I'm using a demo/example code provided by TI to simulate the crash.

Ki said:

instead of printing the value to the console, perhaps you can try buffering the value to target memory somewhere? That may be more efficient.

How can I do that? I'm newbie on C200 micros and CCS. 

I'm using GC v2.

Pedro Paulo said:

Nope, 0.1 milliseconds

That is a very fast refresh rate. CCS certainly does not support view refresh rate at that speed. I'm skeptical that you can log a variable at that speed with GEL. Can you confirm that it was actually logging at that speed consistently?

Pedro Paulo said:

How can I do that? I'm newbie on C200 micros and CCS. 

Your target code would simply read the value of the register and the write it to some buffer (like an array you created in free memory)