I suggest you NOT to use any USB hubs, but directly connect to the PC. >From my experience, they can cause many problems, such as firmware burning, packet loss, etc... Not all of them and not all the time, but you don't wont to be a part of statistics :)
Arik On Fri, Mar 5, 2010 at 10:58, Isabelle Hang < [email protected]> wrote: > I have tried something else: > I connect a sensor mote onto a mib520-board to the computer, type in > my command and get the mentioned error. Then, I disconnect the board > and repeat the command once or twice. I reconnect the device and > repeat the command again. After one or two times, the firmware is > recognized and I get the programm upload. > > It also seems, that some usb ports works better than others. > > I try to look for usbhubs or an alternative machine and will continue > to test and post my results. > > Has anybody an explanation for this yet? > > Best regards, > Isa > ------------------- > > Yes, I went and looked. The low port # is the programmer, > > high # is for MOTECOM. Perhaps you can try your programmer > > on a different host machine? Or different USB jack/hub/etc? > > > > MS > > > > > > Isabelle Hang wrote: > > > Using the first port, I get the described error, using the second > > > port, I get the message 'Programmer is not responding'. > > > I guess the latter is the data port. > > > Really weird is, that the uploading sometimes works.(Perhaps one > time > > > out of fifty). > > > I have really no idea! Have anybody a clue? > > > > > > Best regards, > > > Isabelle > > > ------------------- > > >> I think the MIB520 has two ports, one for programming > > >> and one for data I/O. I of course forget which is which, > > >> have you tried both? Do you have any motes already programmed > > >> to send data to the PC that you can try as well? > > >> > > >> I could be wrong about motelist. It might work in some > > >> fashion with the 520 since it is a USB device as well. > > >> Each vendor and version seems to have a different version > > >> of the program, so the Moteview one could work as you say. > > >> > > >> MS > > >> > > >> Isabelle Hang wrote: > > >>> Finally, I have reinstalled the system, but still I get the same > > >>> error. > > >>> The device manager seems to show quite normal results: Com3 and > > > Com4 > > >>> are recognized, so the driver is installed. > > >>> Could it be a driver-problem? Has anybody an idea? > > >>> > > >>> Thank you for the information about the motelist command. It has > > >>> worked with Moteview and Micaz and so I thought, it must also > work > > >>> here. > > >>> > > >>> Best regards > > >>> Isabelle > > >>> > > >>> ------------------- > > >>>> Did you move the USB cable to a different port? > > >>>> Widows seems to like to re-assign COM port numbers > > >>>> based on where they are connected. You might try > > >>>> looking in the Device Manager under "Ports" to see > > >>>> if it has any enlightening details. > > >>>> > > >>>> On the subject of Motelist. It only works with telos > > >>>> type devices. The micas don't respond to USB inquiries. > > >>>> > > >>>> MS > > >>>> > > >>>> Isabelle Hang wrote: > > >>>>> Hi all, > > >>>>> > > >>>>> I use Cygwin on Windows XP, a mib520 and a micaz mote. (I am > > > quite > > >>>>> new, so do you need further information?) > > >>>>> It was all working fine and I was able to program the motes. > > >>>>> But suddenly I get the following error, if I try to install a > > >>> program > > >>>>> on a mote: > > >>>>> > > >>>>> > > >>>>> $make micaz install mib510./dev/ttyS2 > > >>>>> mkdir -p build/micaz > > >>>>> ..... > > >>>>> ..... > > >>>>> ..... > > >>>>> writing TOS image > > >>>>> cp build/micaz/main.srec build/micaz/main.srec.out > > >>>>> installing micaz binary using mib510 > > >>>>> uisp -dprog=mib510 -dserial=/dev/ttyS2 --wr_fuse_h=0xd9 > > >>>>> -dpart=ATmega128 --wr_fuse_e=ff --erase --upload > > >>>>> if=build/micaz/main.srec.out > > >>>>> Firmware Version: . > > >>>>> Failed to enter programming mode. > > >>>>> make: *** [program] Error 2 > > >>>>> > > >>>>> I have looked in the mailinglist, but there was no proper > > > solution > > >>> for > > >>>>> this problem. > > >>>>> Please can you help me? I have no idea how to fix this > problem. > > >>>>> > > >>>>> Best regards, > > >>>>> Isa > > >>>>> _______________________________________________ > > >>>>> Tinyos-help mailing list > > >>>>> [email protected] > > >>>>> > > > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-he > > >>> lp > > >>> _______________________________________________ > > >>> Tinyos-help mailing list > > >>> [email protected] > > >>> > > > > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-he > > > lp > > > _______________________________________________ > Tinyos-help mailing list > [email protected] > https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help > -- Best Regards, Arik Sapojnik
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
