Ashish,

 

I replace my tos-set-symbols file, but without the extension .dat. The
original file in /usr/bin/ directory hasn’t this extension. Next, everything
is all right. The application compiles, I’ve been able to install on an IRIS
mote and it works. The only difference between original file and this new
file is in the line number 81, where it was ‘die “Could not find…”…’, and
now it’s ‘warn “Could not find…”…’.

 

BR,

Eva

 

De: ashish makani [mailto:[EMAIL PROTECTED] 
Enviado el: miércoles, 23 de abril de 2008 15:25
Para: Eva Maria Garcia
Asunto: Fwd: [Tinyos-help] Still unable to program Blink onto a crossbow
irismote(XM2110) using the MIB520 USB interface board on tinyos-2.0.2(using
cygwin on Windows XP )

 

Eva,

 

This is the email i received from Janos. the tos-set-symbols file is
attached.

 

I tried replacing my tos-set-symbols-file, but so far it has not worked....

 

Try this, & let me know if it works for you or not.

 

All the best,

 

cheers

ashish

 

============================================================================
============================================================================
==================================

---------- Forwarded message ----------
From: Janos Sallai <[EMAIL PROTECTED]>
Date: Tue, Apr 22, 2008 at 11:47 AM
Subject: RE: [Tinyos-help] Still unable to program Blink onto a crossbow
irismote(XM2110) using the MIB520 USB interface board on tinyos-2.0.2(using
cygwin on Windows XP )
To: ashish makani <[EMAIL PROTECTED]>
Cc: [email protected]



Ashis,

 

Good point. When you compile Blink with avr-gcc 4, indeed, there is no data
section. For most other apps there is, so tos-set-symbols wouldn't fail.

 

Please replace /usr/bin/tos-set-symbols with the attached one. It'll fix
your problem.

 

Janos

 

From: ashish makani [mailto:[EMAIL PROTECTED] 
Sent: Monday, April 21, 2008 11:56 PM
To: Janos Sallai
Cc: [email protected]
Subject: Re: [Tinyos-help] Still unable to program Blink onto a crossbow
irismote(XM2110) using the MIB520 USB interface board on tinyos-2.0.2(using
cygwin on Windows XP )

 

Hi Janos, others

First up, thanks a million for your extremely helpful & informative
response.

I tried it, & it almost worked, but did not :)

1. I followed the IRIS instructions given on this ISIS link
http://www.isis.vanderbilt.edu/projects/NEST/tinyos-2.x-iris/doc/html/instal
l-tinyos-iris.html

I made 1 goof-up( ?) though...i did step-4,updating the tinyos source tree,
in the instructions above, first,
and then did step 2 &3, updating the atmel toolchain( avr-binutils,
avr-libc, avr-gcc) & installing avrdude.

I think step-4, we are not really *installing* anything, so i should be
fine, but just wanted to make sure.

2. I then tried compiling for iris & it works

here is what i see as output, when i type the command "make iris" from the
/opt/tinyos-2.x/apps/Blink directory .

<<>>

[EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink
$ make iris
mkdir -p build/iris
    compiling BlinkAppC to a iris binary
ncc -o build/iris/main.exe -Os -Wall -Wshadow -Wnesc-all -target=iris
-fnesc-cfi
le=build/iris/app.c -board=micasb -DIDENT_PROGRAM_NAME=\"BlinkAppC\"
-DIDENT_USE
R_ID=\"User\" -DIDENT_HOSTNAME=\"LENOVO-F238501F\"
-DIDENT_USER_HASH=0xa90f30ddL
 -DIDENT_UNIX_TIME=0x480d68b4L -DIDENT_UID_HASH=0xd3494904L
-fnesc-dump=wiring -
fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs,
comp
onents)' -fnesc-dumpfile=build/iris/wiring-check.xml BlinkAppC.nc -lm
    compiled BlinkAppC to build/iris/main.exe
            2434 bytes in ROM
              51 bytes in RAM
avr-objcopy --output-target=srec build/iris/main.exe build/iris/main.srec
avr-objcopy --output-target=ihex build/iris/main.exe build/iris/main.ihex
    writing TOS image

[EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink
$ ls -alp
total 697
drwxr-xr-x+  4 User None      0 Apr 18 15:18 ./
drwxr-xr-x+ 18 User None      0 Apr 18 15:21 ../
-rw-r--r--   1 User None   2120 Dec 12  2006 BlinkAppC.nc
-rw-r--r--   1 User None   2384 Dec 12  2006 BlinkC.nc
drwxr-xr-x+  2 User None      0 Apr 18 15:18 CVS/
-rw-r--r--   1 User None     42 Jul 12  2006 Makefile
-rw-r--r--   1 User None    678 Dec 12  2006 README.txt
-rw-r--r--   1 User None      0 Apr 17 21:57 _TOSSIM.dll
-rw-r--r--   1 User None 698415 Apr 17 21:59 app.xml
drwxr-xr-x+  4 User None      0 Apr 22 00:25 build/
<<>>

3.
However, when i try to install the compiled blink code, onto the mote, i get
a "Could not find data section in build/iris/main.exe, aborting.
make: *** [setid] Error 255 "

{
[EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink
$ make iris install.0 mib510,COM5
mkdir -p build/iris
    compiling BlinkAppC to a iris binary
ncc -o build/iris/main.exe -Os -Wall -Wshadow -Wnesc-all -target=iris
-fnesc-cfi
le=build/iris/app.c -board=micasb -DIDENT_PROGRAM_NAME=\"BlinkAppC\"
-DIDENT_USE
R_ID=\"User\" -DIDENT_HOSTNAME=\"LENOVO-F238501F\"
-DIDENT_USER_HASH=0xa90f30ddL
 -DIDENT_UNIX_TIME=0x480d68eeL -DIDENT_UID_HASH=0x4077e9c8L
-fnesc-dump=wiring -
fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs,
comp
onents)' -fnesc-dumpfile=build/iris/wiring-check.xml BlinkAppC.nc -lm
    compiled BlinkAppC to build/iris/main.exe
            2434 bytes in ROM
              51 bytes in RAM
avr-objcopy --output-target=srec build/iris/main.exe build/iris/main.srec
avr-objcopy --output-target=ihex build/iris/main.exe build/iris/main.ihex
    writing TOS image
tos-set-symbols build/iris/main.srec build/iris/main.srec.out-0
TOS_NODE_ID=0 Ac
tiveMessageAddressC$addr=0
Could not find data section in build/iris/main.exe, aborting.
make: *** [setid] Error 255

[EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink
}

I tried several permutations of the install, reinstall commands.

make iris install,0 mib510,COM5 (. instead of the .)
and nodeid 42 ( nodeid other than 0)

[EMAIL PROTECTED] /opt/tinyos-2.x/apps/Blink
$ make iris reinstall,42 mib510,COM5
tos-set-symbols build/iris/main.srec build/iris/main.srec.out-42
TOS_NODE_ID=42
ActiveMessageAddressC$addr=42
Could not find data section in build/iris/main.exe, aborting.
make: *** [setid] Error 255

Where am i going wrong ?

I am really desperate, as i am a grad student working on a course project,
which is due in 2 days

Any suggestions/ideas/workarounds /hacks welcome 


Thanks a ton all of you,

Eagerly looking forward to your responses

cheers

ashish 

 

 

============================================================================
========================================================================

 

On Fri, Apr 18, 2008 at 6:03 PM, Janos Sallai <[EMAIL PROTECTED]>
wrote:

>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 ?

 

This is incorrect: you're compiling for micaz, not the iris. The correct way
of compiling for and programming an iris mote under winXP/cygwin is:

 

make iris install.42 mib510,COM5

 

(where 42 is the node ID and COM5 is the lower virtual com port that shows
up when connecting a MIB520 to the PC)

 

Janos

 

 

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of ashish
makani
Sent: Friday, April 18, 2008 12:39 AM


To: [email protected]

Subject: [Tinyos-help] Unable to program Blink on a crossbow
irismote(XM2110) using the MIB520 USB interface board on atinyos-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 

 

 

_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Reply via email to