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
2. Start GDB
Display All
Best regards
haley
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
2. Start GDB
Source Code
- 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
- GNU gdb (GNU Tools for ARM Embedded Processors 6-2017-q2-update) 7.12.1.20170417-git
- Copyright (C) 2017 Free Software Foundation, Inc.
- License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
- This is free software: you are free to change and redistribute it.
- There is NO WARRANTY, to the extent permitted by law. Type "show copying"
- and "show warranty" for details.
- This GDB was configured as "--host=i686-w64-mingw32 --target=arm-none-eabi".
- Type "show configuration" for configuration details.
- For bug reporting instructions, please see:
- <http://www.gnu.org/software/gdb/bugs/>.
- Find the GDB manual and other documentation resources online at:
- <http://www.gnu.org/software/gdb/documentation/>.
- For help, type "help".
- Type "apropos word" to search for commands related to "word".
- (gdb) target remote localhost:3400
- Remote debugging using localhost:3400
- Reply contains invalid hex digit 32
- (gdb)
Best regards
haley