2011 International Conference on Distributed Computing in Sensor Systems and Workshops (DCOSS) 2011
DOI: 10.1109/dcoss.2011.5982222
|View full text |Cite
|
Sign up to set email alerts
|

Experiences from porting the Contiki operating system to a popular hardware platform

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
19
0

Year Published

2012
2012
2024
2024

Publication Types

Select...
3
2
1

Relationship

3
3

Authors

Journals

citations
Cited by 26 publications
(19 citation statements)
references
References 8 publications
(6 reference statements)
0
19
0
Order By: Relevance
“…Furthermore, Contiki and other state-of-art IoT OS do not have software support for this feature. CC2650 has 20 kB RAM, which is not a large amount for a 32-bit system, taking into account the Contiki OS footprint and the large RAM requirements for network neighbor and routing tables [12]. Not having a neighbor or a routing table entry for an active neighbor can severely reduce the performance and stability of the network [13]; consequently, it is optimal to reserve as many entries as possible, aiming for an entry for each device in the network.…”
Section: B Memory Managementmentioning
confidence: 99%
“…Furthermore, Contiki and other state-of-art IoT OS do not have software support for this feature. CC2650 has 20 kB RAM, which is not a large amount for a 32-bit system, taking into account the Contiki OS footprint and the large RAM requirements for network neighbor and routing tables [12]. Not having a neighbor or a routing table entry for an active neighbor can severely reduce the performance and stability of the network [13]; consequently, it is optimal to reserve as many entries as possible, aiming for an entry for each device in the network.…”
Section: B Memory Managementmentioning
confidence: 99%
“…The authors make the assumption that the routing table contains multiple candidate next hops for the same destination and they propose an algorithm for path aggregation. However, routing table size has an impact on scalability with increasing network size [32] even when the table only lists a single next hop per destination. Storing multiple candidate next hops per destination would impose further memory overheads 4 and should not be considered common practise.…”
Section: Multicast In Traditional Wsnsmentioning
confidence: 99%
“…The port of the Contiki OS for our hardware platform [32] does not support ContikiMAC yet. As a result all experiments were conducted over NullRDC.…”
Section: Hardware Experimentsmentioning
confidence: 99%
See 1 more Smart Citation
“…Gathering these functions in a single device simplifies modules programming and enables and makes it easier and more efficient their implementation, due to the modular architecture of devices. First, the use of available commercial boards such as Zigduino [6] or Zolertia Zl [7] was considered, but BatNet devices have two requirements that are a must: reduced size and the possibility of integrating a wide variety of sensors. To fulfill these requirements a low-cost and low-power processing and communication module has been designed and implemented: the BatMote (see Fig.…”
Section: Batmote: Processing and Communications Modulementioning
confidence: 99%