that should work. i don't understand the pending. sorry i'm not more help.
did you build with debugging symbols? how did you build your binary? what were the compile switches. what platform is this for? what does your make line look like On Fri, Mar 2, 2012 at 4:24 AM, ramakrishna reddy <[email protected]>wrote: > The tools i am using are > > *gdb --- v7.1 > msp430-gdb -- v7.2* > > The procedure i am following is as follows, > > $*mspgdb -jd /dev/ttyUSB0 uif gdb* ---- output is as follows > > MSPDebug version 0.18 - debugging tool for MSP430 MCUs > Copyright (C) 2009-2011 Daniel Beer <[email protected]> > This is free software; see the source for copying conditions. There is NO > warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. > > Trying to open UIF on /dev/ttyUSB0... > Initializing FET... > FET protocol version is 20407001 > Configured for JTAG (2) > Set Vcc: 3000 mV > fet: FET returned error code 4 (Could not find device (or device not > supported)) > fet: command C_IDENT1 failed > fet: identify failed > Trying again... > Initializing FET... > FET protocol version is 20407001 > Configured for JTAG (2) > Sending reset... > Set Vcc: 3000 mV > Device ID: 0xf26f > Device: MSP430F2616 > Code memory starts at 0x2100 > Number of breakpoints: 8 > Bound to port 2000. Now waiting for connection... > > > In second terminal i am invoking the msp430-gdb as follows, > $*msp430-gdb main.exe* -- the out put is as fllows > > GNU gdb (GDB) 7.2 > Copyright (C) 2010 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-pc-linux-gnu --target=msp430". > For bug reporting instructions, please see: > <http://www.gnu.org/software/gdb/bugs/>... > Reading symbols from > /opt/ubiMote/src/app/CH_Switch/RadioCountToLeds/build/ubimote/main.exe...done. > (gdb) *target remote localhost:2000* > Remote debugging using localhost:2000 > _reset_vector__ () at > /opt/mspgcc4-20110312/build/gcc-4.4.5-build/../gcc-4.4.5/libgcc/../gcc/config/msp430/libgcc.S:615 > 615 > /opt/mspgcc4-20110312/build/gcc-4.4.5-build/../gcc-4.4.5/libgcc/../gcc/config/msp430/libgcc.S: > No such file or directory. > in > /opt/mspgcc4-20110312/build/gcc-4.4.5-build/../gcc-4.4.5/libgcc/../gcc/config/msp430/libgcc.S > (gdb) *load main.exe * > Loading section .sec1, size 0x24ec lma 0x2100 > Loading section .sec2, size 0x40 lma 0xffc0 > Start address 0x2100, load size 9516 > Transfer rate: 2 KB/sec, 3172 bytes/write. > (gdb) *break CC2420ControlP__CC2420Config__syncDone* > Function "CC2420ControlP__CC2420Config__syncDone" not defined. > Make breakpoint pending on future shared library load? (y or [n]) y > Breakpoint 1 (CC2420ControlP__CC2420Config__syncDone) pending. > (gdb)* info break* > Num Type Disp Enb Address What > 1 breakpoint keep y <PENDING> > CC2420ControlP__CC2420Config__syncDone > (gdb) *break CC2420ControlP__syncDone__runTask* > Function "CC2420ControlP__syncDone__runTask" not defined. > Make breakpoint pending on future shared library load? (y or [n]) n > (gdb)* info break* > Num Type Disp Enb Address What > 1 breakpoint keep y <PENDING> > CC2420ControlP__CC2420Config__syncDone > (gdb) > > > $*mspdebug --fet-List* is giving the following output > > Devices supported by FET driver: > CC430F5133 MSP430F169 MSP430F2370 MSP430F47197 MSP430F5528 > CC430F5137 MSP430F2012 MSP430F247 MSP430F4784 MSP430F5529 > CC430F6137 MSP430F2013 MSP430F249 MSP430F5418 MSP430FG4618 > MSP430AFE253 MSP430F2121 MSP430F2616 MSP430F5437 MSP430FR5739 > MSP430F1121 MSP430F2122 MSP430F2617 MSP430F5437A MSP430G2231 > MSP430F1232 MSP430F2131 MSP430F2618 MSP430F5438 MSP430G2252 > MSP430F147 MSP430F2132 MSP430F413 MSP430F5438A MSP430G2452 > MSP430F148 MSP430F2234 MSP430F427 MSP430F5510 MSP430G2553 > MSP430F149 MSP430F2272 MSP430F4270 MSP430F5525 > MSP430F1611 MSP430F2274 MSP430F449 MSP430F5526 > MSP430F1612 MSP430F235 MSP430F47173 MSP430F5527 > > Here it is showing that it is not supporting MSP430F2619. it supporting > till MSP430F2618 version. Is this the problem to not able to debug my code > on MSP430F2619 + CC2520? > > > > On Fri, Mar 2, 2012 at 5:02 PM, Eric Decker <[email protected]> wrote: > >> >> what version of gdb are you using? >> >> how are you invoking it? >> >> how are you connecting to the remote gdb server? >> >> If you don't know what a remote gdb server is, you should take a look >> at... http://paretech.com/?p=161. I found this page by doing a google >> search for "mspdebug gdb debugging" >> >> >> Please, the next time you ask for help how about telling us what commands >> you are using, the system you are hosted on, and the versions of the tools >> you are using. >> >> This is like wandering around with a blindfold. >> >> >> On Fri, Mar 2, 2012 at 3:12 AM, ramakrishna reddy < >> [email protected]> wrote: >> >>> Hi everybody, >>> I am working on MSPF2619(MCU) + CC2520(Radio) >>> platform. I am able to program the mote using mspdebug. But when debugging >>> the mote, breakpoints are not setting and break points address are not >>> assigning. It is saying 'function not defined' and 'Make breakpoint pending >>> on future shared library load? (y or [n]) n'. 'info break' command is >>> showing the following message. >>> >>> gdb) info break >>> Num Type Disp Enb Address What >>> 1 breakpoint keep y <PENDING> >>> RadioCountToLedsC__AMSend__send >>> 2 breakpoint keep y <PENDING> >>> RadioCountToLedsC__CC2420Config__syncDone >>> >>> >>> any help is appreciated ! >>> >>> -- >>> With Regards, >>> RamakrishnaReddy.S >>> CDAC,Bangalore. >>> >>> >>> _______________________________________________ >>> Tinyos-help mailing list >>> [email protected] >>> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help >>> >> >> >> >> -- >> Eric B. Decker >> Senior (over 50 :-) Researcher >> >> >> > > > -- > With Regards, > RamakrishnaReddy.S > CDAC,Bangalore. > > -- Eric B. Decker Senior (over 50 :-) Researcher
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
