-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathapp.xml
11661 lines (11661 loc) · 754 KB
/
app.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<nesc xmlns="http://www.tinyos.net/nesC">
<components>
<component qname="SRTreeAppC" loc="3:SRTreeAppC.nc" safe="">
<configuration/>
</component>
<component qname="SRTreeC" loc="3:SRTreeC.nc">
<module/>
</component>
<component qname="MainC" loc="47:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/MainC.nc">
<configuration/>
</component>
<component qname="PlatformC" loc="41:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/PlatformC.nc">
<documentation loc="32:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/PlatformC.nc">
<short> The default simulation platform, which does nothing.</short>
<long> The default simulation platform, which does nothing. @author Phil Levis @date November 22 2005 </long>
</documentation>
<module/>
</component>
<component qname="SimMainP" loc="43:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/SimMainP.nc">
<module/>
</component>
<component qname="TinySchedulerC" loc="42:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/TinySchedulerC.nc">
<documentation loc="32:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/TinySchedulerC.nc">
<short> TOSSIM-specific scheduler implementation, which models tasks as simulation events (in order to capture delay).</short>
<long> TOSSIM-specific scheduler implementation, which models tasks as simulation events (in order to capture delay). @author Philip Levis @date Nov 22 2005 </long>
</documentation>
<configuration/>
</component>
<component qname="SimSchedulerBasicP" loc="47:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/SimSchedulerBasicP.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/sim_event_queue.h">
<short> The event queue is the core of the mote side of TOSSIM.</short>
<long> The event queue is the core of the mote side of TOSSIM. It is a wrapper around the underlying heap. Unlike the 1.x version, it is not re-entrant: merging the Python console and TOSSIM means that functionality like packet injection/reception from external tools is on the Python side. @author Phil Levis @date November 22 2005 </long>
</documentation>
<module/>
</component>
<component qname="SimMoteP" loc="46:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/SimMoteP.nc">
<module/>
</component>
<component qname="ActiveMessageC" loc="42:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/ActiveMessageC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/ActiveMessageC.nc">
<short> The basic chip-independent TOSSIM Active Message layer for radio chips that do not have simulation support.</short>
<long> The basic chip-independent TOSSIM Active Message layer for radio chips that do not have simulation support. @author Philip Levis @date December 2 2005 </long>
</documentation>
<configuration/>
</component>
<component qname="TossimActiveMessageC" loc="44:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/TossimActiveMessageC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/TossimActiveMessageC.nc">
<short> The basic chip-independent TOSSIM Active Message layer for radio chips that do not have simulation support.</short>
<long> The basic chip-independent TOSSIM Active Message layer for radio chips that do not have simulation support. @author Philip Levis @date December 2 2005 </long>
</documentation>
<module/>
</component>
<component qname="TossimPacketModelC" loc="60:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/TossimPacketModelC.nc">
<documentation loc="32:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/sim_csma.h">
<short> Configuration parameters for a CSMA link.</short>
<long> Configuration parameters for a CSMA link. @author Philip Levis @date Dec 10 2005 </long>
</documentation>
<module/>
</component>
<component qname="CpmModelC" loc="53:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/CpmModelC.nc">
<module/>
</component>
<component qname="ActiveMessageAddressC" loc="57:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/ActiveMessageAddressC.nc">
<documentation loc="49:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/ActiveMessageAddressC.nc">
<short> Accessor methods for Active Messages.</short>
<long> Accessor methods for Active Messages. @author Philip Levis @author Morten Tranberg Hansen (added ActiveMessageAddress) @date June 19 2005 </long>
</documentation>
<module/>
</component>
<component qname="RandomC" loc="43:/home/tinyos/local/src/tinyos-2x/tos/system/RandomC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/RandomC.nc">
<short> The standard TinyOS random number generator.</short>
<long> The standard TinyOS random number generator. If your system requires a specific random number generator, it should wire to that component directly. @author Barbara Hohlt @author Phil Levis @date March 1 2005 </long>
</documentation>
<configuration/>
</component>
<component qname="RandomMlcgC" loc="45:/home/tinyos/local/src/tinyos-2x/tos/system/RandomMlcgC.nc" safe="">
<documentation loc="32:/home/tinyos/local/src/tinyos-2x/tos/system/RandomMlcgC.nc">
<short> This code is a fast implementation of the Park-Miller Minimal Standard Generator for pseudo-random numbers.</short>
<long> This code is a fast implementation of the Park-Miller Minimal Standard Generator for pseudo-random numbers. It uses the 32 bit multiplicative linear congruential generator, 		S' = (A x S) mod (2^31 - 1) for A = 16807. @author Barbara Hohlt @date March 1 2005 </long>
</documentation>
<module/>
</component>
<component qname="SRTreeAppC.RoutingMsgTimerC" loc="44(SRTreeAppC.RoutingMsgTimerC):/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<short> The virtualized millisecond timer abstraction.</short>
<long> The virtualized millisecond timer abstraction. Instantiating this component gives an independent millisecond granularity timer. @author Philip Levis @date January 16 2006 @see TEP 102: Timers </long>
</documentation>
<instance number="0">
<component-ref qname="TimerMilliC"/>
</instance>
<configuration/>
</component>
<component qname="TimerMilliP" loc="48:/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliP.nc">
<documentation loc="34:/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliP.nc">
<short> Components should never wire to this component.</short>
<long> Components should never wire to this component. This is the underlying configuration of virtualized millisecond timers. It auto-wires wires the timer implementation (TimerC) to the boot sequence and exports the various Timer interfaces. @author Philip Levis @author Cory Sharp @date May 16 2005 </long>
</documentation>
<configuration/>
</component>
<component qname="HilTimerMilliC" loc="44:/home/tinyos/local/src/tinyos-2x/tos/platforms/mica/sim/HilTimerMilliC.nc">
<documentation loc="34:/home/tinyos/local/src/tinyos-2x/tos/platforms/mica/sim/HilTimerMilliC.nc">
<short> Millisecond timer for the mica family (see TEP102).</short>
<long> Millisecond timer for the mica family (see TEP102). The "millisecond" timer system is built on hardware timer 0, running at 1024Hz. @author Cory Sharp <[email protected]> @author Martin Turon <[email protected]> </long>
</documentation>
<configuration/>
</component>
<component qname="AlarmCounterMilliP" loc="25:/home/tinyos/local/src/tinyos-2x/tos/platforms/mica/AlarmCounterMilliP.nc">
<configuration/>
</component>
<component qname="AlarmCounterMilliP.Atm128AlarmAsyncC" loc="23(AlarmCounterMilliP.Atm128AlarmAsyncC):/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncC.nc">
<documentation loc="11:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncC.nc">
<short> Build a 32-bit alarm and counter from the atmega128's 8-bit timer 0 in asynchronous mode.</short>
<long> Build a 32-bit alarm and counter from the atmega128's 8-bit timer 0 in asynchronous mode. Attempting to use the generic Atm128AlarmC component and the generic timer components runs into problems apparently related to letting timer 0 overflow. So, instead, this version (inspired by the 1.x code and a remark from Martin Turon) directly builds a 32-bit alarm and counter on top of timer 0 and never lets timer 0 overflow. @author David Gay </long>
</documentation>
<instance number="0">
<component-ref qname="Atm128AlarmAsyncC"/>
<arguments>
<type-tag size="I:4" alignment="I:4"><struct-ref ref="0x7ff0201b60b8"/>
<typename><typedef-ref name="TMilli" ref="0x7ff0201b6410"/></typename>
</type-tag>
<value cst="I:3">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="AlarmCounterMilliP.Atm128AlarmAsyncC.Atm128AlarmAsyncP" loc="23(AlarmCounterMilliP.Atm128AlarmAsyncC.Atm128AlarmAsyncP):/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncP.nc">
<documentation loc="11:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncP.nc">
<short> Build a 32-bit alarm and counter from the atmega128's 8-bit timer 0 in asynchronous mode.</short>
<long> Build a 32-bit alarm and counter from the atmega128's 8-bit timer 0 in asynchronous mode. Attempting to use the generic Atm128AlarmC component and the generic timer components runs into problems apparently related to letting timer 0 overflow. So, instead, this version (inspired by the 1.x code and a remark from Martin Turon) directly builds a 32-bit alarm and counter on top of timer 0 and never lets timer 0 overflow. @author David Gay </long>
</documentation>
<instance number="0">
<component-ref qname="Atm128AlarmAsyncP"/>
<arguments>
<type-var size="U:" alignment="U:"><typedef-ref name="precision" scoped="" ref="0x7ff01fb1ac70"/></type-var>
<value cst="U:">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="HplAtm128Timer0AsyncC" loc="50:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/sim/HplAtm128Timer0AsyncC.nc">
<documentation loc="32:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/sim/HplAtm128Timer0AsyncC.nc">
<short> The TOSSIM implementation of the Atm128 Timer0.</short>
<long> The TOSSIM implementation of the Atm128 Timer0. It is built from a timer-specific counter component and a generic compare component. The counter component has an additional simulation-only interface to let the compare component know when its state has changed (e.g., TCNTX was set). @date November 22 2005 @author Philip Levis <[email protected]> @author Martin Turon <[email protected]> @author David Gay <[email protected]> </long>
</documentation>
<configuration/>
</component>
<component qname="HplAtm128Timer0AsyncP" loc="48:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/sim/HplAtm128Timer0AsyncP.nc">
<documentation loc="1:/home/tinyos/local/src/tinyos-2x/tos/platforms/micaz/sim/platform_hardware.h">
<short> IMPORTANT: READ BEFORE DOWNLOADING, COPYING, INSTALLING OR USING.</short>
<long> IMPORTANT: READ BEFORE DOWNLOADING, COPYING, INSTALLING OR USING. By downloading, copying, installing or using the software you agree to this license. If you do not agree to this license, do not download, install, copy or use the software. Copyright (c) 2004-2005 Crossbow Technology, Inc. Copyright (c) 2002-2003 Intel Corporation. Copyright (c) 2000-2003 The Regents of the University of California. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: - Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. - Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. - Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. @author Jason Hill, Philip Levis, Nelson Lee, David Gay @author Alan Broad <[email protected]> @author Matt Miller <[email protected]> @author Martin Turon <[email protected]> $Id: platform_hardware.h,v 1.6 2010-06-29 22:07:54 scipio Exp $ </long>
</documentation>
<module/>
</component>
<component qname="HilTimerMilliC.AlarmToTimerC" loc="46(HilTimerMilliC.AlarmToTimerC):/home/tinyos/local/src/tinyos-2x/tos/lib/timer/AlarmToTimerC.nc">
<documentation loc="36:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/AlarmToTimerC.nc">
<short> AlarmToTimerC converts a 32-bit Alarm to a Timer.</short>
<long> AlarmToTimerC converts a 32-bit Alarm to a Timer. <p>See TEP102 for more details. @param precision_tag A type indicating the precision of the Alarm and Timer being converted. @author Cory Sharp <[email protected]> </long>
</documentation>
<instance number="0">
<component-ref qname="AlarmToTimerC"/>
<arguments>
<type-tag size="I:4" alignment="I:4"><struct-ref ref="0x7ff0201b60b8"/>
<typename><typedef-ref name="TMilli" ref="0x7ff0201b6410"/></typename>
</type-tag>
</arguments>
</instance>
<module/>
</component>
<component qname="HilTimerMilliC.VirtualizeTimerC" loc="46(HilTimerMilliC.VirtualizeTimerC):/home/tinyos/local/src/tinyos-2x/tos/lib/timer/VirtualizeTimerC.nc">
<documentation loc="34:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/VirtualizeTimerC.nc">
<short> VirtualizeTimerC uses a single Timer to create up to 255 virtual timers.</short>
<long> VirtualizeTimerC uses a single Timer to create up to 255 virtual timers. <p>See TEP102 for more details. @param precision_tag A type indicating the precision of the Timer being virtualized. @param max_timers Number of virtual timers to create. @author Cory Sharp <[email protected]> </long>
</documentation>
<instance number="0">
<component-ref qname="VirtualizeTimerC"/>
<arguments>
<type-tag size="I:4" alignment="I:4"><struct-ref ref="0x7ff0201b60b8"/>
<typename><typedef-ref name="TMilli" ref="0x7ff0201b6410"/></typename>
</type-tag>
<value cst="I:4">
<type-int cname="unsigned int" unsigned="" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="HilTimerMilliC.CounterToLocalTimeC" loc="46(HilTimerMilliC.CounterToLocalTimeC):/home/tinyos/local/src/tinyos-2x/tos/lib/timer/CounterToLocalTimeC.nc">
<documentation loc="36:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/CounterToLocalTimeC.nc">
<short> CounterToLocalTimeC converts a 32-bit LocalTime to a Counter.</short>
<long> CounterToLocalTimeC converts a 32-bit LocalTime to a Counter. <p>See TEP102 for more details. @param precision_tag A type indicating the precision of the LocalTime and Counter being converted. @author Cory Sharp <[email protected]> </long>
</documentation>
<instance number="0">
<component-ref qname="CounterToLocalTimeC"/>
<arguments>
<type-tag size="I:4" alignment="I:4"><struct-ref ref="0x7ff0201b60b8"/>
<typename><typedef-ref name="TMilli" ref="0x7ff0201b6410"/></typename>
</type-tag>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.RoutingTimerC" loc="44(SRTreeAppC.RoutingTimerC):/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<short> The virtualized millisecond timer abstraction.</short>
<long> The virtualized millisecond timer abstraction. Instantiating this component gives an independent millisecond granularity timer. @author Philip Levis @date January 16 2006 @see TEP 102: Timers </long>
</documentation>
<instance number="1">
<component-ref qname="TimerMilliC"/>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.RoundTimerC" loc="44(SRTreeAppC.RoundTimerC):/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<short> The virtualized millisecond timer abstraction.</short>
<long> The virtualized millisecond timer abstraction. Instantiating this component gives an independent millisecond granularity timer. @author Philip Levis @date January 16 2006 @see TEP 102: Timers </long>
</documentation>
<instance number="2">
<component-ref qname="TimerMilliC"/>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.DistributionTimerC" loc="44(SRTreeAppC.DistributionTimerC):/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<short> The virtualized millisecond timer abstraction.</short>
<long> The virtualized millisecond timer abstraction. Instantiating this component gives an independent millisecond granularity timer. @author Philip Levis @date January 16 2006 @see TEP 102: Timers </long>
</documentation>
<instance number="3">
<component-ref qname="TimerMilliC"/>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.RoutingSenderC" loc="47(SRTreeAppC.RoutingSenderC):/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc">
<short> The virtualized active message send abstraction.</short>
<long> The virtualized active message send abstraction. Each instantiation of AMSenderC has its own queue of depth one. Therefore, it does not have to contend with other AMSenderC instantiations for queue space. The underlying implementation schedules the packets in these queues using some form of fair-share queueing. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="0">
<component-ref qname="AMSenderC"/>
<arguments>
<value cst="I:22">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.RoutingSenderC.SenderC" loc="47(SRTreeAppC.RoutingSenderC.SenderC):/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc">
<short> The virtualized active message send abstraction.</short>
<long> The virtualized active message send abstraction. Each instantiation of AMSenderC has its own queue of depth one. Therefore, it does not have to contend with other AMSenderC instantiations for queue space. The underlying implementation schedules the packets in these queues using some form of fair-share queueing. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="0">
<component-ref qname="DirectAMSenderC"/>
<arguments>
<value cst="U:">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.RoutingSenderC.SenderC.AMQueueEntryP" loc="43(SRTreeAppC.RoutingSenderC.SenderC.AMQueueEntryP):/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc">
<short> Internal AM component that fills in needed packet fields for the AMSend -> Send transformation.</short>
<long> Internal AM component that fills in needed packet fields for the AMSend -> Send transformation. @author Philip Levis @date Jan 16 2006 </long>
</documentation>
<instance number="0">
<component-ref qname="AMQueueEntryP"/>
<arguments>
<value cst="U:">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="AMQueueP" loc="42:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueP.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueP.nc">
<short> The fair-share send queue for AM radio communication.</short>
<long> The fair-share send queue for AM radio communication. @author Philip Levis @date Jan 16 2006 </long>
</documentation>
<configuration/>
</component>
<component qname="AMQueueP.AMQueueImplP" loc="45(AMQueueP.AMQueueImplP):/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueImplP.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueImplP.nc">
<short> An AM send queue that provides a Service Instance pattern for formatted packets and calls an underlying AMSend in a round-robin fashion.</short>
<long> An AM send queue that provides a Service Instance pattern for formatted packets and calls an underlying AMSend in a round-robin fashion. Used to share L2 bandwidth between different communication clients. @author Philip Levis @date Jan 16 2006 </long>
</documentation>
<instance number="0">
<component-ref qname="AMQueueImplP"/>
<arguments>
<value cst="I:3">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.RoutingReceiverC" loc="43(SRTreeAppC.RoutingReceiverC):/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc">
<short> The virtualized AM reception abstraction.</short>
<long> The virtualized AM reception abstraction. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="0">
<component-ref qname="AMReceiverC"/>
<arguments>
<value cst="I:22">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.DistributionSenderC" loc="47(SRTreeAppC.DistributionSenderC):/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc">
<short> The virtualized active message send abstraction.</short>
<long> The virtualized active message send abstraction. Each instantiation of AMSenderC has its own queue of depth one. Therefore, it does not have to contend with other AMSenderC instantiations for queue space. The underlying implementation schedules the packets in these queues using some form of fair-share queueing. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="1">
<component-ref qname="AMSenderC"/>
<arguments>
<value cst="I:30">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.DistributionSenderC.SenderC" loc="47(SRTreeAppC.DistributionSenderC.SenderC):/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc">
<short> The virtualized active message send abstraction.</short>
<long> The virtualized active message send abstraction. Each instantiation of AMSenderC has its own queue of depth one. Therefore, it does not have to contend with other AMSenderC instantiations for queue space. The underlying implementation schedules the packets in these queues using some form of fair-share queueing. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="1">
<component-ref qname="DirectAMSenderC"/>
<arguments>
<value cst="U:">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.DistributionSenderC.SenderC.AMQueueEntryP" loc="43(SRTreeAppC.DistributionSenderC.SenderC.AMQueueEntryP):/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc">
<short> Internal AM component that fills in needed packet fields for the AMSend -> Send transformation.</short>
<long> Internal AM component that fills in needed packet fields for the AMSend -> Send transformation. @author Philip Levis @date Jan 16 2006 </long>
</documentation>
<instance number="1">
<component-ref qname="AMQueueEntryP"/>
<arguments>
<value cst="U:">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.DistributionReceiverC" loc="43(SRTreeAppC.DistributionReceiverC):/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc">
<short> The virtualized AM reception abstraction.</short>
<long> The virtualized AM reception abstraction. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="1">
<component-ref qname="AMReceiverC"/>
<arguments>
<value cst="I:30">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.ReaggregateSenderC" loc="47(SRTreeAppC.ReaggregateSenderC):/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc">
<short> The virtualized active message send abstraction.</short>
<long> The virtualized active message send abstraction. Each instantiation of AMSenderC has its own queue of depth one. Therefore, it does not have to contend with other AMSenderC instantiations for queue space. The underlying implementation schedules the packets in these queues using some form of fair-share queueing. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="2">
<component-ref qname="AMSenderC"/>
<arguments>
<value cst="I:10">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.ReaggregateSenderC.SenderC" loc="47(SRTreeAppC.ReaggregateSenderC.SenderC):/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc">
<short> The virtualized active message send abstraction.</short>
<long> The virtualized active message send abstraction. Each instantiation of AMSenderC has its own queue of depth one. Therefore, it does not have to contend with other AMSenderC instantiations for queue space. The underlying implementation schedules the packets in these queues using some form of fair-share queueing. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="2">
<component-ref qname="DirectAMSenderC"/>
<arguments>
<value cst="U:">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.ReaggregateSenderC.SenderC.AMQueueEntryP" loc="43(SRTreeAppC.ReaggregateSenderC.SenderC.AMQueueEntryP):/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc">
<short> Internal AM component that fills in needed packet fields for the AMSend -> Send transformation.</short>
<long> Internal AM component that fills in needed packet fields for the AMSend -> Send transformation. @author Philip Levis @date Jan 16 2006 </long>
</documentation>
<instance number="2">
<component-ref qname="AMQueueEntryP"/>
<arguments>
<value cst="U:">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.ReaggregateReceiverC" loc="43(SRTreeAppC.ReaggregateReceiverC):/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc">
<short> The virtualized AM reception abstraction.</short>
<long> The virtualized AM reception abstraction. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<instance number="2">
<component-ref qname="AMReceiverC"/>
<arguments>
<value cst="I:10">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<configuration/>
</component>
<component qname="SRTreeAppC.RoutingSendQueueC" loc="6(SRTreeAppC.RoutingSendQueueC):PacketQueueC.nc">
<instance number="0">
<component-ref qname="PacketQueueC"/>
<arguments>
<value cst="I:5">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.RoutingReceiveQueueC" loc="6(SRTreeAppC.RoutingReceiveQueueC):PacketQueueC.nc">
<instance number="1">
<component-ref qname="PacketQueueC"/>
<arguments>
<value cst="I:3">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.DistributionSendQueueC" loc="6(SRTreeAppC.DistributionSendQueueC):PacketQueueC.nc">
<instance number="2">
<component-ref qname="PacketQueueC"/>
<arguments>
<value cst="I:5">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.DistributionReceiveQueueC" loc="6(SRTreeAppC.DistributionReceiveQueueC):PacketQueueC.nc">
<instance number="3">
<component-ref qname="PacketQueueC"/>
<arguments>
<value cst="I:3">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.ReaggregateSendQueueC" loc="6(SRTreeAppC.ReaggregateSendQueueC):PacketQueueC.nc">
<instance number="4">
<component-ref qname="PacketQueueC"/>
<arguments>
<value cst="I:5">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="SRTreeAppC.ReaggregateReceiveQueueC" loc="6(SRTreeAppC.ReaggregateReceiveQueueC):PacketQueueC.nc">
<instance number="5">
<component-ref qname="PacketQueueC"/>
<arguments>
<value cst="I:3">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</value>
</arguments>
</instance>
<module/>
</component>
<component qname="Atm128AlarmAsyncC" loc="23:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncC.nc" abstract="">
<documentation loc="11:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncC.nc">
<short> Build a 32-bit alarm and counter from the atmega128's 8-bit timer 0 in asynchronous mode.</short>
<long> Build a 32-bit alarm and counter from the atmega128's 8-bit timer 0 in asynchronous mode. Attempting to use the generic Atm128AlarmC component and the generic timer components runs into problems apparently related to letting timer 0 overflow. So, instead, this version (inspired by the 1.x code and a remark from Martin Turon) directly builds a 32-bit alarm and counter on top of timer 0 and never lets timer 0 overflow. @author David Gay </long>
</documentation>
<parameters>
<typedef name="precision" ref="0x7ff01fb1ac70" loc="23:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncC.nc">
<component-ref qname="Atm128AlarmAsyncC"/>
<type-var size="U:" alignment="U:"><typedef-ref name="precision" scoped="" ref="0x7ff01fb1ac70"/></type-var>
</typedef>
<constant name="divider" ref="0x7ff01fb16020" loc="23:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncC.nc">
<component-ref qname="Atm128AlarmAsyncC"/>
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</constant>
</parameters>
<configuration/>
</component>
<component qname="VirtualizeTimerC" loc="46:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/VirtualizeTimerC.nc" abstract="" safe="">
<documentation loc="34:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/VirtualizeTimerC.nc">
<short> VirtualizeTimerC uses a single Timer to create up to 255 virtual timers.</short>
<long> VirtualizeTimerC uses a single Timer to create up to 255 virtual timers. <p>See TEP102 for more details. @param precision_tag A type indicating the precision of the Timer being virtualized. @param max_timers Number of virtual timers to create. @author Cory Sharp <[email protected]> </long>
</documentation>
<parameters>
<typedef name="precision_tag" ref="0x7ff01f95a210" loc="46:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/VirtualizeTimerC.nc">
<component-ref qname="VirtualizeTimerC"/>
<type-var size="U:" alignment="U:"><typedef-ref name="precision_tag" scoped="" ref="0x7ff01f95a210"/></type-var>
</typedef>
<constant name="max_timers" ref="0x7ff01f95a520" loc="46:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/VirtualizeTimerC.nc">
<component-ref qname="VirtualizeTimerC"/>
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</constant>
</parameters>
<module/>
</component>
<component qname="AMQueueImplP" loc="45:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueImplP.nc" abstract="" safe="">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueImplP.nc">
<short> An AM send queue that provides a Service Instance pattern for formatted packets and calls an underlying AMSend in a round-robin fashion.</short>
<long> An AM send queue that provides a Service Instance pattern for formatted packets and calls an underlying AMSend in a round-robin fashion. Used to share L2 bandwidth between different communication clients. @author Philip Levis @date Jan 16 2006 </long>
</documentation>
<parameters>
<constant name="numClients" ref="0x7ff01f8b12a8" loc="45:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueImplP.nc">
<component-ref qname="AMQueueImplP"/>
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</constant>
</parameters>
<module/>
</component>
<component qname="AMReceiverC" loc="43:/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc" abstract="">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc">
<short> The virtualized AM reception abstraction.</short>
<long> The virtualized AM reception abstraction. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<parameters>
<constant name="amId" ref="0x7ff01f84d468" loc="43:/home/tinyos/local/src/tinyos-2x/tos/system/AMReceiverC.nc">
<component-ref qname="AMReceiverC"/>
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</constant>
</parameters>
<configuration/>
</component>
<component qname="AlarmToTimerC" loc="46:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/AlarmToTimerC.nc" abstract="" safe="">
<documentation loc="36:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/AlarmToTimerC.nc">
<short> AlarmToTimerC converts a 32-bit Alarm to a Timer.</short>
<long> AlarmToTimerC converts a 32-bit Alarm to a Timer. <p>See TEP102 for more details. @param precision_tag A type indicating the precision of the Alarm and Timer being converted. @author Cory Sharp <[email protected]> </long>
</documentation>
<parameters>
<typedef name="precision_tag" ref="0x7ff01fb5fc80" loc="46:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/AlarmToTimerC.nc">
<component-ref qname="AlarmToTimerC"/>
<type-var size="U:" alignment="U:"><typedef-ref name="precision_tag" scoped="" ref="0x7ff01fb5fc80"/></type-var>
</typedef>
</parameters>
<module/>
</component>
<component qname="Atm128AlarmAsyncP" loc="23:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncP.nc" abstract="" safe="">
<documentation loc="11:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncP.nc">
<short> Build a 32-bit alarm and counter from the atmega128's 8-bit timer 0 in asynchronous mode.</short>
<long> Build a 32-bit alarm and counter from the atmega128's 8-bit timer 0 in asynchronous mode. Attempting to use the generic Atm128AlarmC component and the generic timer components runs into problems apparently related to letting timer 0 overflow. So, instead, this version (inspired by the 1.x code and a remark from Martin Turon) directly builds a 32-bit alarm and counter on top of timer 0 and never lets timer 0 overflow. @author David Gay </long>
</documentation>
<parameters>
<typedef name="precision" ref="0x7ff01fb0c410" loc="23:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncP.nc">
<component-ref qname="Atm128AlarmAsyncP"/>
<type-var size="U:" alignment="U:"><typedef-ref name="precision" scoped="" ref="0x7ff01fb0c410"/></type-var>
</typedef>
<constant name="divider" ref="0x7ff01fb0c700" loc="23:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/Atm128AlarmAsyncP.nc">
<component-ref qname="Atm128AlarmAsyncP"/>
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
</constant>
</parameters>
<module/>
</component>
<component qname="AMSenderC" loc="47:/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc" abstract="">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc">
<short> The virtualized active message send abstraction.</short>
<long> The virtualized active message send abstraction. Each instantiation of AMSenderC has its own queue of depth one. Therefore, it does not have to contend with other AMSenderC instantiations for queue space. The underlying implementation schedules the packets in these queues using some form of fair-share queueing. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<parameters>
<constant name="AMId" ref="0x7ff01f8e4780" loc="47:/home/tinyos/local/src/tinyos-2x/tos/system/AMSenderC.nc">
<component-ref qname="AMSenderC"/>
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</constant>
</parameters>
<configuration/>
</component>
<component qname="AMQueueEntryP" loc="43:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc" abstract="" safe="">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc">
<short> Internal AM component that fills in needed packet fields for the AMSend -> Send transformation.</short>
<long> Internal AM component that fills in needed packet fields for the AMSend -> Send transformation. @author Philip Levis @date Jan 16 2006 </long>
</documentation>
<parameters>
<constant name="amId" ref="0x7ff01f8d6e48" loc="43:/home/tinyos/local/src/tinyos-2x/tos/system/AMQueueEntryP.nc">
<component-ref qname="AMQueueEntryP"/>
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</constant>
</parameters>
<module/>
</component>
<component qname="PacketQueueC" loc="6:PacketQueueC.nc" abstract="">
<parameters>
<constant name="queueSize" ref="0x7ff01f82ed60" loc="6:PacketQueueC.nc">
<component-ref qname="PacketQueueC"/>
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="uint8_t" ref="0x7ff020e9c020"/></typename>
</type-int>
</constant>
</parameters>
<module/>
</component>
<component qname="DirectAMSenderC" loc="47:/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc" abstract="">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc">
<short> The virtualized active message send abstraction.</short>
<long> The virtualized active message send abstraction. Each instantiation of AMSenderC has its own queue of depth one. Therefore, it does not have to contend with other AMSenderC instantiations for queue space. The underlying implementation schedules the packets in these queues using some form of fair-share queueing. @author Philip Levis @date Jan 16 2006 @see TEP 116: Packet Protocols </long>
</documentation>
<parameters>
<constant name="AMId" ref="0x7ff01f8da348" loc="47:/home/tinyos/local/src/tinyos-2x/tos/system/DirectAMSenderC.nc">
<component-ref qname="DirectAMSenderC"/>
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="am_id_t" ref="0x7ff020278ab0"/></typename>
</type-int>
</constant>
</parameters>
<configuration/>
</component>
<component qname="CounterToLocalTimeC" loc="46:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/CounterToLocalTimeC.nc" abstract="" safe="">
<documentation loc="36:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/CounterToLocalTimeC.nc">
<short> CounterToLocalTimeC converts a 32-bit LocalTime to a Counter.</short>
<long> CounterToLocalTimeC converts a 32-bit LocalTime to a Counter. <p>See TEP102 for more details. @param precision_tag A type indicating the precision of the LocalTime and Counter being converted. @author Cory Sharp <[email protected]> </long>
</documentation>
<parameters>
<typedef name="precision_tag" ref="0x7ff01f90c110" loc="46:/home/tinyos/local/src/tinyos-2x/tos/lib/timer/CounterToLocalTimeC.nc">
<component-ref qname="CounterToLocalTimeC"/>
<type-var size="U:" alignment="U:"><typedef-ref name="precision_tag" scoped="" ref="0x7ff01f90c110"/></type-var>
</typedef>
</parameters>
<module/>
</component>
<component qname="TimerMilliC" loc="44:/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc" abstract="">
<documentation loc="33:/home/tinyos/local/src/tinyos-2x/tos/system/TimerMilliC.nc">
<short> The virtualized millisecond timer abstraction.</short>
<long> The virtualized millisecond timer abstraction. Instantiating this component gives an independent millisecond granularity timer. @author Philip Levis @date January 16 2006 @see TEP 102: Timers </long>
</documentation>
<parameters>
</parameters>
<configuration/>
</component>
</components>
<interfaces>
</interfaces>
<interfacedefs>
<interfacedef qname="SplitControl" loc="87:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<documentation loc="72:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<short> Please refer to TEP 115 for more information about this interface and its intended use.<br><br> This is the split-phase counterpart to the StdContol interface.</short>
<long> Please refer to TEP 115 for more information about this interface and its intended use.<br><br> This is the split-phase counterpart to the StdContol interface. It should be used for switching between the on and off power states of the component providing it. For each <code>start()</code> or <code>stop()</code> command, if the command returns SUCCESS, then a corresponding <code>startDone()</code> or <code>stopDone()</code> event must be signalled. @author Joe Polastre @author Kevin Klues ([email protected]) </long>
</documentation>
<function event="" provided="0" name="startDone" ref="0x7ff0201eae40" loc="113:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<documentation loc="106:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<short> Notify caller that the component has been started and is ready to receive other commands.</short>
<long> Notify caller that the component has been started and is ready to receive other commands. @param <b>error</b> -- SUCCESS if the component was successfully turned on, FAIL otherwise </long>
</documentation>
<interfacedef-ref qname="SplitControl"/>
<type-function size="I:1" alignment="I:1">
<type-void size="I:1" alignment="I:1"></type-void>
<function-parameters>
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="error_t" ref="0x7ff0204f2be8"/></typename>
</type-int>
</function-parameters>
</type-function>
<parameters>
<variable name="error" ref="0x7ff0201eabd0" loc="113:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="error_t" ref="0x7ff0204f2be8"/></typename>
</type-int>
</variable>
</parameters>
</function>
<function event="" provided="0" name="stopDone" ref="0x7ff0201e7290" loc="138:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<documentation loc="132:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<short> Notify caller that the component has been stopped.</short>
<long> Notify caller that the component has been stopped. @param <b>error</b> -- SUCCESS if the component was successfully turned off, FAIL otherwise </long>
</documentation>
<interfacedef-ref qname="SplitControl"/>
<type-function size="I:1" alignment="I:1">
<type-void size="I:1" alignment="I:1"></type-void>
<function-parameters>
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="error_t" ref="0x7ff0204f2be8"/></typename>
</type-int>
</function-parameters>
</type-function>
<parameters>
<variable name="error" ref="0x7ff0201e7020" loc="138:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="error_t" ref="0x7ff0204f2be8"/></typename>
</type-int>
</variable>
</parameters>
</function>
<function command="" provided="0" name="start" ref="0x7ff0201ea258" loc="104:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<documentation loc="89:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<short> Start this component and all of its subcomponents.</short>
<long> Start this component and all of its subcomponents. Return values of SUCCESS will always result in a <code>startDone()</code> event being signalled. @return SUCCESS if the device is already in the process of starting or the device was off and the device is now ready to turn on. After receiving this return value, you should expect a <code>startDone</code> event in the near future.<br> EBUSY if the component is in the middle of powering down i.e. a <code>stop()</code> command has been called, and a <code>stopDone()</code> event is pending<br> EALREADY if the device is already on <br> FAIL Otherwise </long>
</documentation>
<interfacedef-ref qname="SplitControl"/>
<type-function size="I:1" alignment="I:1">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="error_t" ref="0x7ff0204f2be8"/></typename>
</type-int>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
<function command="" provided="0" name="stop" ref="0x7ff0201e8680" loc="130:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<documentation loc="115:/home/tinyos/local/src/tinyos-2x/tos/interfaces/SplitControl.nc">
<short> Start this component and all of its subcomponents.</short>
<long> Start this component and all of its subcomponents. Return values of SUCCESS will always result in a <code>startDone()</code> event being signalled. @return SUCCESS if the device is already in the process of stopping or the device was on and the device is now ready to turn off. After receiving this return value, you should expect a <code>stopDone</code> event in the near future.<br> EBUSY if the component is in the middle of powering up i.e. a <code>start()</code> command has been called, and a <code>startDone()</code> event is pending<br> EALREADY if the device is already off <br> FAIL Otherwise </long>
</documentation>
<interfacedef-ref qname="SplitControl"/>
<type-function size="I:1" alignment="I:1">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="error_t" ref="0x7ff0204f2be8"/></typename>
</type-int>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
</interfacedef>
<interfacedef qname="Boot" loc="50:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Boot.nc">
<documentation loc="42:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Boot.nc">
<short> Interface that notifies components when TinyOS has booted (initialized all of its components), as discussed in TEP 107.</short>
<long> Interface that notifies components when TinyOS has booted (initialized all of its components), as discussed in TEP 107. @author Philip Levis @date January 5 2005 </long>
</documentation>
<function event="" provided="0" name="booted" ref="0x7ff0201eeae8" loc="60:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Boot.nc">
<documentation loc="51:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Boot.nc">
<short> Signaled when the system has booted successfully.</short>
<long> Signaled when the system has booted successfully. Components can assume the system has been initialized properly. Services may need to be started to work, however. @see StdControl @see SplitConrol @see TEP 107: Boot Sequence </long>
</documentation>
<interfacedef-ref qname="Boot"/>
<type-function size="I:1" alignment="I:1">
<type-void size="I:1" alignment="I:1"></type-void>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
</interfacedef>
<interfacedef qname="TaskBasic" loc="55:/home/tinyos/local/src/tinyos-2x/tos/interfaces/TaskBasic.nc">
<function command="" provided="0" name="postTask" ref="0x7ff02022c070" loc="67:/home/tinyos/local/src/tinyos-2x/tos/interfaces/TaskBasic.nc">
<documentation loc="57:/home/tinyos/local/src/tinyos-2x/tos/interfaces/TaskBasic.nc">
<short> Post this task to the TinyOS scheduler.</short>
<long> Post this task to the TinyOS scheduler. At some later time, depending on the scheduling policy, the scheduler will signal the <tt>run()</tt> event. @return SUCCESS if task was successfuly posted; the semantics of a non-SUCCESS return value depend on the implementation of this interface (the class of task). </long>
</documentation>
<interfacedef-ref qname="TaskBasic"/>
<type-function size="I:1" alignment="I:1">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="error_t" ref="0x7ff0204f2be8"/></typename>
</type-int>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
<function event="" provided="0" name="runTask" ref="0x7ff02022c860" loc="75:/home/tinyos/local/src/tinyos-2x/tos/interfaces/TaskBasic.nc">
<documentation loc="69:/home/tinyos/local/src/tinyos-2x/tos/interfaces/TaskBasic.nc">
<short> Event from the scheduler to run this task.</short>
<long> Event from the scheduler to run this task. Following the TinyOS concurrency model, the codes invoked from <tt>run()</tt> signals execute atomically with respect to one another, but can be preempted by async commands/events. </long>
</documentation>
<interfacedef-ref qname="TaskBasic"/>
<type-function size="I:1" alignment="I:1">
<type-void size="I:1" alignment="I:1"></type-void>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
</interfacedef>
<interfacedef qname="HplAtm128TimerAsync" loc="15:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<documentation loc="11:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<short> </short>
<long> @author David Gay </long>
</documentation>
<function command="" provided="0" name="controlBusy" ref="0x7ff01fae3998" loc="38:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<documentation loc="34:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<short> Check if control register TCCR0 is busy (should not be updated if true) </short>
<long> Check if control register TCCR0 is busy (should not be updated if true) @return TRUE if TCCR0 is busy, FALSE otherwise (can be updated) </long>
</documentation>
<interfacedef-ref qname="HplAtm128TimerAsync"/>
<type-function size="I:1" alignment="I:1">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
<function command="" provided="0" name="compareBusy" ref="0x7ff01fae11d8" loc="44:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<documentation loc="40:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<short> Check if compare register OCR0 is busy (should not be updated if true) </short>
<long> Check if compare register OCR0 is busy (should not be updated if true) @return TRUE if OCR0 is busy, FALSE otherwise (can be updated) </long>
</documentation>
<interfacedef-ref qname="HplAtm128TimerAsync"/>
<type-function size="I:1" alignment="I:1">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
<function command="" provided="0" name="setTimer0Asynchronous" ref="0x7ff01fae3290" loc="32:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<documentation loc="29:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<short> Turn on timer 0 asynchronous mode </short>
</documentation>
<interfacedef-ref qname="HplAtm128TimerAsync"/>
<type-function size="I:1" alignment="I:1">
<type-void size="I:1" alignment="I:1"></type-void>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
<function command="" provided="0" name="countBusy" ref="0x7ff01fae1988" loc="50:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<documentation loc="46:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<short> Check if current timer value (TCNT0) is busy (should not be updated if true) </short>
<long> Check if current timer value (TCNT0) is busy (should not be updated if true) @return TRUE if TCNT0 is busy, FALSE otherwise (can be updated) </long>
</documentation>
<interfacedef-ref qname="HplAtm128TimerAsync"/>
<type-function size="I:1" alignment="I:1">
<type-int cname="int" size="I:4" alignment="I:4"></type-int>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
<function command="" provided="0" name="getAssr" ref="0x7ff01fae40d8" loc="21:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<documentation loc="17:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<short> Read timer0 asynchronous status register (ASSR) </short>
<long> Read timer0 asynchronous status register (ASSR) @return Current value of ASSR </long>
</documentation>
<interfacedef-ref qname="HplAtm128TimerAsync"/>
<type-function size="I:1" alignment="I:1">
<type-tag size="I:1" alignment="I:1"><union-ref ref="0x7ff01fb52d90"/>
<typename><typedef-ref name="Atm128Assr_t" ref="0x7ff01fb51228"/></typename>
</type-tag>
<function-parameters>
</function-parameters>
</type-function>
<parameters>
</parameters>
</function>
<function command="" provided="0" name="setAssr" ref="0x7ff01fae4a88" loc="27:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<documentation loc="23:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<short> Set timer0 asynchronous status register (ASSR) </short>
<long> Set timer0 asynchronous status register (ASSR) @param x New value for ASSR </long>
</documentation>
<interfacedef-ref qname="HplAtm128TimerAsync"/>
<type-function size="I:1" alignment="I:1">
<type-void size="I:1" alignment="I:1"></type-void>
<function-parameters>
<type-tag size="I:1" alignment="I:1"><union-ref ref="0x7ff01fb52d90"/>
<typename><typedef-ref name="Atm128Assr_t" ref="0x7ff01fb51228"/></typename>
</type-tag>
</function-parameters>
</type-function>
<parameters>
<variable name="x" ref="0x7ff01fae4818" loc="27:/home/tinyos/local/src/tinyos-2x/tos/chips/atm128/timer/HplAtm128TimerAsync.nc">
<type-tag size="I:1" alignment="I:1"><union-ref ref="0x7ff01fb52d90"/>
<typename><typedef-ref name="Atm128Assr_t" ref="0x7ff01fb51228"/></typename>
</type-tag>
</variable>
</parameters>
</function>
</interfacedef>
<interfacedef qname="TossimPacket" loc="44:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/TossimPacket.nc">
<documentation loc="34:/home/tinyos/local/src/tinyos-2x/tos/types/TinyError.h">
<short> </short>
<long> @author Phil Levis @author David Gay @author Eric B. Decker <[email protected]> Defines global error codes for error_t in TinyOS. </long>
</documentation>
<function command="" provided="0" name="strength" ref="0x7ff01fe20d38" loc="45:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/TossimPacket.nc">
<interfacedef-ref qname="TossimPacket"/>
<type-function size="I:1" alignment="I:1">
<type-int cname="signed char" size="I:1" alignment="I:1">
<typename><typedef-ref name="int8_t" ref="0x7ff020e9d020"/></typename>
</type-int>
<function-parameters>
<type-pointer size="I:8" alignment="I:8">
<type-tag size="I:48" alignment="I:1"><nx_struct-ref name="message_t" ref="0x7ff020264a20"/>
<typename><typedef-ref name="message_t" ref="0x7ff020261020"/></typename>
</type-tag>
</type-pointer>
</function-parameters>
</type-function>
<parameters>
<variable name="msg" ref="0x7ff01fe20ac8" loc="45:/home/tinyos/local/src/tinyos-2x/tos/lib/tossim/TossimPacket.nc">
<type-pointer size="I:8" alignment="I:8">
<type-tag size="I:48" alignment="I:1"><nx_struct-ref name="message_t" ref="0x7ff020264a20"/>
<typename><typedef-ref name="message_t" ref="0x7ff020261020"/></typename>
</type-tag>
</type-pointer>
</variable>
</parameters>
</function>
</interfacedef>
<interfacedef qname="Packet" loc="55:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Packet.nc">
<documentation loc="42:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Packet.nc">
<short> The basic message data type accessors.</short>
<long> The basic message data type accessors. Protocols may use additional packet interfaces for their protocol specific data/metadata. @author Philip Levis @date January 5 2005 @see TEP 116: Packet Protocols </long>
</documentation>
<function command="" provided="0" name="clear" ref="0x7ff0201e0290" loc="65:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Packet.nc">
<documentation loc="58:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Packet.nc">
<short> Clear out this packet.</short>
<long> Clear out this packet. Note that this is a deep operation and total operation: calling clear() on any layer will completely clear the packet for reuse. @param 'message_t* ONE msg' the packet to clear </long>
</documentation>
<interfacedef-ref qname="Packet"/>
<type-function size="I:1" alignment="I:1">
<type-void size="I:1" alignment="I:1"></type-void>
<function-parameters>
<type-pointer size="I:8" alignment="I:8">
<type-tag size="I:48" alignment="I:1"><nx_struct-ref name="message_t" ref="0x7ff020264a20"/>
<typename><typedef-ref name="message_t" ref="0x7ff020261020"/></typename>
</type-tag>
</type-pointer>
</function-parameters>
</type-function>
<parameters>
<variable name="msg" ref="0x7ff0201e0020" loc="65:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Packet.nc">
<type-pointer size="I:8" alignment="I:8">
<type-tag size="I:48" alignment="I:1"><nx_struct-ref name="message_t" ref="0x7ff020264a20"/>
<typename><typedef-ref name="message_t" ref="0x7ff020261020"/></typename>
</type-tag>
</type-pointer>
</variable>
</parameters>
</function>
<function command="" provided="0" name="payloadLength" ref="0x7ff0201df290" loc="78:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Packet.nc">
<documentation loc="67:/home/tinyos/local/src/tinyos-2x/tos/interfaces/Packet.nc">
<short> Return the length of the payload of msg.</short>
<long> Return the length of the payload of msg. This value may be less than what maxPayloadLength() returns, if the packet is smaller than the MTU. If a communication component does not support variably sized data regions, then payloadLength() will always return the same value as maxPayloadLength(). @param 'message_t* ONE msg' the packet to examine @return the length of its current payload </long>
</documentation>
<interfacedef-ref qname="Packet"/>
<type-function size="I:1" alignment="I:1">
<type-int cname="unsigned char" unsigned="" size="I:1" alignment="I:1">
<typename><typedef-ref name="uint8_t" ref="0x7ff020e9c020"/></typename>
</type-int>
<function-parameters>
<type-pointer size="I:8" alignment="I:8">
<type-tag size="I:48" alignment="I:1"><nx_struct-ref name="message_t" ref="0x7ff020264a20"/>
<typename><typedef-ref name="message_t" ref="0x7ff020261020"/></typename>
</type-tag>
</type-pointer>