[Tinyos-help] Deluge/GoldenImage Build Error

jwhui at EECS.Berkeley.EDU jwhui at EECS.Berkeley.EDU
Fri Mar 18 08:18:37 PST 2005


Did you make sure that your *entire* cvs tree is up to date (including tinyos-1.x/tools)?

-- 
Jonathan W. Hui
jwhui at cs.berkeley.edu
http://www.cs.berkeley.edu/~jwhui/ 

----- Original Message -----
From: Krisakorn Rerkrai <kre at mobnets.rwth-aachen.de>
Date: Friday, March 18, 2005 7:39 am
Subject: [Tinyos-help] Deluge/GoldenImage Build Error

> Hi,
>     I've tried to follow the steps in Deluge manual 
> http://www.cs.berkeley.edu/~jwhui/research/projects/deluge/deluge-
> manual.pdf <" 
> target="l">http://www.cs.berkeley.edu/%7Ejwhui/research/projects/deluge/deluge-manual.pdf>
> 
> 
>    I followed the same exact steps. I have 2.2 done
> but I can't build GoldenImage for telosb. Followings
> are what I did:
> 1. updated CVS and used Deluge 2.0 beta version for
> revision B
> 2. copied tinyos-1.x/beta/Deluge/delugetools/* to
> tinyos-1.x/tools/java/net/tinyos/deluge
> 3. set the environment variable in
> /tools/make/Makelocal
>    TINYOS_NP=BNP or even tried $TINYOS_NP=BNP make
> telos
> 4. built and installed Blink app and got LEDs sequence
> correct (2.2 in the manual)
> 
>   Then I tried to compile GoldenImage and I got:
> 
> 
> $ make telos
> mkdir -p build/telosb
>    compiling GoldenImage to a telosb binary
> ncc -o build/telosb/main.exe -Os -DDELUGE_GOLDEN_IMAGE
> -DDELUGE_LEDS -mdisable-h
> wmul -I/opt/tinyos-1.x/tos/lib/CC2420Radio
> -I/opt/tinyos-1.x/tos/../beta/STM25P/
> STM25P -I%T/../beta/Deluge/Deluge
> -Wl,--section-start=.text=0x5000,--defsym=_res
> et_vector__=0x4000 -Wall -Wshadow
> -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=tel
> osb -fnesc-cfile=build/telosb/app.c -board=
> -DTOSH_MAX_TASKS_LOG2=7 -DIDENT_PROG
> RAM_NAME="GoldenImage"
> -DIDENT_PROGRAM_NAME_BYTES="71,111,108,100,101,110,73,109
> ,97,103,101,0" -DIDENT_USER_ID="kre_admin"
> -DIDENT_USER_ID_BYTES="107,114,101,95
> ,97,100,109,105,110,0" -DIDENT_HOSTNAME="gracchus"
> -DIDENT_HOSTNAME_BYTES="103,1
> 14,97,99,99,104,117,115,0"
> -DIDENT_USER_HASH=0x93cf23a9L -DIDENT_UNIX_TIME=0x423
> aee8bL GoldenImage.nc -lm
> C:/UCB/cygwin/opt/tinyos-1.x/beta/Deluge/Deluge/DelugeMetadataM.nc:
> In function
> `execute':
> C:/UCB/cygwin/opt/tinyos-1.x/beta/Deluge/Deluge/DelugeMetadataM.nc:84:
> `STORAGE_
> BLOCK_SIZE' undeclared (first use in this function)
> C:/UCB/cygwin/opt/tinyos-1.x/beta/Deluge/Deluge/DelugeMetadataM.nc:84:
> (Each und
> eclared identifier is reported only once
> C:/UCB/cygwin/opt/tinyos-1.x/beta/Deluge/Deluge/DelugeMetadataM.nc:84:
> for each
> function it appears in.)
> C:/UCB/cygwin/opt/tinyos-1.x/beta/Deluge/Deluge/DelugeMetadataM.nc:
> In function
> `DataWrite.eraseDone':
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/Deluge/Deluge/DelugeMetadataM.nc:329:`STORAGE
> _BLOCK_SIZE' undeclared (first use in this function)
> C:/UCB/cygwin/opt/tinyos-1.x/beta/Deluge/Deluge/DelugeStorageM.nc:
> In function `
> StorageRemap.physicalAddr':
> C:/UCB/cygwin/opt/tinyos-1.x/beta/Deluge/Deluge/DelugeStorageM.nc:208:
> `STORAGE_
> INVALID_ADDR' undeclared (first use in this function)
> In file included from
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/BlockStora
> geM.nc:35:
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:
> At top level:
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:30:
> parse error
> before `addr'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:32:
> parse error
> before `addr'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:35:
> parse error
> before `addr'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:38:
> parse error
> before `stm25p_addr_t'
> In file included from
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/BlockStora
> geM.nc:38:
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManager.nc:29:
> only comma
> nds and events can be defined in interfaces
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManager.nc:29:
> warning: r
> eturn-type defaults to `int'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManager.nc:29:
> parse erro
> r before `getVolumeSize'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/BlockStorageM.nc:
> In function `n
> ewRequest':
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/BlockStorageM.nc:114:
> interface
> has no command or event named `getVolumeSize'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/BlockStorageM.nc:114:
> subscripte
> d value is neither array nor pointer
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/HALSTM25PM.nc:
> In function `chec
> kPost':
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/HALSTM25PM.nc:81:
> `STORAGE_FAIL'
> undeclared (first use in this function)
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManagerM.nc:
> In function
> `actualMount':
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/STM25P/STM25P/StorageManagerM.nc:130:`STORAGE
> _FAIL' undeclared (first use in this function)
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManagerM.nc:
> At top level
> :
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/STM25P/STM25P/StorageManagerM.nc:224:`getVolu
> meSize' is not in interface `StorageManager'
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/STM25P/STM25P/StorageManagerM.nc:245:conflict
> ing types for `SectorStorage.read'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:30:
> previous de
> claration of `SectorStorage.read'
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/STM25P/STM25P/StorageManagerM.nc:266:conflict
> ing types for `SectorStorage.write'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:32:
> previous de
> claration of `SectorStorage.write'
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/STM25P/STM25P/StorageManagerM.nc:286:conflict
> ing types for `SectorStorage.erase'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:35:
> previous de
> claration of `SectorStorage.erase'
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/STM25P/STM25P/StorageManagerM.nc:305:conflict
> ing types for `SectorStorage.computeCrc'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/SectorStorage.nc:38:
> previous de
> claration of `SectorStorage.computeCrc'
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManagerM.nc:
> In function
> `HALSTM25P.pageProgramDone':
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/STM25P/STM25P/StorageManagerM.nc:340:`STORAGE
> _FAIL' undeclared (first use in this function)
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManagerM.nc:
> In function
> `HALSTM25P.sectorEraseDone':
> C:/UCB/cygwin/opt/tinyos-
> 1.x/beta/STM25P/STM25P/StorageManagerM.nc:377:`STORAGE
> _FAIL' undeclared (first use in this function)
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManagerM.nc:
> At top level
> :
> C:/UCB/cygwin/opt/tinyos-1.x/beta/STM25P/STM25P/StorageManagerM.nc:42:
> `StorageM
> anager.stm25p_addr_t' not implemented
> GoldenImageM.nc: In function `DataWrite.writeDone':
> GoldenImageM.nc:249: `STORAGE_FAIL' undeclared (first
> use in this function)
> make: *** [exe0] Error 1
> 
> 
> Can anyone tell me what wrong is my setup?
> I also read many solutions about Deluge in tinyos-help
> but I couldn't find the solution for my case. Any help
> would be appreciated.
> 
> Regards,
> Kris
> 
> 
> _______________________________________________
> Tinyos-help mailing list
> Tinyos-help at Millennium.Berkeley.EDU
> http://mail.Millennium.Berkeley.EDU/mailman/listinfo/tinyos-help
> 



More information about the Tinyos-help mailing list