DOCSLIB.ORG

Tinyos-Tutorial.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Tinyos-Tutorial.Pdf Embedded computing projects, Learning TinyOS & nesC Rahav Dor Spring 2014 Kevin Klues started this lecture series in 2007. It has been inherited and kept up to date with advancements in TinyOS, nesC, and their development environments by Chien-Liang Fok, Gregory Hackmann, Mo Sha, and now Rahav Dor. Lecture topics Ø Embedded Compu9ng projects Ø Coding style, coherent and useful programming Ø Installing TinyOS and compiling your first app Ø Introduc9on to motes Ø Basic nesC syntax Ø Advanced nesC syntax Ø NetworK communicaon Ø Sensor data acquisi9on Ø Debugging tricKs and techniques 2 Lecture topics Ø Embedded Compu9ng projects Ø Coding style, coherent and useful programming Ø Installing TinyOS and compiling your first app Ø Introduc9on to motes Ø Basic nesC syntax Ø Advanced nesC syntax Ø NetworK communicaon Ø Sensor data acquisi9on Ø Debugging tricKs and techniques Robobees, Harvard university 3 Cool projects out there Ø Good night lamp. Ø Plantduino Greenhouse. Ø TwiQer mood light. Ø LED cube. Ø Shoe that lace itself. Ø Turn signal biKing jacKet. Ø Secret KnocK door locK. Ø Tree climbing robot. Ø Sigh collector. 4 Cool projects in here Ø Compare TinyOS and Conki. Ø Turn your mote into a web server, have it support AllJoin (AllSeen), Bonjour, CoAP, NLNA, MQTT, nanoIP, REST, etc. Ø Empirical study of any number of above protocols Ø Develop you own transport protocol, discovery protocol, … Ø Turn RaspberryPi into a 802.15.4 base staon (this is one of the few projects that are allowed on RPi). Ø Comparave study of security for IoT devices q New ideas? Ø Make your smartphone into a 802.15.4 remote control q Support querying, proximity, and simple commands Ø Develop an IoT search engine 5 Get inspired Ø hQp://makezine.com/ Ø hQp://www.instructables.com/ Ø hQp://www.raspberrypi.org/forums/viewforum.php?f=15 q Note that you cannot use the Raspberry Pi as the main plaorm in this course without my prior approval 6 Projects – requirements Ø Embedded system Ø Design, Code, and evaluaon – evenly divided among team Ø Project scope must be approved by me (Rahav) Ø Can repeat past projects as long as they have a twist q But you need to design and author your own code Ø You will be subject to academic disciplinary ac9ons, including failing this course, if you (see course full policy) q Submit program code wriQen outside this course without proper citaon q Simply copy code not wriQen by you q Use code of another student not on your team q Collaboraon and discussions are great exploraon vehicles and are encouraged, but you must aribute the ideas to their originator 7 Projects – artifacts Ø All ar9facts will count toward your grade Ø Design (diagrams and discourse authored in any tool) q Specificaons q Data flow q Logical interac9ons between the components or func9ons q Design consideraons • What you have considered (op9onal) • What you have decided to do Ø README.txt (or readme.txt) q See the readmeFD.txt example, which includes q A short descrip9on of the app q How to install, compile, and run your project (including a command line sec9on, e.g. java MIG) q Hardware dependencies 8 Equipment Ø Equipment, motes, … must be returned in good condi9on q -10% automac reduc9on otherwise q Physical interfacing must be done via connectors q Past evils can be undone • Up to a full grade leQer (on the project part) of extra credit for good ci9zenship: Soldering, Double sided tape, Cleaning Ø See course site for exis9ng equipment q Within reason and 9me we can buy staff to support your inven9on 9 Header comment (1 of 2) Ø Author a header comment at the top of all source files. Use the following format: Ø The name of the file (e.g., HelloWorldC.nc) Ø The name of the deliverable (e.g., Midterm demo. RFID reader.) Ø Name of the chief author and email address Ø Class: CSE 467S – Embedded Compu9ng Systems Ø WUSTL, Spring 2014 Ø The date on which the first release of the code was ready Ø Invariants 10 Header comment (2 of 2) Ø A short paragraph describing the func9onality. This should include, for example the purpose of the file or its role in the project. Be crisp, precise, and informave. Communicate your approach to solving the problem. Ø Version log with q Date q Who made the change, email address, and why q What was the change 11 Header example HelloWorldC.nc Purpose: Final project. Agent updater. Author : Rahav Dor [email protected] Course : CSE 467S -- Embedded Computing Systems WUSTL, Spring 3017 Date : Jan. 2, 3017 Invariants: 10 Hz <= updateFrequency <= 50 Hz Description: Maintain communication between agents and keep a local state when agents are detached from the hive. If communication channels are open this code guarantees information exchange according to the invariant. Version log: 2/1/2013, Jean-Luc Picard Fixed the remote agent bug. 3/10/2013, Seven of Nine An agent can now be detached from the collective, while still maintaining its basic operations. 12 Lecture topics Ø Embedded Compu9ng projects Ø Coding style, coherent and useful programming Ø Installing TinyOS and compiling your first app Ø Introduc9on to motes Ø Basic nesC syntax Ø Advanced nesC syntax Ø NetworK communicaon Ø Sensor data acquisi9on Ø Debugging tricKs and techniques 13 Style Ø Write self documen9ng code: if (lowTemperature(temp)) work = force * displacement * cos(moteToFloorAngle) Ø Indent 3 spaces or equal sized tab stop Ø Use DESCRIPTIVE_CONSTANTS Ø And self explanatory variablesNames Ø FileNames, ClassNames, e.g q Modules are named FallDetectionC q Configuraon is named FallDetectionAppC 14 Style Ø curlyFunctionBraces { … } Ø if (youFollow) { your are in a good starting place; } else { you start from less than optimal condition; } Ø Func9ons must have specs above them that describe the func9on, invariants if any, parameters, and return value Ø Use inline comments as needed 15 Style – TinyOS / nesC Ø Each app has a Configuraon (the wiring) and one ore more Modules (the code) Ø Wiring file are named: HelloWorldAppC.nc q This file name is the one specified in the Makefile as the source to be compiled Ø Code files are named : HelloWorldC.nc Ø Can also end with a P to denote Private 16 Lecture topics Ø Embedded Compu9ng projects Ø Coding style, coherent and useful programming Ø Installing TinyOS and compiling your first app Ø Introduc9on to motes Ø Basic nesC syntax Ø Advanced nesC syntax Ø NetworK communicaon Ø Sensor data acquisi9on Ø Debugging tricKs and techniques 17 TinyOS community q hQp://www.9nyos.net/ 18 TINYOS INSTALLATION – LINUX The next number of slides go over the general concepts of installing TinyOS (my recommendaons as of Jan. 2014). To install the system use the handout available on the course web site. 19 TinyOS recommended installation Ø We will be installing TinyOS, on Linux, running on a VM, that runs on a Host OS Ø Follow the installaon instruc9ons handout Ø I recommend you do the large downloads while on campus and while connected to a wired networK Ø VMware (Fusion version is the one for OS-X and cost 49$), or VirtualBox (free) q Known problems: Cut and Paste, Bluetooth Ø Ubunto 12.x (LTE) or 13.x (other debian flavors may worK equally well) q Consideraon for 32 and 64 bit versions: Memory, TinyOS will not compile on 64, and OS response 9me 20 TinyOS directory structure Ø Aser TinyOS is installed you will have a new tree branch under your home directory: /$HOME/nyos-main (this must correspond to $TOSROOT) q apps q doc q licenses q README q release-notes.txt q support q tools q tos Ø ChecKout TinyOS README file for details 21 Before motes are connected Ø Learn which devices are aached to Linux before you connect any mote to your machine. It will allow you to iden9fy what is the address of motes when you eventually connect them. Use the ls /dev/tty* command to capture data similar to the following: 22 When motes are connected Ø When you connect a mote, the Virtual Machine will asK you where do you want to connect it – chose Linux Ø The ls command as shown on the previous slide, or the command motelist will show you the aached motes Ø Change the permissions on any nyOS related q serial (/dev/yS<N>) q usb (/dev/s/usb<N>, /dev/yUSB<N>) q or parallel (/dev/parport) devices you are going to use, using the following command: sudo chmod 666 /dev/<devicename> Example: sudo chmod 666 /dev/ttyUSB0 Ø See a beQer alternave in the handout 23 TinyOS installation veriRication Ø To check your TinyOs installaon run tos-check-env Ø If you did everything properly you will see only one WARNING about graphviz not being version 1.10 (it will appear twice) Ø This is actually OK because you will have a newer version (likely 2.x). To check run dot –V Ø Later in this lecture, and on the installaon handout, we will also build Blink to conclude the verificaon 24 TinyOS installation Problems Ø If you try to run make micaz sim and it gives you a long error message star9ng with: ...: error: inttypes.h: No such file or directory Ø then you need to install the C library/header files for your own architecture Ø On Ubuntu/Debian, run apt-get install build-essential 25 TINYOS INSTALLATION – LINUX This concludes the general details about installing TinyOS 26 make System Ø TinyOS includes lots of Makefiles to support the build process Ø Create a simple stub Makefile in your app directory that points to main component, and invoKes TinyOS make system.
Load more

