[Tinyos-help] port to atmega16.

[david.deng]

Hello,

 Does anyone ever port tinyos to atmega16? If so, 
could you kindly give some ideas or information about it ? thanks. 

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Help in Understanding Code

[Kannan Srinivasan]

Hi Sumit,

I believe the code is correct. The first call of the timer triggers it after
a random duration. This is to keep the durations different for different
nodes. But once it is triggered you repeatedly call the single shot timer
with a deterministic duration. This deterministic duration will maintain
the original randomness throughout (assuming clock drifts etc are absent).

Hope this helps,
Kannan.
Quoting Sumit Gupta [EMAIL PROTECTED]:

 Hi,

 I am trying to understand the code of SurgeTelos application. Now this
 application is using Component MultiHopLQI (located in
 ..tinyos-1.x/tos/lib/MultiHopLQI/)
 for routing. In this component developer use Timer component for
 triggering
 the collection of data and sending it to base station.

 Now I am bit confused. In this they are using argument TIMER_ONE_SHOT for
 Timer, which I believe is wrong because it should be TIMER_REPEAT to
 repeat
 the process of sending data to base station over and over again. If not
 then
 how it has been implemented. Please explain if you understand what I am
 missing out here.

 They used it at two places. First when application initialized, which
 make
 sense to me as they are awaking each node at random time, but I am not
 sure
 why they are using again at second time with TIMER_ONE_SHOT parameter.
 Please give a look and help me understanding. Is it a typo?

 // First time when timer will initialized
   command result_t StdControl.start() {
 gLastHeard = 0;
 call Timer.start(TIMER_ONE_SHOT,
  call Random.rand() % (1024 * gUpdateInterval));
 return SUCCESS;
   }

 //Second time when timer will fire
   event result_t Timer.fired() {
 post TimerTask();
 call Timer.start(TIMER_ONE_SHOT, 1024 * gUpdateInterval + 1);
 return SUCCESS;
   }

 Is it because Timer is being started again from Timer.fired function? I
 just
 want to make sure that I am understanding it in a right way. Please
 advice.

 Regards,
 Sumit Gupta



___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Cygdrive Problem in Cygwin

[Joe Polastre]

new versions of cygwin don't make it visible.

On 9/10/06, Sumit Gupta [EMAIL PROTECTED] wrote:

it doesnt even show cygdrive at root i.e. /.
 Oh.. i noticed that cygdrive still exist.. I could access cygdrive but why
its not showing... Sorry for inconvinience.. but why its not showing. Infact
I also tried to use find command to find a folder cygdrive which returned
negative results.

 Thanks for your help. Its there but it is invisible in both Cygwin and
Windows (when i use windows explorer to browse the folder). What might be
the reason? Also its just showing c drive in cygdrive folder but not my
cdrom.. is it suppose to be that way.

 Thanks, please tell little more how I can make it visible.

 Thanks.
 Sumit



On 9/10/06, Joe Polastre [EMAIL PROTECTED] wrote:
 What happens when you type cd /cygdrive/c/?

 -Joe

 On 9/10/06, Sumit Gupta [EMAIL PROTECTED] wrote:
  I checked my registry files and they are in order as per my cygwin
location.
  I think I didnt uninstalled cygwin properly due to which every new
  installation is not working properly. Dont know wht? I did uninstall
cygwin
  according to instructions I found online (after i uninstalled tinyos
using
  CD). I've also reported the matter with moteiv support, but havent heard
  from them.
 
   Still struggling to fix it.
 
   Sumit
 
  On 9/10/06, Michael Schippling  [EMAIL PROTECTED] wrote:
   Sorry, I'm unclear on the problem. If you reinstalled from the CD
   to make things work, what's left that needs fixing?
  
   Anyway, just in case this helps...
  
   Using various archaeological methodologies I have found that
   copying the whole cygwin tree from machine to machine works just fine,
   except that there are a small number of registry entries that need to
   be fiddled on each host. As far as I can tell, these entries are the
   sum total of the
  Special-Extra-Hidden-You-Shouldn't-Have-To-Know-About
   elements of the install script that make the /cygdrive/c thing work:
  
  
 
---
   REGEDIT4
  
   [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions]
  
   [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin]
  
   [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus
  Solutions\Cygwin\mounts v2]
   cygdrive prefix=/cygdrive
   cygdrive flags=dword:0022
  
   [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus
  Solutions\Cygwin\mounts v2\/]
   native=C:\\cygwin
   flags=dword:000a
  
   [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus
  Solutions\Cygwin\mounts v2\/usr/bin]
   native=C:\\cygwin/bin
   flags=dword:000a
  
   [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus
  Solutions\Cygwin\mounts v2\/usr/lib]
   native=C:\\cygwin/lib
   flags=dword:000a
  
   [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus
  Solutions\Cygwin\Program Options]
  
  
 
-
  
   Note that I have my cygwin at C:/cygwin so if you have installed
   elsewhere, you need to change that appropriately. If you extract the
   above, between the --, into a file named, say, cygreg.reg and
   double click it, it will execute and install those entries in your
   registry. Then ls /usr should work as advertised on U*IX.
  
   MS
 
 
  Sumit Gupta wrote:
   Hi,
  
   When I re-installed cygwin from moteiv CD second time I couldnot
restore
   cygdrive folder back on system. It was there after first installation
   but not there now. I also tried to update Cygwin from setup file
located
   in cygwin-installationfiles folder but it doesnt work. Then I tried to
   update it from internet which restored the cygdrive folder but changed
   everything else in cygwin. Thus to make things work I had to
re-install
   it from scratch from CD. I need to fix this problem.Can anyone helpme
me
   in fixing this problem?
  
   Hope to hear back.
  
   Regards,
   Sumit
  
  
  
 

  
   ___
   Tinyos-help mailing list
   Tinyos-help@Millennium.Berkeley.EDU
  
 
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 
 
  ___
  Tinyos-help mailing list
  Tinyos-help@Millennium.Berkeley.EDU
 
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
 
 




___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [tinyos-help] TinyOS 2.0 lacks of TEP104 and 105

[Joe Polastre]

I agree, the implementation of TEP105 is stale relative to the
codebase.  However, there are some ideas in there that I believe are
applicable regardless of the details of implementation.  If there is
an active discussion on the new TEP105, please add me to the list.
Thanks,

-Joe

On 9/10/06, Philip Levis [EMAIL PROTECTED] wrote:

On Sep 10, 2006, at 3:22 PM, Joe Polastre wrote:

 1) I originally wrote TEP105 and no one in this group (or any other
 group) has ever asked me to help revisit it, including David Culler.

I judged that TEP 105 is at this point defunct. It was last touched/
discussed 18 months ago, and was based on the 1.x CC2420 and CC1000
implementations, neither of which any longer exist in 2.x. This
should be evident by the use of TOSMsg rather than message_t.

David proposed a related but different TEP regarding CSMA; the WG
discussed whether it would be better to give the TEP a new number or
use it was an opportunity to reuse a defunct number, as they lead to
some confusion. The conclusion was to reuse 105:

http://tinyos.stanford.edu:8000/TinyOS_2.x_WG/07.12.2006

 2) I don't recall any discussions where it was concluded to be
 trickier than originally thought.

I was referring to 104. Apologies if this wasn't clear.

Phil


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Problem in Application Surge for platform telos

[Joe Polastre]

Please search the mailing list archives.  Use SurgeTelos instead.

-Joe

On 9/10/06, Sumit Gupta [EMAIL PROTECTED] wrote:

I have been trying to compile application Surge for telos motes but its
giving me errors. However, it compiled perfectly fine for other platforms
(mica2, pc etc).

 For telos its giving me following errors:


 [EMAIL PROTECTED] /opt/tinyos-1.x/apps/Surge
 $ make telos
 mkdir -p build/telos
 compiling Surge to a telos binary
 ncc -o build/telos/main.exe -O -I%T/lib/Route -I%T/lib/Queue
-I%T/lib/Broadcast
 -mdisable-hwmul -I/opt/tinyos-1.x/tos/lib/CC2420Radio
-I/opt/tinyos-1.x/tos/lib/
 Flash -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -target=telos
-fnesc-cfi
 le=build/telos/app.c -board=micasb -I%T/lib/Deluge
-Wl,--section-start=.text=0x1
 a00,--defsym=_reset_vector__=0x1100
-DIDENT_PROGRAM_NAME=\Surge\ -DIDENT_USER_
 ID=\Sumit\ -DIDENT_HOSTNAME=\superComp\ -DIDENT_USER_HASH=0x85ed13fbL
-DIDEN
 T_UNIX_TIME=0x4504db6aL -DIDENT_UID_HASH=0x291885d3L Surge.nc -lm
 In file included from Surge.nc:42:
 In component `SurgeM':
 SurgeM.nc: In function `SendData':
 SurgeM.nc:89: warning: suggest parentheses around assignment used as truth
