Hi!
On Mon, 18 Jun 2007, Yu-En Tsai wrote:
On 6/17/07, Razvan Musaloiu-E. <[EMAIL PROTECTED]> wrote:
Hi!
On Sun, 17 Jun 2007, Yu-En Tsai wrote:
> Hi Mike,
> I use these 2 instructions to do CVS update:
> cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/tinyos login
> cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/tinyos co -P tinyos-2.x
After this checkout did you update the TOSDIR variable to point the
checkout? The bnp.extra is using the TOSDIR to build the paths the Deluge
T2 needs.
I didn't change TOSDIR. It's /opt/tinyos-2.x/tos.
But the cvs checkout was done in /opt/tinyos-2.x right? :-)
I looked into bnp.extra, the paths are all correct and version is
2007/06/08.
Correct. That's the last version.
> I update my CVS tree again and the same problems still occur.
Did you install the tools/tinyos/misc?
I guess my problems are from this. As in my first post, I can't go through
the section 2 of Deluge T2 manual.
1. There are no "Bootstrap" and "configure" in my $TOSROOT.
It's a mistake in the manual. It should have been $TOSROOT/tools instead.
I'll update it as soon as possible.
2. I run "./Bootstrap" and "./configure" in $TOSROOT/tools and got:
********************************************************
$ ./Bootstrap
+ aclocal
+ autoconf
+ '[' -d config-aux ']'
+ automake -a -c
+ set -x
+ cd platforms/mica/uisp
+ ./bootstrap
autoheader-2.61: WARNING: Using auxiliary files such as `acconfig.h',
`config.h.bot'
autoheader-2.61: WARNING: and `config.h.top', to define templates for
`config.h.in'
autoheader-2.61: WARNING: is deprecated and discouraged.
autoheader-2.61:
autoheader-2.61: WARNING: Using the third argument of `AC_DEFINE' and
autoheader-2.61: WARNING: `AC_DEFINE_UNQUOTED' allows one to define a template
without
autoheader-2.61: WARNING: `acconfig.h':
autoheader-2.61:
autoheader-2.61: WARNING: AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader-2.61: [Define if a function `main' is needed.])
autoheader-2.61:
autoheader-2.61: WARNING: More sophisticated templates can also be produced,
see the
autoheader-2.61: WARNING: documentation.
+ rm -f config.cache src/config.cache
*********************************************************************
$ ./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 ISO C89... 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/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... configure: error: java not found
**************************************************************************
I did install JAVA and environment variables are correct.
The configure script is building the Makefile from the
$TOSROOT/tools/tinyos/misc. I'm not sure why the detection of the JDK is
failing on your system. Can you run please run:
$TOSROOT/tools/tinyos/misc/tos-locate-jre --javac
From what I can see this is the way the configure script tries to locate
the JDK.
3. "make" and "make install" neither work in $TOSROOT/tools/tinyos/misc.
Can you point me how to install the tools/tinyos/misc?
Most of the scripts from there can be installed by just copying them
somewhere in your path. If you don't put any --prefix=... when you run
the configure script then the path is /usr/local/bin.
--
Razvan ME
> Also, I tried to download "bnp.extra" directly from web-based CVS repository.
> It didn't work either.
> Did I miss anything?
Can you be more specific about what exactly have you done?
I did the tools installation part as I mentioned above.
I compiled TOSBoot, then run burn script.
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
installing micaz bootloader using mib510
uisp -dprog=mib510 -dserial=/dev/ttyS0 --wr_fuse_h=0xd9 -dpart=ATmega128
--wr_fuse_e=ff --upload if=
Firmware Version: 2.1
Atmel AVR ATmega128 is found.
Error: No such file or directory
->
make: *** [program_bl] Error 1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
I also tried to install GoldenImage.
vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
$ CFLAGS=-DDELUGE_BASESTATION make micaz install mib510,/dev/ttyS0
mkdir -p build/micaz
compiling GoldenImageC to a micaz binary
ncc -o build/micaz/main.exe -Os -finline-limit=100000 -Wall -Wshadow -Wnesc-all
-target=micaz -fnesc-cfile=build/micaz/app.c -board=micasb -Ibuild/micaz
-DDELUGE_BASESTATION -DDELUGE_BASESTATION -fnesc-dump=wiring
-fnesc-dump='interfaces(!abstract())' -fnesc-dump='referenced(interfacedefs,
components)' -fnesc-dumpfile=build/micaz/wiring-check.xml GoldenImageC.nc -lm
In component `GoldenImageC':
GoldenImageC.nc:31: component DelugeC not found
make: *** [exe0] Error 1
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Ryan,
> I tried your suggestion too.
> There will be more error messages.
>
> In file included from GoldenImageC.nc:31:
> ******************************************************************
> In component `DelugeC':
> /opt/tinyos-2.x/tos/lib/net/Deluge/DelugeC.nc:37: component
FlashVolumeManagerC not found
> /opt/tinyos-2.x/tos/lib/net/Deluge/DelugeC.nc:37: component
`FlashVolumeManagerC ' is not generic
> ...
Manually adding the path to DelugeC is not enough. The path to the
FlashVolumeManager, Dissemination and a bunch of platform specific
components are also necessary. The bnp.extra should properly include
everything.
--
Razvan ME
Thanks so much for all your replies.
Yu-En
_______________________________________________
Tinyos-help mailing list
[email protected]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
