A Problem occured when using J-Link RDI with IAR V4.41 for STR32 Cortex M3 Core

allan · Jun 26th 2008, 4:53am

I have J-Link V5.4 and using software version 3.84 with IAR EWARM V4.41
My Target has STR32 Cortex M3 Core.
When I tried to debug my board using J-Link with IAR V4.41, it had worked well.
But, when I tried to use J-Link RDI with IAR V4.41 for same board, problem had occered.
In J-Link RDI Releast note, above V3.80 of RDI supports Cortex M3(In S/W package 3.84 has RDI V3.82).

but, when using RDI debugging in IAR, EWARM dsplayed Error Message shown below, and halted.

"Could not write CPU register R15: Written: 0x2000004D, Read 0x2000004C"

Below text is from tail of the RDI log file.

T0FFC 001:418 JLINK_ReadProc (h = ARM, Addr = 0x20000E1C, 0x0004 Bytes, RDIAccess_Data32) returns RDIError_NoError (0004ms)
T0FFC 001:422 JLINK_WriteProc(h = ARM, Addr = 0x20000E1C, 0x0004 Bytes, RDIAccess_Data32) returns RDIError_NoError (0008ms)
T0F24 001:430 JLINK_ExecuteProc(..., h = ARM, StopOthers = TRUE)
***** Error: Could not write CPU register R15: Written: 0x2000004D, Read 0x2000004C

What was wrong?

Help!

SEGGER - Rolf · Jun 26th 2008, 6:43pm

IAR V4.41 is an older tool chain. It does not allow debugging of Cortex-M3 via RDI.
RDI is a standard for ARM7/9 cores only; opening it for Cortex-M3 is a new project.

So: Do not use RDI.

allan · Jun 27th 2008, 1:23pm

SEGGER - Rolf wrote:

IAR V4.41 is an older tool chain. It does not allow debugging of Cortex-M3 via RDI.
RDI is a standard for ARM7/9 cores only; opening it for Cortex-M3 is a new project.

So: Do not use RDI.

In that case, what does it mean 'Version 3.80 Support for Cortex-M3' in your RDI release note?

If above note means later version of RDI 3.80 supports Cortex-M3, which tool chain should I use?

SEGGER - Rolf · Jun 27th 2008, 7:42pm

RDI support for Cortex-M3 is a still inofficial, (not approved by ARM) extension
of the RDI protocol. IAR EWARM V5.11 should be able to handle it.

Share