value

 In file included from
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/mic
 asb/Photo.nc:45,
  from Surge.nc:42:
 In C file:
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:
At
 top level:
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:71:
 warning: return-type defaults to `int'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:71:
 warning: data definition has no type or storage class
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:73:
 warning: return-type defaults to `int'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:73:
 warning: data definition has no type or storage class
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:74:
 warning: return-type defaults to `int'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:74:
 warning: data definition has no type or storage class
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:75:
 warning: return-type defaults to `int'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:75:
 warning: data definition has no type or storage class
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:76:
 warning: return-type defaults to `int'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:76:
 warning: data definition has no type or storage class
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:77:
 warning: return-type defaults to `int'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:77:
 warning: data definition has no type or storage class
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:78:
 warning: return-type defaults to `int'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:78:
 warning: data definition has no type or storage class
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:79:
 warning: return-type defaults to `int'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/sensorboard.h:79:
 warning: data definition has no type or storage class
 In file included from
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/mic
 asb/PhotoTemp.nc:58,
  from
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/mic
 asb/Photo.nc:53,
  from Surge.nc:42:
 In component `PhotoTempM':
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:
In
 function `getSample':
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:211:
  implicit declaration of function `TOSH_SET_PHOTO_CTL_PIN'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:212:
  implicit declaration of function `TOSH_MAKE_PHOTO_CTL_OUTPUT'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:213:
  implicit declaration of function `TOSH_CLR_TEMP_CTL_PIN'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:214:
  implicit declaration of function `TOSH_MAKE_TEMP_CTL_INPUT'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:251:
  implicit declaration of function `TOSH_CLR_PHOTO_CTL_PIN'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:252:
  implicit declaration of function `TOSH_MAKE_PHOTO_CTL_INPUT'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:253:
  implicit declaration of function `TOSH_SET_TEMP_CTL_PIN'
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/sensorboards/micasb/PhotoTempM.nc:254:
  implicit declaration of function `TOSH_MAKE_TEMP_CTL_OUTPUT'
 In file included from

[Tinyos-help] Routing Algorithm of SurgeTelos and Surge

[Sumit Gupta]

Hi all,

I have been studing the Routing algorithm of Surge and SurgeTelos. They
both seem to have different routing algorithms. Is it so? I understood
Surge Routing Algorithm pretty much in detail except a few things (and
still trying to understand SurgeTelos) but I want to know things in
more detail and especially for SurgeTelos. Can anyone send me any
link/documentation or explain me about the routings in both of these
application?

Regards.
Sumit
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] repeating tests,no free memory

[Munaretto, Daniel]

Dear all,
   i discover a really strange behavior in my application. 
I repeat more times my code, and after some experiments the motes break down.
So there is a memory problem.
But i'm sure i free all the memory i allocate during the code. I'm using only a 
buffer and i re-use it all the times, instead i allocate memory with calloc() 
only for creating a chain which i delete at the end of each simulation with the 
free command and then i give NULL to the pointers.
So i don't understand where i lose memory each time i re-run the program 
(without re-booting the motes). i'm in tinyos 1.1.15,micaz motes.
I'm using the FlashBridge interface because i'm working on the flash.
I'm supposing that, may be, the problem is in the way Tinyos handles the 
packets received. For example, in the function event TOS_MsgPtr 
Receive.receive(TOS_MsgPtr m), before returning m, do i have to free it?But i 
can see it's wrong to do..
 
Please, if anyone knows where i have to find the waste of memory (may be some 
interfaces)...any helps will be really appreciated
thanks very much
cheers
Daniele

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Make mica compiling problem

[walid hamdi]

make pc is ok but make mica leads to this error:

make mica
compiling Blink to a mica binary
ncc -o build/mica/main.exe -Os -board=micasb
-target=mica  -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d
-Wnesc-all -finline-limit=10
-fnesc-cfile=build/mica/app.c  Blink.nc -lm
/tmp/ccLWz2B6.s: Assembler messages:
/tmp/ccLWz2B6.s:10: Error: unknown opcode `disablecou'
/tmp/ccLWz2B6.s:12: Error: unrecognized symbol type 
/tmp/ccLWz2B6.s:12: Error: unknown opcode `disablecou'
/tmp/ccLWz2B6.s:13: Error: expected comma after name
`HPLPowerManagementM' in .size directive
/tmp/ccLWz2B6.s:13: Error: unknown opcode `disablecou'
/tmp/ccLWz2B6.s:14: Error: unknown opcode `hplpowerma'
/tmp/ccLWz2B6.s:43: Error: unrecognized symbol type 
/tmp/ccLWz2B6.s:43: Error: unknown opcode `doadjustme'
/tmp/ccLWz2B6.s:44: Error: unknown opcode `hplpowerma'
/tmp/ccLWz2B6.s:120: Error: expected comma after name
`HPLPowerManagementM' in .size directive
/tmp/ccLWz2B6.s:120: Error: unknown opcode
`doadjustme'
...
...
/tmp/ccLWz2B6.s:730: Error: missing size expression
/tmp/ccLWz2B6.s:730: Error: unknown opcode `ledson'
make: *** [build/mica/main.exe] Error 1

I am using Ubuntu 6.06 withthe following TinyOS
features:
Version: ncc: 1.2alpha5
nesc: 1.2.7a (latest version)
Version: avr-gcc (GCC) 3.4.3
uisp version 20050519tinyos
GNU assembler 2.15
GNU gdb 6.3

Note that everything i have got is the last version,
i have no avarice, and no msp430-gcc, as i will not
use Telos sensors at the moment..

could anybody help please!






___ 
Découvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet 
! 
Yahoo! Questions/Réponses pour partager vos connaissances, vos opinions et vos 
expériences. 
http://fr.answers.yahoo.com 

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Help me with raw data conversion

[Giovanni Petracca]

Hi all,   i have two questions to you; 1) i'm using Oscilloscope and Delta apps, and i want to convert raw data from ADC into SI data; i 'm using the paper "getting data from moteiv tmote sky sensors" at www.moteiv.com. the external temperature sensor give me a value = 6965 (1B35 in hex) that means a temperature of 30,05 ° C but in the room there is a temperature of maximum 25°! where is the problem? i've tried with other tmote sky modules but the value is the same. is this a problem dependent from sensor, software or is wrong the formula: temp=-39.60 + 0.01 * Reading ?2) when i log packets from oscilloscope or delta apps , i see that the "data" bytes in the multihopmsg are written from right to left, is it normal? i put the log below:1157967601703 Message MultiHopMsg  [sourceaddr=0x9] [originaddr=0x9] [seqno=0x35f] [originseqno=0x35f] [ttl=0x0] [id=0x21] [data="" 0x3 0x0 0x0 0x93 0xb 0x35 0x1b 0x52 0x4 0xbd 0x0 0x7e 0x0 0x3 0x0 0x7e 0x0 ]the "data " bytes are : the first four (0x5b 0x3 0x0 0x0) are seqno, after 2 bytes (0x93 0xb) needs to be read B93. and the others in the same mode. it's right??thank you for help me and sorry for the not so good english.ByeGiovanni
Petracca
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] installation query

[preeti k]

i haven't modified the file but it still doe not seem to workOn 9/11/06, sougata sen [EMAIL PROTECTED]
 wrote:have u modified the AM.h file because it is showing a parse error in 
AM.h. check if u have done some changes in that
On 9/9/06, preeti k [EMAIL PROTECTED]

 wrote: 

Hi,I gave the 'make pc ' command by going to the application stored at ../tinyosdir/tinyos1.x/apps/Blink.But the file did not compile and i got the following error (it is quite long but i am pasting it for your reference) 
[EMAIL PROTECTED] Blink]# make pc compiling Blink to a pc binaryncc -o build/pc/main.exe -g -O0 -board=micasb -pthread -target=pc -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -fnesc-nido-tosnodes=1000 -fnesc-cfile=build/pc/app.c 
Blink.nc -lmIn file included from /home/preeti/tinyosdir/tinyos-1.x/tos/platform/pc/GuiMsg.h:51, from /home/preeti/tinyosdir/tinyos- 
1.x/tos/types/dbg.h:70, from /home/preeti/tinyosdir/tinyos- 1.x/tos/platform/pc/hardware.h:65, from /home/preeti/tinyosdir/tinyos-1.x/tos/system/tos.h:132:/home/preeti/tinyosdir/tinyos- 
1.x/tos/types/AM.h:155: parse error before `struct'/home/preeti/tinyosdir/tinyos- 1.x/tos/types/AM.h:156: parse error before `struct'/home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h:158: parse error before `struct' 
/home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h: In function `TOS_MsgLength':/home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h:183: parse error before `TOS_Msg'In file included from /home/preeti/tinyosdir/tinyos- 
1.x/tos/platform/pc/hardware.h:116, from /home/preeti/tinyosdir/tinyos- 1.x/tos/system/tos.h:132:/home/preeti/tinyosdir/tinyos-1.x/tos/platform/pc/eeprom.c: At top level:/home/preeti/tinyosdir/tinyos- 
1.x/tos/platform/pc/eeprom.c:114: warning: declaration of `length' shadows global declaration /home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h:158: warning: location of shadowed declaration/home/preeti/tinyosdir/tinyos- 
1.x/tos/platform/pc/eeprom.c:144: warning: declaration of `length' shadows global declaration /home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h:158: warning: location of shadowed declarationmake: *** [build/pc/main.exe] Error 1 

