headers
TheMrOrange | 1 Sep 2010 01:53
Picon

modification of duty-cycle while sensing - LowPowerListening

Hi,

I've developed an application for Micaz using the blip stack and low  
power listening

LPL is configured as follow
sleep interval =1024
delay = 2048
retries = 2

I've probed and measured Amperes used by motes while working in single  
hop and I can see two different values for duty-cycle:
- When the MDA sensor-board is NOT connected, dutycycle=1% (10msec)
- When the MDA sensor-board is connected, dutycycle=10% (100msec)

Do you have any idea about the reason why dutycycle changes when  
sensors are red?
Anybody of you experienced modification of dutycycle for particular  
reasons?

Many thanks

Davide
Permalink | Reply | 0 comments |
headers
Davide Pusceddu @ CIT | 1 Sep 2010 01:45
Picon
Favicon

variation of duty-cycle in Low Power Listening while sensing

Hi,

I've developed an application for Micaz using the blip stack and low  
power listening
LPL is configured as follow
sleep interval =1024
delay = 2048
retries = 2

I've probed and measured Amperes used by motes while working in single  
hop and I can see two different values for duty-cycle:
When the MDA sensor-board is NOT connected, dutycycle=1% (10msec)
When the MDA sensor-board is connected, dutycycle=10% (100msec)

Do you have any idea about the reason why dutycycle changes when  
sensors are red?
Anybody of you experienced modification of dutycycle for particular  
reasons?

Many thanks

Davide
Permalink | Reply | 0 comments |
headers
Davide Pusceddu @ CIT | 1 Sep 2010 01:51
Picon
Favicon

variation of duty-cycle while sensing - Low Power Listening

Hi,

I've developed an application for Micaz using the blip stack and low  
power listening

LPL is configured as follow
sleep interval =1024
delay = 2048
retries = 2

I've probed and measured Amperes used by motes while working in single  
hop and I can see two different values for duty-cycle:
- When the MDA sensor-board is NOT connected, dutycycle=1% (10msec)
- When the MDA sensor-board is connected, dutycycle=10% (100msec)

Do you have any idea about the reason why dutycycle changes when  
sensors are red?
Anybody of you experienced modification of dutycycle for particular  
reasons?

Many thanks

Davide
Permalink | Reply | 0 comments |
headers
rupesh vishwakarma | 1 Sep 2010 15:59
Picon
Favicon

help in low power motes

Dear all,

Actually I am a new person in tiny Os field . I have to implement AODV protocol(for multihop ) as you described in your pdf file. some more things I also have to implement -

1. intermediate motes should be in sleep and wakeup at some time to see if there is any message?
2. source should synchronize all nodes with its clock.

for intermediate motes to be in sleep I have implemented like this

when I send a message to intermediate motes I call

  event void Boot.booted() {
  call LPL.setLocalWakeupInterval(2000);

    call AMControl.start();
  }

event void AMControl.startDone(error_t err) {
    if (err == SUCCESS)
 {

       counter++;
 call LPL.setRemoteWakeupInterval(&pkt, 2000);
    if (!busy) {
      BlinkToRadioMsg* btrpkt =
    (BlinkToRadioMsg*)(call Packet.getPayload(&pkt, sizeof(BlinkToRadioMsg)));
      if (btrpkt == NULL) {
    return;
      }
      btrpkt->nodeid = TOS_NODE_ID;
      btrpkt->counter = counter;
     call LPL.setRemoteWakeupInterval(&pkt, 2000);

      if (call AMSend.send(2,
          &pkt, sizeof(BlinkToRadioMsg)) == SUCCESS) {
        busy = TRUE;
      }
    }
 
}
    else {
      call AMControl.start();
    }
  }

does the above code set the remote nodes to wakeup after 2000ms?? or some other method has to be implemented

can you please suggest something regarding clock synchronization  between source and destination?

regards,

rupesh


<div>
<div>Dear all,<br><br>Actually I 
am a new person in tiny Os field . I have to implement AODV protocol(for
 multihop ) as you described in your pdf file. some more things I also 
