Clarifying,
I am using the EZ430-F2013 module. So clock, power are on the target already. msp430-gdbproxy is refusing to connect to the FET. My question is, (I still didn't get this answered) in this thread, it says, the windows version of msp430-gdbproxy got spy-bi-wire support. What about the linux version? My question is, is the reason it is refusing to connect (a) because of no support for spy-bi-wire in the linux version of msp430-gdbproxy (b) because of othe issues (timing of port / something in virtualbox) Thanks Anil Steve Underwood wrote: > > cloud9ine wrote: >> Good one, but I did get that right, actually. I misspelt it in the post.. >> >> Sorry abt that. >> >> >> >> Grant Edwards wrote: >> >>> On 2007-09-27, cloud9ine <cloud9...@gmail.com> wrote: >>> >>> >>>> My command : >>>> >>>> ./msp430-gdbproxy --port=3333 msp430 --spy-biwire /dev/ttyUSB0 >>>> >>>> Am I missing something? >>>> >>> The hyphen between "bi" and "wire"? >>> > > Well, assuming /dev/ttyUSB0 is working OK, this should give you a > working Spy-Bi-Wire debugger. Just take power, clock and data to the > target, and off you go. > > Steve > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mspgcc-users mailing list > Mspgcc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > > -- View this message in context: http://www.nabble.com/Updated-msp430-gdbproxy-tf1494599.html#a12933118 Sent from the MSP430 gcc - Users mailing list archive at Nabble.com.
