90 likes | 233 Vues
This document provides a thorough examination of hardware and software considerations for developing low-power radio frequency (LPRF) devices. It covers essential components like sensors, micro-controllers, radios, and batteries, emphasizing criteria such as low power consumption, standards compliance, and community support. It also highlights development tools for firmware, debugging techniques, and the use of oscilloscopes and spectrum analyzers in the design process. Practical insights and recommendations aim to assist engineers in creating efficient and reliable LPRF systems.
E N D
4. LPRF in Practice Thomas Watteyne @ EDERC 2010
Hardware - Overview sensors micro-controller radio battery mote Thomas Watteyne @ EDERC 2010
Hardware - Criteria • Radio-chip • Low-power • Standards compliant? • Community / Support • Micro-controller • Reasonably fast • Low-power • Multiple I/O options • Reasonable amount of memory • Timing capabilities • Community / support Thomas Watteyne @ EDERC 2010
Hardware - Microcontrollers a used as cache, primary memory is off-chip b at 1MHz c at 8MHz Thomas Watteyne @ EDERC 2010
Hardware - Radios a at 0dBm transmission power b at 3dBm transmission power Thomas Watteyne @ EDERC 2010
Hardware - Motes Thomas Watteyne @ EDERC 2010
Software - Options Thomas Watteyne @ EDERC 2010
Development Tools • Firmware development is complex • not complicated! • developtop-down, always keep an eye on where you’re going • the vast majority of the cases, you’re wrong (not the compiler, not the protocols) • bugs are always due to simple errors • build from atomic building blocks • Multi-dimensional Debugging • choose a meaning for each LED, and stick with it • print out error codes, not text • Use the extension pins with an oscilloscope, the easiest way to measure time • Use a spectrum analyzer to see on what channels you are occupying • Use a sniffer to see the packets flying through the air • A GUI is faster than lines text • Use a JTAG debugger whenever possible Thomas Watteyne @ EDERC 2010
Development Tools • Choosing a scope • analog channels for energy (put resistor in series with power source) • the more digital channels, the better • you don’t need a fast scope • some oscilloscopes will interpret SPI, I2C, UART (e.g. Tektronic MSO2024) • cheap USB scopes available • Spectrum analyzers • are expensive • can be replaced by a sniffer • can be replaced by the poor man’s spectrum analyzer • Sniffer • CC2531 EMK ($49) • Graphical User Interface • Python+PySerial is a good candidate Thomas Watteyne @ EDERC 2010