have to implement -<br><br>
1. intermediate motes should be in sleep and wakeup at some time to see 
if there is any message?<br>
2. source should synchronize all nodes with its clock.<br><br>
for intermediate motes to be in sleep I have implemented like this <br><br>
when I send a message to intermediate motes I call<br><br>
&nbsp; event void Boot.booted() {<br>
&nbsp; call LPL.setLocalWakeupInterval(2000);<br><br>
&nbsp;&nbsp;&nbsp; call AMControl.start();<br>
&nbsp; }<br><br>
event void AMControl.startDone(error_t err) {<br>
&nbsp;&nbsp;&nbsp; if (err == SUCCESS)<br>
&nbsp;{<br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; counter++;<br><span>&nbsp;<span>call LPL.setRemoteWakeupInterval(&amp;pkt, 2000);</span></span><br>
&nbsp;&nbsp;&nbsp; if (!busy) {<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; BlinkToRadioMsg* btrpkt = <br>
&nbsp;&nbsp;&nbsp; (BlinkToRadioMsg*)(call Packet.getPayload(&amp;pkt, 
sizeof(BlinkToRadioMsg)));<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (btrpkt == NULL) {<br>
&nbsp;&nbsp;&nbsp; return;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; btrpkt-&gt;nodeid = TOS_NODE_ID;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; btrpkt-&gt;counter = counter;<br>
&nbsp;&nbsp;&nbsp;<span>&nbsp; call 
LPL.setRemoteWakeupInterval(&amp;pkt, 2000);</span><br><br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; if (call AMSend.send(2, <br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &amp;pkt, sizeof(BlinkToRadioMsg)) == SUCCESS) {<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; busy = TRUE;<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br>
&nbsp;&nbsp;&nbsp; }<br>
&nbsp; <br>
}<br>
&nbsp;&nbsp;&nbsp; else {<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; call AMControl.start();<br>
&nbsp;&nbsp;&nbsp; }<br>
&nbsp; }<br><br>
does the above code set the remote nodes to wakeup after 2000ms?? or 
some other method has to be implemented<br><br>
can you please suggest something regarding clock synchronization&nbsp; 
between source and destination?<br><br>regards,<br><br>
rupesh<br><br>
</div>
<br>
</div>
Permalink | Reply | 1 comment |
headers
Nirvesh Priyadarshi | 1 Sep 2010 18:27
Picon

I added you as a friend on Quepasa.com

xmlns="http://www.w3.org/1999/xhtml">

body { display: block !important; } Quepasa Alerts
Click here to unsubscribe.  


I’d like to be your friend on Quepasa.com.

Would you like to add me as a friend?


Yes No

Thanks!

Nirvesh Priyadarshi


To prevent from getting anymore email notifications from your friends on Quepasa.com, click here.
Unsubscribe I Terms of Use I Privacy Policy I Support
Quepasa Corporation 324 Datura Street, Suite 114, West Palm Beach, FL, 33401.
You are receiving this message because your friend is a registered member of Quepasa.
Add info <at> quepasa.com to your contact list so you always receive your Quepasa email. 
<div>

<p> xmlns="http://www.w3.org/1999/xhtml"&gt;</p>

body { display: block !important; }
Quepasa Alerts<table bgcolor="#f7f7f7" cellspacing="35" width="100%"><tr>
<td>
			<table align="center" border="0" cellpadding="0" cellspacing="0" width="620"><tr>
<td>
					<table bgcolor="#000000" border="0" cellpadding="0" cellspacing="0" height="28" width="622"><tr>
<td width="114"><a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1519.html?url=http://www.quepasa.com/en_US/?mail=tinyos-help <at> millennium.berkeley.edu" title="Quepasa.com"></a></td>
					    <td align="right" width="486">
					    	<a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1528.html?url=http%3A%2F%2Fwww.quepasa.com%2Fen_US%2Fuser%2FcancelQPAlerts.php%3Fsign%3De0c68577a5e194d6a6d5c6b9ec769988%26alert%3D4%26mail%3Dtinyos-help%40millennium.berkeley.edu%26id%3D-1">Click here</a> to unsubscribe.
					    </td>
					    <td width="22">&nbsp;</td>
					</tr></table>
<p> <br></p>
<p>I&rsquo;d like to be your friend on Quepasa.com.</p>
<p>Would you like to <a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1436.html?url=http://www.quepasa.com/qp/120291884.html&amp;mail=tinyos-help <at> millennium.berkeley.edu">add</a> me as a friend?</p>
<br><p>
<span><a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1439.html?url=http://www.quepasa.com/qp/120291884.html&amp;mail=tinyos-help <at> millennium.berkeley.edu">Yes</a></span>

<span><a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1440.html?nofriend=true&amp;url=http://www.quepasa.com/en_US/&amp;mail=tinyos-help <at> millennium.berkeley.edu">No</a></span>
<br><br></p>

<p>Thanks!</p>

<p>
Nirvesh  Priyadarshi
</p>
<p><br></p>
<p>To prevent from getting anymore email notifications from your friends on Quepasa.com, <a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1433.html?url=http%3A%2F%2Fwww.quepasa.com%2Fen_US%2Fuser%2FcancelQPAlerts.php%3Fsign%3De0c68577a5e194d6a6d5c6b9ec769988%26alert%3D4%26mail%3Dtinyos-help%40millennium.berkeley.edu%26id%3D-1">click here</a>.</p>
</td>
                        </tr></table>
<table width="100%" border="0" cellspacing="0" cellpadding="0" height="80"><tr>
<td align="center"> 

<a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1529.html?url=http%3A%2F%2Fwww.quepasa.com%2Fen_US%2Fuser%2FcancelQPAlerts.php%3Fsign%3De0c68577a5e194d6a6d5c6b9ec769988%26alert%3D4%26mail%3Dtinyos-help%40millennium.berkeley.edu%26id%3D-1">Unsubscribe</a> I
<a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1521.html?url=http%3A%2F%2Fwww.quepasa.com%2Ftos_en_US.html">Terms of Use</a> I
<a href="http://www.quepasa.com/metric/email/click/c89707b7c4a0368596c246873975bd87/10545876801/1522.html?url=http%3A%2F%2Fwww.quepasa.com%2Fcommon%2Fprivacypolicy_en_US.html">Privacy Policy</a> I
<a href="mailto:support <at> quepasacorp.com">Support</a><br> 
Quepasa Corporation 324 Datura Street, Suite 114, West Palm Beach, FL, 33401.<br> 
You are receiving this message because your friend is a registered member of Quepasa.
<br> 
Add <a href="mailto:info <at> quepasa.com">info <at> quepasa.com</a> to your contact list so you always receive your Quepasa email. 
</td> 
</tr></table>
</td>
        </tr></table>
</div>
Permalink | Reply | 0 comments |
headers
Christian To | 2 Sep 2010 08:37
Picon
Favicon

Basics of Visualization Tool known as Octopus

Hello!

I am a new user of this visualization tool known as the Octopus Project. I am having trouble with finding a solution to why there are no nodes shown when I execute the OctopusGui.java (I am working on an ubuntu 10.04 lucid lynx with a tinyos-2.1.1 environment, and my Octopus version is V2.1)

The following are the steps I have tried:

1.) cd /opt/tinyos-2.1.1/apps/OctopusDashboard/motes

2.) make micaz

