RM46L852: CCSv12 - Debugger doesn't halt on main()

Gabriel B

Part Number: RM46L852
Other Parts Discussed in Thread: HALCOGEN

Hi,

I'm using Code Composer Studio version 12.2.0.00009 and when I start debugging, the debugger never halts at the main().
The program simply run as if there was no breakpoint. This behaviour makes it very hard to debug initialization code.

Here is my settings configuration:
After reading the FAQ, I think these would make sure the programs halt at the main().

Is there a way to force the debugger to consider my breakpoints?

I saw in another thread that the scripting console could give more information

JS:> eval("DEBUG_DumpBreakpoints()")

CortexR4: GEL Output: 	Memory Map Setup for Flash @ Address 0x0CortexR4: Breakpoint Manager Dump: Total Allocated Logical Breakpoints: 6

CortexR4: Breakpoint Manager Dump: Total Allocated Software Physical Breakpoints: 7

CortexR4: Breakpoint Manager Dump: Total Allocated Legacy Hardware Physical Breakpoints: 0

CortexR4: Breakpoint Manager Dump: Total Allocated 55 Hardware Physical Breakpoints: 0

CortexR4: Breakpoint Manager Dump: Total Allocated Thread Physical Breakpoints: 0

CortexR4: Breakpoint Manager Dump: 

CortexR4: Breakpoint Manager Dump: Enabled: 2

CortexR4: Breakpoint Manager Dump: 

CortexR4: Breakpoint Manager Dump: 	Hardware Configuration

CortexR4: Breakpoint Manager Dump: 		Location: 0x1d67c

CortexR4: Breakpoint Manager Dump: 	Debugger Response

CortexR4: Breakpoint Manager Dump: 		Condition: 

CortexR4: Breakpoint Manager Dump: 		Skip Count: 0

CortexR4: Breakpoint Manager Dump: 			Current Count: 0

CortexR4: Breakpoint Manager Dump: 		Action: Finish Auto Run

CortexR4: Breakpoint Manager Dump: 	Miscellaneous

CortexR4: Breakpoint Manager Dump: 		Group: Default Group

CortexR4: Breakpoint Manager Dump: 		Name: 

CortexR4: Breakpoint Manager Dump: 	Breakpoint set by the system

CortexR4: Breakpoint Manager Dump: 

CortexR4: Breakpoint Manager Dump: 	Hardware Configuration

CortexR4: Breakpoint Manager Dump: 		Location: C:\dev\fz\Example-Hercules-FreeRTOS\Debug/../source/sys_main.c, line 130 ("C:\dev\fz\Example-Hercules-FreeRTOS\Debug\mcu.out") (0x1d690)

CortexR4: Breakpoint Manager Dump: 	Debugger Response

CortexR4: Breakpoint Manager Dump: 		Condition: 

CortexR4: Breakpoint Manager Dump: 		Skip Count: 0

CortexR4: Breakpoint Manager Dump: 			Current Count: 0

CortexR4: Breakpoint Manager Dump: 		Action: Remain Halted

CortexR4: Breakpoint Manager Dump: 	Miscellaneous

CortexR4: Breakpoint Manager Dump: 		Group: Default Group

CortexR4: Breakpoint Manager Dump: 		Name: Breakpoint

CortexR4: Breakpoint Manager Dump: 	Breakpoint set by the user

CortexR4: Breakpoint Manager Dump: 

CortexR4: Breakpoint Manager Dump: Disabled: 4

CortexR4: Breakpoint Manager Dump: 

CortexR4: Breakpoint Manager Dump: 	Hardware Configuration

CortexR4: Breakpoint Manager Dump: 		Location: "C$$IOE$$"

CortexR4: Breakpoint Manager Dump: 	Debugger Response

CortexR4: Breakpoint Manager Dump: 		Condition: 

CortexR4: Breakpoint Manager Dump: 		Skip Count: 0

CortexR4: Breakpoint Manager Dump: 			Current Count: 0

