On Tue, Aug 27, 2013 at 10:40:45AM +1200, Andrew McLaren wrote: > It would have been easy if the problem had been gdbproxy, but no such luck. > Now that mspdebug is running, I'm seeing exactly the same scenario here. The > messages are a tad different, but I think they are saying the same thing. > Everything works fine until mspdebug reports... > > fet: FET returned error code 18 (Could not determine device state) > fet: polling failed > > Once again, eveything appears hung outboard of mspdebug until the target msp > is repowered. If I simply try and restart mspdebug without doing this, it > will report; > > TI3410 device is in boot config, setting active > ti3410: TI_OPEN_PORT failed: A device attached to the system is not > functioning > ti3410: failed to set up port
This looks like some kind of hardware problem. Have you tried different USB ports? Is the board powered externally, or does it draw power from the FET? Cheers, Daniel -- Daniel Beer <dlb...@gmail.com> www.dlbeer.co.nz IRC: inittab (Freenode) PGP key: 2048D/160A553B ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
