AM2432: How to enable debugger breakpoints on core-1

Hi Eli,

The process to set the breakpoints for core-1 is similar to what you have done for core-0. 

Eli Mordel said:

The CCS allows me to put breakpoints for core-0 but refuses for core-1 - "No Assosiated code..".

Can you please tell is this message coming when you try to keep breakpoint at specific line of code or the line of code doesn't matter?

Also can you please provide a video capture of the issue to reproduce or analyze at our end?

Regards,

Tushar

Hi Tushar,

It refuses to put breakpoint on any line.

It worked several weeks ago but I forgot maybe I've changed something by mistake.

so now the code is running and I can single step on disassembly but not c code.

Thanks,

Regards,

Eli

Hi Eli,

It seems the code has changed for the core-1. Can you try once after recompiling the project once?

Please check the build configuration as well before compiling. It should be debug for debug build.

Please refer below image.

Regards,

Tushar

Hi Tushar,

I'm in debug mode with -Og optimization.

The debugger for both cores set to break in main - maybe that's the problem ?

here are the setups 

I see diferences between cores setup - maybe I should check or add something ?

Thanks,

Regards,

Eli

Hi Eli,

Eli Mordel said:

The debugger for both cores set to break in main - maybe that's the problem ?

The breakpoint to main is intentional and not the cause of problem. This breakpoint is the first breakpoint when you load the program via CCS JTAG.

Eli Mordel said:

I see diferences between cores setup - maybe I should check or add something ?

Can you please select all the option in Launch Option menu shown above for Core-1.

Regards,

Tushar

Hi Tushar,

I've set every field on the debug configuration , identical for both cores.

Still only core-0 allows breakpoints.

Core-1 refuses with the same reason - "No Code Is Assosiated with..."

What does it mean "No Code Is Assosiated with..." ?

I did also try "Load Symbols" - but I get the same result.

Thanks,

Regards,

Eli

Hi Eli,

Is this specific to this example or it comes with any example for core-1?

Also have you tried after rebuilding the project once?

Eli Mordel said:

What does it mean "No Code Is Assosiated with..." ?

This means the line/code where you are trying to put breakpoint doesn't exist in the loaded binary.

Regards,

Tushar

Hi Tushar,

I'm not using an example now it's my next product code.

The problem is only at core-1 . Core-0 breakpoints are working fine.

I did clean and rebuild the project - the same.

I've added in properties -> source lookup path , my project folder.

Now I can set a breakpoint only in ccs breakpoint dialog but no blue dot in the code and the code runs but does not stop there (not on any line).

I've put breakpoint on the disassembly - same - no blue dot and doesnt stop there.

Am I missing some setup ?

I must have a way to put breakpoints - the code is very complicated to debug .

Please help me.

Thanks,

Eli

Is there any article I can read ?

Thanks,

Regards,

Eli

Hi Eli,

Eli Mordel said:

Is there any article I can read ?

Please refer breakpoints for details.

Regards,

Tushar

Hi Eli,

Can you please check the *map file generated?

Please check the map file whether the symbols on which you are trying to put breakpoint are compiled or not? Do they exist in the generated map file?

Also what symbol you see when you add breakpoint in the code?

Regards,

Tushar

Hi Tushar,

Yes they are in the map file and the addresses correct - DDR Memory.

I can see them on the disassembly dialog . I can even put a breakpoint on the disassembly dialog but - no blue dot in code view and doesnt stop 

What is the difference between the cores , in that respect ?

Thanks,

Regards,

Eli 

Hi Eli,

Can you please check the below setting for core-1?

Make sure the option to Allow software breakpoints to be used is enabled for core1.

Regards,

Tushar

Hi Tushar,

I think we have the same 

What else can be checked ?

Thanks,

Regards,

Eli

Hi Tushar,

Sorry for my mistake the picture taken for core-0 but for core-1 it's the same.

Thanks,

Regards,

Eli

Hi Eli,

The screenshot you shared above seems to be from core-0. Can you please check the same for core-1?

Can you please do one more experiment? Try loading the example of core1 to core0 and let me know the result.

Regards,

Tushar

Hi Tushar,

Yes it's the same setup for both cores.

I'll try to load core-0 code to core-1.

Thanks,

Regards,

Eli

Hi Tushar,

It's a great idea !

When I load core-1 code to core-0 then I have same problem - no breakpoints.

So what's wrong here ?

Thanks,

Regards,

Eli

Hi Eli,

Thanks for the above the experiment. It means that the issue is not with the core settings but the binary itself. 

I am not sure how to debug this further as I can't reproduce the issue at my end.

You will need to experiment it by commenting some part of the code which you think may led to this issue.

Can you step debug it step by step instead of keeping breakpoint at certain location and check are you able to reach there? 

Regards,

Tushar

Hi Tushar,

Following your idea  it prooves that the problem is not the debugger but the code.

Can you please help me fixing it ?

Thanks,

Regards,

Eli

Hi Tushar,

I can view the disassembly and single step but it's a complicated C++ code - it's not practical to debug this way.

How can code cause such a behaviour ?

Thanks,

Regards,

Eli

Hi Eli,

We can try printing the logs to narrow down the issue. Can you please try adding the debug logs in the code where you want to set breakpoints?

Add the some message in the code and check whether those prints are coming on console or not.

Or you can debug the complete application by adding logs(not efficient way to do it) to the code if it works.

Regards,

Tushar

Hi Tushar,

Yes I can use printf() and logs buts it's a very long way to go I prefer to activate the debugger.

My main() and app_main() are both in DDR.

Is it possible that the debugger cannot set a breakpoint there because it thinks it's not writable ?

Is there a way to make ut writable for the debugger ?

Is there a way to put jtag breakpoint ?

Thanks,

Regards,

Eli

Hi Eli,

Only keep the print statements at location where you want to put breakpoints to narrow down the issue instead of logging the complete application.

Our aim currently is to analyze the behavior of why the binary is not allowing CCS to have a breakpoint.

Regards,

Tushar

Hi Tushar,

Thanks for helping me out.

Please try to find out what should I change in the code.

Regards,

Eli

Hi Eli,

I have not faced this issue till now, so it's bit difficult for me to figure out what going wrong with the binary. 

My next debug steps will be based on results from your experiments.

Regards,

Tushar

Hi Tushar,

I hope you'll find the answer.

Thanks for all your efforts and help.

Regards,

Eli