Hi, Mib520 creates two virtual serial port, one for programming, one for communicating. You probably try to program your motes with the communication port. The programming port is probably /dev/ttyUSB0, but that should be in the /var/log/messages (I think you only attached half of the ftdi log).
Andris On Mon, Oct 8, 2012 at 3:13 PM, ning gu <[email protected]> wrote: > Hi,every one.I am a chinese student. > I have a problem with mib520 as mentioned above. > when I plug the mib520 to my computer, from the /var/log/messages file,it > says: > > Oct 8 05:56:01 localhost kernel: ftdi_sio 2-2.1:1.1: FTDI USB Serial > Device converter detected > Oct 8 05:56:01 localhost kernel: drivers/usb/serial/ftdi_sio.c: > Detected FT2232C > Oct 8 05:56:01 localhost kernel: usb 2-2.1: FTDI USB Serial Device > converter now attached to ttyUSB1 > Oct 8 05:56:01 localhost kernel: usbcore: registered new driver ftdi_sio > Oct 8 05:56:01 localhost kernel: drivers/usb/serial/ftdi_sio.c: > v1.4.3:USB FTDI Serial Converters Driver > > then I enter the Blink diretory,and use the command: > the result is as follow: > > [root@localhost Blink]# make micaz install mib520,/dev/ttyUSB1 > mkdir -p build/micaz > compiling BlinkAppC to a micaz binary > ncc -o build/micaz/main.exe -Os -fnesc-separator=__ -Wall -Wshadow > -Wnesc-all -target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb > -DDEFINED_TOS_AM_GROUP=0x22 --param max-inline-insns-single=100000 > -DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"root\" > -DIDENT_HOSTNAME=\"localhost.local\" -DIDENT_USERHASH=0x53b81074L > -DIDENT_TIMESTAMP=0x5072cf6dL -DIDENT_UIDHASH=0x897f034dL > -fnesc-dump=wiring -fnesc-dump='interfaces(!abstract())' > -fnesc-dump='referenced(interfacedefs, components)' > -fnesc-dumpfile=build/micaz/wiring-check.xml BlinkAppC.nc -lm > compiled BlinkAppC to build/micaz/main.exe > 2052 bytes in ROM > 51 bytes in RAM > avr-objcopy --output-target=srec build/micaz/main.exe build/micaz/main.srec > avr-objcopy --output-target=ihex build/micaz/main.exe build/micaz/main.ihex > writing TOS image > cp build/micaz/main.srec build/micaz/main.srec.out > installing micaz binary using mib510 > uisp -dprog=mib510 -dserial=/dev/ttyUSB1 --wr_fuse_h=0xd9 > -dpart=ATmega128 --wr_fuse_e=ff --erase --upload > if=build/micaz/main.srec.out --verify > Programmer is not responding. > make: *** [program] Error 2 > > I have try this a few times ,however with same results. > I wonder what the problem is,Because I use "make micaz install mib520 " > but the process shows that > "installing micaz binary using mib510 > uisp -dprog=mib510 -dserial=/dev/ttyUSB1 " > > I try to google the problem,However I can not find useful information > because of the GFW.Damn it. > > I am desperate to know how to solve this problem. > Thanks a lot. > > > > -- > Gu Ning > Graduate School at Shenzhen, Tsinghua University > Room H205, Building H > Tsinghua Campus, The University Town, Shenzhen, P.R.China 518055 > _______________________________________________ > 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
