Re: [Tinyos-help] Never get an ACK on Iris motes

[Miklos Maroti]

Hi David,

Do you see any failures? (send fails or sendDone fails?) If any of
those occur, then you have to put the message back to the pool.

Another thing you should do: call Packet.clear before you set up the
data in the message. The values in the pool can be corrupted. I think
this is the source of your problems.

Best,
Miklos

On Sun, Jun 19, 2011 at 11:33 PM, David Piotrowski  wrote:
> Hello again,
>
> I did some more investigations on the ACK error I described in my previous 
> mail. It seems like I had quite the same error about a year ago but since 
> then I used tossim quite a lot and the error did not show up there.
>
> I have written a small example application that shows the error I have. The 
> application has a fixed message_t variable and a pool from which it gets 
> another message_t. It then sends the fixed message_t and the message_t from 
> the pool alternately over and over again. Upon reception the receiving node 
> lights the received message on its LED. The nodes print some debugging 
> information out on the screen showing which kind of message_t they are 
> actually sending and if it is acknowledged.
>
> Depending on the size of the pool used I get different behavior when it comes 
> to acknowledgements. For me the configuration of the program appended yields 
> no ack for packets that come from the pool but the packets not coming from 
> the pool all get acknowledgements. Other pool sizes yield other results. In 
> several (maybe all?) configurations the first two packets never get 
> acknowledged independent of whether they come from the pool or not. Another 
> thing to notice is that although the packets are not acknowledged, they have 
> been properly received, which is signaled by the blinking LEDs. In some 
> configurations the behaviour of ACKs changes between resets of the node.
>
> I am really searching for some advice on this. The actual program I am 
> working on is using at least two pools, which I suspect are the reason why I 
> never get an ack there although all the messages sent are received and 
> everything is working flawless in tossim.
>
> Thanks, David.
>
>
>
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>

___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Never get an ACK on Iris motes

[David Piotrowski]

Hello again,

I did some more investigations on the ACK error I described in my previous 
mail. It seems like I had quite the same error about a year ago but since then 
I used tossim quite a lot and the error did not show up there.

I have written a small example application that shows the error I have. The 
application has a fixed message_t variable and a pool from which it gets 
another message_t. It then sends the fixed message_t and the message_t from the 
pool alternately over and over again. Upon reception the receiving node lights 
the received message on its LED. The nodes print some debugging information out 
on the screen showing which kind of message_t they are actually sending and if 
it is acknowledged.

Depending on the size of the pool used I get different behavior when it comes 
to acknowledgements. For me the configuration of the program appended yields no 
ack for packets that come from the pool but the packets not coming from the 
pool all get acknowledgements. Other pool sizes yield other results. In several 
(maybe all?) configurations the first two packets never get acknowledged 
independent of whether they come from the pool or not. Another thing to notice 
is that although the packets are not acknowledged, they have been properly 
received, which is signaled by the blinking LEDs. In some configurations the 
behaviour of ACKs changes between resets of the node.

I am really searching for some advice on this. The actual program I am working 
on is using at least two pools, which I suspect are the reason why I never get 
an ack there although all the messages sent are received and everything is 
working flawless in tossim.

Thanks, David.



Makefile
Description: Binary data


poolTestAppC.nc
Description: Binary data


poolTestC.nc
Description: Binary data



___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Unknown error

[Sergio Valcarcel]

Hi,

OK, in fact it was a bad guess since I've just also realized that it most
likely would not have let you install the 32bit binaries into a 64bit
machine.

Cheers!
Sergio


On Sun, Jun 19, 2011 at 4:25 PM, adel zalok  wrote:

