Hello,
We want't to debug a Renesas Synergy Platform MCU.
It's a Synergy S7 with Cortex M4 Core running at 240 MHz and equipped with 4MB Flash / 640 kB Ram.
The debugger we use is a jlink ultra+ V4.4, the serial number is 504402241.
So the start of the debug session is not a problem, but when we make some changes, recompile and
download the changed version nearly everytime this message appears:
'Download' has encountered a problem.
Failed to execute MI command:
load "C:\\Users\\myname\\Workspace\\Renesas_Synergy 2.00\\test_lcd_segger\\Debug\\test_lcd_segger.elf"
Error message from debugger back end:
Remote 'g' packet reply is too long: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
We use the Renesas Synergy e2studio Platform with following components:
e2studio 2022-04
SSP 2.30
JLinkARM.dll 7.60e
e2-server-gdb.exe 4.0.0.0
The GDB Command is only :
arm-none-eabi-gdb
Could someone give us an advice where this error come and how to fix it ?
It is very annoying always to close the debug session and to restart it for every little program change again and again.
Best regards,
H.N.
We want't to debug a Renesas Synergy Platform MCU.
It's a Synergy S7 with Cortex M4 Core running at 240 MHz and equipped with 4MB Flash / 640 kB Ram.
The debugger we use is a jlink ultra+ V4.4, the serial number is 504402241.
So the start of the debug session is not a problem, but when we make some changes, recompile and
download the changed version nearly everytime this message appears:
'Download' has encountered a problem.
Failed to execute MI command:
load "C:\\Users\\myname\\Workspace\\Renesas_Synergy 2.00\\test_lcd_segger\\Debug\\test_lcd_segger.elf"
Error message from debugger back end:
Remote 'g' packet reply is too long: ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff
We use the Renesas Synergy e2studio Platform with following components:
e2studio 2022-04
SSP 2.30
JLinkARM.dll 7.60e
e2-server-gdb.exe 4.0.0.0
The GDB Command is only :
arm-none-eabi-gdb
Could someone give us an advice where this error come and how to fix it ?
It is very annoying always to close the debug session and to restart it for every little program change again and again.
Best regards,
H.N.