/opt/tinyos-2.1.1/tos/system/LedsP.nc:151: warning: `Energy.toggleLed' called asynchronously from `Leds.led2Toggle'
/opt/tinyos-2.1.1/tos/system/LedsP.nc:121: warning: `Energy.toggleLed' called asynchronously from `Leds.led1Toggle'
/opt/tinyos-2.1.1/tos/system/LedsP.nc:91: warning: `Energy.toggleLed' called asynchronously from `Leds.led0Toggle'
/opt/tinyos-2.1.1/tos/system/LedsP.nc:131: warning: `Energy.startLed' called asynchronously from `Leds.led2On'
/opt/tinyos-2.1.1/tos/system/LedsP.nc:101: warning: `Energy.startLed' called asynchronously from `Leds.led1On'
/opt/tinyos-2.1.1/tos/system/LedsP.nc:71: warning: `Energy.startLed' called asynchronously from `Leds.led0On'
/opt/tinyos-2.1.1/tos/system/LedsP.nc:141: warning: `Energy.stopLed' called asynchronously from `Leds.led2Off'
/opt/tinyos-2.1.1/tos/system/LedsP.nc:111: warning: `Energy.stopLed' called asynchronously from `Leds.led1Off'
/opt/tinyos-2.1.1/tos/system/LedsP.nc:81: warning: `Energy.stopLed' called asynchronously from `Leds.led0Off'
    compiled OctopusAppC to build/micaz/main.exe
           33290 bytes in ROM
            2457 bytes in RAM
avr-objcopy --output-target=srec build/micaz/main.exe build/micaz/main.srec
avr-objcopy --output-target=ihex build/micaz/main.exe build/micaz/main.ihex
    writing TOS image

