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 ?* ./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 copy the tools from cvs version (download at the day of 4.28) to the corresponding directory and do the operations following deluge-t2-manual.pdf , there is no error. then i test the /apps/tests/deluge/blink erery thing is ok except that when it running at +----------------------------------------------------------------+' | | In the next step the following things will take place: | - the mote will be rebooted | - all the leds will blink for some time as the | reprogramming by tosboot takes place. | - a fading of the leds will indicate the exiting from tosboot. | - the mote should start blinking the 3rd led (blue/yellow). | | Press ENTER to continue... | +----------------------------------------------------------------+ *atfer i pree the ENTER , there is no responding . that is to say the mote does't respond the reboot command . what is reason , Razvan ME ? does it have relation with the tools ? because i copy the tools from the cvs version . * > > > i can use "tos-deluge /dev/ttyS0 micaz -i 0 ./build/micaz/tos_image.xml" to >> download the image to specified slot (section ?) and i also can use >> "tos-deluge /dev/ttyS0 micaz -p 0" to get the information of image. >> >> *but there are alos some problems :* >> 1. i can't reboot the mote to load the image from specified slot to the >> internal flash(128K) in MCU . after i use "tos-deluage /dev/ttyS0 micaz -r >> 1", i find the three leds blink once(i think) , then the red led blink >> quickly and never stop . what is the reason , Razvan ME ? >> > > Can you please give it a try the latest version from the deluge git tree? I > just committed a fix for a bug in the micaz code. *whether there are some differences between the version of ** http://hinrg.cs.jhu.edu/git/deluge/tinyos-2.x.git*<http://hinrg.cs.jhu.edu/git/deluge/tinyos-2.x.git> * and **http://hinrg.cs.jhu.edu/git/tinyos-2.x.git*<http://hinrg.cs.jhu.edu/git/tinyos-2.x.git> * ? * > > > 2 . after i use "make micaz reinstall.1 mib510,/dev/ttyS0" to install the >> programme to the mote , i use "tos-deluge /dev/ttyS0 micaz -i 1 >> ./build/micaz/tos_image.xml" to load another application image to the slot >> 1 >> , then i use "tos-deluge /dev/ttyS0 micaz -p 1" , i can get the >> information >> of image in slot 1. but after i reboot the mote(by hand) , i ping the mote >> using "tos-deluge /dev/ttyS0 micaz -p 1", i get "No valid image was >> detected" . why ? maybe the programme did't save the image information in >> a >> non-volatile storage(link EEPROM) . >> >> all my tests are based on serial port , i have not tested the network >> programme . >> *questions:* >> 1 . how many slots(sections ?) are the external flash partitioned ? >> > > For micaz the volumes are defined in the volumes-at45db.xml file. There are > 4 volumes by default. > > 2 . in the network programme , there is a word named "base station" , is >> it >> the application of BaseStation in /tinos-2.x/apps ? >> > > No. We use the word basestation to denote a mote that in which we can > inject images using the serial port. *which application can be used as basestation ? anyone which support deluge ?* > > > -- > Razvan ME > > > 2008/5/14 Razvan Musaloiu-E. <[EMAIL PROTECTED]>: >> >> Hi! >>> >>> On Wed, 14 May 2008, jiwen zhang wrote: >>> >>> Hello : >>> >>>> I am researching deluge and have some problems when i use the version >>>> of tinyos-2.x.git from http://hinrg.cs.jhu.edu/git/ on the day of >>>> 2008-5-4. >>>> 1. when i put the tinyos-2.x-git tree in two different computers , i >>>> find the compile choices are different. for exaple , when i compile the >>>> application of Blink in the directory of >>>> /opt/tinyos-2.x/apps/tests/deluge/Blink and the compile choice in one >>>> computer is that "-D*IDENT_PROGRAM_NAME*=\"BlinkAppC\" >>>> -*DIDENT_USER_ID*=\"Administrator\" >>>> -*DIDENT_HOSTNAME*=\"zjw\" -*DIDENT_USER_HASH*=0x2567b0c3L -* >>>> DIDENT_UNIX_TIME*=0x482a65deL -*DIDENT_UID_HASH*=0xad6bbf5dL" and the >>>> other >>>> is "-D*IDENT_APPNAME*=\"BlinkAppC\" -D*IDENT_USERNAME*=\"zhangjiwen\" >>>> -D* >>>> IDENT_HOSTNAME*=\"zjw\" -D*IDENT_USERHASH*=0x0eac215cL >>>> -D*IDENT_TIMESTAMP*=0x482a64abL >>>> -D*IDENT_UIDHASH*=0x9bde9ac6L" . i use *the same Tinyos tree* , why are >>>> the >>>> compile choices different ? * where* are these macroes such as >>>> IDENT_USERNAME , IDENT_TIMESTAMP defined ? >>>> >>>> >>> Those flags are generated by tos-ident-flags. The file is part of the >>> tools >>> package and the source of it is in: >>> tinyos-2.x/tools/tinyos/misc >>> The flags are suppose to be different because their purpose is to >>> uniquely >>> identify an image. >>> >>> 2. some files in the directroy of tos/lib/deluge/ contains the macroes >>> >>>> for example , in the file DelugeP.nc , there is a macro named >>>> IDENT_UIDHASH, >>>> in the file FlashVolumeManagerP.nc , there are macroes named >>>> IDENT_APPNAME,IDENT_TIMESTAMP,IDENT_UIDHASH and so on . so when i >>>> compile >>>> the application of Blink in in the directory of >>>> /opt/tinyos-2.x/apps/tests/deluge/Blink on one of the two computers, it >>>> will give errors like "IDENT_APPNAME not defined" , the reason is >>>> obvious, >>>> should i modify all the names which the errors tell me not defined ? i >>>> think >>>> there should be a easy way , because the deluge should be cross-PC(-:)) >>>> . >>>> >>>> >>> You are probably using an older tools package. Can you install the tools >>> from sources (from tinyos-2.x/tools)? >>> >>> 3 . If i want to repot deluge to the platform of mica2 , which files >>> >>>> should i modity ? and how ? >>>> >>>> >>> What is 'repot'? :P I don't have any mica2 motes but the code works fine >>> on >>> micaz. >>> >>> -- >>> Razvan ME >>> >>> >> -- zhang jiwen
_______________________________________________ Tinyos-help mailing list Tinyos-help@millennium.berkeley.edu https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
