Roberto,
[quote user="Roberto Romano"]file is set to stdout, when I enable logging no way to set filename, using browse don't select directory but search for a file. I created qs.log empty file than I set that to logging.[/quote]
I see this issue with the Debug Server log commands. I will file a bug about it.
[quote user="Roberto Romano"]
loaded to launchpad tm4c123gxl then run to breakpoint trace remain stuck at, disable trace reenable and trace run smooth.
Clear all breakpoint reset then run stop again to where breakpoint is, trace step regular.
[/quote]
Thank you for sending the project.
I loaded the code to my TM4C123GXL Launchpad and, if I understood correctly your procedure, I set a breakpoint at a specific location in the code (I set one at line 670 of the <qs-rgb.c> file). Then I ran my code and it halted at that location (which is expected). I then put the code to run (F8 key) a few more times and it always halted at that location (also an expected behaviour). Then I removed the breakpoint and put it to run again (F8 key). The code did not halt this time - it ran free.
I also did a single step when it reached the breakpoint. It worked fine - i.e., it ran to the next line without having to disable/delete the breakpoint.
That is what I think we are seeing different behaviour, is that so? In your case the code is halting all the time even when the breakpoint is cleared or disabled, right?
One detail I just thought about it is that you can try to change the Debug Configuration settings in CCS. Terminate the debug session then go to menu Run --> Debug configurations --> select the qs-rgb configuration on the tree on the left and un-check the option Restore breakpoints from previous session as shown below:
Apart from this, I am unsure on what else to suggest, apart from the Troubleshooting page I sent before (create a new workspace, erase the previous debug configuration settings, erase the temporary files, etc).
Regards,
Rafael