[SOLVED] Jlink Version 6.34, GDB connection error: Reply contains invalid hex digit 32

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

  • [SOLVED] Jlink Version 6.34, GDB connection error: Reply contains invalid hex digit 32

    Hello sirs,
    I use JLinkGDBServerCL.exe and arm-none-eabi-gdb.exe to debugging the my LPC boards, but the gdb cannot connect to the gdbserver due to "Reply contains invalid hex digit 32".
    The boards both used the JLink CDC firmware. I tried the old versions no such issue. Looks like this is a bug.

    JLink version: 6.34
    OS: windows10 & windows 7

    1. Start GDBServer

    Shell-Script

    1. JLinkGDBServerCL.exe -select usb=723160793 -if SWD -speed auto -device LPC54114J256_M4 -port 3400 -singlerun -strict



    2. Start GDB


    Source Code

    1. C:\Dpc\stationscript>C:/PROGRA~2/GNUTOO~1/62017-~1/bin/AR470E~1.EXE --exec C:/Dpc/.workspaces/lpcxpresso54114@1/cmsis_i2c_dma_b2b_transfer_master.out
    2. GNU gdb (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 7.12.1.20170417-git
    3. Copyright (C) 2017 Free Software Foundation, Inc.
    4. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
    5. This is free software: you are free to change and redistribute it.
    6. There is NO WARRANTY, to the extent permitted by law. Type "show copying"
    7. and "show warranty" for details.
    8. This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
    9. Type "show configuration" for configuration details.
    10. For bug reporting instructions, please see:
    11. <http://www.gnu.org/software/gdb/bugs/>.
    12. Find the GDB manual and other documentation resources online at:
    13. <http://www.gnu.org/software/gdb/documentation/>.
    14. For help, type "help".
    15. Type "apropos word" to search for commands related to "word".
    16. (gdb) target remote localhost:3400
    17. Remote debugging using localhost:3400
    18. Reply contains invalid hex digit 32
    19. (gdb)
    Display All





    Best regards
    haley
  • JLinkGDBServerCL.exe console output

    Source Code

    1. JLinkARM.dll V6.34 (DLL compiled Aug 7 2018 15:52:23)
    2. Command line: -select usb=723160793 -if SWD -speed auto -device LPC54114J256_M4 -port 3400 -singlerun -strict
    3. -----GDB Server start settings-----
    4. GDBInit file: none
    5. GDB Server Listening port: 3400
    6. SWO raw output listening port: 2332
    7. Terminal I/O port: 2333
    8. Accept remote connection: localhost only
    9. Generate logfile: off
    10. Verify download: off
    11. Init regs on start: off
    12. Silent mode: off
    13. Single run mode: on
    14. Target connection timeout: 0 ms
    15. ------J-Link related settings------
    16. J-Link Host interface: USB
    17. J-Link script: none
    18. J-Link settings file: none
    19. ------Target related settings------
    20. Target device: LPC54114J256_M4
    21. Target interface: SWD
    22. Target interface speed: auto
    23. Target endian: little
    24. Connecting to J-Link...
    25. J-Link is connected.
    26. Firmware: J-Link LPCXpresso V2 compiled Sep 23 2016 12:14:15
    27. Hardware: V1.00
    28. S/N: 723160793
    29. Checking target voltage...
    30. Target voltage: 3.30 V
    31. Listening on TCP/IP port 3400
    32. Connecting to target...Connected to target
    33. Waiting for GDB connection...Connected to 127.0.0.1
    34. GDB closed TCP/IP connection
    35. Restoring target state and closing J-Link connection...
    36. Shutting down...
    Display All
  • Hello,

    Thank you for your inquiry.
    Keep in mind that this here is no support forum. If you have pressing mattes (especially as a silicon vendor) we recommend using our official support channels, more information can be found in my signature.
    In your case it would be best if everything gets coordinated over Ruth.

    Best regards,
    Nino
    Please read the forum rules before posting: Forum Rules

    Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
    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 contact us per e-mail.
    Alternatively our support ticketing system can be used as well: segger.com/ticket/