CCS/LAUNCHXL-F28379D: Program does not "Halt" on main() and freezes on "Terminate" with --ramfunc=on

Hello Marko,

Marko Gulin said:

(1) Program does not pause when it reaches main(), but it starts as soon as device is programmed. I would like to have the program pause when it reaches main(), is this possible?

When I debug the example you provided, it always halts at main.

Please carefully check the debugger auto-run options and make sure it is configured to run to main:

https://software-dl.ti.com/ccs/esd/documents/users_guide/ccs_debug-main.html#auto-run-and-launch-options

Marko Gulin said:

(2) When I hit the "Terminate" button, program freezes. I tried pressing the RESET button on the LaunchPad, it does not restart the program. I need to power cycle the device in order for program to restart. I would like to have the program keep running when I hit the "Terminate" button, is this possible?

Yes you can terminate while the program is running. I just did that with your example application and I did not see any issues. What CCS version are you using?

Thanks

ki

Hello ki,

Thank you for your reply.

I went through the web page you recommended, and my settings match the settings on the web page.

I am using CCS Version: 9.3.0.00012.

Can you please confirm that when you open the "Blinky" example, the field

Project > Properties > Build > C2000 Compiler > Advanced Symbols > Runtime Model Options > Run functions from RAM. (--ramfunc)

is set to "on". When this field is clear (--ramfunc=off or --ramfunc=), the program halts on main and does not freeze on "Terminate". However, halt-on-main and continue-after-terminate do not work with --ramfunc=on.

Please note that I changed the post title to better describe the problem.

Thank you!
Marko.

Marko Gulin said:

is set to "on". When this field is clear (--ramfunc=off or --ramfunc=), the program halts on main and does not freeze on "Terminate". However, halt-on-main and continue-after-terminate do not work with --ramfunc=on.

ah, I just loaded the program in the attachment. When I checked the build options, I see that the field was clear.

I set it to "on" and rebuilt the application. When I go to debug the project, it does halt at main. But main is at address 0xcc19 and memory at that address is blank. I assume I am missing a step somewhere. Do I need to do tweak some other setting in the project? Or if you have a working application, you can attach that.

Thanks

ki 

Ah, I probably posted wrong version of the example project.

Here is the correct version.

7178.Blinky.zip

Thank you,
Marko.

Thanks, this looks more like it. When you halt the target, do you get a similar error below/

C28xx_CPU1: Trouble Removing Breakpoint with the Action "Finish Auto Run" at 0xcbc3: (Error -1066 @ 0xCBC3) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.4.0.00006) 

I still don't have an issue with the freeze on debug session termination of a running target. Which exact CCS version are you using?

Thanks

ki

Yes, I confirm that when I click "Suspend" I get the same error:

C28xx_CPU1: Trouble Removing Breakpoint with the Action "Finish Auto Run" at 0xcbc3: (Error -1066 @ 0xCBC3) Unable to set/clear requested breakpoint. Verify that the breakpoint address is in valid memory. (Emulation package 8.4.0.00006)

However, target halts, and I can resume it after that. When I suspend again after resuming it, I do not get errors any more. When I terminate the debug session after all this, the program keeps running.

Can you please try terminating the debug session without suspending the target before that. On my LaunchPad, the program freezes, i.e., one of the LEDs is ON and the other is OFF, permanently.

As for CCS version, I use Version: 9.3.0.00012

Thank you,
Marko.

You solution exactly answers my question, the "Run to symbol: __args_main" did the trick.

Thank you for your support!

Best regards,
Marko.