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.

TI CCS: Breakpoint with action as Write Data to File disabled, pops "The selected action is not valid at this time."

Hello Experts,

I am using TI Code Composer StudioTm integrated development environment (IDE) v12.5.0 to debug an example application which works differently on a free run (fails) and stepping through, and as plain breakpoints with the action "Remain Halted" do not help, I am trying to set its action as "Writing data to File" to log the value of a register as encountered over a normal, uninterrupted executable binary run.

With above property set for it, the action breakpoint is always listed as disabled.

On checking it under the Breakpoints tab (from View > Breakpoints) to enable it, it shows the below Pop-up from the Breakpoint Manager:

The selected action is not valid at this time

Even the Read data from File action gave a similar situation but I switched to Write one on realizing that closely matches my requirement. The same behaviour is noted whenever this breakpoint is enabled with the AM263 device execution core R5F_0 is connected and whether the program is paused around its start or the end.

Checking conditional breakpoints documentation from CCS v12.5 didn't help as it doesn't find anything when searched on breakpoints or actions.

Please guide me on how to make use of such an action on CCS.

Thanks for any efforts taken to answer it.

  • Hello,

    I am trying to set its action as "Writing data to File" to log the value of a register as encountered over a normal, uninterrupted executable binary run.

    Please note that this feature using breakpoints under the hood so the target is indeed temporarily halted to write to a file.

    On checking it under the Breakpoints tab (from View > Breakpoints) to enable it, it shows the below Pop-up from the Breakpoint Manager:

    I see several other breakpoints disabled in your screenshot. Do you have the same issue with all of them? Or just the one where you are trying to write to file?

    Thanks

    ki

  • Hi ,

    Thank you for responding.

    Please note that this feature using breakpoints under the hood so the target is indeed temporarily halted to write to a file.

    I now realize that I had missed selecting a .dat file under the Breakpoint Properties to be able to actually write data to the specified file.

    Now that the File property is also set under the breakpoint, I am able to enable this breakpoint from the start of my binary execution, as well as see the data saved on the chosen file as the execution crosses that line.

    Do you have the same issue with all of them? Or just the one where you are trying to write to file?

    Only the highlighted one with its action set as Write Data to File, rest all breakpoints were the default ones as came up on double-clicking a line number and worked as expected by pausing execution on source hit.

    Thanks,
    Harshit