Hi everyone,
I'm using the serial forwarder in c available
herehttp://code.google.com/p/tinyos-main/source/browse/trunk/support/sdk/c/sf/.
After I set up the serial forwarder (use the example sf.c), I succeeded in
both reading from it (sflisten.c) and writing to it (sfsend.c), from the
local
This question has been posted a long time ago. Maybe someone searching
the archives finds this answer useful.
* Aravind Ravisankar [on Tue, 18 Sep 2007 12:01:08 -0700]:
tos-bsl --telosb -c /dev/ttyUSB0 -r -e -I -p build/telosb/main.ihex.out
MSP430 Bootstrap Loader Version: 1.39-telos-8
Mass
Hi,
To explicitly specify the serial port for Tmotes, use the following syntax:
make tmote [re]install[,moteID] bsl,serialport
For instance, if your program is already compiled, you want to install
it on a mote with the mote ID 3 and you somehow know that the mote is
using the first USB serial
Aravind Ravisankar wrote:
This doesn't happen all the time but is very frequent. Sometimes when I
restart my system it helps and I am able to successfully install but then
the errort gets back after some time.
Does the USB communication timeout come on a system with other
USB devices
Hello
I have been trying to install the Blink Application on telosb motes, I m on
OpenSuse. When I give make telosb install, I get the error given below.
This doesn't happen all the time but is very frequent. Sometimes when I
restart my system it helps and I am able to successfully install but
1. Yes I am using a wireless keyboard and mouse both of which have a single
base which is connected to a USB drive. I am using the second USB drive for
installing motes. Should I remove the wireless keyboard?
2. No I haven't defined the env variable MOTECOM
Thanks
On 9/18/07, John Griessen
I don't think MOTECOM is significant to downloading programs,
only 'listening' to data messages. I believe the tmote system
has some magic for determining what USB port to use for downloads.
You might try reviewing the setup info in the tmote manual,
I remember there being some way to explicitly