On 10/02/11 00:10, Daniel Beer wrote: > Quoting Asser <[email protected]>: > >> Hello, anyone else ran into this? >> >> "(mspdebug) run >> Running. Press Ctrl+C to interrupt... >> ...after a while.... >> olimex.c: can't receive data: Numerical result out of range >> fet: polling failed" > > Hi Asser, > > Can't be sure exactly what's happening there, but it looks like the > error message is one from libusb (and is probably something somewhat > low-level). Have you tried it on any other host systems? > > - Daniel > 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) 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. Regards, Robert von Knobloch ------------------------------------------------------------------------------ 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
