Quoting bob <[email protected]>: > I am using mspgcc (V 0.13) on opensuse 11.0 and experience a very > similar effect: > > (mspdebug) run > Running. Press Ctrl+C to interrupt... > fet: FET returned error code 18 (Could not determine device state) > fet: polling failed > (mspdebug)
In this case, the error message you're seeing is reported by the FET itself. It's possible that it's a JTAG communication error. > My TI Launchpad disconnects at irregular intervals and often won't > re-connect without a power-down. > I often have to detach my target processor from the launchpad board to > test and it can't re-connect after this either, which means power-down > and re-start mspdebug. > This uses up quite a lot of time per software change (mostly more time > than the software changes). > If someone could point me to where in the source I should start looking, > I would try to analyse / debug this. When you try unsuccessfully to reconnect, what output do you get from MSPDebug? This problem might be helped by polling less frequently. Have you tried modifying the usleep interval in fet_poll (in fet.c)? - Daniel -- D.L. Beer Engineering www.dlbeer.co.nz ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
