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!