*** I assume that this means that the compilation is successful ***

3.) make micaz install,0 mib520,/dev/ttyUSB0
==> then do this for the other nodes, incrementing only the number beside the "install"; i.e.) install,1

4.) cd /opt/tinyos-2.1.1/apps/OctopusDashboard/java

6.) make

7.) export MOTECOM=serial <at> /dev/ttyUSB1:micaz

8.) java OctopusGui

The GUI displayed itself with the following message on the terminal:

serial <at> /dev/ttyUSB1:57600: resynchronising

*** The GUI works (I think) but it doesn't show any nodes on the screen. ***

Please help. I am trying to use a visualization tool like the Octopus Project to test if my proposed time-synchronization algorithm is sufficient to reduce clock offset and skew. Unfortunately, there is no TinyViz in tinyos-2.x, so my options are Octopus and MViz. But MViz can only express a one-hop type of algorithm, it doesn't support multi-hop (which I have incorporated in my time-synchronization algorithm)

Any help would be great! Thank You!

*******************************************************************************************************

Christian To
University of the Philippines


<div>
<table cellspacing="0" cellpadding="0" border="0"><tr><td valign="top">Hello!<br><br>I am a new user of this visualization tool known as the 
Octopus Project. I am having trouble with finding a solution to why 
there are no nodes shown when I execute the OctopusGui.java (I am 
working on an ubuntu 10.04 lucid lynx with a tinyos-2.1.1 environment, 
and my Octopus version is V2.1)<br><br>The following are the steps I have tried:<br><br>1.) cd /opt/tinyos-2.1.1/apps/OctopusDashboard/motes<br><div>
<br>2.) make micaz<br><br>/opt/tinyos-2.1.1/tos/system/LedsP.nc:151: warning: `Energy.toggleLed' called asynchronously from `Leds.led2Toggle'<br>
/opt/tinyos-2.1.1/tos/system/LedsP.nc:121: warning: `Energy.toggleLed' called asynchronously from `Leds.led1Toggle'<br>/opt/tinyos-2.1.1/tos/system/LedsP.nc:91: warning: `Energy.toggleLed' called asynchronously from `Leds.led0Toggle'<br>
/opt/tinyos-2.1.1/tos/system/LedsP.nc:131: warning: `Energy.startLed' called asynchronously from `Leds.led2On'<br>/opt/tinyos-2.1.1/tos/system/LedsP.nc:101: warning: `Energy.startLed' called asynchronously from `Leds.led1On'<br>
/opt/tinyos-2.1.1/tos/system/LedsP.nc:71: warning: `Energy.startLed' called asynchronously from `Leds.led0On'<br>/opt/tinyos-2.1.1/tos/system/LedsP.nc:141: warning: `Energy.stopLed' called asynchronously from `Leds.led2Off'<br>
/opt/tinyos-2.1.1/tos/system/LedsP.nc:111: warning: `Energy.stopLed' called asynchronously from `Leds.led1Off'<br>/opt/tinyos-2.1.1/tos/system/LedsP.nc:81: warning: `Energy.stopLed' called asynchronously from `Leds.led0Off'<br>
&nbsp;&nbsp;&nbsp; compiled OctopusAppC to build/micaz/main.exe<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 33290 bytes in ROM<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2457 bytes in RAM<br>avr-objcopy --output-target=srec build/micaz/main.exe build/micaz/main.srec<br>avr-objcopy --output-target=ihex build/micaz/main.exe build/micaz/main.ihex<br>
&nbsp;&nbsp;&nbsp; writing TOS image<br><br>*** I assume that this means that the compilation is successful ***<br><br>3.) make micaz install,0 mib520,/dev/ttyUSB0<br>==&gt; then do this for the other nodes, incrementing only the number beside the "install"; i.e.) install,1<br><br>4.) cd /opt/tinyos-2.1.1/apps/OctopusDashboard/java<br><div>

