uVision Debugger Crashes

 uVision Debugger Crashes

Cortex M3 Cpu.

I'm having a number of problems with the uVision debugger; we have two setups one with V3.40 and one with 3.50 installed, building the same project.

On version 3.40 we must keep a memory window open pointing at internal flash, otherwise the debugger when it starts running outputs "Cannot Access Memory", on the times it won't start, clicking the debug icon, causes entry then rapid exit from the debugger. the only way to recover seems to be to quickly access the memory window and change the address.
When the debugger is happy everything runs as expected.

On version 3.50, we get the problems above with the additional the program when it finishes initialising the heap section before calling the rt_init it hard faults, with “Cannot access memory†in the output window and internal flash appears to of gone AWOL.

The hardware is 100% the same, we have an external SRAM device that uses 8bit accesses, both setups use the same startup file where we configure the FMSC timing.

The project files are the same, the jtag is different I.E ulink2 and ulink me, but swapping them made no difference, and using two ulink2' made no difference.

Does anyone have any ideas, I'm all out...

TIA,
Dave

 RE: uVision Debugger Crashes

Coming back to my own question/problem.

Even though V3.50 had been installed and a hardboot done, when I came in today, hit build all, loaded into the debugger, and now it works 100%... I must admit I'm not happy that I don't know why it was failing, and why it was failing where it was.

This is not the first time we have had symptoms like this. So when you have problems on your on your target reboot the development machine!

 RE: uVision Debugger Crashes

FYR. (Not sure if it will be helpful.)

http://www.keil.com/forum/docs/thread14502.asp

(Just guess.)
Maybe, try it on a new PC with a new installed OS, and only use one USB device?

 RE: uVision Debugger Crashes

Thanks John, that explains some other symptoms we have experienced, I don't think it relates to the issue we were having but the next time it crops up I'll see if it has any effect.

Cheers,
Dave