CortexR4: Breakpoint Manager Dump: 		Action: Process CIO

CortexR4: Breakpoint Manager Dump: 	Miscellaneous

CortexR4: Breakpoint Manager Dump: 		Group: Default Group

CortexR4: Breakpoint Manager Dump: 		Name: 

CortexR4: Breakpoint Manager Dump: 	Breakpoint set by the system

CortexR4: Breakpoint Manager Dump: 

CortexR4: Breakpoint Manager Dump: 	Hardware Configuration

CortexR4: Breakpoint Manager Dump: 		Location: "C$$EXIT" (0x1e62e)

CortexR4: Breakpoint Manager Dump: 	Debugger Response

CortexR4: Breakpoint Manager Dump: 		Condition: 

CortexR4: Breakpoint Manager Dump: 		Skip Count: 0

CortexR4: Breakpoint Manager Dump: 			Current Count: 0

CortexR4: Breakpoint Manager Dump: 		Action: Terminate Program Execution

CortexR4: Breakpoint Manager Dump: 	Miscellaneous

CortexR4: Breakpoint Manager Dump: 		Group: Default Group

CortexR4: Breakpoint Manager Dump: 		Name: 

CortexR4: Breakpoint Manager Dump: 	Breakpoint set by the system

CortexR4: Breakpoint Manager Dump: 

CortexR4: Breakpoint Manager Dump: 	Hardware Configuration

CortexR4: Breakpoint Manager Dump: 		Location: "C$$IO$$"

CortexR4: Breakpoint Manager Dump: 	Debugger Response

CortexR4: Breakpoint Manager Dump: 		Condition: 

CortexR4: Breakpoint Manager Dump: 		Skip Count: 0

CortexR4: Breakpoint Manager Dump: 			Current Count: 0

CortexR4: Breakpoint Manager Dump: 		Action: Process CIO

CortexR4: Breakpoint Manager Dump: 	Miscellaneous

CortexR4: Breakpoint Manager Dump: 		Group: Default Group

CortexR4: Breakpoint Manager Dump: 		Name: 

CortexR4: Breakpoint Manager Dump: 	Breakpoint set by the system

CortexR4: Breakpoint Manager Dump: 

CortexR4: Breakpoint Manager Dump: 	Hardware Configuration

CortexR4: Breakpoint Manager Dump: 		Location: "C$$EXITE"

CortexR4: Breakpoint Manager Dump: 	Debugger Response

CortexR4: Breakpoint Manager Dump: 		Condition: 

CortexR4: Breakpoint Manager Dump: 		Skip Count: 0

CortexR4: Breakpoint Manager Dump: 			Current Count: 0

CortexR4: Breakpoint Manager Dump: 		Action: Terminate Program Execution

CortexR4: Breakpoint Manager Dump: 	Miscellaneous

CortexR4: Breakpoint Manager Dump: 		Group: Default Group

CortexR4: Breakpoint Manager Dump: 		Name: 

CortexR4: Breakpoint Manager Dump: 	Breakpoint set by the system

Best regards,
Gabriel

over 3 years ago

0 jagadish gundavarapu over 3 years ago

TI__Guru* 77936 points

Hi Gabriel,

After entering into debug mode, can you please click on Disconnect Target and Connect Target?

You will get this option by right click on the debugger.

Thanks & Regards,
Jagadish.

0 Gabriel B over 3 years ago in reply to jagadish gundavarapu

Intellectual 371 points

Hi Jagadish,

Thanks for your answer.

After doing the test, It still doesn't halt on main().

0 jagadish gundavarapu over 3 years ago in reply to Gabriel B

TI__Guru* 77936 points

Hi Gabriel,

Are you getting or not the "Loading Program window" before it taking to the actual debug screen?

Thanks & Regards,

Jagadish.

0 Gabriel B over 3 years ago in reply to jagadish gundavarapu

Intellectual 371 points

Yes; I do.

To be clear, my breakpoints do work.
Just not at startup. I need to pause the program so the breakpoints are "registered".

