We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Hello,
my problem is that with ULINK2 and AT91SAM7 ARM controllers I get a data abort exception when single stepping my code. It comes suddenly and may be at the first or more steps (1 to about 10 I guess). I haven't noticed that before. I cannot think it came directly after I updated my MDK ARM compiler. I have tried with various source codes and different boards. I have tried with ULINK-ME where the problem seems not to exist. When I run the code without the debugger no data abort is ussued. So I ask myself is the ULINK2 defective? Can it be repaired? Is there a firware issue with the ULINK2?
Has anybody experienced a similar problem so far?
Looking forward to hear your comments.
I don't know what the debugger can do or how to check what it actually does. But why should this happen? Bug in the debugger firmware? Since all ARM7 CPUs cannot do unaligned memory access.
I have just upgraded my MDK license to 4.11 - the most recent. Then I was asked to do a firware update of the debugger - Ulink-ME connected. after this upgrade I now have the same problems with the ULINK-ME as with the ULINK. My conclusion is - this must be a firwmare bug. Now I have 2 debuggers which don't work. Is there nobody else having this problem?
Lookin' forward to your replys.
When I think about it - it may be as you said an alignement problem. Maybe Keil have made a mistake with the introduction of the SAM3 controllers which support unaligned data access.