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

Segger and debugging

When I try to debug my nrf9160 app through segger, it never starts. Hitting the pause button brings me to main.c in the mcuboot project, and it stops on line 214, Unable to find Bootable image. 

 

The code runs  perfectly outside the debugger. I use mfw 1.1.0 and Segger V4.20a. 

Suggestions?

Tron

  • Hi!

    Due to an answer in this thread already being verified, I did not receive a notification from your comment, so apologies for the late reply. I was just made aware of it today. In the future, you will receive an answer much quicker if you create a new ticket.

    I can't find any bug report about this, so I will put one in and let you know when I hear back regarding your issue.

    Best regards,

    Heidi

  • Hi!

    Does it help to run "Project" -> "Run CMake"? This will start the configuration phase of the build process again, which might be easier than restarting the whole project again.

  • Heidi, I was not able to reply to the latest message, thus replying to the main post.

    "Does it help to run "Project" -> "Run CMake"?" I dont remember did I try that Cmake re-run or not, I will check that if the problem is coming later again.
    At the moment (thanks to latest project restarting and maybe due to disabling some debug prints) seems to be working. 

    Also my colleague said that he started to have similar problems, he also "solved" those by re-installing some parts.

    On the last week I had took copies of debugging-ok and debugging-nok folders of my app. some notes of comparison by beyond compare.

    no difference in source code

    build_nrf9160dk_nrf9160ns/zephyr/zephyr.map files are exactly the same (but different dates, that's good to show that those had been re-compiled)

    build_nrf9160dk_nrf9160ns/mcuboot directory:

    .ninja_deps: file sizes very different, OK: 230k, NOK: 389k

    zephyr.map files are exactly the same (but different dates, that's good to show that those had been re-compiled)

    zephyr\edt.pickle: not exactly the same. I dont know meaning of that file but non-working one has one extra part starting on 0x000032E5 and beyond compare shows for its content to be partition related, even if just above is similar section (and that above section is also in the file in OK folder). Attached image shows it.

  • I had again these errors but now found this, and clearing all the breakpoints really solved the issue, at least now.

    devzone.nordicsemi.com/.../nrf9160-ses-4-18-sudden-weird-reflashing-after-debugging-session-started

Related