This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SES Debug not working with CLI example in nRF52 DK

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

Parents
  • 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?  )

  • 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...

Reply
  • 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...

Children
No Data
Related