I've seen this a lot with openocd and arm cortex-m targets. There's always lots of finger pointing, but it's "incompatible" gdb version and gdbserver version. It's to do with the gdbserver sending an XML memory map that your version of gdb doesn't understand. (or at least, doesn't understand receiving it from the target) The "easiest" is finding the "right" version of gdb to use with the gdbserver you're using, which may be an up or a downgrade. There's some workarounds with manually specifying target type architecture and pointing to local memory map xml files and so on, but it's increasingly ugly.

Seeing as it looks like the gdb is built by openwrt, can you check if it has xml support built in?

Cheers,
Karl P


On 06/09/2013 02:06 AM, jonsm...@gmail.com wrote:
Any idea what I am doing wrong? Why are the registers too long?

jonsmirl@terra:/home/apps/openwrt$
./staging_dir/toolchain-mipsel_dsp_gcc-4.7.2_uClibc-0.9.33.2/bin/mipsel-openwrt-linux-uclibc-gdb
GNU gdb (Linaro GDB) 7.5-2012.12-1
Copyright (C) 2012 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=x86_64-linux-gnu
--target=mipsel-openwrt-linux-uclibc".
For bug reporting instructions, please see:
<http://bugs.launchpad.net/gdb-linaro/>.
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
Remote 'g' packet reply is too long:
00000000620000000a0000004000000000000000000000001050f780c080fc80439d11001050f780d0b2fc80d52ef5800000000000000000ca2ef580000000000040fb80a02ff580b02ff780000000000000000000000000000000000000000000000000ac72fc800000ff810000000060c2fc80d830f5800000000055aa55aa060000000000000001000000424644202c8000600402008000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
(gdb) show architecture
The target architecture is set automatically (currently mips)
(gdb)


---------------------------------------------------------------------

jonsmirl@terra:~$ openocd -f interface/olimex-arm-usb-ocd.cfg -f ralink.cfg
Open On-Chip Debugger 0.5.0 (2011-12-03-10:15)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.berlios.de/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'jtag'
2000 kHz
adapter_nsrst_delay: 100
jtag_ntrst_delay: 100
rt3050.cpu
Info : clock speed 2000 kHz
Info : JTAG tap: rt3050.cpu tap/device found: 0x1535024f (mfg: 0x127,
part: 0x5350, ver: 0x1)
Info : accepting 'telnet' connection from 4444
target state: halted
target halted in MIPS32 mode due to debug-request, pc: 0x80000204
Info : accepting 'gdb' connection from 3333
Warn : acknowledgment received, but no packet pending
Info : dropped 'gdb' connection


--
Jon Smirl
jonsm...@gmail.com
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to