[SOLVED] Debugger Error Remote 'g' packet is too long

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [SOLVED] Debugger Error Remote 'g' packet is too long

    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.
  • Hi,

    To the best of my knowledge, e2studio uses the J-Link API directly.
    At least we have never heard of J-Link GDB Server being used e2studio internally.

    It is still possible that there is a wrapper inside e2studio that uses the “e2-server-gdb.exe” to abstract bewteen GDB and J-Link.

    Long story short:
    As the e2-server-gdb.exe seems to handle the GDB communication + comes from Renesas and you see a GDB communication issue, SEGGER is the wrong place to ask. You are better off asking Renesas here.

    Alternatively, you can debug the ELF file generated by e2studio via SEGGER Ozone:
    segger.com/products/development-tools/ozone-j-link-debugger/
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.