Hi,
I am referring to this post https://developer.qualcomm.com/forum/qdn-forums/hardware/qca4020-qca4024...
I have the same problem. I am running Eclipse on a Windows host, OpenOcd and GCC are exactly the versions that are required by the documentation for the dev board. All jumpers are set correctly and the sleep mode is OFF. I can build, download and run the hello world demo. I can start the debugging in Eclipse and hit the default breakpoint @app_start as set in the debug configuration. From there on I can single step, but when I set a breakpont somewhere else it does not get hit. For example in hello_world.c line 65 where the "hello world" string gets printed.
If I exchange the app_start breakpoint with the breakpoint mentioned above in the debug configuration, the breakpoint gets hit once during start-up. From this point on it will not get hit.
What I can observe in Eclipse is that the icon for the breakpoint is different from the breakpoints that are set using gdb.init. Currently I have no clue what these different icons stand for.
Doing the same with gdb and openOcd on a command line results in the same behavior. The breakpoint is not hit!
There must be a way to set breakpoints and debug an application in the usual way. I can not believe that no one is doing this.
Thanks and best regards for your help
Andreas
Kindly refer to https://developer.qualcomm.com/project/hello-world-w-qca4020-dev-kit and set breakpoint at "app_init" instead of "app_start" and in case of error, provide us the console log after you hit the first breakpoint and not able to set the breakpoint issue.
Hi Raja,
thanks for the reply. Actually app_start was a typo, the first breakpoint in the debug configuration is set to app_init. That is confirmed. Nevertheless the issue still exists. The first breakpoint is hit correctly all others that will be set during the debug session are not. Here is my console log, after hitting the first breakpoint. There is no additional console output, when I set an additional breakpoint.
Thanks Andreas
Console log
Well, I provided the requested data, but I do not get any response on that?
Note: Try to limit the breakpoints to maximum of 4-5, make sure you delete the older breakpoints to verify if the workaround helps:
Let me know if you still face any issue while setting breakpoint in eclipse.
Hi Raja,
thanks for the reply. Actually my status is the following: If I change my Eclipse debug configuration to not start the gdb server but only the openOCD ( <debug_configuration>/ tab:Debugger: uncheck "Start GDB session" = unchecked) and I start the GDB server externally via a command console, the behavior is the same as you described above. I can delete and set breakpoints, the brekpoints are hit.
The drawback is of course there is no link to the source code shown in Eclipse. Debugging works only command line based with GDB, no Eclipse support, which is not what I want.
It seems that the breakpoint set commands generated in Eclpse (double click) will not be forwarded to GDB.
Do you have a working setup for a debug configuration for Eclipse, that allow for source code based debugging support as expected for Eclipse CDT?
Thanks and best regards
Andreas