SES Debug not working with CLI example in nRF52 DK

[Jchristf]

I have a strange problem running the CLI example in the DK on the Nordic dev board with SES:  It works fine with build/run, but when trying to debug it pops up a message that it cant find a variety of files.  See attached screenshot.

I notice that the directory it is looking in (C:\build\...) is completely irrelevant and non-existing on my machine, so looks like it is a hardcoded path in SES/nordic project?

Even more strange:  If I ESC all the messages, it will start debugging (seemingly OK), but then suddenly pop up the same messages later in the session...

SES 4.16

nRF5_SDK_15.3.0_59ac345

[Jchristf]

I was able to solve this specific issue  by cleaning and rebuilding. I still have a problem that it doesn’t seem to be able to single step inside event handlers - quickly ends up in the assembly code only. Is there a know trick / setting to allow this? Thx

[Jørgen Holmefjord]

What kind of event handler are you not able to single step inside? Are you using softdevice in your application?

[Jchristf]

Im working today at my main office, which is a different DK, PC etc.  Im now getting the same error message as original stated, but a rebuild does NOT fix.   I'm adding screenshot of the secondary popup I receive as well. I receive both message for a lot of files.  As mentioned that path (C:/build/.. etc) does not make any sense on my PC, so must be a fossil from the project/SES?  )

[Jchristf]

PS: grepping the NRF5_SDK dir for the strange path, I get these hits:

Binary file components/nfc/t2t_lib/nfc_t2t_lib_gcc.a matches
Binary file components/nfc/t2t_lib/nfc_t2t_lib_gcc_no_fpu.a matches
Binary file components/nfc/t2t_lib/nfc_t2t_lib_iar.a matches
Binary file components/nfc/t4t_lib/nfc_t4t_lib_gcc.a matches
Binary file components/nfc/t4t_lib/nfc_t4t_lib_gcc_no_fpu.a matches
Binary file components/nfc/t4t_lib/nfc_t4t_lib_iar.a matches
Binary file examples/ble_central_and_peripheral/experimental/ble_app_interactive/pca10040/s132/ses/Output/Release/Exe/ble_app_interactive_s132_pca10040.elf matches

Looks like problem is the NFC library source information, not available where it expects?

I looked at excluding NFC from project, which would be fine for me, but there are just too many references across the CLI project to make that feasible...

[Jørgen Holmefjord]

You get this warning because the debugger is trying to locate the source files for the prebuild NFC T2T library, to allow you to debug these files as well. Since this library is not delivered in source code, you will not be able to debug it. Removing the checkmark next to "Show this dialog next time" and selecting Yes should allow you to continue the debug session.