<br>6.) make<br><br>7.) export MOTECOM=serial <at> /dev/ttyUSB1:micaz<br><br>8.) java OctopusGui</div>
<br>The GUI displayed itself with the following message on the terminal:<br><br>serial <at> /dev/ttyUSB1:57600: resynchronising<br><br>*** The GUI works (I think) but it doesn't show any nodes on the screen. ***<br><br>Please help. I am trying to use a visualization tool like the Octopus 
Project to test if my proposed time-synchronization algorithm is 
sufficient to reduce clock offset and skew. Unfortunately, there is no 
TinyViz in tinyos-2.x, so my options are Octopus and MViz. But MViz can 
only express a one-hop type of algorithm, it doesn't support multi-hop 
(which I have incorporated in my time-synchronization algorithm)<br><br>Any help would be great! Thank You!<br><br><div>*******************************************************************************************************<br>
<br>Christian To<br>University of the Philippines</div>
<br>
</div>
</td></tr></table>
<br>
</div>
Permalink | Reply | 2 comments |
headers
JC de Dios | 2 Sep 2010 09:44
Picon

TestFtsp with Microsecond Resolution

Hello,


I'm playing around with the TestFtsp application with MicaZ platform, and tested both milli and 32k versions. I would like to know if it possible to use the microsecond resolution so I can get the time sync error exactly as much as possible. I found out that CC2420TimeSyncMessageC component does not offer the microsecond interface and I'm wondering if the radio can support it. If it is possible, what changes can I make?

Based on my tests on TestFtsp using 32k time, I found out that the average time synchronization error between to MicaZs is close to millisecond. I have also read the paper on FTSP and it claims that it has an average time sync error within microsecond. Can I know if there is any modifications that I must do to reach that microsecond error? Or am I just currently doing something wrong?

Thanks for the help.

JC de Dios
University of the Philippines
<div>
<p>Hello,</p>
<div><br></div>
<div>I'm playing around with the TestFtsp application with MicaZ platform, and tested both milli and 32k versions. I would like to know if it possible to use the microsecond resolution so I can get the time sync error exactly as much as possible. I found out that CC2420TimeSyncMessageC component does not offer the microsecond interface and I'm wondering if the radio can support it. If it is possible, what changes can I make?</div>
<div><br></div>
<div>Based on my tests on TestFtsp using 32k time, I found out that the average time synchronization error between to MicaZs is close to millisecond. I have also read the paper on FTSP and it claims that it has an average time sync error within microsecond. Can I know if there is any modifications that I must do to reach that microsecond error? Or am I just currently doing something wrong?</div>
<div><br></div>
<div>Thanks for the help.</div>
<div><br></div>
<div>JC de Dios</div>
<div>University of the Philippines</div>
</div>
Permalink | Reply | 0 comments |
headers
Haripriya priya | 2 Sep 2010 14:00
Picon

How to generate synrchronous counter?

Hi

I need a sender-receiver pair...

 that pair should maintain a synchronous counter..

How it can be done ??

In IEEE paper for LLSP its given that FRS can be used to generate synchronous counter ...


What does FRS mean??

--
Regards,
S.Haripriya

<div><p>Hi<br><br>I need a sender-receiver pair...<br><br>&nbsp;that pair should maintain a synchronous counter.. <br><br>How it can be done ??<br><br>In IEEE paper for LLSP its given that FRS can be used to generate synchronous counter ...<br><br><br>What does FRS mean??<br clear="all"><br>-- <br>Regards,<br>S.Haripriya<br><br></p></div>
Permalink | Reply | 0 comments |
headers
TheMrOrange | 2 Sep 2010 19:18
Picon

Ieee154Packet.source called asynchronously from CC2420Receive.receive

Hi all,

I get a warning when I call  I cal "Ieee154Packet.source" from the  
event "CC2420Receive.receive"

