Johny Mattsson | 1 May 01:54 2012
Picon

Re: Stopping Radio Activity

On 30 April 2012 13:04, kaustav das <kaustavdas1989 <at> gmail.com> wrote:
> Thanks. I have tried with resource arbitration by giving exclusive access of
> SPI for flash writing. But that didn't work.

The idea is that thanks to resource arbitration you don't need to
worry about exclusivity - the arbiter grants exclusive access in
sequence, ensuring there are no conflicts. If for some reason (I can't
see why though) you need to not have anyone else even request bus
access while you're doing your flash I/O, then you'll need to stop
those components.

Regards,
/Johny

PS. It's good to keep the list cc'd for archival purposes, plus it
gives others a chance to contribute further information.
--

-- 
Johny Mattsson
Senior Software Engineer

DiUS Computing Pty. Ltd.
where ideas are engineered
kaustav das | 1 May 07:03 2012
Picon

Re: Stopping Radio Activity

When I am calling the function for acquiring SPI resource for flash writing the radio stops receiving packets. I am not understanding what is happening?

On Tue, May 1, 2012 at 5:24 AM, Johny Mattsson <jmattsson <at> dius.com.au> wrote:
On 30 April 2012 13:04, kaustav das <kaustavdas1989 <at> gmail.com> wrote:
> Thanks. I have tried with resource arbitration by giving exclusive access of
> SPI for flash writing. But that didn't work.

The idea is that thanks to resource arbitration you don't need to
worry about exclusivity - the arbiter grants exclusive access in
sequence, ensuring there are no conflicts. If for some reason (I can't
see why though) you need to not have anyone else even request bus
access while you're doing your flash I/O, then you'll need to stop
those components.


Regards,
/Johny

PS. It's good to keep the list cc'd for archival purposes, plus it
gives others a chance to contribute further information.
--
Johny Mattsson
Senior Software Engineer

DiUS Computing Pty. Ltd.
where ideas are engineered



--
Kaustav Das,
M.Tech Student,
Department of CSE,
IIT Bombay

<div>
<p>When I am calling the function for acquiring SPI resource for flash writing the radio stops receiving packets. I am not understanding what is happening?<br><br></p>
<div class="gmail_quote">On Tue, May 1, 2012 at 5:24 AM, Johny Mattsson <span dir="ltr">&lt;<a href="mailto:jmattsson <at> dius.com.au" target="_blank">jmattsson <at> dius.com.au</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div class="im">On 30 April 2012 13:04, kaustav das &lt;<a href="mailto:kaustavdas1989 <at> gmail.com">kaustavdas1989 <at> gmail.com</a>&gt; wrote:<br>

&gt; Thanks. I have tried with resource arbitration by giving exclusive access of<br>
&gt; SPI for flash writing. But that didn't work.<br><br>
</div>The idea is that thanks to resource arbitration you don't need to<br>
worry about exclusivity - the arbiter grants exclusive access in<br>
sequence, ensuring there are no conflicts. If for some reason (I can't<br>
see why though) you need to not have anyone else even request bus<br>
access while you're doing your flash I/O, then you'll need to stop<br>
those components.<br><br><br>
Regards,<br>
/Johny<br><br>
PS. It's good to keep the list cc'd for archival purposes, plus it<br>
gives others a chance to contribute further information.<br><div class="im HOEnZb">--<br>
Johny Mattsson<br>
Senior Software Engineer<br><br>
</div>
<div class="HOEnZb"><div class="h5">DiUS Computing Pty. Ltd.<br>
where ideas are engineered<br>
</div></div>
</blockquote>
</div>
<br><br clear="all"><br>-- <br>Kaustav Das,<div>M.Tech Student,</div>
<div>Department of CSE,</div>
<div>IIT Bombay</div>
<br>
</div>
kaustav das | 1 May 07:35 2012
Picon

Re: Stopping Radio Activity

Before flash writing I am requesting for the SPI resource but it not granted. How to overcome this situation?

On Tue, May 1, 2012 at 10:33 AM, kaustav das <kaustavdas1989 <at> gmail.com> wrote:
When I am calling the function for acquiring SPI resource for flash writing the radio stops receiving packets. I am not understanding what is happening?


On Tue, May 1, 2012 at 5:24 AM, Johny Mattsson <jmattsson <at> dius.com.au> wrote:
On 30 April 2012 13:04, kaustav das <kaustavdas1989 <at> gmail.com> wrote:
> Thanks. I have tried with resource arbitration by giving exclusive access of
> SPI for flash writing. But that didn't work.

The idea is that thanks to resource arbitration you don't need to
worry about exclusivity - the arbiter grants exclusive access in
sequence, ensuring there are no conflicts. If for some reason (I can't
see why though) you need to not have anyone else even request bus
access while you're doing your flash I/O, then you'll need to stop
those components.


Regards,
/Johny

PS. It's good to keep the list cc'd for archival purposes, plus it
gives others a chance to contribute further information.
--
Johny Mattsson
Senior Software Engineer

DiUS Computing Pty. Ltd.
where ideas are engineered



--
Kaustav Das,
M.Tech Student,
Department of CSE,
IIT Bombay




--
Kaustav Das,
M.Tech Student,
Department of CSE,
IIT Bombay

<div>
<p>Before flash writing I am requesting for the SPI resource but it not granted. How to overcome this situation?<br><br></p>
<div class="gmail_quote">On Tue, May 1, 2012 at 10:33 AM, kaustav das <span dir="ltr">&lt;<a href="mailto:kaustavdas1989 <at> gmail.com" target="_blank">kaustavdas1989 <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">When I am calling the function for acquiring SPI resource for flash writing the radio stops receiving packets. I am not understanding what is happening?<div class="HOEnZb">
<div class="h5">
<br><br><div class="gmail_quote">On Tue, May 1, 2012 at 5:24 AM, Johny Mattsson <span dir="ltr">&lt;<a href="mailto:jmattsson <at> dius.com.au" target="_blank">jmattsson <at> dius.com.au</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div>On 30 April 2012 13:04, kaustav das &lt;<a href="mailto:kaustavdas1989 <at> gmail.com" target="_blank">kaustavdas1989 <at> gmail.com</a>&gt; wrote:<br>

&gt; Thanks. I have tried with resource arbitration by giving exclusive access of<br>
&gt; SPI for flash writing. But that didn't work.<br><br>
</div>The idea is that thanks to resource arbitration you don't need to<br>
worry about exclusivity - the arbiter grants exclusive access in<br>
sequence, ensuring there are no conflicts. If for some reason (I can't<br>
see why though) you need to not have anyone else even request bus<br>
access while you're doing your flash I/O, then you'll need to stop<br>
those components.<br><br><br>
Regards,<br>
/Johny<br><br>
PS. It's good to keep the list cc'd for archival purposes, plus it<br>
gives others a chance to contribute further information.<br><div>--<br>
Johny Mattsson<br>
Senior Software Engineer<br><br>
</div>
<div><div>DiUS Computing Pty. Ltd.<br>
where ideas are engineered<br>
</div></div>
</blockquote>
</div>
<br><br clear="all"><br>
</div>
</div>
<div class="HOEnZb"><div class="h5">-- <br>Kaustav Das,<div>M.Tech Student,</div>
<div>Department of CSE,</div>
<div>IIT Bombay</div>
<br>
</div></div>
</blockquote>
</div>
<br><br clear="all"><br>-- <br>Kaustav Das,<div>M.Tech Student,</div>
<div>Department of CSE,</div>
<div>IIT Bombay</div>
<br>
</div>
pavel somavat | 1 May 13:05 2012

Starting documentation for MicaZ and MTS400


Hi everyone

I am absolutely new to the field and wish to work with MicaZ and MTS400 components available in the lab. I tried to look for kind of "Getting started" documentation but could not identify latest and up to the point information. It will be nice if any one can guide me finding the soft copies of the relevant documentation and recommendations regarding getting started.

Thanks in advance.

Somavat  


