HI Andy If you have the FET430UIF as a /dev/tty*, you're almost done. The MSP-EXP430F5438 experimenter board is connected over the JTAG but your log mentions Spy-By-Wire. Try adding -j to the mspgdebug call
Best Matthias On 15.04.2012, at 20:14, Andy Turk wrote: > I'm pulling out my hair (and I don't have much to lose) trying to get > mspdebug to talk to a MSP-EXP430F5438 experimenter board through TI's > MSP-FET430UIF. Here's what I'm getting: > > $ MSPDEBUG_TI3410_FW=/opt/local/lib/mspdebug/ti_3410.fw.ihex mspdebug -d > /dev/tty*FET* uif > MSPDebug version 0.19 - debugging tool for MSP430 MCUs > Copyright (C) 2009-2012 Daniel Beer <dlb...@gmail.com> > 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/tty.MSP-FET430UIF26230... > Initializing FET... > FET protocol version is 20401000 > Configured for Spy-Bi-Wire > Set Vcc: 3000 mV > fet: FET returned error code 4 (Could not ... ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