"Ieee154Packet.source' called asynchronously from  
`CC2420Receive.receive"

Could you suggest me how to properly get source and destination from a  
message received by CC2420?

Many thanks

Davide
Permalink | Reply | 0 comments |
headers
Gaurav Agrawal | 3 Sep 2010 03:16
Picon

error: undefined reference to "library function name"


Dear friends,

I am using tinyos 2.1.  i was trying to create a library for sending debug messages on the UART just like the available printf library. I
followed the printf tutorial. 

i created a folder in /home/P09/tinyos-2.x/tos/lib/printdbg/ 
and created the files for sending messages to the UART.

in the printdbg.h header file i have declared the function printdbg, the function that is used in the library files to send messages.
void printdbg(char* buf, uint8_t msgint);

in my makefile of the application i have written
CFLAGS += -I$(TOSDIR)/lib/printdbg

I tried to send some debug messages from the blink application. I included  printdbg.h in each of the files of the blink application
from where i m calling printdbg(..) function.

everything works fine but i get a strange, possibly a linking error at compile time that can be seen at the end of the below long message.

I tried adding -v to see the verbose output but all in vain.
ERROR:

   compiling BlinkAppC to a amulet2 binary
ncc  -Os -finline-limit=100000 -Wall -Wshadow -Wnesc-all
-target=amulet2 -conly -fnesc-cfile=build/amulet2/main_arm.c
-fnesc-separator=__ -DDEFINED_TOS_AM_GROUP=0x22
-I/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/printdbg
-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"agrawalg\"
-DIDENT_HOSTNAME=\"pg024\" -DIDENT_USERHASH=0x1cab6c09L
-DIDENT_TIMESTAMP=0x4c8040faL -DIDENT_UIDHASH=0x1259a713L BlinkAppC.nc
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/printdbg/DebugMsgSendP.nc:157:1:
warning: "/*" within comment
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/hpl/HplC.nc:37:
warning: call via function pointer
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/serial/PlatformSerialP.nc:33:
warning: `Serial.WriteStream' called asynchronously from
`UartStream.send'
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/led/PlatformLedsP.nc:19:
warning: `Paralell.read' called asynchronously from `setState'
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/led/PlatformLedsP.nc:21:
warning: `Paralell.write' called asynchronously from `setState'
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/HdlcTranslateC.nc:103:
warning: `lcd.GoTo' called asynchronously from
`SerialFrameComm.putData'
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/HdlcTranslateC.nc:118:
warning: `lcd.GoTo' called asynchronously from `UartStream.sendDone'
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/HdlcTranslateC.nc:104:
warning: `lcd.WriteString' called asynchronously from
`SerialFrameComm.putData'
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/HdlcTranslateC.nc:119:
warning: `lcd.WriteString' called asynchronously from
`UartStream.sendDone'
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/timer/Amulet2TimerMilliP.nc:15:
warning: non-atomic accesses to shared variable `currentTime':
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/timer/Amulet2TimerMilliP.nc:67:
warning:   non-atomic read
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:146:
warning: non-atomic accesses to shared variable `rxState':
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:207:
warning:   non-atomic write
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:165:
warning: non-atomic accesses to shared variable `offPending':
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:484:
warning:   non-atomic read
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:150:
warning: non-atomic accesses to shared variable `rxCRC':
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:211mainly
consisting of the warnings: warning:   non-atomic write
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:415:
warning:   non-atomic write
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/hpl/HplC.nc:10:
warning: non-atomic accesses to shared variable `sleeping':
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/hpl/HplC.nc:52:
warning:   non-atomic read
arm-elf-gcc -mcpu=arm6  -o build/amulet2/BlinkAppC
build/amulet2/main_arm.c -lm
/tmp/ccgJ4gnE.o(.text+0x18c8): In function `BlinkC__Boot__booted':
: undefined reference to `printdbg'
/tmp/ccgJ4gnE.o(.text+0x3bd4): In function `BlinkC__Timer0(float, int,
long double,...)(double)':
: undefined reference to `printdbg'
collect2: ld returned 1 exit status
make: *** [exe0] Error 1

I saw some previous archives discussing similar problem for the same error occurring while executing code in TOSSIM. the solution suggested was to add -shared option. but i am in confusion whether it will make any difference to me coz i m not simulating the code instead i m running the code on my amulet motes.

please help friends i m desperate to solve this error.

Thanks in advance
Gaurav

<div>
<br>Dear friends,<br><div class="gmail_quote">
<br>
I am using tinyos 2.1. &nbsp;i was trying to create a library for sending&nbsp;debug messages on the UART just like the available printf library. I<br>
followed the printf tutorial.&nbsp;<br><br>
i created a folder in /home/P09/tinyos-2.x/tos/lib/printdbg/&nbsp;</div>
<div class="gmail_quote">and created the files for sending messages to the UART.<br><br>
in the printdbg.h header file i have declared the function printdbg,&nbsp;the function that is used in the library files to send messages.</div>
<div class="gmail_quote">void printdbg(char* buf, uint8_t msgint);<br><br>
in my makefile of the application i have written<br>
CFLAGS += -I$(TOSDIR)/lib/printdbg<br><br>
I tried to send some debug messages from the blink application. I&nbsp;included &nbsp;printdbg.h in each of the files of the blink application<br>
from where i m calling printdbg(..) function.<br><br>
everything works fine but i get a strange, possibly a linking error at&nbsp;compile time that can be seen at the end of the below long message.<br><br>
I tried adding -v to see the verbose output but all in vain.<br>
ERROR:<br><br>
 &nbsp; &nbsp;compiling BlinkAppC to a amulet2 binary<br>
ncc &nbsp;-Os -finline-limit=100000 -Wall -Wshadow -Wnesc-all<br>
-target=amulet2 -conly -fnesc-cfile=build/amulet2/main_arm.c<br>
-fnesc-separator=__ -DDEFINED_TOS_AM_GROUP=0x22<br>
-I/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/printdbg<br>
-DIDENT_APPNAME=\"BlinkAppC\" -DIDENT_USERNAME=\"agrawalg\"<br>
-DIDENT_HOSTNAME=\"pg024\" -DIDENT_USERHASH=0x1cab6c09L<br>
-DIDENT_TIMESTAMP=0x4c8040faL -DIDENT_UIDHASH=0x1259a713L BlinkAppC.nc<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/printdbg/DebugMsgSendP.nc:157:1:<br>
warning: "/*" within comment<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/hpl/HplC.nc:37:<br>
warning: call via function pointer<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/serial/PlatformSerialP.nc:33:<br>
warning: `Serial.WriteStream' called asynchronously from<br>
`UartStream.send'<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/led/PlatformLedsP.nc:19:<br>
warning: `Paralell.read' called asynchronously from `setState'<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/led/PlatformLedsP.nc:21:<br>
warning: `Paralell.write' called asynchronously from `setState'<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/HdlcTranslateC.nc:103:<br>
warning: `lcd.GoTo' called asynchronously from<br>
`SerialFrameComm.putData'<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/HdlcTranslateC.nc:118:<br>
warning: `lcd.GoTo' called asynchronously from `UartStream.sendDone'<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/HdlcTranslateC.nc:104:<br>
warning: `lcd.WriteString' called asynchronously from<br>
`SerialFrameComm.putData'<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/HdlcTranslateC.nc:119:<br>
warning: `lcd.WriteString' called asynchronously from<br>
`UartStream.sendDone'<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/timer/Amulet2TimerMilliP.nc:15:<br>
warning: non-atomic accesses to shared variable `currentTime':<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/timer/Amulet2TimerMilliP.nc:67:<br>
warning: &nbsp; non-atomic read<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:146:<br>
warning: non-atomic accesses to shared variable `rxState':<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:207:<br>
warning: &nbsp; non-atomic write<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:165:<br>
warning: non-atomic accesses to shared variable `offPending':<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:484:<br>
warning: &nbsp; non-atomic read<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:150:<br>
warning: non-atomic accesses to shared variable `rxCRC':<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:211mainly<br>
consisting of the warnings: warning: &nbsp; non-atomic write<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/lib/serial/SerialP.nc:415:<br>
warning: &nbsp; non-atomic write<br>/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/hpl/HplC.nc:10:<br>
warning: non-atomic accesses to shared variable `sleeping':<br>
/home/P09/agrawalg/mywork/tinyos-2.x/tos/platforms/amulet2/hpl/HplC.nc:52:<br>
warning: &nbsp; non-atomic read<br>
arm-elf-gcc -mcpu=arm6 &nbsp;-o build/amulet2/BlinkAppC<br>
build/amulet2/main_arm.c -lm<br>
/tmp/ccgJ4gnE.o(.text+0x18c8): In function `BlinkC__Boot__booted':<br>
: undefined reference to `printdbg'<br>
/tmp/ccgJ4gnE.o(.text+0x3bd4): In function `BlinkC__Timer0(float, int,<br>
long double,...)(double)':<br>
: undefined reference to `printdbg'<br>
collect2: ld returned 1 exit status<br>
make: *** [exe0] Error 1<br><br>
I saw some previous archives discussing similar problem for the same error&nbsp;occurring&nbsp;while executing code in TOSSIM. the solution suggested was to add -shared option. but i am in confusion whether it will make any difference to me coz i m not&nbsp;simulating&nbsp;the code instead i m running the code on my amulet motes.</div>
<div class="gmail_quote">
<br>
please help friends i m desperate to solve this error.<br><br>
Thanks in advance<br>Gaurav<br>
</div>
<br>
</div>
Permalink | Reply | 2 comments |

Gmane