Follow Rediff Deal ho jaye! to get exciting offers in your city everyday.
<div>
<br>Hi everyone<div><br></div>
<div>I am absolutely new to the field and wish to work with MicaZ and MTS400 components available in the lab. I tried to look for kind of "Getting started" documentation but could not identify latest and up to the point information. It will be nice if any one can guide me finding the soft copies of the relevant documentation and recommendations regarding getting started.</div>
<div><br></div>
<div>Thanks in advance.</div>
<div><br></div>
<div>Somavat &nbsp;</div>
<br><a href="http://sigads.rediff.com/RealMedia/ads/click_nx.ads/www.rediffmail.com/signatureline.htm <at> Middle?" target="_blank"></a><br><table width="578" border="0" cellspacing="0" cellpadding="0"><tr><td><span>Follow&nbsp;<span><a href="http://track.rediff.com/click?url=___http://dealhojaye.rediff.com?sc_cid=rediffmailsignature___&amp;cmp=signature&amp;lnk=rediffmailsignature&amp;newservice=deals" target="_blank">Rediff Deal ho jaye!</a></span>&nbsp;to get exciting offers in your city everyday.</span></td></tr></table>
</div>
SURA ALI | 1 May 15:47 2012
Picon

Re: help


Da: SURA ALI <suib200684 <at> yahoo.com>
A: "tinyos-help <at> millennium.berkeley.edu" <tinyos-help <at> millennium.berkeley.edu>
Inviato: Lunedì 30 Aprile 2012 10:09
Oggetto:

I have a project, use 7 Sensor and place one of them is required to set a defined place the sensor using Dissemination,direct , collection by RSSI,
Code the needy, and how they can access applicationsRSSI inside tinyos


<div><div>
<div><span></span></div>
<div><br></div>  <div> <div> <div dir="ltr">  <span>Da:</span> SURA ALI &lt;suib200684 <at> yahoo.com&gt;<br><span>A:</span> "tinyos-help <at> millennium.berkeley.edu" &lt;tinyos-help <at> millennium.berkeley.edu&gt; <br><span>Inviato:</span> Luned&igrave; 30 Aprile 2012 10:09<br><span>Oggetto:</span> <br> </div> <br><div><div><div>
<span class="yiv119663588" lang="en"><span class="yiv119663588hps">I have a</span> <span class="yiv119663588hps">project</span><span>, use</span> <span class="yiv119663588hps">7</span> <span class="yiv119663588hps">Sensor</span> <span class="yiv119663588hps">and</span> <span class="yiv119663588hps">place</span> <span class="yiv119663588hps">one of them</span> <span class="yiv119663588hps">is</span> <span class="yiv119663588hps">required to</span> <span class="yiv119663588hps">set a</span> <span class="yiv119663588hps">defined</span> <span class="yiv119663588hps">place</span> <span class="yiv119663588hps">the</span> <span class="yiv119663588hps">sensor</span> <span class="yiv119663588hps">using</span> <span class="yiv119663588hps">Dissemination</span><span>,direct , collection by
 RSSI,<br></span></span><span class="yiv119663588" lang="en"><span class="yiv119663588hps yiv119663588alt-edited">Code</span> <span class="yiv119663588hps">the</span> <span class="yiv119663588hps">needy</span><span>,</span> <span class="yiv119663588hps">and how they</span> <span class="yiv119663588hps">can
 access</span> <span class="yiv119663588hps">applicationsRSSI inside tinyos</span></span>
</div></div></div>
<br><br>
</div> </div>  </div></div>
Michael Schippling | 1 May 18:44 2012

Re: Config ADC for Mica2 (Urgent Please help)

I'm going to assume that you mean "receiving an analog signal"...

Look at the code for the light or temp modules. It will take a
little digging but you should be able to get down to the raw
ADC level. Then copy it, probably all you need to do is change
the ADC channel used.

MS

Hasib1 wrote:
> Dear all, 
> 
> I want to configure a ADC channel for sending analog signal. My temperature
> and light sensor is working. now i want to connect an analog signal of
> voltage level 0-3 V to any one of the ADC port provided in MDA100. I am
> using MIB520 as Base station. If any one can help e in configuring that i
> would be really really grateful.
> 
> I have not used this before so ay help would be of great value. 
> 
> Regards,
> 
> Hasib   
Xiaohui Liu | 1 May 21:48 2012
Picon

will packets with CCA disabled backoff if channel is busy?

Hi,


The following snippet is from CC2420TransmitP:

  call CSN.clr();
  status = m_cca ? call STXONCCA.strobe() : call STXON.strobe();
  if ( !( status & CC2420_STATUS_TX_ACTIVE ) ) {
    status = call SNOP.strobe();
    if ( status & CC2420_STATUS_TX_ACTIVE ) {
      congestion = FALSE;
    }
  }

  m_state = congestion ? S_SAMPLE_CCA : S_SFD;
  call CSN.set();
}

if ( congestion ) {
  totalCcaChecks = 0;
  releaseSpiResource();
  congestionBackoff();
} else {
  call BackoffTimer.start(CC2420_ABORT_PERIOD);
}

I understand call STXONCCA.strobe() will not send the packet if channel is busy. Will call STXON.strobe() always return CC2420_STATUS_TX_ACTIVE and send the packet regardless of the channel state? If no, under what condition can this happen? Thanks for your attention.

--
-Xiaohui Liu
<div>
<p>Hi,</p>
<div><br></div>
<div>The following snippet is from CC2420TransmitP:</div>
<div><br></div>
<div>
<div>&nbsp; call CSN.clr();</div>
<div>&nbsp; status = m_cca ? call STXONCCA.strobe() : call STXON.strobe();</div>
<div>&nbsp; if ( !( status &amp; CC2420_STATUS_TX_ACTIVE ) ) {</div>
<div>&nbsp; &nbsp; status = call SNOP.strobe();</div>
<div>&nbsp; &nbsp; if ( status &amp; CC2420_STATUS_TX_ACTIVE ) {</div>
<div>&nbsp; &nbsp; &nbsp; congestion = FALSE;</div>
<div>&nbsp; &nbsp; }</div>
<div>
&nbsp; }</div>
<div><br></div>
<div>&nbsp; m_state = congestion ? S_SAMPLE_CCA : S_SFD;</div>
<div>&nbsp; call CSN.set();</div>
<div>}</div>
<div><br></div>
<div>if ( congestion ) {</div>
<div>&nbsp; totalCcaChecks = 0;</div>
<div>&nbsp; releaseSpiResource();</div>
<div>&nbsp; congestionBackoff();</div>
<div>} else {</div>
<div>&nbsp; call BackoffTimer.start(CC2420_ABORT_PERIOD);</div>
<div>}</div>
<div><br></div>
<div>I understand&nbsp;call STXONCCA.strobe() will not send the packet if channel is busy.&nbsp;Will&nbsp;<span>call STXON.strobe()&nbsp;</span>always return&nbsp;CC2420_STATUS_TX_ACTIVE and send the packet regardless of the channel state? If no, under what condition can this happen? Thanks for your attention.</div>
<div><br></div>-- <br>-Xiaohui Liu<br>
</div>
</div>
SURA ALI | 1 May 22:23 2012
Picon

Re: Tinyos-help Digest, Vol 109, Issue 1

Link, who arrived to help does not contain any words not understood

Da: "tinyos-help-request <at> millennium.berkeley.edu" <tinyos-help-request <at> millennium.berkeley.edu>
A: tinyos-help <at> millennium.berkeley.edu
Inviato: Martedì 1 Maggio 2012 12:00
Oggetto: Tinyos-help Digest, Vol 109, Issue 1

Send Tinyos-help mailing list submissions to
    tinyos-help <at> millennium.berkeley.edu

To subscribe or unsubscribe via the World Wide Web, visit
    https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

or, via email, send a message with subject or body 'help' to
    tinyos-help-request <at> millennium.berkeley.edu

You can reach the person managing the list at
    tinyos-help-owner <at> millennium.berkeley.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Tinyos-help digest..."


Today's Topics:

  1. Re: Stopping Radio Activity (kaustav das)
  2. Re: Stopping Radio Activity (kaustav das)
  3. Starting documentation for MicaZ and MTS400 (pavel  somavat)
  4. Re: help (SURA ALI)
  5. Re: Config ADC for Mica2 (Urgent Please help) (Michael Schippling)


