Dear all,

I developed a firmware for AT91SAM7S64 microcontroller on IAR Workbench v. 5.30 by IAR Systems.
When I download the code into microcontroller's RAM or Flash, the jtag shows this error message: "Memory access timed out @FFFFF240->JTAG speed too high?". I tried to change the JTAG speed in General Option\J-link/J-Trace\JTAG/SWD\ of IAR Workbench, but I haven't got any result.
Please note that the jlink software version is 4.08h and the JTAG speed is shown by jlink.exe software is 5kHz.

Have you got any idea about the cause of the problem?
Thanks in advance.
Best Regards.
Chobin.

Dear Alex,

Many thanks for your answer.
I launched the JLink exe file, and I noted that unfortunately the version of our J-Link-ARM's hardware is V3.0 and the DLL version is 4.08e.

The speed setting that I use in my EWARM project is auto, with the initial value 32kHz.
Which's the latest hardware version of the J-Link ARM?

Many thanks.
Best Regards.
Chobin.

Dear Alex,

I bought a J-Link ARM hardware version V8 and I've tested my firmware.
I haven't got the "Memory access timed out @FFFFF240->JTAG speed too high?" error message any more but I'm still having an issue when I try to launch the project in RAM debug modality.

If I set a breakpoint at the beginning of the code, the other part of it is executed correctly; otherwise launching the program without setting any breakpoint, the code is not executed properly.

Have I missed to set something else in the project option? Do I need to change the speed?
Currently the speed is set as auto, initial value 32k.

Many thanks for your support.

Best regards,
Chobin

Dear Alex,

Many thanks for your support and sorry for my late replay and if I didn't explain my problem clearly.

My issue is the following: there is a main subroutine from which a series of other subroutine is called.
In the compiling phase I don't have any error or warning meassage.
During the Flash debugging, I've noted that the firmware doesn't work as expected in the meaning that the code doesn't enter in a few of the subroutines called by the main subroutine i.e. setting a breakpoint inside these subroutines, the code doesn't stop on it. Making a 'Break' operation, the code seems trapped in the following code part.

__data_handler:
ldr pc,[pc,#+24] ;; Data abort
DC32 0xFFFFFFFF ;; RESERVED

From my understanding, the code jumps there in the case it doesn't find a correct address to go into. So, I suppose the subroutines in question are not compiled correctly by the Workbench.
Placing a breakpoint at the beginning at the main subroutine and making a 'step by step' debug, when the code arrives to the subroutines in issue, the error message "Missing pre-instruction" is printed out.

None code optimization level is selected in the project.

Please note the code is developped on IAR Workbench v5.20, the hardware version of the J-Link is 8.0 and its driver is updated to the latest version.

Any hint to solve the problem would be very appreciated.

Many thanks in advance for your support.

Best regards,
Chobin.