Setting breakpoints in Keil

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
vmore
Offline
Last seen:7 months 1 week ago
加入:2018-03-01十八22
Setting breakpoints in Keil

Hello,

I was trying to set breakpoints in the code for a test example - proximity reporter. When the debugger starts, I get the following error:


BS \\prox_reporter_580\../src/platform/user_periph_setup.c\112
_______________________^
*** error 35: undefined line number

In this example, I set a break point at periph_init() function and as I can step through this code manually, it means that the debugger touches that line. This looks like something to do with the relative path not being recognised by Keil and some forward slash business. Is there a way to explicitly define a breakpoint(full file path)?

Device:
PM_Dialog
Offline
Last seen:5 days 8 hours ago
工作人员
加入:2018-02-08 11:03
Hi vmore,

Hi vmore,

This error was occurred because you added a breakpoint in a comment and not in code line. If you check again the code into periph_init() the 112 line is a comment. If you are in the debug mode, you will see that you are not able to add a break point in line 112. As I can imagine, first you added the breakpoint and then you went into the debug mode. In order to debug correctly your code, you should add the breakpoint into a code line, so just add it in a line before or in a line after the comment.

Thanks, PM_Dialog