Actually I'm not entirely clear who is connected to whom and
which is dying first, but...
I will hazard that the xlisten or SF connection is hung-up
in some data or close wait state, which are sometimes not even
interruptible. I don't know how thy implement their exit()s
but it's a good bet that they don't completely close the ports before
blowing out of the water... In which case SF may still be hung up
connected to a zombie someplace and holding onto the COM port as well.
You can look at inet port behavior with "netstat -a" and other options.
And there are some free-tilies for I/O port monitoring, PORTMON once
worked for me, but no recent ones come to mind off hand.
MS
Chris Byers wrote:
How come when I use Xlisten to get the Time of packet arrival: xlisten
–t crimson freezes up and I have to close out of it? It freezes up when
I try to stop the incoming data stream. To stop it I turn off the mote
and then left click in the output window and click “kill process” Does
anyone know why this is messing me up? Then when I renter it I cant
connect to the serial port because serialforwarder is giving me this error:
Listening to [EMAIL PROTECTED]
Listening for client connections on port 9001
[EMAIL PROTECTED]:19200 died - restarting (java.io.IOException: Port COM1 busy)
[EMAIL PROTECTED]:19200 died - restarting (java.io.IOException: Port COM1 busy)
[EMAIL PROTECTED]:19200 died - restarting (java.io.IOException: Port COM1 busy)
[EMAIL PROTECTED]:19200 died - restarting (java.io.IOException: Port COM1 busy)
[EMAIL PROTECTED]:19200 died - restarting (java.io.IOException: Port COM1 busy)
Any ideas how to fix this?
Chris Byers
MacAulay Brown Inc.
4021 Executive Dr.
Dayton OH 45430
937-426-3421 (phone)
937-426-5364 (fax)
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
