Hi!
On Wed, 21 May 2008, jiwen zhang wrote:
Hello Razvan ME :
today , i tested the apps/tests/deluge/blink (the verison of git
http://hinrg.cs.jhu.edu/git/tinyos-2.x.git download on 2008.05.15), i find
some problems , i don't know whether these have relation to my deluge tools:
1. i use the command make micaz install.0 mib510,/dev/ttyS0 to install
the application to the mote
if i don't install any image in the external flash , i can use the
command tos-deluge /dev/ttyS0 micaz -r 1 .
If you don't have any image in the external flash the -r 1 should not
work.
but after i install the image , for example slot 1 , then if use the
command tos-deluge /dev/ttyS0 micaz -r 1 , the red flash will flash
quickly and never stop . what is the reason ?
2 . after i install an image to slot of the external flsh , i reboot the
mote by hand , then i use the command tos-deluge /dev/ttyS0 micaz -p 1 ,
it give me the information that No valid image was detected . i think
the mote lose the information after rebooting .
Are you able to successfully run the burn from apps/test/deluge/Blink?
3 . after i install the image , i use the command tos-deluge /dev/ttyS0
micaz -e 1 to erase the image , it is successful . then i use tos-deluge
/dev/ttyS0 micaz -p 1 , it show the information of image i have installed .
that is to say it does not erase the image .
If the erased was successful you should get a message that says 'No valid
image was detected.'.
questions :
although i can't pass the command ./configure , maybe i can copy the files
in /opt/tinyos-2.x/tools/tinyos/misc to /usr/local/bin , so i can use the
right deluge tools ? are there any potential problems ?
If you have a reasonable new tools installed it might work.
Suggestion :
Deluge is a very good tool and convenient . so i think it is better to give
an document to describe how to build the environment the deluge needs , what
do you think about , Razvan ME ? can you rebuild the environment that the
deluge needs on another computer and give us an document ? :-) i think it is
necessary , or the user can't use deluge .
You are using Windows and I cannot reproduce the errors you get on my
Windows so unfortunately there is not much that I can do. :-(
--
Razvan ME
2008/5/21 Razvan Musaloiu-E. <[EMAIL PROTECTED]>:
Hi!
On Tue, 20 May 2008, jiwen zhang wrote:
Hello :
2008/5/20 Razvan Musaloiu-E. <[EMAIL PROTECTED]>:
Hi!
On Sun, 18 May 2008, jiwen zhang wrote:
Hello :
2008/5/16 Razvan Musaloiu-E. <[EMAIL PROTECTED]>:
Hi!
On Thu, 15 May 2008, jiwen zhang wrote:
Hello Razvan ME :
today, i modify the application in the directory of app/Blink and let it
support deluge :
- in the BlinkAppC.nc , use the component DelugeC and then DelugeC.Leds ->
LedsC
- Modify the Makefile , add "TINYOS_NP = BNP ","CFLAGS +=
-DDELUGE_BASESTATION"
Have you first tried the burn and burn-net from
apps/tests/deluge/Blink?
Today(5.18) , i spend much time downloading the deluge/tinyos-2.x from
http://hinrg.cs.jhu.edu/git/deluge/tinyos-2.x.git . ( it is so slow to
download it -:( )
i do according to deluge-t2-manual.pdf .
the process is that :
./Bootstrap
+ aclocal
+ autoconf
+ [ -d config-aux ]
+ automake -a -c
+ set -x
+ cd platforms/mica/uisp
+ ./bootstrap
autoheader: WARNING: Using auxiliary files such as `acconfig.h',
`config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `
config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows to define a template
without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader: [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced,
see the
autoheader: WARNING: documentation.
+ rm -f config.cache src/config.cache
*there are some warnings . are there some influence ?*
It should be ok, I also get them.
./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-cygwin
checking host system type... i686-pc-cygwin
checking for gcc... gcc
checking for C compiler default output file name... a.exe
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... .exe
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking for ranlib... ranlib
checking for perl... /usr/bin/perl
checking for python... /usr/local/bin/python
checking for nescc... /usr/bin/nescc
configure: Default ncc build target is mica
configure: ...but using a tos/.default-platform file is a better choice
configure: TinyOS directory is /opt/tinyos-2.x/tos
checking for cygwin... yes
checking for JDK location... /cygdrive/d/Program Files/Java/jdk1.5.0_01
configure: creating ./config.status
config.status: creating Makefile
config.status: error: cannot find input file: Makefile .in
*there is an error , the it jump out . what is the reason ?*
I don't have much experience with Cywgin. On my Windows machine when I run
'./configure --prefix=$HOME/local' I didn't get any errors. I don't know
if
it makes a different or not but I'm using the latest Cygwin.
i have download tinyos-2.x.git and /deluge/tinyos-2.x.git , and when i run
I just committed the latest version also to CVS so you can also grab it
from there.
./configure , i get the same error as i said before.
maybe it's the problem of cygwin .
these are the tools i have installed : (according to the specification
of TinyOS 2.0 install instructions
file:///G:/tinyos/文档资料/doc/html/install-tinyos.html)
avr-gcc-3.4.3-1
avarice-2.4-1
nesc-1.2.8b-1
tinyos-2.0.2-2
msp430tools-binutils-2.16-20050607
msp430tools-libc-20050308cvs-20050608
avr-binutils-2.15tinyos-3
avr-libc-1.2.3-1
avr-insight-6.3-1
tinyos-tools-1.2.4-2
msp430tools-base-0.1-20050607
msp430tools-gcc-3.2.3-20050607
msp430tools-python-tools-1.0-1
the cygwin version in my computer is cygwin-1.2a.tgz . in addition , i
have
update the version of python to 2.4.5 .
I didn't use cygwin-1.2a.tgz. I just installed the latest Cygwin using the
latest setup.exe from here:
http://www.cygwin.com/setup.exe
Then I installed the following rpms:
4806 Mar 8 20:53 msp430tools-base-0.1-20050607.cygwin.i386.rpm
8091730 Mar 8 20:54 msp430tools-binutils-2.16-20050607.cygwin.i386.rpm
3985679 Mar 8 20:54 msp430tools-gcc-3.2.3-20050607.cygwin.i386.rpm
402602 Mar 8 20:54 msp430tools-libc-20050308cvs-20050608.cygwin.i386.rpm
81149 Mar 8 20:53 msp430tools-python-tools-1.0-1.cygwin.noarch.rpm
1097975 Mar 8 20:54 nesc-1.2.8b-1.cygwin.i386.rpm
After that I checkout the latest CVS version of tinyos and compile and
install the tools. I also had to add set some variables in ~/.bashrc
(TOSROOT, TOSDIR and MAKERULES).
what are your tools you have installed ?
you know the whole cygwin is very large , maybe i have no need to
download all the files . i what to know which files do i have to download?
I have very limited experience with Windows. I don't remember exactly what
packages I had to select.
another question :
i have seen the Deluge T2 document you update , i find there is no much
difference with deluge-t2-manual.pdf . you say you will explain the
DelugeP
and how to reprogram the mote selectively , i can't find these .
That part is not there yet. The amount of time I had for Deluge T2 right
now is still limited. :-(
--
Razvan ME
--
zhang jiwen
_______________________________________________
Tinyos-help mailing list
[email protected]
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
