pe, 2011-02-11 kello 10:31 +0100, bob kirjoitti: > On 10/02/11 20:17, Daniel Beer wrote: > > 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 > > > More info: > The very first connection to the FET ('mspdebug rf2500' from power-up) > always fails with: > "usbutil: unable to find a device matching 0451:f432" > whereas lsusb reports: > "Bus 004 Device 002: ID 0451:f432 Texas Instruments, Inc." > The second connection attempt always succeeds. > This startup behaviour is 100% repeatable. > > When all is running, I need to detach the target processor from the > Launchpad board (to measure current consumption etc.), I cannot then > re-attach it without a power-down of the launchpad board. > Attempting this results in: > > "(mspdebug) reset > fet: FET returned error code 30 (Could not access device - security fuse > is blown) > fet: reset failed > (mspdebug)" > > Of course, this may be a problem with the launchpad software, I cannot > tell (so I'll ask you for advice) :-) > > I'll try changing the usleep interval and see if that helps with > 'random' disconnects. > > btw. on "http://mspdebug.sourceforge.net/history.html";, the latest > version is given as '0.14 7-Feb-2011', but the download area has 0.13. > I don't know if 0.14 has any changes relevant to my problem, of course. > > Many thanks Daniel, > Bob > Hello,
I tried to reproduce the problem on my other computer, which runs Ubuntu 10.04. I installed from natty package, and it seems to work without any problem. I'm guessing the problem is in some of the libraries used by mspdebug after all? -Asser ------------------------------------------------------------------------------ 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
