-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
I'm having a lot of difficulty trying to debug a 1611 target on a Linux machine. I have the most recent Linux version of msp430-gdbproxy that is available on the website (dated 2003/03/04). I have also downloaded and built the most recent versions of binutils-050107, gcc-3.2.3, gdb-5.1.1, and msp430-libc with the appropriate files from the mspgcc CVS as of Friday, January 7th. I can build for the 1611 target with no problem. I've also been able to debug a 149 target with no problem. msp430-gdbproxy doesn't seem to recognize the 1611 microcontrollers. It might be worth noting that I'm running gdbproxy and gdb on seperate computers, and I don't have the full toolchain installed on the one running msp430-gdbproxy. Has anybody successfully debugged a 1611 target using gdb under Linux? Is there a more recent version of msp430-gdbproxy? Any help is greatly appreciated. Here's a capture of my gdb session, with debug output from msp430-gdbproxy following: [j...@smarty]$ msp430-gdb GNU gdb 5.1.1 Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=msp430". (gdb) set remoteaddresssize 64 (gdb) set remotetimeout 999999 (gdb) file build/msp430x1611/superbob/superbob.elf Reading symbols from build/msp430x1611/superbob/superbob.elf...done. (gdb) target remote random:2000 Remote debugging using random:2000 _reset_vector__ () at rs_startup.c:24 24 __asm__ __volatile__ ( (gdb) monitor identify Current target device is a 'Device unknown' (type 0), so: ~ Main memory is from 0xF000 to 0xFFFF (4096 bytes) ~ Info memory is from 0x1000 to 0x10FF (256 bytes) ~ RAM is from 0x200 to 0x2FF (256 bytes) ~ Up to 2 breakpoints are supported ~ Emulation level is 0 ~ Clock control level is 0 ~ VCC is from 1.800V to 3.600V ~ Has a test Vpp pin (gdb) break main Breakpoint 1 at 0x661e: file sb_main.c, line 955. (gdb) cont Continuing. warning: Remote failure reply: E00 [j...@random]$ msp430-gdbproxy --debug --port=2000 msp430 Remote proxy for GDB, v0.7.1, Copyright (C) 1999 Quality Quorum Inc. MSP430 adaption Copyright (C) 2002 Chris Liechti and Steve Underwood GDBproxy comes with ABSOLUTELY NO WARRANTY; for details use `--warranty' option. This is Open Source software. You are welcome to redistribute it under certain conditions. Use the '--copying' option for details. debug: msp430: msp430_open() info: msp430: Target device is a 'Device unknown' (type 0) notice: msp430-gdbproxy: waiting on TCP port 2000 notice: msp430-gdbproxy: connected debug: msp430: msp430_connect() debug: msp430: msp430_current_thread_query() debug: msp430: msp430_offsets_query() debug: msp430: msp430_set_gen_thread() debug: msp430: msp430_read_registers() debug: msp430: msp430_read_mem(0xE000, ptr, 2, ptr) debug: msp430: msp430_read_mem(0xE002, ptr, 2, ptr) debug: msp430: msp430_remcmd() debug: msp430: msp430_rcmd_identify() debug: msp430: msp430_read_mem(0x6618, ptr, 2, ptr) debug: msp430: msp430_read_mem(0x6618, ptr, 2, ptr) debug: msp430: msp430_read_mem(0x661A, ptr, 2, ptr) debug: msp430: msp430_read_mem(0x661C, ptr, 2, ptr) debug: msp430: msp430_add_break(0, 0x661e, 2) error: msp430: Invalid parameter(s) (3) debug: msp430: msp430_set_ctrl_thread() debug: msp430: msp430_resume_from_current(run, 6) error: msp430: Unknown device (5) - --- Jacob Welch -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFB4p9DqGrC+n10BqoRAoqFAJ9XU9K7IzArMv7XtZyQCTF0oum74ACgtzBC VHEhCWsfxysxSRIDx6JlL4o= =7uV/ -----END PGP SIGNATURE-----
