I have had this problem. I fixed it to some extent by changing the settings of the build script. There is a flag that adds delay in the programming step. Digging up the code is too hard right now, sorry.
I found that I only rarely had to remove the motes with this adjustment in place. There apparently has been some change in the USB driver for the FTDI chip that affects this; some of my computers had an earlier version of the kernel that never displayed this problem, even if I was programming up to 21 motes at the same time. Eric 2009/3/17 Xiaohui Liu <[email protected]>: > Hi all, > > I am running an experiment on a testbed consisting of TelosB motes connected > to laptops via usb to serial cable; after I schedule a job to program all of > the motes, there are invariantly a couple of motes not cooperating, saying: > [r...@localhost Blink]# make telosb reinstall bls,/dev/ttyUSB0 > cp build/telosb/main.ihex build/telosb/main.ihex.out > found mote on /dev/ttyUSB0 (using bsl,auto) > installing telosb binary using bsl > tos-bsl --telosb -c /dev/ttyUSB0 -r -e -I -p build/telosb/main.ihex.out > MSP430 Bootstrap Loader Version: 1.39-telos-8 > Mass Erase... > An error occoured: > Timeout > make: *** [program] Error 1 > And each time I schedule a new job, some motes fail to cooperate, not > necessarily the previously failed ones. Having dived into the tinyos help > archive, I find many similar issues regarding this timeout error. > Nevertheless, none of the solutions(e.g., tos-bsl ----invert-reset, change > telos to telosb) seems working for my case. Also have I tried tuning various > options of tos-bsl, which deos not work neither. Then I attempted to > software reboot the problematic motes by removing and reloading the > usbserial drives. Again, timeout error remains. > > In the meantime, I could only mitigate this problem by manually unpluging > and pluging failed motes, which enables the motes programmable again. > Apparently, this is not a ultimate solution. Is there an approach to solve > this problem without physical unpluging? Any help would be greatly > appreciated. > > BTW, additional error message is gained by using tos-bsl debug mode and > listed below : > MSP430 Bootstrap Loader Version: 1.39-telos-8 > Debug level set to 1 > Python version: 2.5.1 (r251:54863, Oct 30 2007, 13:54:11) > [GCC 4.1.2 20070925 (Red Hat 4.1.2-33)] > using serial port '/dev/ttyUSB5' > Preparing device ... > Mass Erase... > Traceback (most recent call last): > File "/usr/bin/tos-bsl", line 1619, in <module> > main() > File "/usr/bin/tos-bsl", line 1560, in main > for f in toinit: f() > File "/usr/bin/tos-bsl", line 961, in actionMassErase > 0xa506) #Required setting for mass erase! > File "/usr/bin/tos-bsl", line 652, in bslTxRx > rxFrame = self.comTxRx(cmd, dataOut, len(dataOut)) #Send frame > File "/usr/bin/tos-bsl", line 416, in comTxRx > rxHeader, rxNum = self.comRxHeader() #receive header > File "/usr/bin/tos-bsl", line 322, in comRxHeader > if not hdr: raise BSLException("Timeout") > __main__.BSLException: Timeout > > Cheers, > Xiaohui > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