Recommended publications
  • NSLU2 for TF5800PVR Access Over Ethernet
    Configure NSLU2 for TF5800PVR access over Ethernet Summary A Linksys NSLU2 is a paperback size unit that has Ethernet and USB ports. Using this the Topfield TF5800 PVR can be accessed over a home network. The NSLU2 is about £55 but needs custom firmware to access the Topfield. This document describes the installation process on a Windows PC. This configuration does not use any USB drives on the NSLU2. Make sure you read the appendix for latest info. Author Malcolm Reeves ([email protected]) Issue: Draft H Date: 6-May-06 Contents 1. Initial Test 2 2. RedBoot 3 3. Install Unslung 4 4. Install ftpd-topfield 5 5. Upgrades and Configuration 7 5.1 Turbo Mode 8 Appendix A - Rafe’s Comments 9 1. Initial Test So you’ve bought a NSLU2. Let’s test it and make sure it’s working. So connect it your home network. Most home networks are 192.168.0.xxx (where xxx is any number between 1 and 254) with a mask of 255.255.255.0. This range is reserved for local networks and it’s what Windows defaults to. You’ll need to change the mask to 255.255.254.0 on your PC and on your router if you have one. This is because the default IP address of the NSLU2 is 192.168.1.77 which is not on the default local network. After changing the mask enter 192.168.1.77 in a browser URL bar. This should bring up the Linksys web setup pages for the NSLU2.
    [Show full text]
  • NSLU2-Linux Howto Overclocktheslug
    NSLU2-Linux | HowTo / OverClockTheSlug http://www.nslu2-linux.org/wiki/HowTo/OverClockTheSlug?action=print From NSLU2-Linux HowTo: OverClockTheSlug There appear to be two models around -- please verify that you are running at 133 before doing anything else ''' Tired of sluggish performance? Want to squeeze a bit more out of your slug? Feel that you're not getting the dish you paid for? Overclocking (De-underclocking) the Linksys NSLU2! (or how to get your own TurboSlug) Notes on Slugs supplied at 266Mhz: Edit: My brand new Slug comes from factory with BogoMIPS : 263.78, so it is already running at 266 MHz ?. The Slug is marked with a sticker: Manufactured 05/2006. Maybe someone from Linksys has read this page :) Edit: Mine also comes from factory running at 266Mhz ;) - Manufactured 05/2006 Edit by Bullfrog: Mine also comes from factory running at 266Mhz ;) - Manufactured 05/2006 - R64 is also now no longer fitted next to flash chip near serial port which with R83 fitted and R81 missing - gives the undocumented code for 266Mhz Edit by Charly: Mine also comes from factory running at 266Mhz ;) - Manufactured 05/2006. Also the French power adapter is twice smaller for same power (5V 2.0A) Edit by halfer: purchased 10/May/2007 and found that the " XScale ??-IXP425/IXC1100 " is already running at 263.78 BogoMIPS Notes on Slugs supplied at the standard half speed: Edit by Steve 2/25/2007: Purchased yesterday. Mine came with V2.3R73. Only a windows guy so couldn't verify speed. Task manager showed 31% network usage on large files (>2 GBytes ?).
    [Show full text]
  • A Wee Server for the Home
    A wee server for the home Sudarshan S. Chawathe 2018-03-24 Home server: what? why? • Something to provide small-scale local services • Printing from local network • File server • Easily and privately share files with household • Destination for backups of other computers, photos, videos • Music server • Control playback on attached home audio system • Serve music to play elsewhere • Stream music from elsewhere • Web server: Photo and video galleries • Personal XMPP/Jabber chat server • Landing spot for remote login • Wake up other computers using wake-on-LAN. • Email server, … ? • Under personal control. • Free (libre) • Independent of non-local network • availability, latency, bandwidth S.S. Chawathe, A wee server for the home 1 Why a wee server? • Low power consumption • Always-on is a nice if it only uses a few watts. • Low heat dissipation • Compact • easily stash on a shelf, behind other equipment, … • Low cost • ~ 100 USD. • Hardware options that are more open • than mainstream servers • Fun • low-risk hardware experimentation: flashing, etc. • easy hardware interfacing • blinking lights, motors, sensors, … S.S. Chawathe, A wee server for the home 2 This presentation • For, and by, a non-expert • Not very novel or unique; see FreedomBox, … • Expert advice welcome • Brief how-to and invitation • Buy, build, configure a wee home server • Use, learn, and contribute to libre software • One person’s choices and experience • not comprehensive, nor ideal • but actually used, long term • Small technical excursions (still non-expert) • udev rules • randomness • Sharing • experiences with home servers • suggestions, concerns, future directions S.S. Chawathe, A wee server for the home 3 Hardware choices • many options • examples, not exhaustive lists • what I chose and why S.S.
    [Show full text]
  • Smart Home Automation with Linux Smart
    CYAN YELLOW MAGENTA BLACK PANTONE 123 C BOOKS FOR PROFESSIONALS BY PROFESSIONALS® THE EXPERT’S VOICE® IN LINUX Companion eBook Available Smart Home Automation with Linux Smart Dear Reader, With this book you will turn your house into a smart and automated home. You will learn how to put together all the hardware and software needed for Automation Home home automation, to control appliances such as your teakettle, CCTV, light switches, and TV. You’ll be taught about the devices you can build, adapt, or Steven Goodwin, Author of hack yourself from existing technology to accomplish these goals. Cross-Platform Game In Smart Home Automation with Linux, you’ll discover the scope and possi- Programming bilities involved in creating a practical digital lifestyle. In the realm of media and Game Developer’s Open media control, for instance, you’ll learn how you can read TV schedules digitally Source Handbook and use them to program video remotely through e-mail, SMS, or a web page. You’ll also learn the techniques for streaming music and video from one machine to another, how to give your home its own Twitter and e-mail accounts for sending automatic status reports, and the ability to remotely control the home Smart Home lights or heating system. Also, Smart Home Automation with Linux describes how you can use speech synthesis and voice recognition systems as a means to converse with your household devices in new, futuristic, ways. Additionally, I’ll also show you how to implement computer-controlled alarm clocks that can speak your daily calendar, news reports, train delays, and local with weather forecasts.
    [Show full text]
  • Call Your Netbsd
    Call your NetBSD BSDCan 2013 Ottawa, Canada Pierre Pronchery ([email protected]) May 17th 2013 Let's get this over with ● Pierre Pronchery ● French, based in Berlin, Germany ● Freelance IT-Security Consultant ● OSDev hobbyist ● NetBSD developer since May 2012 (khorben@) Agenda 1.Why am I doing this? 2.Target hardware: Nokia N900 3.A bit of ARM architecture 4.NetBSD on ARM 5.Challenges of the port 6.Current status 7.DeforaOS embedded desktop 8.Future plans 1. A long chain of events ● $friend0 gives me Linux CD ● Computer not happy with Linux ● Get FreeBSD CD shipped ● Stick with Linux for a while ● Play with OpenBSD on Soekris hardware ● $friend1 gets Zaurus PDA ● Switch desktop and laptop to NetBSD ● I buy a Zaurus PDA ● I try OpenBSD on Zaurus PDA 1. Chain of events, continued ● $gf gets invited to $barcamp ● I play with my Zaurus during her presentation ● $barcamp_attender sees me doing this ● Begin to work on the DeforaOS desktop ● Get some of it to run on the Zaurus ● Attend CCC Camp near Berlin during my bday ● $gf offers me an Openmoko Neo1973 ● Adapt the DeforaOS desktop to Openmoko 1. Chain of events, unchained ● $barcamp_attender was at the CCC Camp, too ● We begin to sell the Openmoko Freerunner ● Create a Linux distribution to support it ● Openmoko is EOL'd and we split ways ● $friend2 gives me sparc64 boxes ● Get more involved with NetBSD ● Nokia gives me a N900 during a developer event ● $barcamp_attender points me to a contest ● Contest is about creating an OSS tablet 1. Chain of events (out of breath) ● Run DeforaOS on NetBSD on the WeTab tablet ● Co-win the contest this way ● $friend3 boots NetBSD on Nokia N900 ● Give a talk about the WeTab tablet ● Promise to work on the Nokia N900 next thing ● Apply to BSDCan 2013 ● Taste maple syrup for the first time in Canada ● Here I am in front of you Pictures: Sharp Zaurus Pictures: Openmoko Freerunner Pictures: WeTab Pictures: DeforaOS 2.
    [Show full text]
  • Debian 1 Debian
    Debian 1 Debian Debian Part of the Unix-like family Debian 7.0 (Wheezy) with GNOME 3 Company / developer Debian Project Working state Current Source model Open-source Initial release September 15, 1993 [1] Latest release 7.5 (Wheezy) (April 26, 2014) [±] [2] Latest preview 8.0 (Jessie) (perpetual beta) [±] Available in 73 languages Update method APT (several front-ends available) Package manager dpkg Supported platforms IA-32, x86-64, PowerPC, SPARC, ARM, MIPS, S390 Kernel type Monolithic: Linux, kFreeBSD Micro: Hurd (unofficial) Userland GNU Default user interface GNOME License Free software (mainly GPL). Proprietary software in a non-default area. [3] Official website www.debian.org Debian (/ˈdɛbiən/) is an operating system composed of free software mostly carrying the GNU General Public License, and developed by an Internet collaboration of volunteers aligned with the Debian Project. It is one of the most popular Linux distributions for personal computers and network servers, and has been used as a base for other Linux distributions. Debian 2 Debian was announced in 1993 by Ian Murdock, and the first stable release was made in 1996. The development is carried out by a team of volunteers guided by a project leader and three foundational documents. New distributions are updated continually and the next candidate is released after a time-based freeze. As one of the earliest distributions in Linux's history, Debian was envisioned to be developed openly in the spirit of Linux and GNU. This vision drew the attention and support of the Free Software Foundation, who sponsored the project for the first part of its life.
    [Show full text]
  • How-To Build Meteohub on Sheevaplug (The Easy Way)
    How-To Build Meteohub on SheevaPlug (the easy way) The SheevaPlug is a low power, small form factor device that can be seen as the successor of the famous NSLU2. Meteohub has now been experimentally ported to the SheevaPlug. Please be aware that this port is rather alpha, but it seems to work. At the moment Meteohub on SheevaPlug has these limitations: ● no WebCam support: This is also not planned for the future ● no WLAN support: Might be added via USB WLAN sticks in the future (low priority) ● no Labjack support: unclear if this can be added by a home-brew kernel module, low priority Meteohub on SheevaPlug makes use of a SD card where operating system, Meteohub application and data are stored. Capacity is 4GB. It should be a SLC based card. As not all SD cards are working with the plug, you might have some experiments in front of you. SLC-based SD card that is proven to be working ● Transcend SDHC Class 6 150x: TS4GSDHC150 Weather stations are connected to the Meteohub by USB connector. This one USB port can be extended with an USB hub. It looks like it can be a passive USB hub, as the Meteohub provides the 500mA on USB and this should be enough to drive a few weather station USB connections and/or RS232-USB converter. Meteohub on SheevaPlug consumes about 5 watts , which is really effective. Meteohub's performance looks fine. It can do about 900 records per second during recomputation (NSLU2 is about 200, x86 Geode platforms are up to 2000).
    [Show full text]
  • Low-Cost Conversion of Single-Zone HVAC Systems to Multi-Zone Control Systems Using Low-Power Wireless Sensor Networks
    sensors Article Low-Cost Conversion of Single-Zone HVAC Systems to Multi-Zone Control Systems Using Low-Power Wireless Sensor Networks Julio Antonio Jornet-Monteverde 1 and Juan José Galiana-Merino 1,2,* 1 Department of Physics, Systems Engineering and Signal Theory, University of Alicante, Crta. San Vicente del Raspeig, s/n, 03080 Alicante, Spain; [email protected] 2 University Institute of Physics Applied to Sciences and Technologies, University of Alicante, Crta. San Vicente del Raspeig, s/n, 03080 Alicante, Spain * Correspondence: juanjo@dfists.ua.es; Tel.: +34-965-909-636 Received: 31 May 2020; Accepted: 25 June 2020; Published: 27 June 2020 Abstract: This paper presents a novel approach to convert a conventional house air conditioning installation into a more efficient system that individually controls the temperature of each zone of the house through Wi-Fi technology. Each zone regulates the air flow depending on the detected temperature, providing energy savings and increasing the machine performance. Therefore, the first step was to examine the communication bus of the air conditioner and obtain the different signal codes. Thus, an alternative Controller module has been designed and developed to control and manage the requests on the communication bus (Bus–Wi-Fi gateway). A specific circuit has been designed to adapt the signal of the serial port of the Controller with the communication bus. For the acquisition of the temperature and humidity data in each zone, a Node module has been developed, which communicates with the Controller through the Wi-Fi interface using the Message Queuing Telemetry Transport (MQTT) protocol with Secure Sockets Layer / Transport Layer Security (SSL/TLS) certificates.
    [Show full text]
  • Plugcomputer
    Fakultat¨ Informatik Institut f ¨urTechnische Informatik, Professur f ¨urVLSI-Entwurfssysteme, Diagnostik und Architektur PLUGCOMPUTER Alte Idee, Neuer Ansatz Thomas Gartner¨ Dresden, 14.7.2010 Ubersicht¨ Motivation Alte Idee: NSLU2 Neuer Ansatz: PlugComputer Quellen TU Dresden, 14.7.2010 PlugComputer Folie 2 von 24 Motivation Problemstellung Wie kann ich meine personlichen¨ Daten und Dateien moglichst¨ effizient, f ¨urmich und ausgewahlte¨ Personen, ¨uberallund immer verf ¨ugbarmachen? • Soziale Netzwerke • Hostingdienste wie z.B. Flickr, Google Suite, YouTube . • Server anmieten Probleme: • Daten ¨ubergabean Dritte • Dienste wegen ihrer Große¨ f ¨urAngreifer attraktiv TU Dresden, 14.7.2010 PlugComputer Folie 3 von 24 Motivation Losungsansatz¨ Idee: Eigener Server im eigenen, sicheren Netz das inzwischen meistens ohnehin standig¨ mit dem Internet verbunden ist. Vorteile: • Beschrankter¨ physikalischer Zugang f ¨urDritte • Voll anpassbar Nachteile: • Konfigurationsaufwand • Energieverbrauch • Larm¨ • Verantwortung f ¨urdie eigenen Daten TU Dresden, 14.7.2010 PlugComputer Folie 4 von 24 Motivation Losungsansatz¨ TU Dresden, 14.7.2010 PlugComputer Folie 5 von 24 Alte Idee: NSLU2 Allgemein Mit dem Network Storage Link von Linksys konnen¨ Sie die Speicherkapazitat¨ Ihres Netzwerks schnell und einfach um viele Gigabyte erweitern. Dieses kleine Netzwerkgerat¨ verbindet USB2.0-Festplatten direkt mit Ihrem Ethernet- Netzwerk. [Lina] TU Dresden, 14.7.2010 PlugComputer Folie 6 von 24 Alte Idee: NSLU2 Außen • 130 mm x 21 mm x 91 mm • 1x 10/100-RJ-45-Ethernet-Port • 2x USB 2.0-Port • 1x Stromanschluss TU Dresden, 14.7.2010 PlugComputer Folie 7 von 24 Alte Idee: NSLU2 Innen • Intel IXP420 (ARMv5TE) • 133 MHz, spater¨ 266 MHz • 8 MB Flash • 32 MB SDRAM TU Dresden, 14.7.2010 PlugComputer Folie 8 von 24 Alte Idee: NSLU2 Modifikationen • NSLU2 Firmware basiert auf Linux! • Ersetzbar durch Debian, OpenWrt, SlugOS .
    [Show full text]
  • Running Debian on Inexpensive Network Attached Storage Devices
    Running Debian on Inexpensive Network Attached Storage Devices Martin Michlmayr [email protected] This is my personal opinion; no recommendation implied FOSDEM Brussels, Belgium Martin Michlmayr Running Debian on Inexpensive Network Attached Storage Devices Network Attached Storage devices For most people, a Network Attached Storage device (NAS) is an external hard drive on steroids For geeks, a NAS is a complete computer Martin Michlmayr Running Debian on Inexpensive Network Attached Storage Devices Advantages of NAS Power efficient Quiet Cheap Makes a nice home server Martin Michlmayr Running Debian on Inexpensive Network Attached Storage Devices Linksys NSLU2, aka Slug Intel IXP42x, 133 or 266 MHz 32 MB RAM 8 MB flash no internal disk 1 10/100 Ethernet 2 USB Martin Michlmayr Running Debian on Inexpensive Network Attached Storage Devices Linksys NSLU2 Advantages: It’s cheap It’s quiet (no fan) Firmware can be upgraded via the network It can run on flash only Disadvantages: Ethernet needs proprietary microcode It’s slooow and doesn’t have much memory Martin Michlmayr Running Debian on Inexpensive Network Attached Storage Devices Linksys NSLU2 Feature complete, maintenance mode Packages nslu2-utils and ixp4xx-microcode Support for LEDs, beeper, Ethernet Ethernet driver: Krzysztof Halasa Some new ideas about improving d-i support (example: mounting ext3 as ext2) Gordon Farquharson, Joey Hess, NSLU2-Linux team Martin Michlmayr Running Debian on Inexpensive Network Attached Storage Devices Thecus N2100 Intel IOP 80219, 600 MHz 1 DDR400 slot (up
    [Show full text]
  • Raspbian Server Installation Auf Raspberry Pi
    Raspbian Server Installation auf Raspberry Pi Evil [email protected] http://evil.hn.vc 11. Mai 2014 1 Inhaltsverzeichnis 1 Vorwort 5 2 Hardware 6 2.1 Komponenten . 6 2.2 Schnittstellen . 7 2.2.1 Modell B (zusätzlich) . 7 2.3 Abmessungen . 7 2.4 Versorgung/Netzteil . 7 2.5 Netzteil . 7 2.6 Aktiver USB - Hub . 7 2.7 Leistungsaufnahme . 8 2.7.1 Herstellerangaben . 8 2.7.2 Tchibo/Eduscho Flachnetzteil . 8 2.7.3 LogiLink UA0106 . 8 2.8 Komponeten . 8 2.9 Übersicht Eigenschaften . 9 3 Unterstützte Debian Versionen 9 4 Basis Installation 9 4.1 Debian Squeeze . 9 4.2 Raspbian (Debian Wheezy armhf) . 11 5 Basis Einrichtung 12 5.1 Debian Squeeze . 12 5.2 Raspbian (Debian Wheezy) . 13 6 Installation 14 6.1 Watchdog . 14 6.2 Zeitsynchronisierung . 15 6.3 Netzwerk . 15 6.3.1 LAN - Statische Adresse . 15 6.3.2 LAN - Dynamische Adresse (DHCP) . 16 6.3.3 WLAN - Dynamische Adresse (DHCP) . 16 6.4 Sound . 18 7 Optimierungen 18 7.1 Root Benutzer aktivieren . 18 7.2 Turbo Modus (Overcockling) . 18 7.3 USB Blockgröÿe . 19 7.4 Puer Writeback auf 15 Sekunden . 20 2 8 Tools 20 8.1 Entwicklung . 20 8.2 Wartung . 20 8.3 Diagnose . 20 8.4 Komprimierungsprogramme . 20 8.4.1 unrar - Erstellung aus Source . 20 8.4.2 unrar aktivieren . 21 9 Software die nicht installiert werden soll 21 10 System-Information 22 10.1 /proc/cpuinfo . 22 10.1.1 Raspberry PI 256 MB (Juli 2012) . 22 10.1.2 Raspberry PI 512 MB (Dezember 2012) .
    [Show full text]
  • Trophy Ott Back-End Solution
    TROPHY OTT BACK-END SOLUTION TROPHY OTT BACK-END SOLUTION TROPHY OTT BACK-END SOLUTION CONTENTS Page INTRODUCTION 1 BACK-END SYSTEM 2 DVB-S2 to IP STREAMERS 3 H.264 TRANSCODER 9 NGINX SERVER 14 DSC-01 SERVER 16 CONTENTS TROPHY OTT BACK-END SOLUTION INTRODUCTION TROPHY OTT Back-End System is a high-tech, based on know-how, cost-effective solution. In particular, it helps OTT providers take full advantage of back-end equipment & SW. Over-the-top content (OTT) is a term used in broadcasting and technology business reporting to refer to audio, video, and other media transmitted via the Internet without an operator of multiple cable or direct-broadcast satellite television systems (so-called ) controlling or distributing the content. Hardware and software can be divided into two main groups. Front-end and back-end are the terms of software engineering, which are distinguished according to the principle of shared responsibility between the external representation and internal implementation, respectively. Front-end is interaction between the user interface and the basic software and hardware (back-end). Front-end and back-end can be distributed between one or more systems. The software architecture can be many levels between the hardware and the end user, each of which may also have a front-end and back-end. Front-end is an abstraction that provides a user interface. Front-End (or client side) is any user-controlled component, and the Back-End is performed on the server. BACK-END FRONT-END (user interface) 1 INTRODUCTION TROPHY OTT BACK-END SOLUTION OTT BACK-END SYSTEM H.264 TRANSCODING OTT BACK-END is the most convinient and versatile for IPTV&OTT solution.
    [Show full text]