NRF9160 SES 4.18 sudden weird reflashing after debugging session started

[GJSea]

Hi,

So I've been developing just fine on the latest V1.0.0 SDK and SES 4.18. I literally stopped and started a new debugging session and suddenly SES is trying to reflash something after the first line of the main call - Now I'm unable to develop at all and at a loss as to what happened.

- F5 debug (well after this previous bug's workaround)

- Breakpoint hit in z_thread_entry (thread_entry.c)

- Next breakpoint hit in void main(void)

- F10 to step to the first code line in main() and this dialog appears:

If I try and pause debugging it is spinning in the k_cpu_idle loop in z_SysFatalErrorHandler() The below in the Output window:

J-Link: Flash download: Bank 2 @ 0x00000000: Skipped. Contents already match
Download successful
Timeout while preparing target, RAMCode did not respond in time. (PC = 0x0002A848, CPSR = 0x0002A848, LR = 0x01000007)!
Failed to prepare RAMCode using RAM
Timeout while preparing target, RAMCode did not respond in time. (PC = 0x0002A848, CPSR = 0x0002A848, LR = 0x01000003)!
Failed to prepare RAMCode using RAM
Timeout while programming sector, RAMCode did not respond in time. (PC = 0x0002A848, CPSR = 0x0002A848, LR = 0x01000003)!
Timeout while erasing sectors, RAMCode did not respond in time. (PC = 0x0002A848, CPSR = 0x0002A848, LR = 0xA1000003)!
Failed to erase sectors.

No clue why SES is trying to reflash during a debugging session as soon as execution starts.

Thx!

[Joakim Jakobsen]

Hi. 

I can confirm that we are seeing issues when programming from SES. The feedback we have gotten is that this should be fixed in the upcoming 4.18A version. 
Unfortunately I don't have any more information to when this release is going to be available. 

Best regards, 
Joakim

[sread]

Any update on the timeline for SES 4.18A release?

[GJSea]

Interestingly I recently discovered what was causing this weird unexpected re-flashing of the device. It ended up being a certain number of breakpoints set in SES, or set in a certain combination that triggered SES to do something strange with JLink. All I needed to do to resolve the issue was remove the last breakpoint I set when the reflashing appeared, or Clear All Breakpoints and the reflashing ceased.

[Joakim Jakobsen]

Thanks for the feedback.

I'll see if I can get some more information about the upcoming release.

Cheers