Segger and debugging

RE: Segger and debugging

KMK — Tue, 11 Jan 2022 17:40:32 GMT

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

RE: Segger and debugging

KMK — Mon, 19 Apr 2021 09:48:55 GMT

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.

RE: Segger and debugging

Heidi — Tue, 13 Apr 2021 14:49:07 GMT

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.

RE: Segger and debugging

Heidi — Mon, 12 Apr 2021 14:03:59 GMT

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

RE: Segger and debugging

KMK — Fri, 09 Apr 2021 09:17:12 GMT

Also continuing to have the same problem with 1.5.0, in the different PC than where 1.4.1 was.

RE: Segger and debugging

KMK — Wed, 30 Dec 2020 13:05:39 GMT

I have also the same problem (using sdk v1.4.1 also with nrf9). First (a) few segger debug sessions with own build works ok but then starting to get the same bootable image error.
Like others already commented, also for me works if I reset my env and re-start again (in practice via git ). I have tried to look the differences in own vs default configuration settings in my application folder but have not found anything useful for this.

RE: Segger and debugging

Luca Gradassi — Fri, 14 Aug 2020 11:28:01 GMT

I've the same issue. This happens 2 or 3 times per day !! I've every time to clean up the build and restart....

RE: Segger and debugging

Tron — Fri, 07 Feb 2020 06:53:11 GMT

I found a solution, deleted the old build, and started a new.

THat is no explanation, however 🙂. This just happened, and now I know the fix the next time around .

RE: Segger and debugging

Heidi — Thu, 06 Feb 2020 15:25:20 GMT

Hi, I apologize for the late reply.

I'm looking into this, as I'm not sure why that's happening.

Best regards,

Heidi