----------------------------------------------------------------------

Message: 1
Date: Tue, 1 May 2012 10:33:22 +0530
From: kaustav das <kaustavdas1989 <at> gmail.com>
Subject: Re: [Tinyos-help] Stopping Radio Activity
To: Johny Mattsson <jmattsson <at> dius.com.au>
Cc: Tinyos-help <at> millennium.berkeley.edu
Message-ID:
    <CABrgOvwmykkwa5mBnNFo_Hu+Ee1J3oVXWio1zNKgjmE9Jdx4LQ <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

When I am calling the function for acquiring SPI resource for flash writing
the radio stops receiving packets. I am not understanding what is happening?

On Tue, May 1, 2012 at 5:24 AM, Johny Mattsson <jmattsson <at> dius.com.au>wrote:

> On 30 April 2012 13:04, kaustav das <kaustavdas1989 <at> gmail.com> wrote:
> > Thanks. I have tried with resource arbitration by giving exclusive
> access of
> > SPI for flash writing. But that didn't work.
>
> The idea is that thanks to resource arbitration you don't need to
> worry about exclusivity - the arbiter grants exclusive access in
> sequence, ensuring there are no conflicts. If for some reason (I can't
> see why though) you need to not have anyone else even request bus
> access while you're doing your flash I/O, then you'll need to stop
> those components.
>
>
> Regards,
> /Johny
>
> PS. It's good to keep the list cc'd for archival purposes, plus it
> gives others a chance to contribute further information.
> --
> Johny Mattsson
> Senior Software Engineer
>
> DiUS Computing Pty. Ltd.
> where ideas are engineered
>



--
Kaustav Das,
M.Tech Student,
Department of CSE,
IIT Bombay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/2307c4cd/attachment-0001.htm

------------------------------

Message: 2
Date: Tue, 1 May 2012 11:05:43 +0530
From: kaustav das <kaustavdas1989 <at> gmail.com>
Subject: Re: [Tinyos-help] Stopping Radio Activity
To: Johny Mattsson <jmattsson <at> dius.com.au>
Cc: Tinyos-help <at> millennium.berkeley.edu
Message-ID:
    <CABrgOvx6QAPB1N3f6=dG5PPiTToDovTyG0vwfieFN3x_kx8eyA <at> mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

Before flash writing I am requesting for the SPI resource but it not
granted. How to overcome this situation?

On Tue, May 1, 2012 at 10:33 AM, kaustav das <kaustavdas1989 <at> gmail.com>wrote:

> When I am calling the function for acquiring SPI resource for flash
> writing the radio stops receiving packets. I am not understanding what is
> happening?
>
>
> On Tue, May 1, 2012 at 5:24 AM, Johny Mattsson <jmattsson <at> dius.com.au>wrote:
>
>> On 30 April 2012 13:04, kaustav das <kaustavdas1989 <at> gmail.com> wrote:
>> > Thanks. I have tried with resource arbitration by giving exclusive
>> access of
>> > SPI for flash writing. But that didn't work.
>>
>> The idea is that thanks to resource arbitration you don't need to
>> worry about exclusivity - the arbiter grants exclusive access in
>> sequence, ensuring there are no conflicts. If for some reason (I can't
>> see why though) you need to not have anyone else even request bus
>> access while you're doing your flash I/O, then you'll need to stop
>> those components.
>>
>>
>> Regards,
>> /Johny
>>
>> PS. It's good to keep the list cc'd for archival purposes, plus it
>> gives others a chance to contribute further information.
>> --
>> Johny Mattsson
>> Senior Software Engineer
>>
>> DiUS Computing Pty. Ltd.
>> where ideas are engineered
>>
>
>
>
> --
> Kaustav Das,
> M.Tech Student,
> Department of CSE,
> IIT Bombay
>
>


--
Kaustav Das,
M.Tech Student,
Department of CSE,
IIT Bombay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/72a2564d/attachment-0001.htm

------------------------------

Message: 3
Date: 1 May 2012 11:05:58 -0000
From: "pavel  somavat" <pavelsomavat <at> rediffmail.com>
Subject: [Tinyos-help] Starting documentation for MicaZ and MTS400
To: "tinyos-help <at> millennium.berkeley.edu"
    <tinyos-help <at> millennium.berkeley.edu>
Message-ID: <20120501110558.10367.qmail <at> f4mail-235-90.rediffmail.com>
Content-Type: text/plain; charset="utf-8"


Hi everyone
I am absolutely new to the field and wish to work with MicaZ and MTS400 components available in the lab. I tried to look for kind of "Getting started" documentation but could not identify latest and up to the point information. It will be nice if any one can guide me finding the soft copies of the relevant documentation and recommendations regarding getting started.
Thanks in advance.
Somavat &nbsp;
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/5eb80e38/attachment-0001.htm

------------------------------

Message: 4
Date: Tue, 1 May 2012 14:47:39 +0100 (BST)
From: SURA ALI <suib200684 <at> yahoo.com>
Subject: Re: [Tinyos-help] help
To: "tinyos-help <at> millennium.berkeley.edu"
    <tinyos-help <at> millennium.berkeley.edu>
Message-ID:
    <1335880059.59496.YahooMailNeo <at> web29504.mail.ird.yahoo.com>
Content-Type: text/plain; charset="iso-8859-1"





________________________________
Da: SURA ALI <suib200684 <at> yahoo.com>
A: "tinyos-help <at> millennium.berkeley.edu" <tinyos-help <at> millennium.berkeley.edu>
Inviato: Luned? 30 Aprile 2012 10:09
Oggetto:


I have a project, use 7 Sensor and place one of them is required to set a defined place the sensor using Dissemination,direct , collection by RSSI,
Code the needy, and how they can access applicationsRSSI inside tinyos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/2943d0f0/attachment-0001.htm

------------------------------

Message: 5
Date: Tue, 01 May 2012 10:44:30 -0600
From: Michael Schippling <schip <at> santafe.edu>
Subject: Re: [Tinyos-help] Config ADC for Mica2 (Urgent Please help)
To: Hasib1 <ahnion <at> hotmail.com>
Cc: tinyos-help <at> millennium.berkeley.edu
Message-ID: <4FA012EE.7090906 <at> santafe.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I'm going to assume that you mean "receiving an analog signal"...

Look at the code for the light or temp modules. It will take a
little digging but you should be able to get down to the raw
ADC level. Then copy it, probably all you need to do is change
the ADC channel used.

MS

Hasib1 wrote:
> Dear all,
>
> I want to configure a ADC channel for sending analog signal. My temperature
> and light sensor is working. now i want to connect an analog signal of
> voltage level 0-3 V to any one of the ADC port provided in MDA100. I am
> using MIB520 as Base station. If any one can help e in configuring that i
> would be really really grateful.
>
> I have not used this before so ay help would be of great value.
>
> Regards,
>
> Hasib 


------------------------------

_______________________________________________
Tinyos-help mailing list
Tinyos-help <at> millennium.berkeley.edu
https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

End of Tinyos-help Digest, Vol 109, Issue 1
*******************************************