Can anyone help please?Preeti

On 9/9/06, Sumit Gupta [EMAIL PROTECTED] 
 wrote: 


Hi,make pc is a command to compile which will store the compiled binary file in build folder in your computer.For example: If you want to compile application 

Blink stored in ../tinyos-1.x/apps/Blink/ then you need to give following command:make platformthus for tossim (or PC platform), it is: 
make pc (it will store binary in .../Blink/build/pc/main.exe)and for other platforms like mica2 it is: 
make mica2 
(it will store binary in .../Blink/build/mica2/main.exe)Now to run the file on TOSSIM (which comes with Tinyos-1.x by defualt, thus u dont have to install it) - stay in Blink directory and type:

build/pc/main.exe number of nodes you want to simulatethus for example for 10 nodes network:build/pc/main.exe 10. To see the result of simulation you have to learn more about tinyos's tools and options and you might want to go through TOSSIM tutorial located at 
http://www.tinyos.net/tinyos-1.x/doc/nido.pdfI hope it helped.Sumit 


On 9/8/06, preeti k  [EMAIL PROTECTED] 
 wrote:



Hello there..i have been trying to install tinyos1.x on fedora core 5 . I need to use tossim as well. i typed 'make pc ' on the prompt to get tossim running but i could not. Can anyone help please
Preeti
___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDU 
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help 
___Tinyos-help mailing list

Tinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help 
-- Sougata SenBangalore 


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] installation query

[preeti k]

yes, toscheck completes without any errorsOn 9/10/06, Tarun Bansal [EMAIL PROTECTED] wrote:
Have you gone through these tests:
http://www.tinyos.net/tinyos-1.x/doc/tutorial/verifyhw.htmlTarun___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Noise on TelosB PAR Sensor!

[Jose L. Ponce]

Hello,

I am using TelosB motes with Hamamatsu's PAR and TSR light sensors. I
am monitoring the readings of the PAR sensor and I have noticed the
following, using constant light intensity:

- For low levels of light intensity (ADC output being approx. 0.7V),
sampling over time of the light sensors returns a constant light
level, as expected.

- For higher levels of light intensity, noise a noise which is between
2-3Hz and proportional to the light intensity appears. This noise has
an amplitude of up to 0.04V, which is a lot, considering the light
measures are in the range of 1V.

Suspecting the noise was related to the AC-Current, I tried different
configurations and different lights, but I am always getting the same
noise, so it looks like it is a problem in the mote itself. And all
nodes have it.

Is this a known problem and if so, is there a solution for it other
than trying to implement a digital filter on the sensor nodes? Or is
this not normal and I am probably doing something wrong?

Thanks a lot,

- J.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] Help me with raw data conversion

[Ben Kelley]

Are the motes plugged into a USB port or by 
themselves? I saw something of a 2 to 5 degree celsius increase when I did 
some tests with the external sensors when they were plugged into the USB 
cable.



  
  
  From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  Giovanni PetraccaSent: Monday, September 11, 2006 
  05:04To: tinyos-help@Millennium.Berkeley.EDUSubject: 
  [Tinyos-help] Help me with raw data conversion
  
  Hi 
  all,  i have two questions to you; 
  1) i'm using Oscilloscope and Delta apps, and i want to convert raw data 
  from ADC into SI data; i 'm using the paper "getting data from moteiv tmote 
  sky sensors" at www.moteiv.com. the external temperature sensor give me a 
  value = 6965 (1B35 in hex) that means a temperature of 30,05 ° C but in 
  the room there is a temperature of maximum 25°! where is the problem? i've 
  tried with other tmote sky modules but the value is the same. is this a 
  problem dependent from sensor, software or is wrong the formula: temp=-39.60 + 
  0.01 * Reading ?2) when i log packets from oscilloscope or delta apps 
  , i see that the "data" bytes in the multihopmsg are written from right to 
  left, is it normal? i put the log below:1157967601703 Message 
  MultiHopMsg  [sourceaddr=0x9] [originaddr=0x9] [seqno=0x35f] [originseqno=0x35f] 
  [ttl=0x0] [id=0x21] [data="" 0x3 0x0 0x0 0x93 0xb 0x35 
  0x1b 0x52 0x4 0xbd 0x0 0x7e 0x0 0x3 0x0 0x7e 0x0 ]the "data " bytes 
  are : the first four (0x5b 0x3 0x0 0x0) are seqno, after 2 bytes (0x93 0xb) 
  needs to be read B93. and the others in the same mode. it's 
  right??thank you for help me and sorry for the not so good 
  english.ByeGiovanni 
Petracca
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [tinyos-help] TinyOS 2.0 lacks of TEP104 and 105

[Tie Luo]

I believe both TEP 104(Radio Physical Layer) andTEP 105 (Radio Link Layer)areinteresting parts and deserve effort, especially for those working on physical and MAC layers rather than higher layers.


Can I take a look at the latest draft on TEP105 (since 104 is not available), although it may be incomplete or a bit stale? Thanks.
Tie
On 9/11/06, Joe Polastre [EMAIL PROTECTED] wrote:
I agree, the implementation of TEP105 is stale relative to thecodebase.However, there are some ideas in there that I believe are
applicable regardless of the details of implementation.If there isan active discussion on the new TEP105, please add me to the list.Thanks,-JoeOn 9/10/06, Philip Levis 
[EMAIL PROTECTED] wrote: On Sep 10, 2006, at 3:22 PM, Joe Polastre wrote:  1) I originally wrote TEP105 and no one in this group (or any other  group) has ever asked me to help revisit it, including David Culler.
 I judged that TEP 105 is at this point defunct. It was last touched/ discussed 18 months ago, and was based on the 1.x CC2420 and CC1000 implementations, neither of which any longer exist in 
2.x. This should be evident by the use of TOSMsg rather than message_t. David proposed a related but different TEP regarding CSMA; the WG discussed whether it would be better to give the TEP a new number or
 use it was an opportunity to reuse a defunct number, as they lead to some confusion. The conclusion was to reuse 105: http://tinyos.stanford.edu:8000/TinyOS_2.x_WG/07.12.2006
  2) I don't recall any discussions where it was concluded to be  trickier than originally thought. I was referring to 104. Apologies if this wasn't clear.
 Phil___Tinyos-help mailing listTinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help-- Regards,Tie 
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] installation query

[Ben Kelley]

