[Tinyos-help] Test Deluge in Telos Rev. B
mazzara at fing.edu.uy
Fri Mar 11 07:08:50 PST 2005
The problem was that there is a proxy here that blocks the cvs client.
Fortunately this problem was circunvected and the entire tinyos-1.x
update could be done.
Now we have GoldenImage on image 0 in several nodes. Injecting Blink to
image 1 disseminates the application to all the nodes but, rebooting the
nodes, the GoldenImage application continues executing (we spected that
it has to change to execute Blink).
How can we change the execution to Blink?
We also wonder were are located this images, I mean in the internal or
in the external flash?
Jonathan W. Hui wrote:
> You should run 'cvs update' on your *entire* tinyos-1.x tree. Your
> specific problem is due to 'tinyos-1.x/tools/' not being up to date.
> Jonathan W. Hui
> jwhui at cs.berkeley.edu
> Pablo Mazzara wrote:
>> Post cvs update compilation of GoldenImage gives the messages:
>> GoldenImageM.nc:58: `IDENT_USER_ID_BYTES' undeclared here (not in a
>> GoldenImageM.nc:58: initializer element is not constant
>> GoldenImageM.nc:58: (near initialization for `imageInfo.user_id')
>> GoldenImageM.nc:59: `IDENT_HOSTNAME_BYTES' undeclared here (not in a
>> GoldenImageM.nc:59: initializer element is not constant
>> GoldenImageM.nc:59: (near initialization for `imageInfo.hostname')
>> make: *** [exe0] Error 1
>> This problem dissapear adding to tinyos-1.x/tos/system/Ident.h this
>> #ifndef IDENT_USER_ID_BYTES
>> #define IDENT_USER_ID_BYTES 0
>> #ifndef IDENT_HOSTNAME_BYTES
>> #define IDENT_HOSTNAME_BYTES 0
>> Are this values correct?
>> jwhui at EECS.Berkeley.EDU wrote:
>>> The warning from the CC2420 stack is normal and expected.
>>> A node with an app with Deluge compiled in is sufficient for
>>> propagating to other Deluge nodes.
>>> Try updating your tinyos tree with 'cvs update'. Some bug fixes have
>>> been committed recently. Also, you should be using 'GoldenImage.nc'
>>> not 'GoldenImageWriter.nc'.
More information about the Tinyos-help