There's one more twist here: avrdude, the in-system programmer used for the iris motes, wants COM5 instead of /dev/ttyS4 on winXP.
Janos From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of ashish makani Sent: Friday, April 18, 2008 9:26 AM To: Murray, Ben Cc: [email protected] Subject: Re: [Tinyos-help] Unable to program Blink on a crossbow iris mote(XM2110) using the MIB520 USB interface board on atinyos-2.0.2(using cyg win on Windows XP ) Hi Ben Thanks a million for your super-prompt response. I will give it a try. But, just to ensure we are on the same page & i understood you correctly, what you are saying is that in cygwin (on win xp) for virtual COM ports, COMn, is addressed as /dev/ttyS(n-1) ? My understanding is, that it is not a "regular" COM port,as the MIB520, connects to the host pc using a usb cable, but the FTD driver for the mib520, present it to the OS, as a *virtual COM port.* windows calls them USB Serial Ports, & they show up in the device manager, as 2 consecutive ports n & (n+1). xbow's mib520 user guide here <http://www.xbow.com/support/Support_pdf_files/MPR-MIB_Series_Users_Manu al.pdf> ,on page 51 of 64, & this tinyos link http://www.tinyos.net/tinyos-2.x/doc/html/tutorial/programmers.html, recommend that use make micaz install mib510, /dev/ttySn, on cygwin(winXP) where /dev/ttySn is the serial port, where the programmer is attached i.e. if windows has ports n & (n+1), use the lower one, i.e.n for programming the mote, & (n+1) for retrieving data from the mote to the host pc. Thanks for your help, cheers ashish =============================================================== On 4/18/08, Murray, Ben <[EMAIL PROTECTED]> wrote: > /dev/ttyS5 is equivalent to COM6. I've not used a mib520 but you said you > wanted to use COM5, therefore you could try /dev/ttyS4 perhaps? > > Just a guess. > -Ben > > p.s. try searching for a flash error and mib520: > http://www.tinyos.net/scoop/special/support#mailing-lists > <http://www.tinyos.net/scoop/special/support#mailing-lists> > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of ashish > makani > Sent: 18 April 2008 06:39 > To: [email protected] > Subject: [Tinyos-help] Unable to program Blink on a crossbow iris > mote(XM2110) using the MIB520 USB interface board on a tinyos-2.0.2(using > cygwin on Windows XP ) > > > Hi Folks > > I need some help desperately. > > I am running tinyos-2.0.2 on winXP using cygwin. > > I am unable to program the basic Blink application onto a xbow > <http://www.xbow.com/Products/productdetails.aspx?sid=264> IRIS mote, using > the USB <http://www.xbow.com/Products/productdetails.aspx?sid=227> > programming board MIB520 . > > i can compile the blink app(located in/opt/tinyos-2.x/apps/Blink ) but when > i try to program/flash it into a mote i am unable to do so. > > 1. When I connect the MIB520 board using a usb cable to my winxp host, > windows detects 2 virtual com ports(windows calls them USB Serial Ports), > COM5 & COM6. > So I am using /dev/ttyS5, in cygwin(on WinXP) for programming the mote... > > Is the command, > $ make micaz reinstall mib510,/dev/ttyS5 > correct for programming an iris mote, connected to virtual com port(com5) on > cygwin(on winXP), using a mib520(usb programming board/gateway ? > > > 2.Here are the commands i used (the commands are in bold below, the prompt > is the $ sign & my username is "User" ) > > [EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink > $ pwd > /opt/tinyos-2.x/apps/Blink > > [EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink > $ make micaz reinstall mib510,/dev/ttyS5 > cp build/micaz/main.srec build/micaz/main.srec.out > installing micaz binary using mib510 > uisp -dprog=mib510 -dserial=/dev/ttyS5 --wr_fuse_h=0xd9 -dpart=ATmega128 > --wr_fu > se_e=ff --erase --upload if=build/micaz/main.srec.out > Programmer is not responding. > make: *** [program] Error 2 > > [EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink > $ > > 3. I am using an IRIS mote from crossbow, which uses an Atmel processor just > like the micaz. So i tried specifying the target in the make command as iris > instead of micaz, but then make complains that iris is not a valid target. > > the code-fragment is below > { > > [EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink > $ make iris reinstall mib510,/dev/ttyS5 > /opt/tinyos-2.x/support/make/Makerules:168: *** > > Usage: make <target> <extras> > make <target> help > > Valid targets: all clean eyesIFX eyesIFXv1 eyesIFXv2 intelmote2 > mica2 mi > ca2dot micaz null telos telosa telosb tinynode tmote > Valid extras: appdoc bnp docs ident_flags nowiring sim sim-fast > tos_imag > e verbose wiring > > Welcome to the TinyOS make system! > > You must specify one of the valid targets and possibly some combination of > the extra options. Many targets have custom extras and extended help, so > be > sure to try "make <target> help" to learn of all the available features. > > Global extras: > > docs : compile additional nescdoc documentation > tinysec : compile with TinySec secure communication > > ERROR, "iris reinstall mib510 ident_flags tos_image bnp" does not specify a > vali > d target. Stop. > > [EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink > $ > } > > 4. I looked at the datasheets of the micaz & the iris motes closely, & saw > that they use different Atmel processors. > Iris uses AtMega1281 & Micaz uses AtMega128L. > So, my question is , Is the xbow iris mote(XM2110) supported by tinyos-2.0.2 > ? > If yes, what target should i specify, while programming a Iris mote, iris or > micaz. > > > 5.I also tried the command with mib520, but remember Phil telling me > sometime back(~ july-2006) that will not work, as TinyOS 2.x make system > currently does not support the mib520, & mib510 should work, as to make, it > still appears, as if a mib510 is connected on the virtual com port. > > But i just tried it for the heck of it( guessing that tos might now have > explicit support for mib520), & then i get a huge error > > { > > [EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink > $ make micaz reinstall mib520,/dev/ttyS5 > cp build/micaz/main.srec build/micaz/main.srec.out > installing micaz binary with dapa > uisp -dprog=dapa --wr_fuse_h=0xd9 -dpart=ATmega128 --wr_fuse_e=ff --erase > pulse > Atmel AVR ATmega128 is found. > Erasing device ... > pulse > Reinitializing device > Atmel AVR ATmega128 is found. > > Fuse High Byte set to 0xd9 > > Fuse Extended Byte set to 0xff > sleep 1 > uisp -dprog=dapa --wr_fuse_h=0xd9 -dpart=ATmega128 --wr_fuse_e=ff --upload > if=b > uild/micaz/main.srec.out > pulse > Atmel AVR ATmega128 is found. > Uploading: flash > > Fuse High Byte set to 0xd9 > > $ > sleep 1 > uisp -dprog=dapa --wr_fuse_h=0xd9 -dpart=ATmega128 --wr_fuse_e=ff --verify > if=b > uild/micaz/main.srec.out > pulse > Atmel AVR ATmega128 is found. > Verifying: flash > flash error at address 0x0: file=0x0c, mem=0x00 > flash error at address 0x1: file=0x94, mem=0x00 > flash error at address 0x2: file=0x49, mem=0x00 > flash error at address 0x4: file=0x0c, mem=0x00 > flash error at address 0x5: file=0x94, mem=0x00 > flash error at address 0x6: file=0x66, mem=0x00 > flash error at address 0x8: file=0x0c, mem=0x00 > flash error at address 0x9: file=0x94, mem=0x00 > flash error at address 0xa: file=0x66, mem=0x00 > flash error at address 0xc: file=0x0c, mem=0x00 > flash error at address 0xd: file=0x94, mem=0x00 > flash error at address 0xe: file=0x66, mem=0x00 > flash error at address 0x10: file=0x0c, mem=0x00 > flash error at address 0x11: file=0x94, mem=0x00 > . > . > . > . > . > > i terminated this withe ctrl+c, & the last few lines read : > flash error at address 0xf8: file=0x91, mem=0x00 > flash error at address 0xf9: file=0xf0, mem=0x00 > flash error at address 0xfa: file=0x80, mem=0x00 > flash error at address 0xfb: file=0x91, mem=0x00 > make: *** [program] Interrupt > } > > > > Where am i going wrong ? > > Any suggestions/ideas/workarounds > /hacks welcome > > > Thanks a ton all of you, > > Looking forward to your responses > > cheers > > ashish > > > ************************************************************************ ******* > Please consider the environment before printing this email. > ************************************************************************ ******* > This email and any files transmitted with it are intended solely for the use > of > the individual or entity to whom they are addressed and may not be divulged > to > any third party without the express permission of the originator. Any views > expressed in this message are those of the individual sender, except where > the > sender specifically states them to be the views of Thales Research & > Technology > (UK) Limited. > ************************************************************************ ******* > >
_______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