The problem appears to be the GCC 4.x vs GCC 3.x problem if 
I remember correctly. It should be in the archives on how to change your 
compiler version from 4 to 3. 

  
  
  From: 
  [EMAIL PROTECTED] 
  [mailto:[EMAIL PROTECTED] On Behalf Of 
  sougata senSent: Monday, September 11, 2006 00:17To: 
  preeti kCc: tinyos-help@Millennium.Berkeley.EDUSubject: 
  Re: [Tinyos-help] installation query
  have u modified the AM.h file because it is showing a parse error 
  in AM.h. check if u have done some changes in that
  On 9/9/06, preeti k 
  [EMAIL PROTECTED]  
  wrote: 
  
Hi,I gave the 'make pc ' command by going to the application 
stored at ../tinyosdir/tinyos1.x/apps/Blink.But the file did not compile 
and i got the following error (it is quite long but i am pasting it 
for your reference) [EMAIL PROTECTED] Blink]# make 
pc compiling Blink to a pc binaryncc -o 
build/pc/main.exe -g -O0 -board=micasb -pthread -target=pc -Wall 
-Wshadow -DDEF_TOS_AM_GROUP=0x7d -Wnesc-all -fnesc-nido-tosnodes=1000 
-fnesc-cfile=build/pc/app.c Blink.nc -lmIn file included 
from 
/home/preeti/tinyosdir/tinyos-1.x/tos/platform/pc/GuiMsg.h:51, 
from /home/preeti/tinyosdir/tinyos- 
1.x/tos/types/dbg.h:70, 
from /home/preeti/tinyosdir/tinyos- 
1.x/tos/platform/pc/hardware.h:65, 
from 
/home/preeti/tinyosdir/tinyos-1.x/tos/system/tos.h:132:/home/preeti/tinyosdir/tinyos- 
1.x/tos/types/AM.h:155: parse error before 
`struct'/home/preeti/tinyosdir/tinyos- 1.x/tos/types/AM.h:156: parse 
error before 
`struct'/home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h:158: parse 
error before `struct' /home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h: 
In function 
`TOS_MsgLength':/home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h:183: 
parse error before `TOS_Msg'In file included from 
/home/preeti/tinyosdir/tinyos- 
1.x/tos/platform/pc/hardware.h:116, 
from /home/preeti/tinyosdir/tinyos- 
1.x/tos/system/tos.h:132:/home/preeti/tinyosdir/tinyos-1.x/tos/platform/pc/eeprom.c: 
At top level:/home/preeti/tinyosdir/tinyos- 
1.x/tos/platform/pc/eeprom.c:114: warning: declaration of `length' shadows 
global declaration /home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h:158: 
warning: location of shadowed declaration/home/preeti/tinyosdir/tinyos- 
1.x/tos/platform/pc/eeprom.c:144: warning: declaration of `length' shadows 
global declaration /home/preeti/tinyosdir/tinyos-1.x/tos/types/AM.h:158: 
warning: location of shadowed declarationmake: *** [build/pc/main.exe] 
Error 1 
Can anyone help 
please?Preeti

On 9/9/06, Sumit 
Gupta [EMAIL PROTECTED]  wrote: 


  Hi,make pc is a 
  command to compile which will store the compiled binary file in build 
  folder in your computer.For example: If you want to compile 
  application Blink stored in ../tinyos-1.x/apps/Blink/ then you need 
  to give following command:make platformthus for tossim (or PC platform), it 
  is: make pc (it 
  will store binary in .../Blink/build/pc/main.exe)and for other 
  platforms like mica2 it is: make mica2 (it will store binary in 
  .../Blink/build/mica2/main.exe)Now to run the file on TOSSIM 
  (which comes with Tinyos-1.x by defualt, thus u dont have to install it) - 
  stay in Blink directory and type:build/pc/main.exe number of nodes you want 
  to simulatethus for example for 10 nodes 
  network:build/pc/main.exe 10. 
  To see the result of simulation you have to learn more 
  about tinyos's tools and options and you might want to go through TOSSIM 
  tutorial located at http://www.tinyos.net/tinyos-1.x/doc/nido.pdfI 
  hope it helped.Sumit 
  
  On 9/8/06, preeti k  [EMAIL PROTECTED] 
   wrote:
  
  
  
  Hello there..i have been trying to install tinyos1.x on fedora 
  core 5 . I need to use tossim as well. i typed 'make pc ' on the 
  prompt to get tossim running but i could not. Can anyone help 
  please
  Preeti
  ___Tinyos-help 
  mailing listTinyos-help@Millennium.Berkeley.EDU https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help 
  ___Tinyos-help 
mailing listTinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help 
-- Sougata 
  SenBangalore 
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] Help me with raw data conversion

[Giovanni Petracca]

Yes, the motes are connected to PC by USB port. is 
this a problem? the increase here is of 4 to 5 degree celsius always. Someone have info in this problem? I have to

change the conversion formula?? 
thanks a lot

G. Petracca

- Original Message -

From: Ben Kelley

To: 'Giovanni Petracca' ; tinyos-help@Millennium.Berkeley.EDU


Sent: Monday, September 11, 2006 1:43

PM
Subject: RE: [Tinyos-help] Help me with raw

data conversion

Are the motes plugged into a USB port or by themselves? I

saw something of a 2 to 5 degree celsius increase when I did some tests with the 
external sensors when they were plugged into the USB cable.





From: [EMAIL PROTECTED]

[mailto:[EMAIL PROTECTED] On Behalf Of 
Giovanni PetraccaSent: Monday, September 11, 2006 
05:04To: tinyos-help@Millennium.Berkeley.EDUSubject:

[Tinyos-help] Help me with raw data conversion

Hi all,  i have two

questions to you; 1) i'm using Oscilloscope and Delta apps, and i want to 
convert raw data from ADC into SI data; i 'm using the paper "getting data from 
moteiv tmote sky sensors" at www.moteiv.com. the external temperature sensor 
give me a value = 6965 (1B35 in hex) that means a temperature of 30,05 ° C but 
in the room there is a temperature of maximum 25°! where is the problem? i've 
tried with other tmote sky modules but the value is the same. is this a problem 
dependent from sensor, software or is wrong the formula: temp=-39.60 + 0.01 * 
Reading ?2) when i log packets from oscilloscope or delta apps , i see 
that the "data" bytes in the multihopmsg are written from right to left, is it 
normal? i put the log below:1157967601703 Message MultiHopMsg 
 [sourceaddr=0x9] [originaddr=0x9]<B! r=""> [seqno=0x35f]

[originseqno=0x35f] [ttl=0x0] [id=0x21] [data="" 0x3 0x0 0x0

0x93 0xb 0x35 0x1b 0x52 0x4 0xbd 0x0 0x7e 0x0 0x3 0x0 0x7e 0x0 ]the 
"data " bytes are : the first four (0x5b 0x3 0x0 0x0) are seqno, after 2 bytes 
(0x93 0xb) needs to be read B93. and the others in the same mode. it's 
right??thank you for help me and sorry for the not so good 
english.ByeGiovanni 
Petracca__ Informazione NOD32 1.1748 
(20060911) __Questo messaggio è stato controllato dal Sistema 
Antivirus NOD32http://www.nod32.it
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] FW: Problems on switching back to tinyos-1.x

[Munaretto, Daniel]

 

-Original Message- 
From: Munaretto, Daniel 
Sent: Mon 9/11/2006 2:32 PM 
To: tinyos-help@Millennium.Berkeley.EDU 
Cc: 
Subject: Problems on switching back to tinyos-1.x


Dear all,
  i have some problems on switching back from 2.x to 1.x.
I'm able to compile Blink apps (it's a test) in tinyos2.x but when i 
switch back to tinyos1.x, i find the problem in the file attached on compiling 
the Blink app (under 1.x)  ...why?
 
i'm following the instructions in the web site and i also looked for it 
in the mailing list but i cannot find the solution. Is there something not 
backwardly compatible?...
 
Thanks in advance for any helps,
cheers
Daniele
 
 



check.rar
Description: check.rar
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Deluge 2.0 instalation problems.

[Orlando Delgadillo]

Im running TinyOS 1.1.15. and going through the tutorial as given in Deluge 
2.0-TinyosOS Network Programming.
Everything was going ok untill i tried to install the Golden image. Typing 
this command:


java net.tinyos.tools.Deluge --inject --tosimage=tos_image.xml --imgnum=0

This error returned is:

java.lang.NullPointerException
at net.tinyos.deluge.TOSBootImage.init(TOSBootImage.java:95)
at net.tinyos.tools.Deluge.execute(Deluge.java:263)
at net.tinyos.tools.Deluge.main(Deluge.java:322)
--
Exception in thread main java.lang.NullPointerException
at net.tinyos.deluge.TOSBootImage.getBytes(TOSBootImage.java:
202)
at net.tinyos.deluge.ImageInjector.init(ImageInjector.java:
64)
at net.tinyos.tools.Deluge.execute(Deluge.java:267)
at net.tinyos.tools.Deluge.main(Deluge.java:322)

What im i doing wrong??? am i missing something???
Thanks in advance
Orlando

_
realestate.com.au: the biggest address in property  
http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Frealestate%2Eninemsn%2Ecom%2Eau_t=754895450_r=Hotmail_end_text_m=EXT


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] TOSSIM 2.x doesn't run

[Munaretto, Daniel]

Dear all,
   following the tutorial and archive cause of some problems, i compiled Blink 
apps as:
 
make micaz sim- cygwin
 
in order to run then TOSSIM.
But after writing
from TOSSIM import *
in python environment, the bash displays no module named TOSSIM. Does it mean 
that with the sim- cygwin command i cannot run TOSSIM in tinyos-2.x?
 
cheers
Daniele

 


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Re: [Tinyos-devel] Fwd: [6lowpan] Re: Some comments aboutdraft-ietf-6lowpan-format-04

[Chang Li]

Is 6LowPan going to be an international standard?


This message went out on the IETF 6lowpan mailing list the other day.  
This IETF WG is exploring how to provide IP networking on low-power  
wireless (currently, just 802.15.4). I forwarded the message here in  
case anyone is interested in collaborating with David Green.


Begin forwarded message:

Would anyone in this group be interested in working on an open- 
source free (as in free beer) IPv6 6LowPAN stack for 802.15.4 if we  
make the project available? The license would likely be creative  
commons. The first target environment is a 32 bit ARM-7 controller.  
My company would supply the reference stack for all to hack on and  
compile for their architectures. We would do the ARM-7 port and  
hope others would port to their architectures and post. This would  
create a license free alternative to Zigbee so we can buy cheap  
sensor radios for our work.


If interested, please let me know. I believe we could have this set  
up by year's end.


David Green | VP of RD | Command Information
13655 Dulles Technology Drive, Suite 100 |  Herndon, VA 20171
O: 703.561.5937 | M: 703.899.9663 | [EMAIL PROTECTED]



Phil
___
Tinyos-devel mailing list
[EMAIL PROTECTED]
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-devel

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] repeating tests,no free memory

[Michael Schippling]

You need to return the same pointer that you get in receive(TOS_MsgPtr m),
the system will recycle it. There isn't any way for you to free it
yourself. Perhaps you can run your program under TOSSIM or something
so your can trace memory usage to see if you've really got a leak.
Otherwise you could have a runaway pointer or something that wouldn't
crash immediately...
MS

Munaretto, Daniel wrote:

Dear all,
   i discover a really strange behavior in my application. 
I repeat more times my code, and after some experiments the motes break down.

So there is a memory problem.
But i'm sure i free all the memory i allocate during the code. I'm using only a buffer and i re-use it all 
the times, instead i allocate memory with calloc() only for creating a chain which i delete at 
the end of each simulation with the free command and then i give NULL to the pointers.
So i don't understand where i lose memory each time i re-run the program 
(without re-booting the motes). i'm in tinyos 1.1.15,micaz motes.
I'm using the FlashBridge interface because i'm working on the flash.
I'm supposing that, may be, the problem is in the way Tinyos handles the packets 
received. For example, in the function event TOS_MsgPtr Receive.receive(TOS_MsgPtr 
m), before returning m, do i have to free it?But i can see it's wrong to do..
 
Please, if anyone knows where i have to find the waste of memory (may be some interfaces)...any helps will be really appreciated

thanks very much
cheers
Daniele

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Help me with raw data conversion

[Michael Schippling]

on question 2)...yes, data is sent low byte first (little-endian).
I'm not sure that the seqno is 4 bytes however. Look at the struct
and see if it is a long or int.
MS

Giovanni Petracca wrote:

Hi all,

   i have two questions to you;
1) i'm using Oscilloscope and Delta apps, and i want to convert raw data 
from ADC into SI data; i 'm using the paper getting data from moteiv 
tmote sky sensors at www.moteiv.com. the external temperature sensor 
give me a value = 6965 (1B35 in hex) that means a temperature of 30,05 ° 
C  but in the room there is a temperature of maximum 25°! where is the 
problem? i've tried with other tmote sky modules but the value is the 
same. is this a problem dependent from sensor, software or is wrong the 
formula: temp=-39.60 + 0.01 * Reading ?


2) when i log packets from oscilloscope or delta apps , i see that the 
data bytes in the multihopmsg are written from right to left, is it 
normal? i put the log below:


1157967601703 Message MultiHopMsg
  [sourceaddr=0x9]
  [originaddr=0x9]   [seqno=0x35f]
  [originseqno=0x35f]
  [ttl=0x0]
  [id=0x21]
  [data=0x5b 0x3 0x0 0x0 0x93 0xb 0x35 0x1b 0x52 0x4 0xbd 0x0 0x7e 0x0 
0x3 0x0 0x7e 0x0 ]


the data  bytes are : the first four (0x5b 0x3 0x0 0x0) are seqno, 
after 2 bytes (0x93 0xb) needs to be read B93. and the others in the 
same mode. it's right??


thank you for help me and sorry for the not so good english.

Bye

Giovanni Petracca




___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TOSSIM 2.x doesn't run

[Philip Levis]

On Sep 11, 2006, at 6:42 AM, Munaretto, Daniel wrote:


Dear all,
   following the tutorial and archive cause of some problems, i  
compiled Blink apps as:


make micaz sim- cygwin

in order to run then TOSSIM.
But after writing
from TOSSIM import *
in python environment, the bash displays no module named TOSSIM.  
Does it mean that with the sim- cygwin command i cannot run TOSSIM  
in tinyos-2.x?


You need to add tinyos-2.x/support/sdk/python to your PYTHONPATH  
variable.


Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Make mica compiling problem

[Philip Levis]

On Sep 11, 2006, at 2:16 AM, walid hamdi wrote:


make pc is ok but make mica leads to this error:

make mica
compiling Blink to a mica binary
ncc -o build/mica/main.exe -Os -board=micasb
-target=mica  -Wall -Wshadow -DDEF_TOS_AM_GROUP=0x7d
-Wnesc-all -finline-limit=10
-fnesc-cfile=build/mica/app.c  Blink.nc -lm
/tmp/ccLWz2B6.s: Assembler messages:
/tmp/ccLWz2B6.s:10: Error: unknown opcode `disablecou'
/tmp/ccLWz2B6.s:12: Error: unrecognized symbol type 
/tmp/ccLWz2B6.s:12: Error: unknown opcode `disablecou'
/tmp/ccLWz2B6.s:13: Error: expected comma after name
`HPLPowerManagementM' in .size directive
/tmp/ccLWz2B6.s:13: Error: unknown opcode `disablecou'
/tmp/ccLWz2B6.s:14: Error: unknown opcode `hplpowerma'
/tmp/ccLWz2B6.s:43: Error: unrecognized symbol type 
/tmp/ccLWz2B6.s:43: Error: unknown opcode `doadjustme'
/tmp/ccLWz2B6.s:44: Error: unknown opcode `hplpowerma'
/tmp/ccLWz2B6.s:120: Error: expected comma after name
`HPLPowerManagementM' in .size directive
/tmp/ccLWz2B6.s:120: Error: unknown opcode
`doadjustme'
...
...
/tmp/ccLWz2B6.s:730: Error: missing size expression
/tmp/ccLWz2B6.s:730: Error: unknown opcode `ledson'
make: *** [build/mica/main.exe] Error 1

I am using Ubuntu 6.06 withthe following TinyOS
features:
Version: ncc: 1.2alpha5
nesc: 1.2.7a (latest version)
Version: avr-gcc (GCC) 3.4.3
uisp version 20050519tinyos
GNU assembler 2.15
GNU gdb 6.3

Note that everything i have got is the last version,
i have no avarice, and no msp430-gcc, as i will not
use Telos sensors at the moment..

could anybody help please!



Check the FAQ:

http://www.tinyos.net/faq.html#SEC-104

Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] interrupts and async events question

[Adam]

Since variables in async function can be preempted by another interupt, then
we need add atomic keyword to protect them. Unfortunately, I notice
atomic section is ignored in async function when it is converted to
app.c -- see following instance:

I have tried to compare SurgeM.nc with app.c under build/telosb. I notice
this atomic section is not atomic in app.c -- is this a bug? Or when the
atomic keyword will be ignored?

  async event result_t ADC.dataReady(uint16_t data) {  
atomic {
  if (!gfSendBusy) {
gfSendBusy = TRUE; 
gSensorData = data;
post SendData();
  }
}
return SUCCESS;
  } 

The corresponding code in app.c is

# 222 SurgeM.nc
static inline   result_t SurgeM$Sensor$dataReady(uint16_t data)
#line 222
{

  {
  }
#line 224
  ;
  {
if (!SurgeM$gfSendBusy) {
SurgeM$gfSendBusy = TRUE;
SurgeM$gSensorData = data;
TOS_post(SurgeM$SendData);
  }
  }

  return SUCCESS;
}

There should be __nesc_atomic_t __nesc_atomic = __nesc_atomic_start(); to
replace atomic. How to explain this? A bug???


-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Philip
Levis
Sent: Sunday, September 10, 2006 2:31 PM
To: jose m
Cc: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help] interrupts and async events question

On Sep 9, 2006, at 7:33 AM, jose m wrote:


 Conor Todd says that the async events can't be interrupted by another 
 interrupt. Philip Levis says that te interrupts are enabled when an 
 interrupt declared with the INTERRUPT keyword is running (and so every 
 async event signalled by this one). What's the true?

The latter.

There are two VERY SEPARATE considerations: whether code can preempt, and
whether it can be preempted. There are well established (and
accepted) reasons why low-level systems must distinguish the two behaviors;
attempts to unify them (generally) lead to problems when implementing
certain basic abstractions, and therefore the possible benefit from unifying
them is completely outweighed by the limitations it places.

By default (tasks), TinyOS code cannot preempt other code. The async keyword
indicates that code can preempt running code. Therefore, variables which are
accessed within an async function need to have proper protection so that
data races do not occur.

By default, TinyOS code can be preempted (e.g., by async code). The atomic
keyword indicates that a statement is not preemptible (at least, in a
fashion that is not atomic). Therefore, variables which are accessed from
async code -- meaning they can have preemptive accesses -- must be in an
atomic statement or there is a data race.

Many interrupt handlers are declared so that their entire body executes in
an atomic block, therefore cannot be preempted. However, this is determined
by the call root, and not by async functions themselves.

Examples from more traditional systems:

async POSIX signals: can preempt, cannot be preempted (signals do not
execute recursively)

interrupt handlers: in most *IX oses, an interrupt top half preempts and
cannot be preempted, while the bottom half preempts and can be preempted

Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [tinyos-help] TinyOS 2.0 lacks of TEP104 and 105

[Philip Levis]

On Sep 11, 2006, at 4:45 AM, Tie Luo wrote:

I believe both TEP 104 (Radio Physical Layer) and TEP 105 (Radio  
Link Layer) are interesting parts and deserve effort, especially  
for those working on physical and MAC layers rather than higher  
layers.


Can I take a look at the latest draft on TEP105 (since 104 is not  
available), although it may be incomplete or a bit stale? Thanks.




The old version of 105 (authored by Joe) lives in tinyos-1.x/beta/ 
teps/txt/tep105.txt. 104 lives there as well.


If you'd like a different version of 105 that reflects current TinyOS  
2.x code, then contacting David Culler is your best bet.


Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] RSSI value on micaz

[Adam Scheuring]

Dear list members,
Im making measurements of received radio signal strength of micaz
motes. My setup contains a transmitter and a receiver. The receiver is
connected to a MIB520 board and im changing the distance between the
transmitter and the receiver to get a rssi-range characteristic.
I have the following problem: i have programmed the transmitter's
radio to 0dBm and -25dBm transmit power and the none the
characteristic nor the values were changed significantly. I have
checked that they are really programmed to different transmit power
leves by checking the maximum transmit range, but the RSSI values were
nearly the same in both cases.
Is it possible that the RSSI calculates with the transmitter's power?
I have only found this in the Chipcon CC2420 datasheet:

CC2420 has a built-in RSSI (Received Signal Strength Indicator)
giving a digital value that can be read form the 8 bit, signed 2's
complement RSSI.RSSI_VAL register. The RSSI value is always averaged
over 8 symbol periods (128 μs), in accordance with [1]. The RSSI_VALID
status bit (Table 5) indicates when the RSSI value is valid, meaning
that the receiver has been enabled for at least 8 symbol periods. The
RSSI register value RSSI.RSSI_VAL can be referred to the power P at
the RF pins by using the following equations: P = RSSI_VAL +
RSSI_OFFSET [dBm] where the RSSI_OFFSET is found empirically during
system development from the front end gain. RSSI_OFFSET is
approximately �C45. E.g. if reading a value of �C20 from the RSSI
register, the RF input power is approximately �C65 dBm.

Thanks for your help in advance
Adam Scheuring

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] RSSI value on micaz

[Philip Levis]

On Sep 11, 2006, at 9:12 AM, Adam Scheuring wrote:


Dear list members,
Im making measurements of received radio signal strength of micaz
motes. My setup contains a transmitter and a receiver. The receiver is
connected to a MIB520 board and im changing the distance between the
transmitter and the receiver to get a rssi-range characteristic.
I have the following problem: i have programmed the transmitter's
radio to 0dBm and -25dBm transmit power and the none the
characteristic nor the values were changed significantly. I have
checked that they are really programmed to different transmit power
leves by checking the maximum transmit range, but the RSSI values were
nearly the same in both cases.
Is it possible that the RSSI calculates with the transmitter's power?
I have only found this in the Chipcon CC2420 datasheet:



It's not calculated with the transmitter's power. You should see  
different RSSI values.


My best guess is that the way you're changing the transmit power  
isn't working.


Phil


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] RSSI value on micaz

[Michael Collett]

It's likely that you are not actually changing the transmit power. Other people 
have had a similar problems:

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-September/019053.html

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-September/019026.html

It's all about keeping track of what header files are being included by your 
code, and changing all the right ones. The help archives should point you in 
the right direction...

Mike

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Philip
Levis
Sent: 11 September 2006 17:36
To: Adam Scheuring
Cc: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help] RSSI value on micaz


On Sep 11, 2006, at 9:12 AM, Adam Scheuring wrote:

 Dear list members,
 Im making measurements of received radio signal strength of micaz
 motes. My setup contains a transmitter and a receiver. The receiver is
 connected to a MIB520 board and im changing the distance between the
 transmitter and the receiver to get a rssi-range characteristic.
 I have the following problem: i have programmed the transmitter's
 radio to 0dBm and -25dBm transmit power and the none the
 characteristic nor the values were changed significantly. I have
 checked that they are really programmed to different transmit power
 leves by checking the maximum transmit range, but the RSSI values were
 nearly the same in both cases.
 Is it possible that the RSSI calculates with the transmitter's power?
 I have only found this in the Chipcon CC2420 datasheet:


It's not calculated with the transmitter's power. You should see  
different RSSI values.

My best guess is that the way you're changing the transmit power  
isn't working.

Phil


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

---
This e-mail and any attachments may contain confidential and/or
privileged material; it is for the intended addressee(s) only.
If you are not a named addressee, you must not use, retain or
disclose such information.

NPL Management Ltd cannot guarantee that the e-mail or any
attachments are free from viruses.

NPL Management Ltd. Registered in England and Wales. No: 2937881
Registered Office: Serco House, 16 Bartley Wood Business Park,
   Hook, Hampshire, United Kingdom  RG27 9UY
---

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: RE: [Tinyos-help] RSSI value on micaz

[Adam Scheuring]

Thanks for your help
I use xbow's CntToLedsAndRfm application to send the packets so I
thought changing the RF power in the MakeXbowlocal file was going to
work.

On 9/11/06, Michael Collett [EMAIL PROTECTED] wrote:

It's likely that you are not actually changing the transmit power. Other people 
have had a similar problems:

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-September/019053.html

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2006-September/019026.html

It's all about keeping track of what header files are being included by your 
code, and changing all the right ones. The help archives should point you in 
the right direction...

Mike

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Philip
Levis
Sent: 11 September 2006 17:36
To: Adam Scheuring
Cc: tinyos-help@Millennium.Berkeley.EDU
Subject: Re: [Tinyos-help] RSSI value on micaz


On Sep 11, 2006, at 9:12 AM, Adam Scheuring wrote:

 Dear list members,
 Im making measurements of received radio signal strength of micaz
 motes. My setup contains a transmitter and a receiver. The receiver is
 connected to a MIB520 board and im changing the distance between the
 transmitter and the receiver to get a rssi-range characteristic.
 I have the following problem: i have programmed the transmitter's
 radio to 0dBm and -25dBm transmit power and the none the
 characteristic nor the values were changed significantly. I have
 checked that they are really programmed to different transmit power
 leves by checking the maximum transmit range, but the RSSI values were
 nearly the same in both cases.
 Is it possible that the RSSI calculates with the transmitter's power?
 I have only found this in the Chipcon CC2420 datasheet:


It's not calculated with the transmitter's power. You should see
different RSSI values.

My best guess is that the way you're changing the transmit power
isn't working.

Phil


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

---
This e-mail and any attachments may contain confidential and/or
privileged material; it is for the intended addressee(s) only.
If you are not a named addressee, you must not use, retain or
disclose such information.

NPL Management Ltd cannot guarantee that the e-mail or any
attachments are free from viruses.

NPL Management Ltd. Registered in England and Wales. No: 2937881
Registered Office: Serco House, 16 Bartley Wood Business Park,
   Hook, Hampshire, United Kingdom  RG27 9UY
---

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] repeating tests,no free memory

[David Moss]

Daniele,

This was one thing I noticed about the code I looked at but failed to warn
against, because I didn't know any better until I read up on it afterwards.

Below are a few emails from this list that may point you in the right
direction.

-David

https://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-February/007
712.html :

The TinyOS programming methodology frowns on malloc, for several 
reasons:

1) No memory protection so you can smash your stack
2) Unforeseen rate mismatches can cause you to do 1 (you start 
receiving packets faster than you can forward them)
3) Event-driven execution models can make free()ing a hard thing to do 
right (hence pool allocations, etc.)

If you want dynamic allocation, look at TinyAlloc (which Joe 
mentioned). It allows you to allocate a static chunk of RAM which you 
then parcel out dynamically. But using it in the presence of 
conflicting components is a recipe for disaster. Systems such as TinyDB 
get away with it because all their parts are designed to work together.

Phil



Hi all,

  Refer to the paper The NesC Language: A Holistic Approach to
Networked Embedded Systems, dynamic memory allocation and function
pointers are prohibited in NesC language. For dynamic memory
allocation, it's quite clear to me why we can't use it in TinyOS as
refered to
https://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-February/007
712.html
. We can use TinyAlloc or MemAlloc instead of directly calling
malloc() and so on. But for function pointers, it's not clear to me
that we can or can't use it in TinyOS. What would be the problems if I
use that?




Short answer: it leads to more reliable code.

Long answer:

Here's a pointer (haha!):

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-February/0077
12.html

There's a difference between malloc() and dynamic allocation. nesC  
does not forbid dynamic memory allocation: there's nothing stopping  
you from writing a component that allocates a pool of memory and has  
dynamic allocation interfaces. Take a look at TinyAlloc, for example.

nesC does, however, frown on malloc, for the reasons described in the  
above mail. Modern coding styles generally assume unbounded memory,  
in as much that you have swap space so will see tremendous  
performance degradation before the system crashes. General  
application behavior on allocation failure is to exit(2) and  
therefore deallocate everything. With a processes, multitasking, and  
automatic page reclamation, this works fine. But on an embedded  
system with no memory protection, well, it's not so clean.

Part of the issue is that while dynamic allocation among a set of  
cooperating components can work fine (e.g., TinyDB, Ben Greenstein  
@UCLA's work on signal processing), dynamic allocation between  
arbitrary components (a single shared pool) is a recipe for disaster.  
One bad component can bring the entire system down, as the shared  
resource breaks inter-component isolation.

The reason why nesC frowns on function pointers is because they are  
dangerous and except for a few edge cases (e.g., dynamically linking  
new binary modules), unnecessary. You know the call graph at compile- 
time. Instead of storing a function pointer in memory, which could be  
corrupted and lead you to jump to certain doom, you can just use a  
parameterized interface and call based on a function ID. This also  
gives you type checking for the functions It is more robust, just as  
easy (once you get used to it), and generally uses less RAM (no need  
to store the pointer). Function pointers are a basic result of C's  
linking model. nesC's linking model does not have the same  
complications (interfaces are bidirectional), so you can avoid them.

Phil

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Munaretto,
Daniel
Sent: Monday, September 11, 2006 1:51 AM
To: tinyos-help@Millennium.Berkeley.EDU
Subject: [Tinyos-help] repeating tests,no free memory


Dear all,
   i discover a really strange behavior in my application. 
I repeat more times my code, and after some experiments the motes break
down.
So there is a memory problem.
But i'm sure i free all the memory i allocate during the code. I'm using
only a buffer and i re-use it all the times, instead i allocate memory with
calloc() only for creating a chain which i delete at the end of each
simulation with the free command and then i give NULL to the pointers.
So i don't understand where i lose memory each time i re-run the program
(without re-booting the motes). i'm in tinyos 1.1.15,micaz motes.
I'm using the FlashBridge interface because i'm working on the flash.
I'm supposing that, may be, the problem is in the way Tinyos handles the
packets received. For example, in the function event TOS_MsgPtr
Receive.receive(TOS_MsgPtr m), before returning m, do i have to free it?But
i can see it's wrong to do..
 
Please, if anyone knows where i have to find the waste of memory 

[Tinyos-help] TinyOS 2.x CC1000

[David Moss]

Title: Message



Still working with 
this problem - 

I downloaded TinyOS 
2.x beta2 to three computers now, and have tried compiling/installing the 
RadioCountToLeds app from all three computers onto a mix of mica2 motes, 
including regular mica2's and mica2 OEM's.I can see that their radio 
sendDone events are called correctly by editing the code to toggle the leds when 
sendDone is called, but nothing is being transmitted over the radio. 


I have verified 
nothing is being transmitted by using A) another mote programmed up with 
RadioCountToLeds which receives nothing, B)a BaseStation mote that 
receives nothing, and C) a spectrum analyzer that shows no transmissions in the 
902-928 MHz band.

I can usually nail 
these problems down to something, but on this one I'm stuck. Any ideas on 
where to look?

-David
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

RE: [Tinyos-help] repeating tests,no free memory

[David Moss]

And you shouldn't have to free anything in TinyOS.  The message you received
was not dynamically allocated. Just use its pointer in the receive event,
return it, and forget it.

-David

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Moss
Sent: Monday, September 11, 2006 10:56 AM
To: 'Munaretto, Daniel'; tinyos-help@Millennium.Berkeley.EDU
Subject: RE: [Tinyos-help] repeating tests,no free memory


Daniele,

This was one thing I noticed about the code I looked at but failed to warn
against, because I didn't know any better until I read up on it afterwards.

Below are a few emails from this list that may point you in the right
direction.

-David

https://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-February/007
712.html :

The TinyOS programming methodology frowns on malloc, for several 
reasons:

1) No memory protection so you can smash your stack
2) Unforeseen rate mismatches can cause you to do 1 (you start 
receiving packets faster than you can forward them)
3) Event-driven execution models can make free()ing a hard thing to do 
right (hence pool allocations, etc.)

If you want dynamic allocation, look at TinyAlloc (which Joe 
mentioned). It allows you to allocate a static chunk of RAM which you 
then parcel out dynamically. But using it in the presence of 
conflicting components is a recipe for disaster. Systems such as TinyDB 
get away with it because all their parts are designed to work together.

Phil



Hi all,

  Refer to the paper The NesC Language: A Holistic Approach to
Networked Embedded Systems, dynamic memory allocation and function
pointers are prohibited in NesC language. For dynamic memory
allocation, it's quite clear to me why we can't use it in TinyOS as
refered to
https://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-February/007
712.html
. We can use TinyAlloc or MemAlloc instead of directly calling
malloc() and so on. But for function pointers, it's not clear to me
that we can or can't use it in TinyOS. What would be the problems if I
use that?




Short answer: it leads to more reliable code.

Long answer:

Here's a pointer (haha!):

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-February/0077
12.html

There's a difference between malloc() and dynamic allocation. nesC  
does not forbid dynamic memory allocation: there's nothing stopping  
you from writing a component that allocates a pool of memory and has  
dynamic allocation interfaces. Take a look at TinyAlloc, for example.

nesC does, however, frown on malloc, for the reasons described in the  
above mail. Modern coding styles generally assume unbounded memory,  
in as much that you have swap space so will see tremendous  
performance degradation before the system crashes. General  
application behavior on allocation failure is to exit(2) and  
therefore deallocate everything. With a processes, multitasking, and  
automatic page reclamation, this works fine. But on an embedded  
system with no memory protection, well, it's not so clean.

Part of the issue is that while dynamic allocation among a set of  
cooperating components can work fine (e.g., TinyDB, Ben Greenstein  
@UCLA's work on signal processing), dynamic allocation between  
arbitrary components (a single shared pool) is a recipe for disaster.  
One bad component can bring the entire system down, as the shared  
resource breaks inter-component isolation.

The reason why nesC frowns on function pointers is because they are  
dangerous and except for a few edge cases (e.g., dynamically linking  
new binary modules), unnecessary. You know the call graph at compile- 
time. Instead of storing a function pointer in memory, which could be  
corrupted and lead you to jump to certain doom, you can just use a  
parameterized interface and call based on a function ID. This also  
gives you type checking for the functions It is more robust, just as  
easy (once you get used to it), and generally uses less RAM (no need  
to store the pointer). Function pointers are a basic result of C's  
linking model. nesC's linking model does not have the same  
complications (interfaces are bidirectional), so you can avoid them.

Phil

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Munaretto,
Daniel
Sent: Monday, September 11, 2006 1:51 AM
To: tinyos-help@Millennium.Berkeley.EDU
Subject: [Tinyos-help] repeating tests,no free memory


Dear all,
   i discover a really strange behavior in my application. 
I repeat more times my code, and after some experiments the motes break
down.
So there is a memory problem.
But i'm sure i free all the memory i allocate during the code. I'm using
only a buffer and i re-use it all the times, instead i allocate memory with
calloc() only for creating a chain which i delete at the end of each
simulation with the free command and then i give NULL to the pointers.
So i don't understand where i lose memory each time i re-run the 

[Tinyos-help] --help on CC2420 radio messaging

[Madhu Mudigonda]

Hello ,How to send radio messages directly over CC2420 without using GenericComm and AMStandard?What I mean is, how should be the packet structure?Any kind of help is appreciated. Thanks in advance.
Thanks- Madhu Mudigonda
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] RE: TinyOS 2.x Mica2 OEM

[David Moss]

I've also now tried it on regular mica2's with the same results, using
several different computers with clean 2.x beta2 installations.

I'll keep looking into it.

-David

-Original Message-
From: David Gay [mailto:[EMAIL PROTECTED] 
Sent: Monday, September 11, 2006 12:03 PM
To: David Moss
Cc: tinyos-help@millennium.berkeley.edu
Subject: Re: TinyOS 2.x Mica2 OEM


On 9/8/06, David Moss [EMAIL PROTECTED] wrote:
 I have TinyOS 2.x beta2 installed on two different computers with no
 modifications.  When I attempt to program RadioCountToLeds onto several
 mica2 OEM's, none of them talk to each other.

 There are a few minor hardware differences between the OEM and the regular
 mica2, but there shouldn't be any differences on the radio end.  Has
anyone
 encountered this issue?

No, but I don't have any mica2 oem modules, so I can't test for this...

David Gay


___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] --help on telosb mote battery-ADC

[Madhu Mudigonda]

Hello,I want to read the battery voltage of the mote from the ADC on the telosb mote? Is there any connection to ADC from battery terminals on telosb mote? Does telosb mote has such kind of connecsiotns between ADC and battery.
if anybody have knowledge on this, please provide information.Any kind of help is appreciated.Thanks in advance.Thanks-- Madhu MudigondaGraduate StudentPh.# 216-856-0127Fax.#: 360-233-0127
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] --help on telosb mote battery-ADC

[R. Steve McKown]

On Monday 11 September 2006 01:07 pm, Madhu Mudigonda wrote:
 I want to read the battery voltage of the mote from the ADC on the telosb
 mote? Is there any connection to ADC from battery terminals on telosb mote?

If you're using TinyOS 2.x, look at $TOSROOT/tos/platforms/telosb/DemoSensorC, 
which reads the system voltage using the MSP430's internal voltage channel 
connected to the ADC peripheral.  Note that the channel actually reads 1/2 * 
Vcc.
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TinyOS 2.x CC1000

[Conor Todd]

Is the radio on? Has it had enough time to power up? Is it tuned correctly? Have you done the Truffle Shuffle?

 - Conor
On 9/11/06, David Moss [EMAIL PROTECTED] wrote:



Still working with this problem - 

I downloaded TinyOS 2.x beta2 to three computers now, and have tried compiling/installing the RadioCountToLeds app from all three computers onto a mix of mica2 motes, including regular mica2's and mica2 OEM's.I
 can see that their radio sendDone events are called correctly by editing the code to toggle the leds when sendDone is called, but nothing is being transmitted over the radio. 


I have verified nothing is being transmitted by using A) another mote programmed up with RadioCountToLeds which receives nothing, B)a BaseStation mote that receives nothing, and C) a spectrum analyzer that shows no transmissions in the 902-928 MHz band.


I can usually nail these problems down to something, but on this one I'm stuck. Any ideas on where to look?

-David___Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
-- Thought is only a flash in the middle of a long night, but the flash that means everything.- Poincaré-=-=-=-=-=-=-=-=-I'm going to run the Houston Marathon, but finishing's not my only goal: help me raise money for cancer research!
http://www.active.com/donate/tnttxgc/tnttxgcCToddThanks! 
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Display receive message on screen and store in a file

[bhushan bhatt]

Hi everyone, I would like to dispaly all the messages received by the mote connected to the computer acting as base station to display on the screen and save it in the file. i have tried working with Delta application ot Moteiv and it works fine. I want to know how can i use the similar application for my program. Any feedback is appreciated.Thanks,Bhushan 
		How low will we go? Check out Yahoo! Messenger’s low  PC-to-Phone call rates.___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] TinyOS 2.x CC1000

[Philip Levis]

On Sep 11, 2006, at 2:09 PM, Conor Todd wrote:

Is the radio on?  Has it had enough time to power up?  Is it tuned  
correctly?  Have you done the Truffle Shuffle?




Given that these are stock apps (RadioCountToLeds), they use the  
SplitControl interface, respond to power-up, and tune the radio.


I'll take a look tomorrow to verify that the app works for me.

Phil
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Compile Mate error message

[Hui KANG]

Dr. Levis:
I installed Mate on tinyos-1.x v 1.1.15. When I make pc for BombillaMica,
I have the following error message. I checked out VM and script from CVS.
Could you check it? Thanks.

In file included from
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/tos.h:190
:
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/Ident.h:55:
`MateTopLevel' unde
clared here (not in a function)
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/Ident.h:55: initializer
element
 is not constant