0 Gabriel B over 3 years ago in reply to jagadish gundavarapu

Intellectual 371 points

Here's a gif of what's happening.

As you can see, the breakpoint just doesn't do anything.

0 jagadish gundavarapu over 3 years ago in reply to Gabriel B

TI__Guru* 77936 points

Hi Gabriel,

Is this issue happening for this particular project only or happening for all projects?

Did you try any simple example projects of HALCoGen like LED blink?

..\hercules_examples\Launchpad\RM\RM46L8\Project_0

hercules_examples/hercules_examples - Software Examples for Hercules Processors (ti.com)

Thanks & Regards,
Jagadish.

0 Gabriel B over 3 years ago in reply to jagadish gundavarapu

Intellectual 371 points

Hi Jagadish,

Indeed, the example project stops at main(), which is exactly what I want.

The problem: The example project settings are identical to one of my projects.
The only difference I can see between the example project and mine is the usage of FreeRTOS...

I'm confused. Is there another settings page for the debugger?

Regards,
Gabriel

0 jagadish gundavarapu over 3 years ago in reply to Gabriel B

TI__Guru* 77936 points

Hi Gabriel,

Is your FreeRTOS project generated from HALCoGen?

I am suspecting clock initializations may not happening properly. So,

Is it possible for you to include your project source code into the example project and test it? And keep initializations same as example project.

Thanks & regards,
Jagadish.

0 Gabriel B over 3 years ago in reply to jagadish gundavarapu

Intellectual 371 points

Hi Jagadish,

jagadish gundavarapu said:
Is your FreeRTOS project generated from HALCoGen?

Yes exactly.

jagadish gundavarapu said:
I am suspecting clock initializations may not happening properly

What makes you think its a clock problem? Everything seems to work fine.
The only problem I have is the debugger not stopping on main properly.

jagadish gundavarapu said:
Is it possible for you to include your project source code into the example project and test it? And keep initializations same as example project.

The test has been done and it seems to work...
The CCS seems to be somehow configured differently than when I created one from scratch.

Do you have an idea where in the files CCS stores the configuration (in .cproject maybe)?
We could use those to compare the two instead of using the GUI.

0 jagadish gundavarapu over 3 years ago in reply to Gabriel B

TI__Guru* 77936 points

Hi Gabriel,

Gabriel B said:
Do you have an idea where in the files CCS stores the configuration (in .cproject maybe)?

I have no idea and i have to check with internal team on that.

Can you check below was properly set in debug configurations

You can find Debug configurations option in Run menu

Thanks & Regards,
Jagadish.

0 Gabriel B over 3 years ago in reply to jagadish gundavarapu

Intellectual 371 points

Hi Jagadish,

You will find my configuration in the first message of this thread.
As you can see, the configuration seems to be identical.

Currently, I'm copy-pasting the CCS project that works to create a new project.
It works, but it's less than ideal: I feel more confident when there's no "magic" in my build system.

0 jagadish gundavarapu over 3 years ago in reply to Gabriel B

TI__Guru* 77936 points

Hi Gabriel,

Gabriel B said:
As you can see, the configuration seems to be identical.

Yes, it is identical.

Is it possible for you to share your entire non-working project?

0 Gabriel B over 3 years ago in reply to jagadish gundavarapu

Intellectual 371 points

Hi Jagadish.

Right now, copy-pasting the valid project seems to work; I'm gonna close this thread.
Sorry for the people reading this thread; I don't have a solution for you.

Let me know if you find something else.

Regards,
Gabriel.

0 jagadish gundavarapu over 3 years ago in reply to Gabriel B

TI__Guru* 77936 points

Gabriel B said:
Right now, copy-pasting the valid project seems to work

Okay.

Gabriel B said:
Let me know if you find something else.

Sure, i will.

C2000™︎ microcontrollers

C2000 microcontrollers forum

RM46L852: CCSv12 - Debugger doesn't halt on main()