[Solved][GDB-Server] flash-download: Reply contains invalid hex digit 116

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

  • [Solved][GDB-Server] flash-download: Reply contains invalid hex digit 116

    Hi,

    often while flashing an LPC2368 I receive an error message from gdb:

    Source Code

    1. Transfer rate: 3071 KB/sec, 3773 bytes/write.
    2. Ignoring packet error, continuing...
    3. C:\workspace\Openkeyer_v2\openkeyer\armkeyer_v3/flash.gdb:27: Error in sourced c
    4. ommand file:
    5. Reply contains invalid hex digit 116


    Sometimes it is possible to reconnect to the core using the 'target remote' command, sometimes not. If not I get the following message:

    Source Code

    1. Remote communication error: No error.


    The log output from GDB-Server is:

    Source Code

    1. ...
    2. Downloading 4096 bytes @ address 0x0000BFA0
    3. Downloading 2664 bytes @ address 0x0000CFA0
    4. Downloading 792 bytes @ address 0x0000DA08
    5. Resetting target
    6. Debugger terminated connection ! // <-- "Reply contains invalid hex digit 116"
    8. Connected to 127.0.0.1
    9. Debugger terminated connection ! // <-- "target remote..."


    This is the flash script:

    Source Code

    1. # File to flash
    2. file armkeyer_v3.elf
    4. # Connect to GDB Server
    5. target remote localhost:2331
    7. # Flash configuration
    8. monitor flash device = LPC2368
    9. monitor flash download = 1
    11. # Set speed to maximum
    12. monitor speed auto
    14. # GDB Server defaults to big endian
    15. monitor endian little
    17. # Reset device
    18. monitor reset 0
    20. # Remap first 64 bytes to flash
    21. monitor long 0xE01FC040 = 1
    23. # Flash device
    24. load
    26. # Run
    27. monitor reset
    28. monitor go
    Display All


    The JTAG-Speed does not affect this behaviour. I am using arm-elf-gdb v6.8.50 and arm-eabi-gdb v6.8 from Yagarto and tried GDB-Server v3.90d and v3.94.
    I am using the ARM board for about one year now and it used to work with j-Link and flash-download.
    Debugging works more often than not. Sometimes the program on the controller does not start after issuing the 'continue' command and the GDB-Server looses the connection to gdb. After a power-cycle of the ARM-board and reflashing the controller it will most likely work. Once the 'continue' command succeeded the debugging session is stable.

    Does anyone have any ideas?

    Thank you

    - Michael Geselbracht

    The post was edited 1 time, last by let ().

  • It seems to be a problem with the newer GDB-Server versions. I have downgraded to v3.82 and everything seems to work.
    There is still the message 'ignoring packet error' but apparently it does not harm.