C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/Ident.h:55: (near
initializatio
n for `G_Ident.program_name')
make: *** [vm_specific/BombillaMicaVMConstants.java] Interrupt

Regards,
Hui

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] sync and async event

[yicheng]

Hi Folks,



I get some questions about event:

1. Is Timer fired event or sendDone
sync event? Is it true that by default, if an event isnt explicitly declared
as async, then its synchronous, which means it cant
interrupt other events or tasks?

2. If the above is true - all events that arent
explicitly declared as async are synchronous events, then are
they all in the same level of priority? whats the difference between event
and task?

Thanks!



Best Regards!

Yicheng






___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Custom Sensor

[DoomaR]

Hello all

Ive a general question about the available Wireless
sensor network modules I think they are called motes??-

Is designing a custom sensors for an available mote lets
say the MICA2 -straight forward?

And if so, how to get/set data from the sensor? Does it has
an address or something? And how to specify it when designing?












___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Re: Compile Mate error message

[Hui KANG]

 It looks like it's picking it up (hence the statement that  
 MateTopLevel isn't defined), but there's something wrong with the  
 parentheses. The idea is that \ at the command line should  
 translate to  in the actual define, so you get

 MateTopLevel

 but for some reason that isn't working, so the define is

 MateTopLevel

 which C doesn't recognize as an OK string (hence, saying it's an  
 undeclared identifier).

 Given that Mate doesn't use Ident.h, I'd suggest putting a copy of  
 Ident.h in your app directory and remove the offending line.

Dr. Levis:
What do you mean by removing the offending line? Which file does you
refer to
Makefile or Ident.h.
The Ident.h in my tinyos system has
static const Ident_t G_Ident = {
  unix_time : IDENT_UNIX_TIME,
  user_hash : IDENT_USER_HASH,
  program_name : IDENT_PROGRAM_NAME,
};

Thanks.

Regards,
Hui



On 9/11/2006, Philip Levis [EMAIL PROTECTED] wrote:


On Sep 11, 2006, at 2:54 PM, Hui KANG wrote:


 Dr. Levis:
 I installed Mate on tinyos-1.x v 1.1.15. When I make pc for
 BombillaMica,
 I have the following error message. I checked out VM and script
 from CVS.
 Could you check it? Thanks.

 In file included from
 C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/tos.h:190
 :
 C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/Ident.h:55:
 `MateTopLevel' unde
 clared here (not in a function)
 C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/Ident.h:55:
 initializer
 element
  is not constant
 C:/PROGRA~1/UCB/cygwin/opt/tinyos-1.x/tos/system/Ident.h:55: (near
 initializatio
 n for `G_Ident.program_name')
 make: *** [vm_specific/BombillaMicaVMConstants.java] Interrupt

 Regards,
 Hui

This thread from July 2005 goes into the problem:

http://mail.millennium.berkeley.edu/pipermail/tinyos-help/2005-July/
010483.html

Phil

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

[Tinyos-help] Delta Application

[Sumit Gupta]

Hi all,

I need to know about this application which applies Multihop Routing.
Where it is located in TinyOs tree? I tried to search it but I found
too many files at different location. Can any1 tell me tht.

Regards,
Sumit 
___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] --help on telosb mote battery-ADC

[siva prasad]

yes..there r 10+6 external ports on the mote...

go through the moteiv quick start guide...andsee the following links..it is briefly explained there...

http://www.moteiv.com/community/Moteiv_Community
http://www.moteiv.com/community/Connecting_External_Sensors
i hope this helps


On 9/11/06, R. Steve McKown [EMAIL PROTECTED] wrote:
On Monday 11 September 2006 01:07 pm, Madhu Mudigonda wrote: I want to read the battery voltage of the mote from the ADC on the telosb
 mote? Is there any connection to ADC from battery terminals on telosb mote?If you're using TinyOS 2.x, look at $TOSROOT/tos/platforms/telosb/DemoSensorC,which reads the system voltage using the MSP430's internal voltage channel
connected to the ADC peripheral.Note that the channel actually reads 1/2 *Vcc.___Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Delta Application

[Chalermphol T.]

I guess, you just missed p.19 of the moteiv's tmote - Quick Start Guide.

Good Luck,
Chalermphol
On 9/12/06, Sumit Gupta [EMAIL PROTECTED] wrote:

Hi all,I need to know about this application which applies Multihop Routing. Where it is located in TinyOs tree? I tried to search it but I found too many files at different location. Can any1 tell me tht.
Regards,
Sumit ___Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help

Re: [Tinyos-help] Delta Application

[Sumit Gupta]

hi,

The guide which I have only 18 pages. I think you are talking about the
upgraded version of software. The CD i have doesnt install in that way
which is mentioned (just seen online the new guide) on the guide which
you are refering. I am using the older version and it doesnt have a the
directory moteiv at all on it.

I guess I will use SurgeTelos Application for Multihop Routing as I
dont have a newer version of software. I hope it will be fine for
testing purpose. Isn't it?

Please advice.

Regards,
SumitOn 9/11/06, Chalermphol T. [EMAIL PROTECTED] wrote:
I guess, you just missed p.19 of the moteiv's tmote - Quick Start Guide.

Good Luck,
Chalermphol
On 9/12/06, Sumit Gupta 
[EMAIL PROTECTED] wrote:

Hi all,I need to know about this application which applies
Multihop Routing. Where it is located in TinyOs tree? I tried to search
it but I found too many files at different location. Can any1 tell me
tht.
Regards,
Sumit ___Tinyos-help mailing list

Tinyos-help@Millennium.Berkeley.EDUhttps://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help



___
Tinyos-help mailing list
Tinyos-help@Millennium.Berkeley.EDU
https://mail.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help