CCS/IWR6843ISK: Breakpoint enabled but not visible

Hello Paulina,

In the screenshot of the source file, line 1193 has a comment on it. This leads me to believe that the source file opened in the editor is not the same as the one used to build the executable. How did you set the breakpoint? Did you double click in the editor margin of that source file? If so, the entry appeared in the breakpoints view but not the editor margin of the source file?

Thanks

ki

Hi,

usually I use hardware breakpoints, which is why I right klick and use breakpoint ->hardware breakpoint. That break point shows up in the list but not on the margin. I have to enable it manually in the list and then it is marked as enabled but still not visible.

Additionally I tried to double click. Then again: break point shows up in the list but not on the margin. However I cannot enable that breakpoint- it tells me:

But then again I can set a breakpoint with double click in the mmwave.c file which is in the same folder as the mmwave_link.c folder. That breakpoint is visible in the file.

Do you need more information?

Thanks a lot in advance.

PaulinaL said:

Additionally I tried to double click. Then again: break point shows up in the list but not on the margin. However I cannot enable that breakpoint- it tells me:

Yes, as i suspected, the association is off. 

Did you build the executable on this same PC? Or was it built on another PC and you are trying to just debug it?

The executable itself was build on my PC, but the file I am trying to debug is from the SDK which I just downloaded.
I have had this error message before and after research in the forum I edited my lookup path. Until now I didn't have problems with that particular error anymore. I added the mmwave.c example, because as you can see on the bottom of the screenshot from the prior post, the mmwave.c file has the same compilation path but I can debug it without any problems. And since both files are in one folder I assumed that when one of the files is found due to the edited lookup path the other would be too.
Maybe you can avise me a better solution than editing the lookup path. 

Thanks a lot!
Paulina

PaulinaL said:

The executable itself was build on my PC, but the file I am trying to debug is from the SDK which I just downloaded.

I was experimenting with some of the mmwave examples and I have a better understanding of the environment now.

Both mmwave.c and mmwave_link.c are part of one of the libraries that are included in the project. Hence those source files are not compiled on your local machine. 

PaulinaL said:

I have had this error message before and after research in the forum I edited my lookup path.

Yes, hence how the modules view is able to find them.

Do you have multiple versions of the sdk? It looks like the mmwave_link.c file in your debug source search path is not the one used by the library.... like you are pointing to the wrong version than the one used to compile the library.

I do have two versions of the sdk on my PC and this is how my lookup path looks like. As there is an up and down option I assume that the order of the paths might be important. Maybe you can give me some more input on that.

Still I wonder how it is possible that one of the files (mmwave.c) is located correctly and apparently the other (mmwave_link.c) isn't as they are located in the same folder and the lab should be using files from the same sdk version.

Thank you for working through this with me.

Paulina

I did solve the problem to delete the path to the unused sdk. Thanks a lot!