<div><div>
<span class="" lang="en"><span class="hps">Link</span><span class="">, who arrived</span> <span class="hps">to</span> <span class="hps">help</span> <span class="hps">does not contain</span> <span class="hps">any</span> <span class="hps">words</span> <span class="hps">not understood</span></span><div><br></div>  <div> <div> <div dir="ltr">  <span>Da:</span> "tinyos-help-request <at> millennium.berkeley.edu" &lt;tinyos-help-request <at> millennium.berkeley.edu&gt;<br><span>A:</span> tinyos-help <at> millennium.berkeley.edu <br><span>Inviato:</span> Marted&igrave; 1 Maggio 2012 12:00<br><span>Oggetto:</span> Tinyos-help Digest, Vol 109, Issue 1<br> </div> <br>Send Tinyos-help mailing list submissions to<br>&nbsp;&nbsp;&nbsp; <a ymailto="mailto:tinyos-help <at> millennium.berkeley.edu" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a><br><br>To subscribe or unsubscribe via the World Wide Web, visit<br>&nbsp;&nbsp;&nbsp; <a href="https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help" target="_blank">https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help</a><br><br>or, via email, send a message with subject or body 'help' to<br>&nbsp;&nbsp;&nbsp; <a ymailto="mailto:tinyos-help-request <at> millennium.berkeley.edu" href="mailto:tinyos-help-request <at> millennium.berkeley.edu">tinyos-help-request <at> millennium.berkeley.edu</a><br><br>You can reach the person managing the list
 at<br>&nbsp;&nbsp;&nbsp; <a ymailto="mailto:tinyos-help-owner <at> millennium.berkeley.edu" href="mailto:tinyos-help-owner <at> millennium.berkeley.edu">tinyos-help-owner <at> millennium.berkeley.edu</a><br><br>When replying, please edit your Subject line so it is more specific<br>than "Re: Contents of Tinyos-help digest..."<br><br><br>Today's Topics:<br><br>&nbsp;  1. Re: Stopping Radio Activity (kaustav das)<br>&nbsp;  2. Re: Stopping Radio Activity (kaustav das)<br>&nbsp;  3. Starting documentation for MicaZ and MTS400 (pavel&nbsp; somavat)<br>&nbsp;  4. Re: help (SURA ALI)<br>&nbsp;  5. Re: Config ADC for Mica2 (Urgent Please help) (Michael Schippling)<br><br><br>----------------------------------------------------------------------<br><br>Message: 1<br>Date: Tue, 1 May 2012 10:33:22 +0530<br>From: kaustav das &lt;<a ymailto="mailto:kaustavdas1989 <at> gmail.com" href="mailto:kaustavdas1989 <at> gmail.com">kaustavdas1989 <at> gmail.com</a>&gt;<br>Subject: Re: [Tinyos-help]
 Stopping Radio Activity<br>To: Johny Mattsson &lt;<a ymailto="mailto:jmattsson <at> dius.com.au" href="mailto:jmattsson <at> dius.com.au">jmattsson <at> dius.com.au</a>&gt;<br>Cc: <a ymailto="mailto:Tinyos-help <at> millennium.berkeley.edu" href="mailto:Tinyos-help <at> millennium.berkeley.edu">Tinyos-help <at> millennium.berkeley.edu</a><br>Message-ID:<br>&nbsp;&nbsp;&nbsp; &lt;CABrgOvwmykkwa5mBnNFo_Hu+<a ymailto="mailto:Ee1J3oVXWio1zNKgjmE9Jdx4LQ <at> mail.gmail.com" href="mailto:Ee1J3oVXWio1zNKgjmE9Jdx4LQ <at> mail.gmail.com">Ee1J3oVXWio1zNKgjmE9Jdx4LQ <at> mail.gmail.com</a>&gt;<br>Content-Type: text/plain; charset="iso-8859-1"<br><br>When I am calling the function for acquiring SPI resource for flash writing<br>the radio stops receiving packets. I am not understanding what is happening?<br><br>On Tue, May 1, 2012 at 5:24 AM, Johny Mattsson &lt;<a ymailto="mailto:jmattsson <at> dius.com.au" href="mailto:jmattsson <at> dius.com.au">jmattsson <at> dius.com.au</a>&gt;wrote:<br><br>&gt; On 30 April 2012 13:04,
 kaustav das &lt;<a ymailto="mailto:kaustavdas1989 <at> gmail.com" href="mailto:kaustavdas1989 <at> gmail.com">kaustavdas1989 <at> gmail.com</a>&gt; wrote:<br>&gt; &gt; Thanks. I have tried with resource arbitration by giving exclusive<br>&gt; access of<br>&gt; &gt; SPI for flash writing. But that didn't work.<br>&gt;<br>&gt; The idea is that thanks to resource arbitration you don't need to<br>&gt; worry about exclusivity - the arbiter grants exclusive access in<br>&gt; sequence, ensuring there are no conflicts. If for some reason (I can't<br>&gt; see why though) you need to not have anyone else even request bus<br>&gt; access while you're doing your flash I/O, then you'll need to stop<br>&gt; those components.<br>&gt;<br>&gt;<br>&gt; Regards,<br>&gt; /Johny<br>&gt;<br>&gt; PS. It's good to keep the list cc'd for archival purposes, plus it<br>&gt; gives others a chance to contribute further information.<br>&gt; --<br>&gt; Johny Mattsson<br>&gt; Senior Software
 Engineer<br>&gt;<br>&gt; DiUS Computing Pty. Ltd.<br>&gt; where ideas are engineered<br>&gt;<br><br><br><br>-- <br>Kaustav Das,<br>M.Tech Student,<br>Department of CSE,<br>IIT Bombay<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/2307c4cd/attachment-0001.htm" target="_blank">https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/2307c4cd/attachment-0001.htm</a> <br><br>------------------------------<br><br>Message: 2<br>Date: Tue, 1 May 2012 11:05:43 +0530<br>From: kaustav das &lt;<a ymailto="mailto:kaustavdas1989 <at> gmail.com" href="mailto:kaustavdas1989 <at> gmail.com">kaustavdas1989 <at> gmail.com</a>&gt;<br>Subject: Re: [Tinyos-help] Stopping Radio Activity<br>To: Johny Mattsson &lt;<a ymailto="mailto:jmattsson <at> dius.com.au" href="mailto:jmattsson <at> dius.com.au">jmattsson <at> dius.com.au</a>&gt;<br>Cc: <a ymailto="mailto:Tinyos-help <at> millennium.berkeley.edu" href="mailto:Tinyos-help <at> millennium.berkeley.edu">Tinyos-help <at> millennium.berkeley.edu</a><br>Message-ID:<br>&nbsp;&nbsp;&nbsp; &lt;CABrgOvx6QAPB1N3f6=<a ymailto="mailto:dG5PPiTToDovTyG0vwfieFN3x_kx8eyA <at> mail.gmail.com" href="mailto:dG5PPiTToDovTyG0vwfieFN3x_kx8eyA <at> mail.gmail.com">dG5PPiTToDovTyG0vwfieFN3x_kx8eyA <at> mail.gmail.com</a>&gt;<br>Content-Type: text/plain; charset="iso-8859-1"<br><br>Before flash writing I am requesting for the SPI resource but it not<br>granted. How to overcome this situation?<br><br>On Tue, May 1, 2012 at 10:33 AM, kaustav das &lt;<a ymailto="mailto:kaustavdas1989 <at> gmail.com" href="mailto:kaustavdas1989 <at> gmail.com">kaustavdas1989 <at> gmail.com</a>&gt;wrote:<br><br>&gt; When I am calling the function for acquiring SPI resource for flash<br>&gt; writing the radio stops receiving packets. I am not understanding what is<br>&gt; happening?<br>&gt;<br>&gt;<br>&gt; On Tue, May 1, 2012 at
 5:24 AM, Johny Mattsson &lt;<a ymailto="mailto:jmattsson <at> dius.com.au" href="mailto:jmattsson <at> dius.com.au">jmattsson <at> dius.com.au</a>&gt;wrote:<br>&gt;<br>&gt;&gt; On 30 April 2012 13:04, kaustav das &lt;<a ymailto="mailto:kaustavdas1989 <at> gmail.com" href="mailto:kaustavdas1989 <at> gmail.com">kaustavdas1989 <at> gmail.com</a>&gt; wrote:<br>&gt;&gt; &gt; Thanks. I have tried with resource arbitration by giving exclusive<br>&gt;&gt; access of<br>&gt;&gt; &gt; SPI for flash writing. But that didn't work.<br>&gt;&gt;<br>&gt;&gt; The idea is that thanks to resource arbitration you don't need to<br>&gt;&gt; worry about exclusivity - the arbiter grants exclusive access in<br>&gt;&gt; sequence, ensuring there are no conflicts. If for some reason (I can't<br>&gt;&gt; see why though) you need to not have anyone else even request bus<br>&gt;&gt; access while you're doing your flash I/O, then you'll need to stop<br>&gt;&gt; those components.<br>&gt;&gt;<br>&gt;&gt;<br>&gt;&gt;
 Regards,<br>&gt;&gt; /Johny<br>&gt;&gt;<br>&gt;&gt; PS. It's good to keep the list cc'd for archival purposes, plus it<br>&gt;&gt; gives others a chance to contribute further information.<br>&gt;&gt; --<br>&gt;&gt; Johny Mattsson<br>&gt;&gt; Senior Software Engineer<br>&gt;&gt;<br>&gt;&gt; DiUS Computing Pty. Ltd.<br>&gt;&gt; where ideas are engineered<br>&gt;&gt;<br>&gt;<br>&gt;<br>&gt;<br>&gt; --<br>&gt; Kaustav Das,<br>&gt; M.Tech Student,<br>&gt; Department of CSE,<br>&gt; IIT Bombay<br>&gt;<br>&gt;<br><br><br>-- <br>Kaustav Das,<br>M.Tech Student,<br>Department of CSE,<br>IIT Bombay<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/72a2564d/attachment-0001.htm" target="_blank">https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/72a2564d/attachment-0001.htm</a>
 <br><br>------------------------------<br><br>Message: 3<br>Date: 1 May 2012 11:05:58 -0000<br>From: "pavel&nbsp; somavat" &lt;<a ymailto="mailto:pavelsomavat <at> rediffmail.com" href="mailto:pavelsomavat <at> rediffmail.com">pavelsomavat <at> rediffmail.com</a>&gt;<br>Subject: [Tinyos-help] Starting documentation for MicaZ and MTS400<br>To: "<a ymailto="mailto:tinyos-help <at> millennium.berkeley.edu" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a>"<br>&nbsp;&nbsp;&nbsp; &lt;<a ymailto="mailto:tinyos-help <at> millennium.berkeley.edu" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a>&gt;<br>Message-ID: &lt;<a ymailto="mailto:20120501110558.10367.qmail <at> f4mail-235-90.rediffmail.com" href="mailto:20120501110558.10367.qmail <at> f4mail-235-90.rediffmail.com">20120501110558.10367.qmail <at> f4mail-235-90.rediffmail.com</a>&gt;<br>Content-Type: text/plain; charset="utf-8"<br><br><br>Hi everyone<br>I am
 absolutely new to the field and wish to work with MicaZ and MTS400 components available in the lab. I tried to look for kind of "Getting started" documentation but could not identify latest and up to the point information. It will be nice if any one can guide me finding the soft copies of the relevant documentation and recommendations regarding getting started.<br>Thanks in advance.<br>Somavat &amp;nbsp;<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/5eb80e38/attachment-0001.htm" target="_blank">https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/5eb80e38/attachment-0001.htm</a> <br><br>------------------------------<br><br>Message: 4<br>Date: Tue, 1 May 2012 14:47:39 +0100 (BST)<br>From: SURA ALI &lt;<a ymailto="mailto:suib200684 <at> yahoo.com" href="mailto:suib200684 <at> yahoo.com">suib200684 <at> yahoo.com</a>&gt;<br>Subject: Re: [Tinyos-help] help<br>To: "<a ymailto="mailto:tinyos-help <at> millennium.berkeley.edu" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a>"<br>&nbsp;&nbsp;&nbsp; &lt;<a ymailto="mailto:tinyos-help <at> millennium.berkeley.edu" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a>&gt;<br>Message-ID:<br>&nbsp;&nbsp;&nbsp; &lt;<a ymailto="mailto:1335880059.59496.YahooMailNeo <at> web29504.mail.ird.yahoo.com" href="mailto:1335880059.59496.YahooMailNeo <at> web29504.mail.ird.yahoo.com">1335880059.59496.YahooMailNeo <at> web29504.mail.ird.yahoo.com</a>&gt;<br>Content-Type: text/plain; charset="iso-8859-1"<br><br><br><br><br><br>________________________________<br> Da: SURA ALI &lt;<a ymailto="mailto:suib200684 <at> yahoo.com" href="mailto:suib200684 <at> yahoo.com">suib200684 <at> yahoo.com</a>&gt;<br>A: "<a ymailto="mailto:tinyos-help <at> millennium.berkeley.edu" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a>" &lt;<a ymailto="mailto:tinyos-help <at> millennium.berkeley.edu" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a>&gt; <br>Inviato: Luned? 30 Aprile 2012 10:09<br>Oggetto: <br><br><br>I have a project, use 7 Sensor and place one of them is required to set a defined place the sensor using Dissemination,direct , collection by RSSI,<br>Code the needy, and how they can access applicationsRSSI inside tinyos<br>-------------- next part --------------<br>An HTML attachment was scrubbed...<br>URL: <a href="https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/2943d0f0/attachment-0001.htm" target="_blank">https://www.millennium.berkeley.edu/pipermail/tinyos-help/attachments/20120501/2943d0f0/attachment-0001.htm</a>
 <br><br>------------------------------<br><br>Message: 5<br>Date: Tue, 01 May 2012 10:44:30 -0600<br>From: Michael Schippling &lt;<a ymailto="mailto:schip <at> santafe.edu" href="mailto:schip <at> santafe.edu">schip <at> santafe.edu</a>&gt;<br>Subject: Re: [Tinyos-help] Config ADC for Mica2 (Urgent Please help)<br>To: Hasib1 &lt;<a ymailto="mailto:ahnion <at> hotmail.com" href="mailto:ahnion <at> hotmail.com">ahnion <at> hotmail.com</a>&gt;<br>Cc: <a ymailto="mailto:tinyos-help <at> millennium.berkeley.edu" href="mailto:tinyos-help <at> millennium.berkeley.edu">tinyos-help <at> millennium.berkeley.edu</a><br>Message-ID: &lt;<a ymailto="mailto:4FA012EE.7090906 <at> santafe.edu" href="mailto:4FA012EE.7090906 <at> santafe.edu">4FA012EE.7090906 <at> santafe.edu</a>&gt;<br>Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br><br>I'm going to assume that you mean "receiving an analog signal"...<br><br>Look at the code for the light or temp modules. It will take a<br>little digging but you should be able to
 get down to the raw<br>ADC level. Then copy it, probably all you need to do is change<br>the ADC channel used.<br><br>MS<br><br>Hasib1 wrote:<br>&gt; Dear all, <br>&gt; <br>&gt; I want to configure a ADC channel for sending analog signal. My temperature<br>&gt; and light sensor is working. now i want to connect an analog signal of<br>&gt; voltage level 0-3 V to any one of the ADC port provided in MDA100. I am<br>&gt; using MIB520 as Base station. If any one can help e in configuring that i<br>&gt; would be really really grateful.<br>&gt; <br>&gt; I have not used this before so ay help would be of great value. <br>&gt; <br>&gt; Regards,<br>&gt; <br>&gt; Hasib&nbsp;  <br><br><br>------------------------------<br><br>_______________________________________________<br>Tinyos-help mailing list<br><a ymailto="mailto:Tinyos-help <at> millennium.berkeley.edu" href="mailto:Tinyos-help <at> millennium.berkeley.edu">Tinyos-help <at> millennium.berkeley.edu</a><br><a href="https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help" target="_blank">https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help</a><br><br>End of Tinyos-help Digest, Vol 109, Issue 1<br>*******************************************<br><br><br>
</div> </div>  </div></div>
gate 2012 | 1 May 06:12 2012
Picon

Multihop communication

Hello everyone, I am doing project on multihop communication and for that I am using "MultihopOscilloscope".  But I also want to print the route followed that is the id's of the mote through which packet is being forwarded to the base therefore I will be highly thankful for your assistance.
Thankyou.

<div><p>Hello everyone, I am doing project on multihop communication and for that I am using "MultihopOscilloscope".&nbsp; But I also want to print the route followed that is the id's of the mote through which packet is being forwarded to the base therefore I will be highly thankful for your assistance.<br>
Thankyou.<br></p></div>
Prateek G V | 1 May 20:06 2012
Picon

Tinyos on Ubuntu 12.04 Install

Hello Everyone,

I'm Prateek. I tried installing tinyos-2.1.1 on Ubuntu 12.04 and I'm facing some issues. Kindly help me rectify it.

Steps followed
1. Added the deb path http://tinyos.stanford.edu/tinyos/dists/ubuntu/ to the sources.list file
2. Did a sudo apt-get install tinyos-2.1.1
3. Installed it successfully.
4. Connected a telosb mote and did motelist. It detected the mote. No issues with this.
5. Went to the following directory /opt/tinyos-2.1.1/tos/lib/tosboot/ and executed "make micaz" - No problem with this.
6. In the same directory I executed the command "make telosb" - This is where I am facing the problem right now.

This is what the error looks like - Kindly help me fix it

mkdir -p build/telosb
    compiling TosBootC to a telosb binary
ncc -o build/telosb/main.exe  -Os -O -DNESC_BUILD_BINARY -mdisable-hwmul -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DTOSBOOT_START=0x4000 -DTOSBOOT_END=0x4a00 -Imsp430 -Imsp430f1611 -Istm25p -Itelosb -Ilib -I../net/Deluge -DIDENT_APPNAME=\"TosBootC\" -DIDENT_USERNAME=\"prateekgv\" -DIDENT_HOSTNAME=\"ssplablaptop\" -DIDENT_USERHASH=0xab3d9c1bL -DIDENT_TIMESTAMP=0x4fa022fdL -DIDENT_UIDHASH=0x0aefaf8bL  TosBootC.nc -lm
In file included from /opt/tinyos-2.1.1/tos/chips/msp430/msp430hardware.h:29,
                 from telosb/hardware.h:34,
                 from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41:
/usr/bin/../lib/gcc/msp430/4.5.3/../../../../msp430/include/io.h:153:2: warning: #warning "Unknown arch! Please check"
In file included from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41,
                 from /opt/tinyos-2.1.1/tos/system/TinySchedulerC.nc:40:
telosb/hardware.h: In function `TOSH_SET_PIN_DIRECTIONS':
telosb/hardware.h:67: `P3SEL' undeclared (first use in this function)
telosb/hardware.h:67: (Each undeclared identifier is reported only once
telosb/hardware.h:67: for each function it appears in.)
telosb/hardware.h:69: `P1DIR' undeclared (first use in this function)
telosb/hardware.h:70: `P1OUT' undeclared (first use in this function)
telosb/hardware.h:72: `P2DIR' undeclared (first use in this function)
telosb/hardware.h:73: `P2OUT' undeclared (first use in this function)
telosb/hardware.h:75: `P3DIR' undeclared (first use in this function)
telosb/hardware.h:76: `P3OUT' undeclared (first use in this function)
telosb/hardware.h:78: `P4DIR' undeclared (first use in this function)
telosb/hardware.h:79: `P4OUT' undeclared (first use in this function)
telosb/hardware.h:81: `P5DIR' undeclared (first use in this function)
telosb/hardware.h:82: `P5OUT' undeclared (first use in this function)
telosb/hardware.h:84: `P6DIR' undeclared (first use in this function)
telosb/hardware.h:85: `P6OUT' undeclared (first use in this function)
In file included from /opt/tinyos-2.1.1/tos/system/TinySchedulerC.nc:41:
In component `McuSleepC':
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc: In function `getPowerState':
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:69: `TACCTL0' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:69: `CCIE' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:70: `TACCTL1' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:71: `TACCTL2' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:72: `TACTL' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:72: `TASSEL_3' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:72: `TASSEL_2' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `ME1' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `UTXE0' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `URXE0' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `U0TCTL' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `SSEL1' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:74: `ME2' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:74: `UTXE1' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:74: `URXE1' undeclared (first use in this function)
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:74: `U1TCTL' undeclared (first use in this function)
In file included from stm25p/ExtFlashC.nc:43,
                 from TosBootC.nc:42:
In component `HplUsart0C':
msp430/HplUsart0C.nc: In function `HplUsartControl.disableSPI':
msp430/HplUsart0C.nc:41: `ME1' undeclared (first use in this function)
msp430/HplUsart0C.nc:42: `U0CTL' undeclared (first use in this function)
msp430/HplUsart0C.nc:43: `U0TCTL' undeclared (first use in this function)
msp430/HplUsart0C.nc:44: `U0RCTL' undeclared (first use in this function)
msp430/HplUsart0C.nc: In function `HplUsartControl.setModeSPI':
msp430/HplUsart0C.nc:52: `U0CTL' undeclared (first use in this function)
msp430/HplUsart0C.nc:52: `SWRST' undeclared (first use in this function)
msp430/HplUsart0C.nc:52: `CHAR' undeclared (first use in this function)
msp430/HplUsart0C.nc:52: `SYNC' undeclared (first use in this function)
msp430/HplUsart0C.nc:52: `MM' undeclared (first use in this function)
msp430/HplUsart0C.nc:55: `U0TCTL' undeclared (first use in this function)
msp430/HplUsart0C.nc:55: `STC' undeclared (first use in this function)
msp430/HplUsart0C.nc:55: `CKPH' undeclared (first use in this function)
msp430/HplUsart0C.nc:55: `SSEL_SMCLK' undeclared (first use in this function)
msp430/HplUsart0C.nc:58: `U0BR0' undeclared (first use in this function)
msp430/HplUsart0C.nc:59: `U0BR1' undeclared (first use in this function)
msp430/HplUsart0C.nc:62: `ME1' undeclared (first use in this function)
msp430/HplUsart0C.nc:62: `USPIE0' undeclared (first use in this function)
msp430/HplUsart0C.nc:67: `IFG1' undeclared (first use in this function)
msp430/HplUsart0C.nc: In function `HplUsartControl.disableI2C':
msp430/HplUsart0C.nc:77: `U0CTL' undeclared (first use in this function)
msp430/HplUsart0C.nc:77: `I2CEN' undeclared (first use in this function)
msp430/HplUsart0C.nc:78: `I2C' undeclared (first use in this function)
msp430/HplUsart0C.nc:79: `I2CTCTL' undeclared (first use in this function)
msp430/HplUsart0C.nc: In function `HplUsartControl.setModeI2C':
msp430/HplUsart0C.nc:86: `U0CTL' undeclared (first use in this function)
msp430/HplUsart0C.nc:86: `I2C' undeclared (first use in this function)
msp430/HplUsart0C.nc:86: `SYNC' undeclared (first use in this function)
msp430/HplUsart0C.nc:86: `MST' undeclared (first use in this function)
msp430/HplUsart0C.nc:89: `I2CTCTL' undeclared (first use in this function)
msp430/HplUsart0C.nc:89: `I2CSSEL_2' undeclared (first use in this function)
msp430/HplUsart0C.nc:89: `I2CTRX' undeclared (first use in this function)
msp430/HplUsart0C.nc:92: `I2CEN' undeclared (first use in this function)
msp430/HplUsart0C.nc: In function `HplUsartControl.isTxEmpty':
msp430/HplUsart0C.nc:98: `U0TCTL' undeclared (first use in this function)
msp430/HplUsart0C.nc:98: `TXEPT' undeclared (first use in this function)
msp430/HplUsart0C.nc: In function `HplUsartControl.isTxIntrPending':
msp430/HplUsart0C.nc:105: `IFG1' undeclared (first use in this function)
msp430/HplUsart0C.nc:105: `UTXIFG0' undeclared (first use in this function)
msp430/HplUsart0C.nc: In function `HplUsartControl.isRxIntrPending':
msp430/HplUsart0C.nc:113: `IFG1' undeclared (first use in this function)
msp430/HplUsart0C.nc:113: `URXIFG0' undeclared (first use in this function)
msp430/HplUsart0C.nc: In function `HplUsartControl.tx':
msp430/HplUsart0C.nc:121: `U0TXBUF' undeclared (first use in this function)
msp430/HplUsart0C.nc: In function `HplUsartControl.rx':
msp430/HplUsart0C.nc:125: `U0RXBUF' undeclared (first use in this function)
In file included from TosBootC.nc:43:
In component `HardwareC':
msp430/HardwareC.nc: In function `Hardware.init':
msp430/HardwareC.nc:40: `BCSCTL1' undeclared (first use in this function)
msp430/HardwareC.nc:40: `RSEL0' undeclared (first use in this function)
msp430/HardwareC.nc:40: `RSEL1' undeclared (first use in this function)
msp430/HardwareC.nc:40: `RSEL2' undeclared (first use in this function)
msp430/HardwareC.nc:40: `XT2OFF' undeclared (first use in this function)
msp430/HardwareC.nc:41: `DCOCTL' undeclared (first use in this function)
msp430/HardwareC.nc:41: `DCO0' undeclared (first use in this function)
msp430/HardwareC.nc:41: `DCO1' undeclared (first use in this function)
msp430/HardwareC.nc:41: `DCO2' undeclared (first use in this function)
msp430/HardwareC.nc: In function `Hardware.reboot':
msp430/HardwareC.nc:45: `WDTCTL' undeclared (first use in this function)
In file included from TosBootC.nc:44:
In component `InternalFlashC':
msp430/InternalFlashC.nc: In function `InternalFlash.write':
msp430/InternalFlashC.nc:84: `FCTL2' undeclared (first use in this function)
msp430/InternalFlashC.nc:84: `FWKEY' undeclared (first use in this function)
msp430/InternalFlashC.nc:84: `FSSEL1' undeclared (first use in this function)
msp430/InternalFlashC.nc:84: `FN2' undeclared (first use in this function)
msp430/InternalFlashC.nc:85: `FCTL3' undeclared (first use in this function)
msp430/InternalFlashC.nc:86: `FCTL1' undeclared (first use in this function)
msp430/InternalFlashC.nc:86: `ERASE' undeclared (first use in this function)
msp430/InternalFlashC.nc:88: `WRT' undeclared (first use in this function)
msp430/InternalFlashC.nc:102: `LOCK' undeclared (first use in this function)
In file included from TosBootC.nc:47:
In component `ProgFlashC':
msp430/ProgFlashC.nc: In function `ProgFlash.write':
msp430/ProgFlashC.nc:52: `FCTL2' undeclared (first use in this function)
msp430/ProgFlashC.nc:52: `FWKEY' undeclared (first use in this function)
msp430/ProgFlashC.nc:52: `FSSEL1' undeclared (first use in this function)
msp430/ProgFlashC.nc:52: `FN2' undeclared (first use in this function)
msp430/ProgFlashC.nc:53: `FCTL3' undeclared (first use in this function)
msp430/ProgFlashC.nc:54: `FCTL1' undeclared (first use in this function)
msp430/ProgFlashC.nc:54: `ERASE' undeclared (first use in this function)
msp430/ProgFlashC.nc:56: `WRT' undeclared (first use in this function)
msp430/ProgFlashC.nc:64: `LOCK' undeclared (first use in this function)
In file included from TosBootC.nc:48:
In component `VoltageC':
msp430/VoltageC.nc: In function `Voltage.okToProgram':
msp430/VoltageC.nc:48: `ADC12CTL0' undeclared (first use in this function)
msp430/VoltageC.nc:48: `ADC12ON' undeclared (first use in this function)
msp430/VoltageC.nc:48: `SHT0_2' undeclared (first use in this function)
msp430/VoltageC.nc:48: `REFON' undeclared (first use in this function)
msp430/VoltageC.nc:50: `ADC12CTL1' undeclared (first use in this function)
msp430/VoltageC.nc:50: `SHP' undeclared (first use in this function)
msp430/VoltageC.nc:52: `ADC12MCTL0' undeclared (first use in this function)
msp430/VoltageC.nc:52: `EOS' undeclared (first use in this function)
msp430/VoltageC.nc:52: `SREF_1' undeclared (first use in this function)
msp430/VoltageC.nc:52: `INCH_11' undeclared (first use in this function)
msp430/VoltageC.nc:57: `ENC' undeclared (first use in this function)
msp430/VoltageC.nc:59: `ADC12SC' undeclared (first use in this function)
msp430/VoltageC.nc:61: `ADC12IFG' undeclared (first use in this function)
msp430/VoltageC.nc:61: `BIT0' undeclared (first use in this function)
msp430/VoltageC.nc:68: `ADC12MEM0' undeclared (first use in this function)
make: *** [exe0] Error 1

<div><p>Hello Everyone,<br><br>I'm Prateek. I tried installing tinyos-2.1.1 on Ubuntu 12.04 and I'm facing some issues. Kindly help me rectify it.<br><br>Steps followed<br>1. Added the deb path <a href="http://tinyos.stanford.edu/tinyos/dists/ubuntu/">http://tinyos.stanford.edu/tinyos/dists/ubuntu/</a> to the sources.list file<br>
2. Did a sudo apt-get install tinyos-2.1.1<br>3. Installed it successfully.<br>4. Connected a telosb mote and did motelist. It detected the mote. No issues with this.<br>5. Went to the following directory /opt/tinyos-2.1.1/tos/lib/tosboot/ and executed "make micaz" - No problem with this.<br>
6. In the same directory I executed the command "make telosb" - This is where I am facing the problem right now.<br><br>This is what the error looks like - Kindly help me fix it<br><br>mkdir -p build/telosb<br>
&nbsp;&nbsp;&nbsp; compiling TosBootC to a telosb binary<br>ncc -o build/telosb/main.exe&nbsp; -Os -O -DNESC_BUILD_BINARY -mdisable-hwmul -fnesc-separator=__ -Wall -Wshadow -Wnesc-all -target=telosb -fnesc-cfile=build/telosb/app.c -board= -DDEFINED_TOS_AM_GROUP=0x22 -DTOSBOOT_START=0x4000 -DTOSBOOT_END=0x4a00 -Imsp430 -Imsp430f1611 -Istm25p -Itelosb -Ilib -I../net/Deluge -DIDENT_APPNAME=\"TosBootC\" -DIDENT_USERNAME=\"prateekgv\" -DIDENT_HOSTNAME=\"ssplablaptop\" -DIDENT_USERHASH=0xab3d9c1bL -DIDENT_TIMESTAMP=0x4fa022fdL -DIDENT_UIDHASH=0x0aefaf8bL&nbsp; TosBootC.nc -lm <br>
In file included from /opt/tinyos-2.1.1/tos/chips/msp430/msp430hardware.h:29,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from telosb/hardware.h:34,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41:<br>/usr/bin/../lib/gcc/msp430/4.5.3/../../../../msp430/include/io.h:153:2: warning: #warning "Unknown arch! Please check"<br>
In file included from /opt/tinyos-2.1.1/tos/system/SchedulerBasicP.nc:41,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from /opt/tinyos-2.1.1/tos/system/TinySchedulerC.nc:40:<br>telosb/hardware.h: In function `TOSH_SET_PIN_DIRECTIONS':<br>telosb/hardware.h:67: `P3SEL' undeclared (first use in this function)<br>
telosb/hardware.h:67: (Each undeclared identifier is reported only once<br>telosb/hardware.h:67: for each function it appears in.)<br>telosb/hardware.h:69: `P1DIR' undeclared (first use in this function)<br>telosb/hardware.h:70: `P1OUT' undeclared (first use in this function)<br>
telosb/hardware.h:72: `P2DIR' undeclared (first use in this function)<br>telosb/hardware.h:73: `P2OUT' undeclared (first use in this function)<br>telosb/hardware.h:75: `P3DIR' undeclared (first use in this function)<br>
telosb/hardware.h:76: `P3OUT' undeclared (first use in this function)<br>telosb/hardware.h:78: `P4DIR' undeclared (first use in this function)<br>telosb/hardware.h:79: `P4OUT' undeclared (first use in this function)<br>
telosb/hardware.h:81: `P5DIR' undeclared (first use in this function)<br>telosb/hardware.h:82: `P5OUT' undeclared (first use in this function)<br>telosb/hardware.h:84: `P6DIR' undeclared (first use in this function)<br>
telosb/hardware.h:85: `P6OUT' undeclared (first use in this function)<br>In file included from /opt/tinyos-2.1.1/tos/system/TinySchedulerC.nc:41:<br>In component `McuSleepC':<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc: In function `getPowerState':<br>
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:69: `TACCTL0' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:69: `CCIE' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:70: `TACCTL1' undeclared (first use in this function)<br>
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:71: `TACCTL2' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:72: `TACTL' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:72: `TASSEL_3' undeclared (first use in this function)<br>
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:72: `TASSEL_2' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `ME1' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `UTXE0' undeclared (first use in this function)<br>
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `URXE0' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `U0TCTL' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:73: `SSEL1' undeclared (first use in this function)<br>
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:74: `ME2' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:74: `UTXE1' undeclared (first use in this function)<br>/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:74: `URXE1' undeclared (first use in this function)<br>
/opt/tinyos-2.1.1/tos/chips/msp430/McuSleepC.nc:74: `U1TCTL' undeclared (first use in this function)<br>In file included from stm25p/ExtFlashC.nc:43,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; from TosBootC.nc:42:<br>In component `HplUsart0C':<br>
msp430/HplUsart0C.nc: In function `HplUsartControl.disableSPI':<br>msp430/HplUsart0C.nc:41: `ME1' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:42: `U0CTL' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:43: `U0TCTL' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:44: `U0RCTL' undeclared (first use in this function)<br>msp430/HplUsart0C.nc: In function `HplUsartControl.setModeSPI':<br>
msp430/HplUsart0C.nc:52: `U0CTL' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:52: `SWRST' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:52: `CHAR' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:52: `SYNC' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:52: `MM' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:55: `U0TCTL' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:55: `STC' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:55: `CKPH' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:55: `SSEL_SMCLK' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:58: `U0BR0' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:59: `U0BR1' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:62: `ME1' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:62: `USPIE0' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:67: `IFG1' undeclared (first use in this function)<br>msp430/HplUsart0C.nc: In function `HplUsartControl.disableI2C':<br>
msp430/HplUsart0C.nc:77: `U0CTL' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:77: `I2CEN' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:78: `I2C' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:79: `I2CTCTL' undeclared (first use in this function)<br>msp430/HplUsart0C.nc: In function `HplUsartControl.setModeI2C':<br>msp430/HplUsart0C.nc:86: `U0CTL' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:86: `I2C' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:86: `SYNC' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:86: `MST' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:89: `I2CTCTL' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:89: `I2CSSEL_2' undeclared (first use in this function)<br>msp430/HplUsart0C.nc:89: `I2CTRX' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:92: `I2CEN' undeclared (first use in this function)<br>msp430/HplUsart0C.nc: In function `HplUsartControl.isTxEmpty':<br>msp430/HplUsart0C.nc:98: `U0TCTL' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:98: `TXEPT' undeclared (first use in this function)<br>msp430/HplUsart0C.nc: In function `HplUsartControl.isTxIntrPending':<br>msp430/HplUsart0C.nc:105: `IFG1' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:105: `UTXIFG0' undeclared (first use in this function)<br>msp430/HplUsart0C.nc: In function `HplUsartControl.isRxIntrPending':<br>msp430/HplUsart0C.nc:113: `IFG1' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc:113: `URXIFG0' undeclared (first use in this function)<br>msp430/HplUsart0C.nc: In function `HplUsartControl.tx':<br>msp430/HplUsart0C.nc:121: `U0TXBUF' undeclared (first use in this function)<br>
msp430/HplUsart0C.nc: In function `HplUsartControl.rx':<br>msp430/HplUsart0C.nc:125: `U0RXBUF' undeclared (first use in this function)<br>In file included from TosBootC.nc:43:<br>In component `HardwareC':<br>msp430/HardwareC.nc: In function `Hardware.init':<br>
msp430/HardwareC.nc:40: `BCSCTL1' undeclared (first use in this function)<br>msp430/HardwareC.nc:40: `RSEL0' undeclared (first use in this function)<br>msp430/HardwareC.nc:40: `RSEL1' undeclared (first use in this function)<br>
msp430/HardwareC.nc:40: `RSEL2' undeclared (first use in this function)<br>msp430/HardwareC.nc:40: `XT2OFF' undeclared (first use in this function)<br>msp430/HardwareC.nc:41: `DCOCTL' undeclared (first use in this function)<br>
msp430/HardwareC.nc:41: `DCO0' undeclared (first use in this function)<br>msp430/HardwareC.nc:41: `DCO1' undeclared (first use in this function)<br>msp430/HardwareC.nc:41: `DCO2' undeclared (first use in this function)<br>
msp430/HardwareC.nc: In function `Hardware.reboot':<br>msp430/HardwareC.nc:45: `WDTCTL' undeclared (first use in this function)<br>In file included from TosBootC.nc:44:<br>In component `InternalFlashC':<br>msp430/InternalFlashC.nc: In function `InternalFlash.write':<br>
msp430/InternalFlashC.nc:84: `FCTL2' undeclared (first use in this function)<br>msp430/InternalFlashC.nc:84: `FWKEY' undeclared (first use in this function)<br>msp430/InternalFlashC.nc:84: `FSSEL1' undeclared (first use in this function)<br>
msp430/InternalFlashC.nc:84: `FN2' undeclared (first use in this function)<br>msp430/InternalFlashC.nc:85: `FCTL3' undeclared (first use in this function)<br>msp430/InternalFlashC.nc:86: `FCTL1' undeclared (first use in this function)<br>
msp430/InternalFlashC.nc:86: `ERASE' undeclared (first use in this function)<br>msp430/InternalFlashC.nc:88: `WRT' undeclared (first use in this function)<br>msp430/InternalFlashC.nc:102: `LOCK' undeclared (first use in this function)<br>
In file included from TosBootC.nc:47:<br>In component `ProgFlashC':<br>msp430/ProgFlashC.nc: In function `ProgFlash.write':<br>msp430/ProgFlashC.nc:52: `FCTL2' undeclared (first use in this function)<br>msp430/ProgFlashC.nc:52: `FWKEY' undeclared (first use in this function)<br>
msp430/ProgFlashC.nc:52: `FSSEL1' undeclared (first use in this function)<br>msp430/ProgFlashC.nc:52: `FN2' undeclared (first use in this function)<br>msp430/ProgFlashC.nc:53: `FCTL3' undeclared (first use in this function)<br>
msp430/ProgFlashC.nc:54: `FCTL1' undeclared (first use in this function)<br>msp430/ProgFlashC.nc:54: `ERASE' undeclared (first use in this function)<br>msp430/ProgFlashC.nc:56: `WRT' undeclared (first use in this function)<br>
msp430/ProgFlashC.nc:64: `LOCK' undeclared (first use in this function)<br>In file included from TosBootC.nc:48:<br>In component `VoltageC':<br>msp430/VoltageC.nc: In function `Voltage.okToProgram':<br>msp430/VoltageC.nc:48: `ADC12CTL0' undeclared (first use in this function)<br>
msp430/VoltageC.nc:48: `ADC12ON' undeclared (first use in this function)<br>msp430/VoltageC.nc:48: `SHT0_2' undeclared (first use in this function)<br>msp430/VoltageC.nc:48: `REFON' undeclared (first use in this function)<br>
msp430/VoltageC.nc:50: `ADC12CTL1' undeclared (first use in this function)<br>msp430/VoltageC.nc:50: `SHP' undeclared (first use in this function)<br>msp430/VoltageC.nc:52: `ADC12MCTL0' undeclared (first use in this function)<br>
msp430/VoltageC.nc:52: `EOS' undeclared (first use in this function)<br>msp430/VoltageC.nc:52: `SREF_1' undeclared (first use in this function)<br>msp430/VoltageC.nc:52: `INCH_11' undeclared (first use in this function)<br>
msp430/VoltageC.nc:57: `ENC' undeclared (first use in this function)<br>msp430/VoltageC.nc:59: `ADC12SC' undeclared (first use in this function)<br>msp430/VoltageC.nc:61: `ADC12IFG' undeclared (first use in this function)<br>
msp430/VoltageC.nc:61: `BIT0' undeclared (first use in this function)<br>msp430/VoltageC.nc:68: `ADC12MEM0' undeclared (first use in this function)<br>make: *** [exe0] Error 1<br><br></p></div>

Gmane