> Dear sergio,
> I am using a 32 bit system,
> I Beleive that both versions are available in the repository.
>
> Best regards,
> Adel.
>
> On Sun, Jun 19, 2011 at 10:07 AM, Sergio Valcarcel 
> wrote:
>
>> Just a hint that may (or may not) help...
>> Are you using a 64bit or 32 bit system?
>> Are both versions of the toolchain available in the repository?
>>
>> Cheers!
>> Sergio
>>
>>
>> On Sun, Jun 19, 2011 at 4:03 PM, Martin Zoller 
>> wrote:
>>
>>> **
>>> Hi Adel,
>>> What exactly are you compiling, i.e. where are you doing "make micaz"? I
>>> suggest that you start with the "Blink" application. Then you should have a
>>> look at the BEGINNING of the output, because that's where you usually find
>>> the relevant error. Maybe a wrong compiler and/or makefile is being used.
>>> Also, check your paths, e.g. "less $MAKERULES" should show you the TinyOS
>>> Makerules file.
>>>
>>> - Martin
>>>
>>> On 06/19/2011 02:57 PM, adel zalok wrote:
>>>
>>> Dear Martin,
>>>
>>> Sorry to bother you, but I have reinstalled tinyOS using the method
>>> described here:
>>> http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT
>>>
>>> and still I am having the same problem.
>>>
>>> On Sun, Jun 19, 2011 at 8:39 AM, adel zalok wrote:
>>>
 Dear martin,

 This is the output of  "nescc -v" :

 nescc: 1.3.1
 gcc -_fnesc-gcc=gcc -specs=/usr/lib/ncc/tdspecs -_fnesc-include=nesc_nx
 -I/usr/lib/ncc -v -DNESC=131
 Using built-in specs.
 Reading specs from /usr/lib/ncc/tdspecs
 COLLECT_GCC=gcc

 COLLECT_LTO_WRAPPER=/usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/lto-wrapper
 Target: i686-linux-gnu
 Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
 4.5.2-8ubuntu4' 
 --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs--enable-languages=c,c++,fortran,objc,obj-c++
  --prefix=/usr
 --program-suffix=-4.5 --enable-shared --enable-multiarch
 --with-multiarch-defaults=i386-linux-gnu --enable-linker-build-id
 --with-system-zlib --libexecdir=/usr/lib/i386-linux-gnu
 --without-included-gettext --enable-threads=posix
 --with-gxx-include-dir=/usr/include/c++/4.5 
 --libdir=/usr/lib/i386-linux-gnu
 --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
 --enable-libstdcxx-time=yes --enable-plugin --enable-gold
 --enable-ld=default --with-plugin-ld=ld.gold --enable-objc-gc
 --enable-targets=all --disable-werror --with-arch-32=i686
 --with-tune=generic --enable-checking=release --build=i686-linux-gnu
 --host=i686-linux-gnu --target=i686-linux-gnu
 Thread model: posix
 gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)
 I believe it is there, however should I uninstall and reinstall again ?

 On Sun, Jun 19, 2011 at 8:23 AM, Martin Zoller <
 mailingli...@zollerit.ch> wrote:

>  I recommend using the installation method described here:
> http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT
> That should work on most systems.
> Apparently you are using mica motes, so you will need the avr-gcc
> toolchain.
> Did you install nesc? What is the output of "nescc -v"?
>
> - Martin
>
>
> On 06/19/2011 03:31 AM, adel zalok wrote:
>
>  This Error I get when I run the make micaz or make micaz sim or any
> make command
>
> On Sat, Jun 18, 2011 at 9:29 PM, adel zalok 
> wrote:
>
>> Dear Sir,
>>
>> I have been trying to install TinyOS on ubuntu 11.04 as well as Ubunut
>> 10.10 and I keep getting a very long error, the error ends with these 
>> lines:
>>
>>
>> In component `AlarmToTimerC':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:38: syntax error
>> before `uint32_t'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:44: syntax error
>> before `m_dt'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:45: syntax error
>> before `m_oneshot'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:47: syntax error
>> before `t0'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function `start':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `m_dt' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `dt' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50: `m_oneshot'
>> undeclared (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50: `oneshot'
>> undeclared (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51: `Alarm'
>> undeclared (first use in this function)
>> /opt/tinyos-2.1.1/to

Re: [Tinyos-help] Unknown error

[Sergio Valcarcel]

Just a hint that may (or may not) help...
Are you using a 64bit or 32 bit system?
Are both versions of the toolchain available in the repository?

Cheers!
Sergio

On Sun, Jun 19, 2011 at 4:03 PM, Martin Zoller wrote:

> **
> Hi Adel,
> What exactly are you compiling, i.e. where are you doing "make micaz"? I
> suggest that you start with the "Blink" application. Then you should have a
> look at the BEGINNING of the output, because that's where you usually find
> the relevant error. Maybe a wrong compiler and/or makefile is being used.
> Also, check your paths, e.g. "less $MAKERULES" should show you the TinyOS
> Makerules file.
>
> - Martin
>
> On 06/19/2011 02:57 PM, adel zalok wrote:
>
> Dear Martin,
>
> Sorry to bother you, but I have reinstalled tinyOS using the method
> described here:
> http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT
>
> and still I am having the same problem.
>
> On Sun, Jun 19, 2011 at 8:39 AM, adel zalok wrote:
>
>> Dear martin,
>>
>> This is the output of  "nescc -v" :
>>
>> nescc: 1.3.1
>> gcc -_fnesc-gcc=gcc -specs=/usr/lib/ncc/tdspecs -_fnesc-include=nesc_nx
>> -I/usr/lib/ncc -v -DNESC=131
>> Using built-in specs.
>> Reading specs from /usr/lib/ncc/tdspecs
>> COLLECT_GCC=gcc
>>
>> COLLECT_LTO_WRAPPER=/usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/lto-wrapper
>> Target: i686-linux-gnu
>> Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
>> 4.5.2-8ubuntu4' 
>> --with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs--enable-languages=c,c++,fortran,objc,obj-c++
>>  --prefix=/usr
>> --program-suffix=-4.5 --enable-shared --enable-multiarch
>> --with-multiarch-defaults=i386-linux-gnu --enable-linker-build-id
>> --with-system-zlib --libexecdir=/usr/lib/i386-linux-gnu
>> --without-included-gettext --enable-threads=posix
>> --with-gxx-include-dir=/usr/include/c++/4.5 --libdir=/usr/lib/i386-linux-gnu
>> --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
>> --enable-libstdcxx-time=yes --enable-plugin --enable-gold
>> --enable-ld=default --with-plugin-ld=ld.gold --enable-objc-gc
>> --enable-targets=all --disable-werror --with-arch-32=i686
>> --with-tune=generic --enable-checking=release --build=i686-linux-gnu
>> --host=i686-linux-gnu --target=i686-linux-gnu
>> Thread model: posix
>> gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)
>> I believe it is there, however should I uninstall and reinstall again ?
>>
>> On Sun, Jun 19, 2011 at 8:23 AM, Martin Zoller 
>> wrote:
>>
>>>  I recommend using the installation method described here:
>>> http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT
>>> That should work on most systems.
>>> Apparently you are using mica motes, so you will need the avr-gcc
>>> toolchain.
>>> Did you install nesc? What is the output of "nescc -v"?
>>>
>>> - Martin
>>>
>>>
>>> On 06/19/2011 03:31 AM, adel zalok wrote:
>>>
>>>  This Error I get when I run the make micaz or make micaz sim or any
>>> make command
>>>
>>> On Sat, Jun 18, 2011 at 9:29 PM, adel zalok wrote:
>>>
 Dear Sir,

 I have been trying to install TinyOS on ubuntu 11.04 as well as Ubunut
 10.10 and I keep getting a very long error, the error ends with these 
 lines:


 In component `AlarmToTimerC':
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:38: syntax error before
 `uint32_t'
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:44: syntax error before
 `m_dt'
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:45: syntax error before
 `m_oneshot'
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:47: syntax error before
 `t0'
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function `start':
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `m_dt' undeclared
 (first use in this function)
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `dt' undeclared
 (first use in this function)
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50: `m_oneshot'
 undeclared (first use in this function)
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50: `oneshot'
 undeclared (first use in this function)
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51: `Alarm' undeclared
 (first use in this function)
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51: `t0' undeclared
 (first use in this function)
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:54: syntax error before
 `dt'
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
 `Timer.startPeriodic':
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:55: `Alarm' undeclared
 (first use in this function)
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:55: `dt' undeclared
 (first use in this function)
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
 /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:57: syntax error before
 `d

Re: [Tinyos-help] radio model CC2420

[Sergio Valcarcel]

Hi Hugo,

there is no gain in a radio chip, that concept is more related to the
antenna and it is usually a fix parameter based on the radiation pattern.

However, you can set the transmitting RSSI (power) using the CC2420Packet
interface. Have a look into the tos chips cc2420 interfaces and you will
find the getrssi and setrssi interfaces.

Cheers!
Sergio

On Sat, Jun 18, 2011 at 5:03 PM, Hugo Vinicius wrote:

> Hi,
>
> What's gain of radio model CC2420 used to TinyOS in RadioCoutToLeds
> application?
> Is there a default value? Can I change this value? The TinyOS send the
> packages with differents gain values or same gain values?
>
> Hugo
>
>
>
> ___
> Tinyos-help mailing list
> Tinyos-help@millennium.berkeley.edu
> https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
>
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Unknown error

[Martin Zoller]

Hi Adel,
What exactly are you compiling, i.e. where are you doing "make micaz"? I 
suggest that you start with the "Blink" application. Then you should 
have a look at the BEGINNING of the output, because that's where you 
usually find the relevant error. Maybe a wrong compiler and/or makefile 
is being used.
Also, check your paths, e.g. "less $MAKERULES" should show you the 
TinyOS Makerules file.


- Martin

On 06/19/2011 02:57 PM, adel zalok wrote:

Dear Martin,

Sorry to bother you, but I have reinstalled tinyOS using the method 
described here:

http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT

and still I am having the same problem.

On Sun, Jun 19, 2011 at 8:39 AM, adel zalok > wrote:


Dear martin,

This is the output of  "nescc -v" :

nescc: 1.3.1
gcc -_fnesc-gcc=gcc -specs=/usr/lib/ncc/tdspecs
-_fnesc-include=nesc_nx -I/usr/lib/ncc -v -DNESC=131
Using built-in specs.
Reading specs from /usr/lib/ncc/tdspecs
COLLECT_GCC=gcc

COLLECT_LTO_WRAPPER=/usr/lib/i386-linux-gnu/gcc/i686-linux-gnu/4.5.2/lto-wrapper
Target: i686-linux-gnu
Configured with: ../src/configure -v
--with-pkgversion='Ubuntu/Linaro 4.5.2-8ubuntu4'
--with-bugurl=file:///usr/share/doc/gcc-4.5/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.5 --enable-shared --enable-multiarch
--with-multiarch-defaults=i386-linux-gnu --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib/i386-linux-gnu
--without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.5
--libdir=/usr/lib/i386-linux-gnu --enable-nls --with-sysroot=/
--enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-plugin --enable-gold
--enable-ld=default --with-plugin-ld=ld.gold --enable-objc-gc
--enable-targets=all --disable-werror --with-arch-32=i686
--with-tune=generic --enable-checking=release
--build=i686-linux-gnu --host=i686-linux-gnu --target=i686-linux-gnu
Thread model: posix
gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4)
I believe it is there, however should I uninstall and reinstall
again ?

On Sun, Jun 19, 2011 at 8:23 AM, Martin Zoller
mailto:mailingli...@zollerit.ch>> wrote:

I recommend using the installation method described here:
http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT
That should work on most systems.
Apparently you are using mica motes, so you will need the
avr-gcc toolchain.
Did you install nesc? What is the output of "nescc -v"?

- Martin


On 06/19/2011 03:31 AM, adel zalok wrote:

This Error I get when I run the make micaz or make micaz sim
or any make command

On Sat, Jun 18, 2011 at 9:29 PM, adel zalok
mailto:adel.zalok...@gmail.com>> wrote:

Dear Sir,

I have been trying to install TinyOS on ubuntu 11.04 as
well as Ubunut 10.10 and I keep getting a very long
error, the error ends with these lines:

In component `AlarmToTimerC':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:38:
syntax error before `uint32_t'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:44:
syntax error before `m_dt'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:45:
syntax error before `m_oneshot'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:47:
syntax error before `t0'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In
function `start':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49:
`m_dt' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `dt'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50:
`m_oneshot' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50:
`oneshot' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51:
`Alarm' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51: `t0'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top
level:
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:54:
syntax error before `dt'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In
function `Timer.startPeriodic':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:55:
`Alarm' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:55: `dt'
undeclared (first use in this 

Re: [Tinyos-help] Unknown error

[Martin Zoller]

I recommend using the installation method described here: 
http://docs.tinyos.net/tinywiki/index.php/Installing_from_SVN/GIT

That should work on most systems.
Apparently you are using mica motes, so you will need the avr-gcc toolchain.
Did you install nesc? What is the output of "nescc -v"?

- Martin

On 06/19/2011 03:31 AM, adel zalok wrote:
This Error I get when I run the make micaz or make micaz sim or any 
make command


On Sat, Jun 18, 2011 at 9:29 PM, adel zalok > wrote:


Dear Sir,

I have been trying to install TinyOS on ubuntu 11.04 as well as
Ubunut 10.10 and I keep getting a very long error, the error ends
with these lines:

In component `AlarmToTimerC':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:38: syntax error
before `uint32_t'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:44: syntax error
before `m_dt'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:45: syntax error
before `m_oneshot'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:47: syntax error
before `t0'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function `start':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `m_dt'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `dt'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50: `m_oneshot'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50: `oneshot'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51: `Alarm'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51: `t0'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:54: syntax error
before `dt'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
`Timer.startPeriodic':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:55: `Alarm'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:55: `dt'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:57: syntax error
before `dt'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
`Timer.startOneShot':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:58: `Alarm'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:58: `dt'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
`Timer.stop':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:61: `Alarm'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
`fired.runTask':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:65: `m_oneshot'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:66: `Alarm'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:66: `m_dt'
undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:71: unknown
interface `Alarm'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
`Alarm.fired':
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:71: task
interface `TaskBasic' has no command named `postTask'
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
/opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:73: syntax error
before `Timer'
AlarmToTimerC: `Timer.startPeriodicAt' not implemented
AlarmToTimerC: `Timer.startOneShotAt' not implemented
In file included from
/opt/tinyos-2.1.1/tos/platforms/mica/HilTimerMilliC.nc:45,
 from /opt/tinyos-2.1.1/tos/system/TimerMilliP.nc:41,
 from /opt/tinyos-2.1.1/tos/system/TimerMilliC.nc:40,
 from BlinkAppC.nc:46:
In component `VirtualizeTimerC':
/opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:37: syntax
error before `uint8_t'
/opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:50: syntax
error before `uint32_t'
/opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:50: warning:
no semicolon at end of struct or union
/opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:51: syntax
error before `dt'
/opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:52: syntax
error before `isoneshot'
/opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:53: syntax
error before `isrunning'
/opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:54: syntax
error before `_reserved'
VirtualizeTimerC: `

[Tinyos-help] Compilation Error

[adel zalok]

Dear Sir,

I am getting a very long error when I am trying to compile tinyOS using make
micaz or make micaz sim, I have installed everything correctly but I still
don't get it.
Here is a snippet of the error.

In file included from /opt/tinyos-2.1.1/tos/platforms/micaz/hardware.h:52,
 from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41,
 from /opt/tinyos-2.1.1/tos/system/TinySchedulerC.nc:40:
/opt/tinyos-2.1.1/tos/platforms/mica/MicaTimer.h:109: syntax error before
`counter_one_overflow_t'
/opt/tinyos-2.1.1/tos/platforms/mica/MicaTimer.h:110: syntax error before
`counter_three_overflow_t'
In file included from /opt/tinyos-2.1.1/tos/system/TinySchedulerC.nc:40:
In component `SchedulerBasicP':
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:45: syntax error before
`uint8_t'
In file included from /opt/tinyos-2.1.1/tos/system/TinySchedulerC.nc:40:
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:56: syntax error before
`m_head'
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:57: syntax error before
`m_tail'
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:58: syntax error before
`m_next'
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:67: syntax error before
`popTask'
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:72: `m_next' undeclared here
(not in a function)
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:72: subscripted value is
neither array nor pointer
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:72: warning: data definition
has no type or storage class
/opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:73: syntax error before `if'
SchedulerBasicP: `TaskBasic.error_t' not implemented
SchedulerBasicP: `Scheduler.init' not implemented
SchedulerBasicP: `Scheduler.taskLoop' not implemented
SchedulerBasicP: `Scheduler.bool' not implemented
In file included from /opt/tinyos-2.1.1/tos/chips/atm128/McuSleepC.nc:46,
 from /opt/tinyos-2.1.1/tos/system/TinySchedulerC.nc:41:
In interface `McuPowerOverride':
/opt/tinyos-2.1.1/tos/interfaces/McuPowerOverride.nc:54: only commands and
events can be defined in interfaces
/opt/tinyos-2.1.1/tos/interfaces/McuPowerOverride.nc:54: syntax error before
`lowestState'
In component `McuSleepC':
/opt/tinyos-2.1.1/tos/chips/atm128/McuSleepC.nc:58: syntax error before
`atm128PowerBits'
/opt/tinyos-2.1.1/tos/chips/atm128/McuSleepC.nc:66: syntax error before
`getPowerState'
McuSleepC: `McuSleep.sleep' not implemented
McuSleepC: `McuPowerState.update' not implemented
In C file:
: Scheduler `TinySchedulerC' has no scheduling interface named
`TaskBasic'
RadioCountToLeds.h:34: syntax error before `nx_uint16_t'
RadioCountToLeds.h:34: warning: no semicolon at end of struct or union
RadioCountToLeds.h:35: warning: data definition has no type or storage class
failed to parse message file RadioCountToLeds.h
make: *** [RadioCountMsg.py] Error 1

Best regards,
-- 
Adel Zalok .
___
Tinyos-help mailing list
Tinyos-help@millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Unknown error

[adel zalok]

Thank you for your reply, but I have installed it and removed it 3 times up
till now following the steps on the website and still I do get this problem,
http://docs.tinyos.net/tinywiki/index.php/Installing_TinyOS_2.1.1#Two-step_install_on_your_host_OS_with_Debian_packages

I have installed TinyOS before without such problems, I really need to get
it up and running fast, I have also tried to install tinyOs-required-all
packaged but I had it all. so I don't know what to do, Please help.

Best regards,
Adel Zalok.

On Sat, Jun 18, 2011 at 11:59 PM, Eric Decker  wrote:

> you don't have the toolchains installed right.
>
> On Sat, Jun 18, 2011 at 6:29 PM, adel zalok wrote:
>
>> Dear Sir,
>>
>> I have been trying to install TinyOS on ubuntu 11.04 as well as Ubunut
>> 10.10 and I keep getting a very long error, the error ends with these lines:
>>
>>
>> In component `AlarmToTimerC':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:38: syntax error before
>> `uint32_t'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:44: syntax error before
>> `m_dt'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:45: syntax error before
>> `m_oneshot'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:47: syntax error before
>> `t0'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function `start':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `m_dt' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:49: `dt' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50: `m_oneshot'
>> undeclared (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:50: `oneshot' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51: `Alarm' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:51: `t0' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:54: syntax error before
>> `dt'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
>> `Timer.startPeriodic':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:55: `Alarm' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:55: `dt' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:57: syntax error before
>> `dt'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
>> `Timer.startOneShot':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:58: `Alarm' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:58: `dt' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
>> `Timer.stop':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:61: `Alarm' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
>> `fired.runTask':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:65: `m_oneshot'
>> undeclared (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:66: `Alarm' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:66: `m_dt' undeclared
>> (first use in this function)
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:71: unknown interface
>> `Alarm'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: In function
>> `Alarm.fired':
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:71: task interface
>> `TaskBasic' has no command named `postTask'
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc: At top level:
>> /opt/tinyos-2.1.1/tos/lib/timer/AlarmToTimerC.nc:73: syntax error before
>> `Timer'
>> AlarmToTimerC: `Timer.startPeriodicAt' not implemented
>> AlarmToTimerC: `Timer.startOneShotAt' not implemented
>> In file included from
>> /opt/tinyos-2.1.1/tos/platforms/mica/HilTimerMilliC.nc:45,
>>  from /opt/tinyos-2.1.1/tos/system/TimerMilliP.nc:41,
>>  from /opt/tinyos-2.1.1/tos/system/TimerMilliC.nc:40,
>>  from BlinkAppC.nc:46:
>> In component `VirtualizeTimerC':
>> /opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:37: syntax error
>> before `uint8_t'
>> /opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:50: syntax error
>> before `uint32_t'
>> /opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:50: warning: no
>> semicolon at end of struct or union
>> /opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:51: syntax error
>> before `dt'
>> /opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:52: syntax error
>> before `isoneshot'
>> /opt/tinyos-2.1.1/tos/lib/timer/VirtualizeTimerC.nc:53: syntax error
>> before `isrunning'
>> /opt/tinyos-2.1.1/tos/lib/timer/Virt