RunTimeDynamicLinkingforReprogrammingWireless.pptVIP

Run-Time Dynamic Linking for Reprogramming Wireless SensorNetworks Adam Dunkels, Niclas Finne, Joakim Eriksson, Thiemo Voigt Swedish Institute of Computer Science ACM SenSys 2006 The setting: software updates in sensor networks We all have our own way of doing loadable modules Contiki [EmNetS 2004] Statically linked modules, relocation at run-time SOS [MobiSys 2005] Modules with position independent code Why not just do it the standard “Linux” way? Run-time linking of ELF files Availability of tools, knowledge Are we compelled to do it our own way? Or do we choose to do it our own way? Can we even do it the “Linux” way in microsensor networks? Given the severe resource constraints: 2k RAM, 60k ROM If we could, what would the overhead be? What we’ve done Developed a dynamic linker for Contiki Link, relocate, load standard ELF files CVM (Contiki VM) – a virtual machine Typical, stack-based virtual machine Compiler for a subset of Java Java virtual machine Ported the leJOS Java VM to Contiki Conclusions Proof of concept: dynamic linking of ELF files is possible and feasible for sensor networks Code size 2k, memory size 100 bytes Acceptable transmission overhead (ELF size factor 3) Communication is by far the dominating factor Energy consumption for the dynamic linking is low Depending on the scenario, combinations may be the most efficient Virtual machine code with dynamically loaded native libraries The details… Reprogramming methods Virtual machines, script languages Native code Full image replacement The default method for many embedded systems, TinyOS Delta/diff-based approaches Compare two versions of the compiled code, transmit only the changes Need to know both versions Loadable modules Requires support from operating system Loadable modules Linking, relocation, loading Static pre-linking Do all linking at compile time Must know all core addresses at compile time All nodes must be exactly the same Configuration management nightmare Contiki [EmNetS 200