eLinux.org - User contributions [en]

RPi XBMC

2012-08-09T15:10:08Z

Lxndr:

WORK IN PROGRESS, PLEASE AMEND

As I can't find a decent one-page overview of how to get XBMC working on the Raspberry Pi without resorting to downloading a dedicated image, this page should give everyone a hand getting set up (that is, if I am successful...)

The goal is to be able to run XBMC either standalone or under LXDE from the Foundation's Raspbian image.

This guide combines e.g.
* http://www.raspbian.org/RaspbianXBMC
* http://debian.raspbian.com/qemu/README.txt
* http://linuxclues.blogspot.com/2007/06/installing-qemu-on-windows-vista.html
* http://xecdesign.com/qemu-emulating-raspberry-pi-the-easy-way/
* http://www.raspbmc.com/wiki/technical/building-xbmc/
* http://wiki.xbmc.org/index.php?title=HOW-TO_compile_XBMC_for_Linux_from_source_code
* http://wiki.xbmc.org/index.php?title=HOW-TO_compile_XBMC_for_Linux_on_Debian/Ubuntu

=Ways of installing XBMC=
Getting XBMC from the repos (doesn't work in Wheezy)
Building XBMC on the raspi (takes a long time)
Building XBMC on a Windows machine (Qemu)

So far I haven't got it running...

==Building XBMC from source using Qemu==
Since it is unbelievably slow to build XBMC on the Raspberry Pi, I used a Windows machine with Qemu to do the build. Ubuntu cross-compile should work to0, but I didn't try it yet...

===Preparation===
* Get 'Putty' (Windows Installer) from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
* Get latest 'Qemu for Windows' from http://www.h7.dion.ne.jp/~qemu-win/
* Get 'kernel-qemu' from http://xecdesign.com/downloads/linux-qemu/kernel-qemu (Interesting read: http://xecdesign.com/qemu-emulating-raspberry-pi-the-easy-way/)
* Get most recent Raspbian image ('2012-07-15 Wheezy' at time of writing) from http://www.raspberrypi.org/downloads (The Foundation's version of Raspbian)
* Install OpenVPN to get a working Network TAP driver from http://openvpn.net/index.php/download/community-downloads.html (get the Windows installer)

After installing OpenVPN follow this guide to create (remember it's name and make sure there's no spaces in it) a network TAP interface http://linuxclues.blogspot.com/2007/06/installing-qemu-on-windows-vista.html

On Windows, create folder structure like so:
D:\Qemu (holding the Qemu for Windows 1.0.1+ zip contents)
D:\Qemu\Raspbian (holding the 'kernel-qemu' file and the Raspbian image)

Then create a .bat file under D:\Qemu, containing the following launch string:
qemu-system-arm.exe -M versatilepb -cpu arm1136 -m 1024 -kernel raspbian\kernel-qemu -hda raspbian\2012-07-15-wheezy-raspbian.img -net nic -net tap,ifname=TAP0 -append "root=/dev/sda2 panic=1" -serial stdio

Resize the Raspbian image

Fix raspi-config resize issue with Qemu:

cp /usr/bin/raspi-config ~
sed -i 's/mmcblk0p2/sda2/' ~/raspi-config
sed -i 's/mmcblk0/sda/' ~/raspi-config
sudo ~/raspi-config

http://www.raspbian.org/RaspbianXBMC

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi XBMC

2012-08-09T15:05:47Z

Lxndr:

WORK IN PROGRESS, PLEASE AMEND

As I can't find a decent one-page overview of how to get XBMC working on the Raspberry Pi without resorting to downloading a dedicated image, this page should give everyone a hand getting set up (that is, if I am successful...)

The goal is to be able to run XBMC either standalone or under LXDE from the Foundation's Raspbian image.

This guide combines e.g.
* http://www.raspbian.org/RaspbianXBMC
* http://debian.raspbian.com/qemu/README.txt
* http://linuxclues.blogspot.com/2007/06/installing-qemu-on-windows-vista.html
* http://xecdesign.com/qemu-emulating-raspberry-pi-the-easy-way/
* http://www.raspbmc.com/wiki/technical/building-xbmc/

=Ways of installing XBMC=
Getting XBMC from the repos (doesn't work in Wheezy)
Building XBMC on the raspi (takes a long time)
Building XBMC on a Windows machine (Qemu)

So far I haven't got it running...

==Building XBMC from source using Qemu==
Since it is unbelievably slow to build XBMC on the Raspberry Pi, I used a Windows machine with Qemu to do the build. Ubuntu cross-compile should work to0, but I didn't try it yet...

===Preparation===
* Get 'Putty' (Windows Installer) from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
* Get latest 'Qemu for Windows' from http://www.h7.dion.ne.jp/~qemu-win/
* Get 'kernel-qemu' from http://xecdesign.com/downloads/linux-qemu/kernel-qemu (Interesting read: http://xecdesign.com/qemu-emulating-raspberry-pi-the-easy-way/)
* Get most recent Raspbian image ('2012-07-15 Wheezy' at time of writing) from http://www.raspberrypi.org/downloads (The Foundation's version of Raspbian)
* Install OpenVPN to get a working Network TAP driver from http://openvpn.net/index.php/download/community-downloads.html (get the Windows installer)

After installing OpenVPN follow this guide to create (remember it's name and make sure there's no spaces in it) a network TAP interface http://linuxclues.blogspot.com/2007/06/installing-qemu-on-windows-vista.html

On Windows, create folder structure like so:
D:\Qemu (holding the Qemu for Windows 1.0.1+ zip contents)
D:\Qemu\Raspbian (holding the 'kernel-qemu' file and the Raspbian image)

Then create a .bat file under D:\Qemu, containing the following launch string:
qemu-system-arm.exe -M versatilepb -cpu arm1136 -m 1024 -kernel raspbian\kernel-qemu -hda raspbian\2012-07-15-wheezy-raspbian.img -net nic -net tap,ifname=TAP0 -append "root=/dev/sda2 panic=1" -serial stdio

Resize the Raspbian image

Fix raspi-config resize issue with Qemu:

cp /usr/bin/raspi-config ~
sed -i 's/mmcblk0p2/sda2/' ~/raspi-config
sed -i 's/mmcblk0/sda/' ~/raspi-config
sudo ~/raspi-config

http://www.raspbian.org/RaspbianXBMC

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi XBMC

2012-08-09T14:56:11Z

Lxndr: /* Building XBMC from source using Qemu */

WORK IN PROGRESS, PLEASE AMEND

As I can't find a decent overview of how to get XBMC working on the Raspberry Pi without resorting to downloading a dedicated image, this page should give everyone a hand getting set up (that is, if I am successful...)

=Ways of installing XBMC=
Getting XBMC from the repos (doesn't work in Wheezy)
Building XBMC on the raspi (takes a long time)
Building XBMC on a Windows machine (Qemu)

So far I haven't got it running...

==Building XBMC from source using Qemu==
Since it is unbelievably slow to build XBMC on the Raspberry Pi, I used a Windows machine with Qemu to do the build. Ubuntu cross-compile should work to0, but I didn't try it yet...

===Preparation===
* Get 'Putty' (Windows Installer) from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
* Get latest 'Qemu for Windows' from http://www.h7.dion.ne.jp/~qemu-win/
* Get 'kernel-qemu' from http://xecdesign.com/downloads/linux-qemu/kernel-qemu (Interesting read: http://xecdesign.com/qemu-emulating-raspberry-pi-the-easy-way/)
* Get most recent Raspbian image ('2012-07-15 Wheezy' at time of writing) from http://www.raspberrypi.org/downloads (The Foundation's version of Raspbian)
* Install OpenVPN to get a working Network TAP driver from http://openvpn.net/index.php/download/community-downloads.html (get the Windows installer)

After installing OpenVPN follow this guide to create (remember it's name and make sure there's no spaces in it) a network TAP interface http://linuxclues.blogspot.com/2007/06/installing-qemu-on-windows-vista.html

On Windows, create folder structure like so:
D:\Qemu (holding the Qemu for Windows 1.0.1+ zip contents)
D:\Qemu\Raspbian (holding the 'kernel-qemu' file and the Raspbian image)

Then create a .bat file under D:\Qemu, containing the following launch string:
qemu-system-arm.exe -M versatilepb -cpu arm1136 -m 1024 -kernel raspbian\kernel-qemu -hda raspbian\2012-07-15-wheezy-raspbian.img -net nic -net tap,ifname=TAP0 -append "root=/dev/sda2 panic=1" -serial stdio

Resize the Raspbian image

Fix raspi-config resize issue with Qemu:

cp /usr/bin/raspi-config ~
sed -i 's/mmcblk0p2/sda2/' ~/raspi-config
sed -i 's/mmcblk0/sda/' ~/raspi-config
sudo ~/raspi-config

http://www.raspbian.org/RaspbianXBMC

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi XBMC

2012-08-09T14:49:20Z

Lxndr:

RPi XBMC

2012-08-09T12:10:06Z

Lxndr: Started dedicated XBMC page

RPi Education

2012-08-06T21:57:34Z

Lxndr: added references, template, category

{{Template:RPi_Learning}}

== The Manual ==

A manual is currently in production by members of the [http://www.computingatschool.org.uk/ Computing At School] working group. This began on the 13 October 2011 and is due to be ready for early March 2012. The manual is aimed at the project's target audience, children, so that they can take their "First steps in Computer Science".

For the first release (~January/February 2012), there will mostly likely be very minimal documentation. A 'schools' release is due in June/July 2012.

Contributions to the educational manual can be placed here in the [[RPi_Education/Manual|Manual contribution]] page.

== Your Projects ==

'''Doing a project at school or have a Raspberry Pi Club? Add it in this section to allow others to follow your progress!'''

Please add details of your group and what plans you have for the RPi or provide a link to your homepage.

===Organizations===

==== Puppy ''hacker'' School ====
For smarter kids of all ages, teachers, self-tutored and the fast learner. Based on [http://puppylinux.org/wikka/Organisation doacracy] principles of ''learning by doing'' [http://puppylinux.org/wikka/PuppySchoolProgramming Puppy Hacker School] is open for learning on your existing hardware, using [http://puppylinux.org Puppy Linux]. Whilst awaiting your first punnet of raspberries, get cracking. [http://www.murga-linux.com/puppy/viewtopic.php?p=604710#604710 All bones welcome].

==== Computer History Museum, Silicon Valley ====
[http://www.ComputerHistory.org The Computer History Museum] in the heart of Silicon Valley in Mountain View, California, has an educational program which provides resources to educators and students from pre-school up through graduate school levels. Museum staff and volunteers provide tours of the museum's exhibits that contain the largest collection of computing artifacts in the world, from the abacus through massively-parallel supercomputers. Modern computing fundamentals are introduced, from how individual transistor circuits hold binary values, through data processing, input/output, short and long-term storage, and a wide variety of software, from the earliest punched card programs to current operating systems and programming languages. We will be coordinating hosting Raspberry Pi user groups in the area after boards start being delivered, and will provide assistance to educators and students in setting up their R-Pi systems and learning how to perform software development, from games to whatever anyone wants. We will also participate in developing educational documentation in the [http://elinux.org/RaspberryPiBoard eLinux.org R-Pi wiki] and contributing to the [http://www.computingatschool.org.uk Computing At School (CAS)] initiative.

===Schools===

==== Manchester Grammar School Computing Society, The ====
A new co-curricular club for Y9 boys aimed squarely at the new "UK Computing in Schools" initiative. Details of what we're doing are on the [[MGS Computing Society page]].

==== Winsford E-Act Academy Programming Club ====
This is an after-school club set up to encourage students to learn programming and more about how computers work. There's a blog site to support the club at [http://teampython.wordpress.com/ teampython]. We are very excited about the Raspberry Pi and can't wait to get our hands on one. For the time being, we are learning Python 3 with Pygame. To get the students used to using Linux, we are using a remaster of Puppy that's available here: [http://teampython.wordpress.com/2012/03/03/while-you-wait-for-your-raspberry-pi-why-not-use-racypy2/ RacyPy2]. Anyone who wants to join in online or share ideas is very welcome!

===Universities===
==== Kent - School of Computing, The University of ====
Many of both the students and staff at the [http://www.cs.kent.ac.uk/ School of Computing] have been following the Raspberry Pi for a long time and are eagerly waiting to get started on projects using them. We are also strong supporters of the Foundation's objective in getting more young people interested in "real" computing rather than just playing games or web browsing.

==== Manchester - School of Computer Science, University of ====
[http://pi.cs.man.ac.uk Pi Projects at Manchester]. We've got a competition for the best Raspberry Pi Project starting soon, and are getting activities together for schools and youth groups.

We want to use the Raspberry Pi with a simple hardware board and set of downloadable activities to use it to encourage young people (or anyone else) get into embedded computing. We're currently looking at [http://piface.openlx.org.uk piface] for the interface board and trying to come up with little activities to do. We've got some ideas but would love some more if anyone else wants to get involved.

We already run Linux workshops for schools and the [http://animation12.cs.manchester.ac.uk National UK Schools Animation Competition], which uses Scratch.

== Educational Links ==

===Programming languages===
''Items in '''bold''' specifically support the Raspberry Pi device''

* '''http://www.kidsruby.com/ - Have fun and make games, or hack your homework using Ruby! Just tell your parents or teachers you're learning Ruby programming... ;)'''
* http://scratch.mit.edu/ - Graphical OO-based visual programming environment.
* http://www.alice.org/ - Similar to scratch AFAICT
* http://python.org/ - The original 'designed for teaching' language of the 90s
* http://lua.org/ - Small, extensible and fits in your head
* BBC BASIC - The original 'designed for teaching' language of the 80s - A large number of implementations are listed here: http://www.bbcbasic.co.uk/bbcbasic.html
* http://basic256.org/index_en - Another BASIC variant with integrated IDE and simple graphics.
* C/C++ via GCC + CMake build system for advanced use.
* Alice (http://en.wikipedia.org/wiki/A…..(software)) – event-driven object-oriented programming via drag-and-drop programming. A variant with an even stronger storytelling approach is Story Telling Alice.
* Baltie (http://www.sgpsys.com/) – graphics-oriented programming to execute commands, conjure pictures, exercise logical thinking, etc., via play and imagination.
* CiMPLE (http://www.uptosomething.in/we…..log/?p=531) – visual programming language for the Indian iPitara robotic kit with a strong resemblance to the C programming language.
* E-Slate (http://e-slate.cti.gr) – exploratory learning environment workbench and pre-fabricated, interoperable computational objects. Software Microworlds are easily constructed by plugging components in various configurations, and the behavior of both components and Microworlds can be programmed in a Logo-based scripting language implemented in Java.
* E-Toys (http://www.squeakland.org/) - an educational tool based on Squeak Smalltalk for teaching children powerful ideas via a media-rich authoring environment and visual programming system.
* Fluxus (http://linux.softpedia.com/progDownload/fluxus-Download-15847.html) - reads live audio, OSC network messages, keyboard, or mouse input for simple game development, and a physics engine is included for real-time simulations of rigid-body dynamics. The built-in Scheme code editor runs on top of the renderer, allowing editing of scripts while they are running. Fluxus supports procedural modeling and animation, texturing, and basic material properties.
* Frink (http://futureboy.us/frinkdocs) - a full-featured programming language for physical computations which runs on the Java Virtual Machine and has both a terminal-like interface as well as a standard program editor.
* GA Viewer (http://www.geometricalgebra.net/gaviewer_download.html) - open source Linux graphical calculator for Geometric Algebra (GA) for physical applications, a mathematical lingua franca uniting and replacing vectors, quaternions, differential forms, complex analysis, many linear algebra and tensor applications, and homogenous and conformal systems. It condenses the full, relativistic form of Maxwell`s equations into just four symbols and also works well in every other area of physics, including quantum mechanics.
* Guido van Robot (http://en.wikipedia.org/wiki/G….._van_Robot) – robot control program similar to Logo or Karel, with a minimal Python syntax. A variant that includes the full Python syntax and a canonical set of lessons called RUR-PLE also exists.
* Hackety Hack (http://en.wikipedia.org/wiki/H…..ckety_Hack) – Ruby-based environment aiming to make learning programming easy for teenagers.
* Karel, Karel++, and Karel J. Robot (http://en.wikipedia.org/wiki/K….._language)) – for absolute beginners, used to control a simple robot in a city consisting of a rectangular grid of streets. Karel is its own programming language, Karel++ is a version of Karel implemented in C++, and Karel J. Robot is a version of Karel implemented in Java. NCLab offers free Karel programming (albeit with a modified syntax closer to Python) through a web browser.
* Kodu (http://en.wikipedia.org/wiki/Kodu) – entirely icon-based Microsoft Research project for younger children and especially girls. Programs are composed of pages, which are divided into rules, which are further divided into conditions and actions, and conditions are evaluated simultaneously. Designed for game development and provides specialized primitives derived from gaming scenarios. Programs are expressed in physical terms, using concepts like vision, hearing, and time to control character behavior. Available as a free Windows download in public beta and academic forms, and as a low-cost Xbox 360 Live download.
* Laby (http://www.pps.jussieu.fr/~gimenez/laby) – teaches various programming languages (OCaml, Python, Lua, Ruby, C, Java, Prolog and Perl) via ants and spider webs.
* Learn to Program BASIC (circa 1998) – BASIC interpreter with an interactive course intended to teach the language to middle school students. Game-specific additions to the BASIC language include 2D sprite support. Programs written in "LTPB" could be executed on computers without the software by means of a freely-distributable "runner".
* Lego Mindstorms (http://en.wikipedia.org/wiki/L…..Mindstorms) – Lego sets combining programmable bricks with electric motors, sensors, Lego bricks, and Lego Technic pieces (such as gears, axles, and beams). Mindstorm programs can be implemented in Logo, BASIC, Java derivatives, Smalltalk, and C.
* LegoSheets – a programming language for the Lego Mindstorms based on AgentSheets which had a less steep learning curve than Brick Logo.
* Mama (http://en.wikipedia.org/wiki/M….._(software)) – object oriented programming language for young students in a subset of their local human language, both left-to-right (LTR) and right-to-left (RTL) syntaxes. A variant of Mama was built on top of Alice for scripting of 3-D stage objects for building 3D animations and games.
* OfLiveCoding (http://code.google.com/p/oflivecoding/) - allows modification of a Javascript program at runtime, allowing real-time views of how the modifications affect the behavior and flow of the executed code.
* Phrogram (http://en.wikipedia.org/wiki/Phrogram) – second-gen Kid"s Programming Language is a commercial easy-to-learn programming language and integrated development environment (IDE) that emphasizes graphics and sounds, is a simplified structured language, offers component-based development features such as classes and methods, and is modeled on Eclipse and Visual Studio .NET IDEs to help transition to them.
* Processing (http://processing.org) - an open-source programming language and environment for creating images, animations, and interactions to teach fundamentals of computer programming within a visual context. Interactive programs creating 2-D, 3-D, or PDF output, supports OpenGL accelerated 3-D, projects run online or as double-clickable applications, and over 100 libraries extend the software into sound, video, computer vision, and more.
* ProcessingJS (http://processingjs.org/) - Javascript version of Processing allowing code to be run within a web browser.
* Pynguin (http://code.google.com/p/pynguin) – Python Turtle Graphics editor, interactive console, and graphics display area implemented in Python and the PyQt toolkit (in contrast to the wxPython of PythonTurtle). Meant to be an easy environment for introducing programming concepts to beginning programmers.
* PythonTurtle (http://en.wikipedia.org/wiki/P…..thonTurtle) – LOGO-like turtle graphics implemented in wxPython. There is also Python standard Turtle graphics module (based on TK), and Python Turtle Demo examples for using Python and turtlegraphics in an educational setting.
* RoboMind (http://en.wikipedia.org/wiki/RoboMind) – educational programming environment that lets beginners program a robot via popular programming techniques, some robotics, and artificial intelligence principles. The robot can be programmed in Arabic, Chinese, Dutch, German, English and Swedish.
* Stagecast Creator (http://en.wikipedia.org/wiki/S…..st_Creator) – visual programming system based on programming by demonstration via movement of icons on the screen, and it generates rules for the objects (characters). Users can create two-dimensional simulations that model a concept, multi-level games, interactive stories, etc.

===Communities===

* http://madlab.org.uk/about/ - The Manchester Digital Laboratory
* [http://www.stemnet.org.uk/ The Science, Technology, Engineering and Mathematics Network, UK] - This covers all the red tape that is necessary when working with children, as well as networking with other like-minded volunteers to share ideas.
* [http://www.raspberryprojects.com/ Raspberry Projects] - Site dedicated to blogging plans as well as showing off completed projects.
* [http://www.schoolforge.net/ SchoolForge.net] - SchoolForge's mission is to unify independent organizations that advocate, use, and develop open educational resources.
* [http://www.wise-qatar.org WISE-Quatar.org] - The World Innovation Summit for Education (WISE) is an international platform for creative thinking, debate and action to raise the status of education through year-round programs to transform education by highlighting its leading role in global development, and by fostering innovative thinking and practices. Efforts include:<ul><ul>
<li> [http://www.wise-qatar.org/content/about-summit WISE Summit] - 1,000 top decision-makers, thought-leaders, practitioners and education stakeholders from over 100 countries share best practices</li>
<li> WISE Prize for Education - recognizes an individual or a team for a world-class contribution to education</li>
<li> [http://www.wise-qatar.org/awards WISE Awards] - identify and spotlight each year six of the most innovative projects in education from around the world</li>
<li> [http://www.wise-qatar.org/content/wise-prize-education WISE Publications] - "Innovation in Education: Lessons from Pioneers around the World"</li>
<li> Learners' Voice - encourages students aged 18 - 25 to make their voices heard as full delegates, participating in sessions, conducting video interviews, blogging and tweeting on a year-round basis</li>
<li> Online Collaborative Web Platform - interactive knowledge base that offers a wide range of tools</li>
<li> [http://www.wise-qatar.org/my-wise MyWISE] - social networking that enables the WISE community to connect and share knowledge and best practices on a continuing basis</li>
<li> [http://www.wise-qatar.org/learning_world Learning World] - weekly TV magazine program on education developed in partnership with Euronews broadcast 16 times a week to 155 countries in 11 languages</li>
<li> WISE Haiti Task Force - brings together innovators and successful projects that can contribute to rebuilding Haiti's education system</li>
<li> WISE Program for Education Leadership - helps prepare newly appointed education leaders from the developing world</li>
</ul></ul>

===Software suites===

* http://gcompris.net/-en- - GCompris is a high quality educational software suite comprising of numerous activities for children aged 2 to 10. ''Confirmed working on alpha boards''.
* http://www.sugarlabs.org/ - The Sugar Sweet, a desktop environment used on the XO One Laptop Per Child.
* [http://en.opensuse.org/openSUSE:Education-Li-f-e OpenSUSE Linux for Education (LiFE)] - an open-source Linux operating system with educational software.
* [http://puppylinux.org/wikka/Education PuppyLinux.org/wikka/Education] - Puppy Linux lightweight, open-source, educational distribution including OpenOffice, TuxType2, TuxMath, GCompris and SuperTux.

===Libraries/applications===

* http://arstechnica.com/gaming/news/2006/02/games-perl.ars - Developing games with Perl and SDL
* http://www.pygame.org/ - Simple SDL wrapper for Python.
* http://docs.python.org/library/idle.html - The Python IDE that comes with Python.
* http://love2d.org/ - Something akin to pygame for Lua.
* https://github.com/ntoll/RaspberryPy - An interactive set of programming lessons for Python, written in Python. To be built at PyconUK (http://pyconuk.org) during the sprints. :-)
* http://www.khronos.org/openvg/ - OpenVG vector graphics library. Natively supported by GPU(?)
* [http://en.wikipedia.org/wiki/Hackety_Hack Hackety Hack] - an open source application that teaches coding in a simple manner.

===General resources===

* [http://www.cs4fn.org/ ComputerScienceForFun.org] - Computer Science for Fun
* [http://computingatschool.org.uk/ ComputingAtSchool.org.uk] - Computing at School Working Group
* [http://en.literateprograms.org/LiteratePrograms:Welcome LiteratePrograms.org]- An MIT project to develop programs which are self describing.
* [http://www.happynerds.net/view/linux HappyNerds.net] - External site listing educational programming resources for children.
* [http://projectguts.org/ ProjectGuts.org] - An extracurricular program in the US teaching programming using LOGO-like language.
* [http://www.CodeAcademy.com/ CodeAcademy.com] - Learn how to code - it's interactive, fun, and you can do it with your friends - for free.

===Articles/opinion pieces/trade bodies===

'''In the UK:'''
* http://royalsociety.org/education/policy/computing-in-schools/ - The Royal Society's Computing in Schools project
* http://securiously.wordpress.com/2011/09/09/do-we-really-need-to-teach-our-kids-to-code/ - Teaching the skills associated with programming rather than programming as an aim in itself.

'''General:'''
* http://www.edutopia.org/programming-the-new-literacy - Programming is the new literacy
* http://bengoldacre.posterous.com/three-things-we-have-to-teach-in-schools - Ben Goldacre's list of "Three things we have to teach in schools"

* http://blog.jgc.org/2011/09/teach-our-kids-to-code.html
* http://www.osnews.com/story/6282 - An article on the command-line as a good interface for new users.

===Direct action===

* http://epetitions.direct.gov.uk/petitions/15081 - A petition to the Department for Education about teaching programming in schools (UK only).

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi DatasheetCategories

2012-08-06T21:57:14Z

Lxndr: added references, template, category

{{Template:RPi_Learning}}

'''This is a list of the proposed datasheet numbers for Rpi categories: '''
Created by turbo at frambozenbier.org for the community documentation project 

As discussed on the main raspberrypi.org forums, this documenation will be: 
 
1) Born on the wiki 
2) Peer reviewed on the wiki and approved by community members 
3) Then translated by community members 
4) Then published as a full article or PDF by the frambozenier.org documentation team 
 
'''Categories '''

001-100 Raspberry Pi Foundation product literature 
[[Rpi_Datasheet_001_Raspberry_Pi_Foundation]] 
101-200 Raspberry Pi Foundation announcements 
201-300 Raspberry Pi Computing devices 
[[Rpi_Datasheet_201_Raspberry_Pi_Computer]] 
[[Rpi_Datasheet_202_Rasperry_Pi_IO]] 
301-400 Raspberry Pi Computing accessories 
401-500 Raspberry Pi Getting started guides 
[[Rpi_Datasheet_401_Connecting_Together]] 
501-600 Raspberry Pi Operating system guides 
601-700 Raspberry Pi Development tools and libraries 
701-800 Raspberry Pi Utilities and Code Examples 
[[Rpi_Datasheet_701_Downloading_OS_Images]] 
[[Rpi_Datasheet_751_GPIO_Registers]] 
801-900 Raspberry Pi Hardware compatibility 
901-999 Raspberry Pi Software compatibility 

 '''NOTE: some of this information may initially duplicate other content on this and other Raspberry Pi sites. The purpose of this project is to collate all relevant community documentation into simple 2-page datasheets. '''

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Tasks

2012-08-06T21:56:52Z

Lxndr: added references, template, category

[[Category: Linux]]
[[Category:ARM Development Boards]]
[[Category: Broadcom]]
[[Category: Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]
{{Template:RPi_Learning}}

==About==

This page lists key functionality missing from [http://www.raspberrypi.org Raspberry Pi Foundation's] ultra-low-cost (~15UKP or 25USD) Linux computer for teaching computer programming to children, and encourages the community to provide a solution.

The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409) which exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. We expect this computer to have many other applications both in the developed and the developing world.

'''Please note that the Raspberry Pi has only just been released - this page is a community work in progress in preparation for when people get their devices. Please also note that we will be setting up a repository for uploading contributions, but this isn't ready yet so please simply use [http://pastebin.com http://pastebin.com] or [http://dropbox.com http://dropbox.com] and provide a link from this page, until we have something set up'''

It is intended that these tasks will be implemented by the Raspberry Pi community.

==OTG device mode==

Inspired by the device mode idea below: Allow the Raspberry Pi to work as an USB device. Sharing the SD card as a storage device is one option. But becoming an USB-display is another.

Decisions to make: Run Linux on the "device mode" Raspberry Pi or not?

Difficulties: the Raspberry Pi has a "device mode" connector, but the data pins are unconnected. Solutions: Use the USB connector on a Model A with a custom cable/converter, or find pins on the board to attach patchwires to.

==OTG Device mode==

'''The idea''': A student has damaged or wiped the OS on their SDCard. By plugging two Raspberry Pi's back-to-back using the Mini-AB cable with the white end attached to the working device and a recovery SDcard image in the non-working device, the firmware will allow the non-working unit's SD card to be accessible to the working unit.

'''The detail''': Once both devices are booted, the recovery image runs completely from RAM. The SDcard can be ejected and the damaged or wiped SDcard inserted. The SDcard of the working machine can then be cloned.

'''The task''': The device won’t support device mode out of the box, though we’re using a Synopsys OTG core so the hardware is there and the firmware is open, so it might be possible. I suspect if you forced 5V onto the USB power rail it would boot. (Note: Maybe not: There might be a 140mA Polyfuse in there).

A device driver would need to be written and a recovery image created. A command line tool set will need to be provided to deliver the functionality described above.

===Possibly simpler recovery idea===
How about a recovery application as part of the standard image, that can run from RAM? This just needs a working SDcard. The goal is to clone the working SDcard to a "bricked" SDcard.

Here's a possible workflow:

# Start the device with a working SDCard.
# Start the "recovery" application. This probably does super kernel/driver magic to only provide text out, and SDcard mounting/unmounting, and prompts the user.
# Using the available RAM as buffer, load the first 128/256 MB (minus 1 MB for the recovery thing.)
# Ask the user to switch to the "bricked" card.
# Write the first 128/256 MB to the bricked card.
# Keep swapping, 16 times (or 8, if you have a 256 MB device)
# If the card has two partitions, one for OS, and one for user files, the number of swaps needed is smaller.

With two devices, this can be improved to something similar to the original suggestion, but using a simple binary that comes with the distribution:

# Start device 1 with a working SDcard.
# Run the "brick recovery" application. This makes sure to lock itself in RAM. Prompt user to insert the bad card and connect device 2.
# Start device 2 off the working SDcard and connect to device 1. (How does power work here? That might be really hard without a special "A to A" cable...)
# Run the "brick recovery" application on device 2. This detects that device 1 is already connected, and starts transferring the image from the SDcard.

The nice thing here is that recovery only needs to be a small binary on the original image, and is always available, and would be available even without a USB cable in case 1.

The special affordances needed by the recovery application are:

# Switch graphics into text mode, or some other super-simple presentation mode that doesn't need lots of RAM.
# Run the SDcard port.
# Stop everything else from happening.
# Lock the recovery application and SDcard driver into RAM.
# Optional USB driver for 2-device recovery, also coded into the recovery app.

Once the kernel has that "take over the device" mode, I'm sure some neato to-the-metal applications will also spring up ;-)

===An Even Simpler Backup/Restore Idea===
A much easier and less error-prone recovery method would be to clone the current system's SDcard to another card in a USB writer. The software required could be a simple shell script wrapper around dd, maybe using dialog for prompts and warnings and confirmations.

USB SDcard Reader/Writers are cheap - even Amazon has them for $1.75, retail price for single units, and you can probably find them even cheaper if you google for "USB SDcard writer". Some writers are as small as USB thumb-drives.

They could offered as an optional purchase along with a Raspberry Pi, or schools could be given one or two with larger orders, along with instructions on how to use them to restore a student's damaged SDcard.

This could be treated as a mundane "Backup Your SDcard" procedure, rather than as a scary last resort.

==mkcard.sh==

'''The idea''': A script which partitions and formats the SDcard ready for software.

'''The detail''': BeagleBoard community uses something similar, see http://www.angstrom-distribution.org/demo/beagleboard/ and http://www.xora.org.uk/2009/08/14/omap3-sd-booting/

'''The task''': Write a script to create a FAT32 partition for the GPU firmware and a EXT3 partition for the rootfs.

[[User:Tomato|Tomato]] 22:08, 22 October 2011 (UTC)

Some of my past projects use such a script to generate a sdcard. I modified it, so it does only the requested things ( removed the part that installs a MBR and copies files to the card ). It can be found here http://pastebin.com/u9Qpm5n0. ATM the partitions are ~80 MB for ext, rest of the card for FAT32 (can be changed on request).

==delay_copy.sh==

'''The idea''': A script that copies files from an attached USB flash drive to the SDcard after a delay, allowing the user to unplug the keyboard or mouse and plug in the USB drive.

'''The detail''': See http://www.raspberrypi.org/?page_id=43&mingleforumaction=viewtopic&t=152.0

'''The task''': Write the script. Make it bullet proof.

=== Automatic, no delay solution ===
--[[User:Markit|Markit]] 21:24, 26 October 2011 (UTC)
* Download [http://igurublog.wordpress.com/downloads/script-devmon/ devmon].
* Start a daemon with
** <nowiki>devmon --no-gui --exec-on-drive "cp -r /directory/to/copy/each/time %d;devmon --unmount-recent;echo Copy complete, safe to remove | wall"</nowiki>

[[User:Tomato|Tomato]] 23:38, 26 October 2011 (UTC)

{
* "rsync -ac /directory/to/copy/each/time %d" might be better suited to transfer the files to the card.
* "sync" to flush the buffers afterwards couldn't hurt either
}
* Each time a usb key is added, the daemon will automatically copy the folder, unmount the disk and send a message to all connected local/ssh terminals.
udev could also be used.

== RISC OS ==

*Discussion and task list being developed on the [http://www.riscosopen.org/forum/forums/5/topics/783 ROOL site].

==R-Pi System/Data Management==
--[[User:Meltwater|Meltwater]] 20th Dec 2011

Details here:
[http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1204 Pi in the Sky - Cloud management?]
Basic concept:
Enable ways to easily switch and share system images for the R-Pi and manage user data, allowing joint development and easy management of set-ups.
* Fast/Easy backup of system/data to external storage or network (local or cloud).
* Management/Repository of base images.
* Boot from network

This would enable a number of potential scenarios:
* Keep multiple R-Pi's synced across locations (office vs home or classroom vs home)
* Manage a multiple users of R-Pi's (i.e. classroom setup, each user's data gets synced with network so each user can continue their own work on any R-Pi)
* Easy switching of function by booting to multiple images (i.e. Media centre image, programming image, in-car image)
* Remote management of R-Pi's (by updating the master image)

The project should be able to be divided into a number of smaller projects which when put together may well be able to perform the functions we want.
* User Data sync/web mount
* System Image backup/restore (to online/local network/local)
* Bootloader with boot from online/local network/local image
* Online image repository
Project Wiki Page - [[R-Pi System/Data Management]]

'''First problem'''
Defining how user applications are managed and installed, and thus how the card is partitioned. Straw man proposal:
* FAT GPU (and boot?) partition
* EXT partition for rootfs and /usr and /var /etc ... root writable
* EXT partition for /usr/local ... all user-installed applications go here (note: traditional Linux "rpm -i something.rpm" writing everywhere in the FS is not particularly great for manageability)
* FAT partition for Windows-shareable user files -- perhaps /home is mounted here?
* Do we need swap?
* Default for bigger cards should probably be something like putting 65% of free space on /usr/local (EXT) and 35% on /home (FAT)

==Multi Code==

'''The idea''': One R_pi will be connected to another and both can work on the same code.py. So that way say a teacher wanted to help a student with code without taking over. They can just plug there pi in to the students and go through checking for mistakes ect.

'''The Conection''': Conection will probably be via Ethernet using an ''ad hoc'' Network.

'''Whats needed?''': The program needs to open .py files and edit them. Next it needs to make a shered file that is updated every time a character changes.
A different program (or same does not matter) should then connect to this file and update it in the same way. Every 10 seconds both pi's reload the shared file, thus have the same code. If the changes contradict each other then the host pi will override the connected pi.

Why not just use VNC?

How much of this "collaborative editing" is already built into Sugar? [http://wiki.laptop.org/go/Activity_sharing]

For something a little less intrusive/immediate, a DVCS like mercurial or git keeps people from stepping on each other's toes.

'''Further evolutions''': once/if the initial goals are acheved then further developments to the project would include making the systom compleatly live so there in no 10 second delay to each update. And make it posibal to connect the pi's via the Internet.

'''The initial task''': The first stage In this project is to make a file browser that can open and edit .py files.

'''More info''': for more information about the project follow @Lipj01 on twitter or email me at: Lippojac@gmail.com

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Projects

2012-08-06T21:55:57Z

Lxndr: added references, template, category

[[Category:RaspberryPi]]
{{Template:RPi_Learning}}

==Introduction==
This page contains a set of ongoing projects. When complete, these projects will create new
applications or card images or tutorials or guides. Anybody is welcome to help.

The Raspberry Pi Forum has a list of [http://www.raspberrypi.org/forum/projects-and-collaboration-general/the-projects-list-look-here-for-some-ideas Project Ideas & Links], to help people get started.

Please add links to your projects (and ones you find interesting).

Fill in each section:
* '''Project Title''' (as a link to the project webpage or connected wiki page)
* '''Project Description''' (including any additional links or information
* '''Skill Level/Ages''' it is aimed at (Any/Beginner/Intermediate/Advanced)
* '''Tags''' (Keywords related to the project, i.e. LCD Screen, Teaching, Python)
* '''Author(s) or the group who are producing it''' (also if it is an Open/Community Project for anyone to contribute)
* '''Project Status''' (Theory/Not Started/In-Progress/Available).

==Community Project List==
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Project Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Project Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Level'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[Rubus]]===
| vertical-align:top; border:1px solid #aaa;" |
[[Rubus]] is a project to create a low-cost "classroom-in-a-box" by combining the [http://www.raspberrypi.org Raspberry Pi] with a lightweight Linux distribution, useful software, educational materials, peripherals and necessary storage. The intent is to eventually produce and distribute them as a charity via donations, as well as release [[Rubus_Documentation | Documentation]] on creating the image and providing it for download.

Language localization is a secondary objective, very much based on what storage restrictions arise. It is understood that not everyone speaks English, but most educational material slated for inclusion has the most work completed in English, and even large areas of Africa speak it as a secondary language.

The name [http://eol.org/pages/794574/entries/34450015/overview Rubus] comes from the genus name of the common raspberry; we feel it's fitting for a project based on the [http://www.raspberrypi.org Raspberry Pi].

| vertical-align:top; border:1px solid #aaa;" |
Any
| vertical-align:top; border:1px solid #aaa;" |
Philanthropy, Distro, Classroom, Education, Training, Community
| vertical-align:top; border:1px solid #aaa;" |
[[User:Crouthamela | Andrew Crouthamel]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
In-Progress

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[R-Pi System/Data Management | Pi In The Sky]]===
(Wiki)
| vertical-align:top; border:1px solid #aaa;" |
Cloud Storage and Management - Basic concept: Enable ways to easily switch and share system images for the R-Pi and manage user data, allowing joint development and easy management of set-ups.
* Fast/Easy backup of system/data to external storage or network (local or cloud).
* Management/Repository of base images.
* Boot from network
Forum Link: [http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1204 Pi in the Sky - Cloud management?]

| vertical-align:top; border:1px solid #aaa;" |
Advanced
| vertical-align:top; border:1px solid #aaa;" |
Cloud, Storage, Management
| vertical-align:top; border:1px solid #aaa;" |
[[User:Meltwater | Meltwater]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Not Started

|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://www.berryterminal.com/ BerryTerminal]===
| vertical-align:top; border:1px solid #aaa;" |
[http://www.berryterminal.com/ BerryTerminal] is a project to turn the Raspberry Pi into an affordable thin-client.
It allows the user to login to a central Edubuntu or other LTSP (Linux Terminal Server Project) server, and run all applications on the central server.

Advantages of using a central server include:

* Greatly simplifies management.
* Applications only need to be installed to the central server, and are then available on all Raspberry terminals.
* Only need to backup the central server, instead of the individual Raspberries.
* Because the applications run on the central server, they are not affected by the resource limitations Raspberries have, allowing users to run applications like LibreOffice.
| vertical-align:top; border:1px solid #aaa;" |
Any
| vertical-align:top; border:1px solid #aaa;" |
Thin client, terminal, Edubuntu, LTSP
| vertical-align:top; border:1px solid #aaa;" |
Floris Bos - Open Project
| vertical-align:top; border:1px solid #aaa;" |
First beta released
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[R-Pi Home Automation| Home Automation and Monitoring]]===
| vertical-align:top; border:1px solid #aaa;" |

Home automation using Raspbery Pi is active in different places. Here are a few links

* [http://raspberrypi.homelabs.org.uk/ raspberrypi.homelabs.org.uk]
* [http://www.domoticaforum.eu www.domoticaforum.eu]

| vertical-align:top; border:1px solid #aaa;" |
Any
| vertical-align:top; border:1px solid #aaa;" |
Weather, Heating, Automation, X10, OneWire
| vertical-align:top; border:1px solid #aaa;" |
Open Project
| vertical-align:top; border:1px solid #aaa;" |
Various
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[RaspberryPi Laptop | Raspberry pi... In a laptop ]]===
| vertical-align:top; border:1px solid #aaa;" |
Me and my colleagues are starting a computer company and we are making our first prototype with a raspberry pi! Slim,Sleek, and just plain awesome! Boy, Will this be interesting! Of course it is just a prototype and speed doesn't matter in this case. Stay tuned here and [http://www.raspberrypilaptop.tk here]!
| vertical-align:top; border:1px solid #aaa;" |
Various.
| vertical-align:top; border:1px solid #aaa;" |
Prototype, Laptop
| vertical-align:top; border:1px solid #aaa;" |
[[User:hackery21 | hackery21]] - Suggestions Accepted
| vertical-align:top; border:1px solid #aaa;" |
In-Progress

|-
| vertical-align:top; border:1px solid #aaa;" |

===[[R-Pi Blueproximity2 | BlueProximity 2.0 ]]===
| vertical-align:top; border:1px solid #aaa;" |
Detect presence in any room via a small number of R-Pis and Bluetooth Devices
[[http://blueproximity.sf.net Blueproximity]] is already there, this will be a complete rewrite to manage sensor networks and put some fuzzy logic on top.
| vertical-align:top; border:1px solid #aaa;" |
Medium
| vertical-align:top; border:1px solid #aaa;" |
Bluetooth, Presence, Sensors, Network, Home Automation
| vertical-align:top; border:1px solid #aaa;" |
[[User:highno | highno]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Ideas and first code is setup

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi_Projects/R-Pi Seed Field | Raspberry Pi Seed Field ]]===
| vertical-align:top; border:1px solid #aaa;" |
Provides a simple torrent centre that allows users to host a seedbox.
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Torrents, Seeding, Web, Internet, Linux
| vertical-align:top; border:1px solid #aaa;" |
[[User:SeanB | SeanB]] - Open Project/Suggestion
| vertical-align:top; border:1px solid #aaa;" |
Theory

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[https://docs.google.com/document/d/1tI1sBstetYyMbfRXNgeQF5y3UwWD89jUH46S5X-bHE8/edit | Arr (Audio relay raspi) ]]===
| vertical-align:top; border:1px solid #aaa;" |
The idea is to create a wireless speaker. Being able to get audio from smartphones or computers. Protocols like DLNA, Airplay and A2DP could be supported. An advanced option could be to use pulse audio libraries from linux to synchronize music on multiple raspis.
The speakers attached to the raspberry pi could be a commercial ones or your HiFi but we are also thinking about some DIY solutions. For instance one could install the raspi and the speakers on the ceiling of multiple rooms.
| vertical-align:top; border:1px solid #aaa;" |
Any
| vertical-align:top; border:1px solid #aaa;" |
DLNA, Airplay, Pulse, Audio, Music, Speaker, HiFi
| vertical-align:top; border:1px solid #aaa;" |
[[User:Jordi | Jordi]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
In-Progress

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[http://www.raspberryprojects.com | Raspberry Projects ]]===
| vertical-align:top; border:1px solid #aaa;" |
Collaboration of projects from start to finish from all levels of knowledge.
| vertical-align:top; border:1px solid #aaa;" |
Various.
| vertical-align:top; border:1px solid #aaa;" |
Education, Entertainment, Home, Auto & Others.
| vertical-align:top; border:1px solid #aaa;" |
[[User:symondavis | Symon Davis]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Various

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi_Projects/WiringPi | WiringPi ]]===
| vertical-align:top; border:1px solid #aaa;" |
WiringPi is a library by Gordon Henderson which seeks to bring easy GPIO access in both shared-memory and /sys/class/gpio modes to the Pi. The WiringPi project seeks to wrap this library for a variety of languages, creating a standardised way of working with the Raspberry Pi hardware.

WiringPi currently works with C, Ruby, Python and Perl.

Gordon's pages on WiringPi are here: https://projects.drogon.net/raspberry-pi/wiringpi/

And the GitHub organisation is here: https://github.com/WiringPi
| vertical-align:top; border:1px solid #aaa;" |
Various.
| vertical-align:top; border:1px solid #aaa;" |
GPIO, Serial
| vertical-align:top; border:1px solid #aaa;" |
Original author: Gordon Henderson
Open Project - All ideas and contributions welcome
| vertical-align:top; border:1px solid #aaa;" |
In-Progress

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi_Projects/serialJpegCam | Serial JPEG camera (TTL, µCAM ]]===
| vertical-align:top; border:1px solid #aaa;" |
Attaching the "Serial JPEG µCAM" ([http://www.coolcomponents.co.uk/catalog/camera-module-serial-jpeg-p-369.html?osCsid=j90j5kqfegquksdbumahtmuqg5|coolcomponents, UK]) to the GPIO pins and take pictures on command.
| vertical-align:top; border:1px solid #aaa;" |
Easy hardware wise (no soldering), an understanding of compiling needed.
| vertical-align:top; border:1px solid #aaa;" |
camera, hardware, gpio, ttl, serial ucam, image, photo
| vertical-align:top; border:1px solid #aaa;" |
dirkx
| vertical-align:top; border:1px solid #aaa;" |
completed
--.

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi_Projects/Digital_Signage | Digital Signage ]]===
| vertical-align:top; border:1px solid #aaa;" |
A place to collect information about using the Raspberry Pi to drive displays of useful information.
| vertical-align:top; border:1px solid #aaa;" |
Various
| vertical-align:top; border:1px solid #aaa;" |
digital signage, kiosk, public displays, dashboards
| vertical-align:top; border:1px solid #aaa;" |
[[User:chrowe | chrowe]]
| vertical-align:top; border:1px solid #aaa;" |
Various
--.

<!-- Example List Item: (Please copy and do not remove for future reference)
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi_Projects/Link-To-Project | Title of Project ]]===
| vertical-align:top; border:1px solid #aaa;" |
A Simple description of what it does.
| vertical-align:top; border:1px solid #aaa;" |
The Difficulty goes here.
| vertical-align:top; border:1px solid #aaa;" |
Tags of what it does.
| vertical-align:top; border:1px solid #aaa;" |
[[User:Username-Here | Username-Here]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Project Status
--.

}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Guides

2012-08-06T21:55:42Z

Lxndr: added references, template, category

{{Template:RPi_Learning}}

==Introduction==

This page contains a set of guides to show readers how to do useful tasks. These guides focus on achieving a goal as simply as possible, with the aim to build the confidence of the reader. Hopefully, the reader will also be inspired to learn at the same time.

The Raspberry Pi Forum has a list of [http://www.raspberrypi.org/forum/projects-and-collaboration-general/the-projects-list-look-here-for-some-ideas Project Ideas & Links], to help people get started.

Please add links to your guides (and ones you find interesting).

Fill in each section:
* Guide Title (as a link to the project webpage or connected wiki page)
* Guide Description (including any additional links or information
* Tags (key words related to the project, i.e. LCD Screen, Teaching, Python)
* Author(s) or group who have produced it (also if it is an Open/Community Project for anyone to contribute)
* Guide Status (Not Started/In-Progress/Available).

==Absolute beginners==
Suitable for absolute beginners who have never experimented with Linux before.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[RPi Chromium | Installing Chromium web browser]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing the Chromium web browser on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Chromium
| vertical-align:top; border:1px solid #aaa;" |
bredman
| vertical-align:top; border:1px solid #aaa;" |
Ready for testing
|-
|}

==Easy==
Suitable for beginners who are confident typing commands into Linux but need a lot of guidance.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[R-Pi NAS | Network Attached Storage]]===
| vertical-align:top; border:1px solid #aaa;" |
Network Attached Storage - Basic concept: A place to save copies of all your important files
| vertical-align:top; border:1px solid #aaa;" |
Samba
| vertical-align:top; border:1px solid #aaa;" |
[[User:bredman | bredman]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Tested on Debian, some help needed with Fedora chapter
|-
| vertical-align:top; border:1px solid #aaa;" |

===[[RPi Debian Python3 | Python 3 on Debian]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing the latest Python 3 and common modules on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Python
| vertical-align:top; border:1px solid #aaa;" |
croston
| vertical-align:top; border:1px solid #aaa;" |
Tested. Needs more modules adding
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Debian Auto Login | Debian Auto Login/Startx]]===
| vertical-align:top; border:1px solid #aaa;" |
How to launch LXDE without the need of a username/Password in Debian.
| vertical-align:top; border:1px solid #aaa;" |
LXDE, Boot, Login, Auto
| vertical-align:top; border:1px solid #aaa;" |
Ian Hartwell (helpme1986)
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPiForked-Daapd]]===
| vertical-align:top; border:1px solid #aaa;" |
How to install Forked-Daapd, an itunes media server
| vertical-align:top; border:1px solid #aaa;" |
Debian, streaming,
| vertical-align:top; border:1px solid #aaa;" |
Greg (pr1sm)
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Setting up a static IP in Debian | Setting up a static IP in Debian]]===
| vertical-align:top; border:1px solid #aaa;" |
How to set-up a static IP in Debian
| vertical-align:top; border:1px solid #aaa;" |
Debian, Static IP
| vertical-align:top; border:1px solid #aaa;" |
sleepy
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
|}

==Medium==
Suitable for beginners who are willing to experiment and only need a little guidance.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[R-Pi PXE Server | Classroom Boot Server]]===
| vertical-align:top; border:1px solid #aaa;" |
Classroom boot server - Basic concept: A PXE server to allow cheap computers without hard disks to boot into Windows or Linux.
| vertical-align:top; border:1px solid #aaa;" |
PXE, netboot
| vertical-align:top; border:1px solid #aaa;" |
[[User:bredman | bredman]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
Lots of random text, needs organisation and testing
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Ruby on Rails | Installing Ruby on Rails]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing Ruby on Rails and common modules on Debian.
| vertical-align:top; border:1px solid #aaa;" |
Ruby, Rails
| vertical-align:top; border:1px solid #aaa;" |
Erik
| vertical-align:top; border:1px solid #aaa;" |
Partially tested. Still early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi VNC Server | Share your screen with VNC]]===
| vertical-align:top; border:1px solid #aaa;" |
Installing VNC to allow remote control of the screen from another computer.
| vertical-align:top; border:1px solid #aaa;" |
VNC
| vertical-align:top; border:1px solid #aaa;" |
Simon H
| vertical-align:top; border:1px solid #aaa;" |
Early draft.
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi iSCSI Initiator | iSCSI support and boot]]===
| vertical-align:top; border:1px solid #aaa;" |
Adding iSCSI initiator/target support, setting up iSCSI initiator, and configuring booting from an iSCSI volume.
| vertical-align:top; border:1px solid #aaa;" |
iSCSI, netboot
| vertical-align:top; border:1px solid #aaa;" |
Alex (nidO)
| vertical-align:top; border:1px solid #aaa;" |
Early draft, tested
|-

| vertical-align:top; border:1px solid #aaa;" |
===[[RPi_Email_IP_On_Boot_Debian | Send email containing Pi ip address on boot]]===
| vertical-align:top; border:1px solid #aaa;" |
Send email containing the ip of your Pi so you can access via SSH or other network protocol when your ip changes (moving networks) and you are working headless
| vertical-align:top; border:1px solid #aaa;" |
SSH, email, python
| vertical-align:top; border:1px solid #aaa;" |
--[[User:Geraldcor|Geraldcor]] 03:36, 18 June 2012 (UTC)
| vertical-align:top; border:1px solid #aaa;" |
Early draft, tested
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://www.penguintutor.com/linux/tightvnc Connecting securely to TightVNC over the Internet]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to installing Tightvnc server on the Raspberry Pi and securing it using ssh to allow connecting over the Internet.
| vertical-align:top; border:1px solid #aaa;" |
VNC, ssh
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://www.penguintutor.com/linux/raspberrypi-webserver Configuring a LAMP webserver]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to configuring the Raspberry Pi as a LAMP (Linux, Apache, Mysql, PHP) webserver.
| vertical-align:top; border:1px solid #aaa;" |
apache, mysql, php
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[https://github.com/ewindisch/chefiler Storage Filer/NAS via Chef]===
| vertical-align:top; border:1px solid #aaa;" |
Turn-key package to turn a machine into a storage filer / NAS. Developed and tested on a RaspberryPi. Still in early development. Deploys with Chef.
| vertical-align:top; border:1px solid #aaa;" |
samba, nfs, chef
| vertical-align:top; border:1px solid #aaa;" |
Eric Windisch
| vertical-align:top; border:1px solid #aaa;" |
Alpha/early-stage
|-

|}

==Advanced==
Suitable for confident users who want to try something more advanced.
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Guide Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi building and installing OpenELEC | building and installing OpenELEC]]===
| vertical-align:top; border:1px solid #aaa;" |
How to build and install OpenELEC,a embedded Multimedia Distro. You can learn (cross)compiling, building packages from source, how buildsystems are working and what is needed to install a OS on a SD-card for Raspberry Pi.
| vertical-align:top; border:1px solid #aaa;" |
XBMC, HTPC, Multimedia, Distro, compiling
| vertical-align:top; border:1px solid #aaa;" |
Stephan Raue
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Using Skypekit | Using Skypekit]]===
| vertical-align:top; border:1px solid #aaa;" |
How to get started using Skypekit to make calls & chat. This is currently only useful for advanced users & developers.
| vertical-align:top; border:1px solid #aaa;" |
Skype, Skypekit
| vertical-align:top; border:1px solid #aaa;" |
Henry Cooke
| vertical-align:top; border:1px solid #aaa;" |
Alpha.
|-

| vertical-align:top; border:1px solid #aaa;" |

===[http://www.penguintutor.com/linux/raspberrypi-headless Pre-configuring SD card with a static IP address]===
| vertical-align:top; border:1px solid #aaa;" |
Guide to pre-configuring a SD image so that it boots with a static IP address. Useful for running headless without needing to know what DHCP address will be allocated.
| vertical-align:top; border:1px solid #aaa;" |
networking, tcpip
| vertical-align:top; border:1px solid #aaa;" |
Stewart Watkiss
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

|}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Tutorials

2012-08-06T21:55:17Z

Lxndr: added references, template, category

{{Template:RPi_Learning}}

==Introduction==
This page contains a set of tutorials to help the reader to learn by doing. The reader is encouraged to follow the steps in the tutorials.

The Raspberry Pi Forum has a list of [http://www.raspberrypi.org/forum/projects-and-collaboration-general/the-projects-list-look-here-for-some-ideas Project Ideas & Links], to help people get started.

Please add links to your tutorials (and ones you find interesting).

Fill in each section:
* Tutorial Title (as a link to the project webpage or connected wiki page)
* Tutorial Description (including any additional links or information
* Skill level/Ages it is aimed at (Any/Beginner/Intermediate/Advanced)
* Tags (key words related to the project, i.e. LCD Screen, Teaching, Python)
* Author(s) or group who have produced it (also if it is an Open/Community Project for anyone to contribute)
* Tutorial Status (Not Started/In-Progress/Available).

==Tutorials List==
{| border="1" style="background:transparent;"
| style="width:15%; vertical-align:top; border:1px solid #aaa;" |
'''Tutorial Title and Link'''
| style="width:40%; vertical-align:top; border:1px solid #aaa;" |
'''Description'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Level'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Tags'''
| style="width:10%; vertical-align:top; border:1px solid #aaa;" |
'''Author'''
| style="width:7%; vertical-align:top; border:1px solid #aaa;" |
'''Status'''
|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://log.liminastudio.com/writing/tutorials/tutorial-how-to-use-your-raspberry-pi-like-an-arduino Tutorial: How to use your RPi like an Arduino]===
| vertical-align:top; border:1px solid #aaa;" |
A thorough guide to using the RPi's GPIO pins in Python, Bash and C.
| vertical-align:top; border:1px solid #aaa;" |
Intermediate
| vertical-align:top; border:1px solid #aaa;" |
Teaching, Python, Bash, C
| vertical-align:top; border:1px solid #aaa;" |
T3db0t
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials]===
| vertical-align:top; border:1px solid #aaa;" |
Forum Link: [http://www.raspberrypi.org/forum/educational-applications/video-tutorials Liam Fraser's Video Tutorials]
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Teaching, Python
| vertical-align:top; border:1px solid #aaa;" |
Liam Fraser
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://h2g2.com/dna/h2g2/brunel/A13735596 Introducing the Raspberry Pi]===
| vertical-align:top; border:1px solid #aaa;" |
h2g2 project: [http://h2g2.com/dna/h2g2/brunel/A13735596 Introducing the Raspberry Pi]
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup guide
| vertical-align:top; border:1px solid #aaa;" |
Tufty
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://log.liminastudio.com/writing/tutorials/getting-started-with-the-raspberry-pi Getting Started with the Raspberry Pi]===
| vertical-align:top; border:1px solid #aaa;" |
Introductory tutorial for total beginners to get your Raspberry Pi booted and online : [http://log.liminastudio.com/writing/tutorials/getting-started-with-the-raspberry-pi Getting Started with the Raspberry Pi]
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup guide
| vertical-align:top; border:1px solid #aaa;" |
T3db0t
| vertical-align:top; border:1px solid #aaa;" |
Available
|-

| vertical-align:top; border:1px solid #aaa;" |
===[http://codingclub.cuteseal.co.uk/index.php The Coding Club Free eBook(s)]===
| vertical-align:top; border:1px solid #aaa;" |
Forum Link: [http://www.raspberrypi.org/forum/educational-applications/teaching-youngsters-programming Teaching Youngsters Programming]
| vertical-align:top; border:1px solid #aaa;" |
Beginner (~ages 10)
| vertical-align:top; border:1px solid #aaa;" |
Teaching, Python
| vertical-align:top; border:1px solid #aaa;" |
Sciman
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://dracosoftware.blogspot.com/ DracoSoftware ]===
| vertical-align:top; border:1px solid #aaa;" |
Forum Link: [http://www.raspberrypi.org/forum/projects-and-collaboration-general/blog-about-working-with-raspberry-pi-for-windows-users Blog about working with Raspberry Pi for Windows users]
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Teaching, Windows, Linux
| vertical-align:top; border:1px solid #aaa;" |
dracolytch
| vertical-align:top; border:1px solid #aaa;" |
Available
|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi Tutorial Easy GPIO Hardware & Software | Easy GPIO Hardware & Software]]===
(Wiki)
| vertical-align:top; border:1px solid #aaa;" |
Forum Link: [http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software Easy GPIO Hardware & Software]

Aim to introduce the basic circuits for interfacing through the GPIO.
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Teaching, Basic Hardware
| vertical-align:top; border:1px solid #aaa;" |
[[User:Meltwater | Meltwater]] - Open Project
| vertical-align:top; border:1px solid #aaa;" |
In-Progress
|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://myraspberrypiexperience.blogspot.co.uk/2012/03/using-dd-for-windows.html SD Card setup using DD for Windows]===
| vertical-align:top; border:1px solid #aaa;" |
Blog Link: [http://myraspberrypiexperience.blogspot.co.uk/2012/03/using-dd-for-windows.html My Raspberry Pi Experience]

How to set up an SD Card using DD for Windows - with step by step screenshots
| vertical-align:top; border:1px solid #aaa;" |
Linux Beginner/
Windows Intermediate
| vertical-align:top; border:1px solid #aaa;" |
Startup Guide, OS setup
| vertical-align:top; border:1px solid #aaa;" |
Tass
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |
===[[RPi VICE C64 Emulator | Software: C64 Emulator (VICE)]]===
| vertical-align:top; border:1px solid #aaa;" |
Forum Link: [http://www.raspberrypi.org/forum/projects-and-collaboration-general/c64-emulator How to install the C64 Emulator VICE]
| vertical-align:top; border:1px solid #aaa;" |
Linux Beginner
| vertical-align:top; border:1px solid #aaa;" |
Install Guide, Software, Emulator
| vertical-align:top; border:1px solid #aaa;" |
Frank Buss
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://myraspberrypiexperience.blogspot.co.uk/2012/04/setting-up-vnc.html Setting up VNC]===
| vertical-align:top; border:1px solid #aaa;" |
Blog Link: [http://myraspberrypiexperience.blogspot.co.uk/2012/04/setting-up-vnc.html My Raspberry Pi Experience]

How to set up VNC server on the Raspberry Pi to be able to connect remotely - with step by step screenshots
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup Guide, OS setup
| vertical-align:top; border:1px solid #aaa;" |
Tass
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://fusionstrike.com/2012/installing-apache2-raspberry-pi-debian Setting up Apache2]===
| vertical-align:top; border:1px solid #aaa;" |
Blog Link: [http://fusionstrike.com/2012/installing-apache2-raspberry-pi-debian Fusion Strike]

A guide on setting up an Apache2 web server with Screenshots
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup Guide, server setup
| vertical-align:top; border:1px solid #aaa;" |
Jacob Clark
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://fusionstrike.com/2012/setting-php-raspberry-pi-debian Setting up PHP]===
| vertical-align:top; border:1px solid #aaa;" |
Blog Link: [http://fusionstrike.com/2012/setting-php-raspberry-pi-debian Fusion Strike]

A guide on setting up PHP web server with using Apache & SSH with Screenshots
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup Guide, server setup
| vertical-align:top; border:1px solid #aaa;" |
Jacob Clark
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://fusionstrike.com/2012/setting-mysql-raspberry-pi-debian Setting up MySQL]===
| vertical-align:top; border:1px solid #aaa;" |
Blog Link: [http://fusionstrike.com/2012/setting-mysql-raspberry-pi-debian Fusion Strike]

A guide on setting up MySQL on your Raspberry Pi web server using PHP, Apache & SSH with Screenshots
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup Guide, server setup
| vertical-align:top; border:1px solid #aaa;" |
Jacob Clark
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://log.liminastudio.com/programming/running-puredata-on-the-raspberry-pi Running Puredata on the Raspberry Pi]===
| vertical-align:top; border:1px solid #aaa;" |
How to get Puredata, the open-source sound synthesis platform, running on your R-Pi : [http://log.liminastudio.com/programming/running-puredata-on-the-raspberry-pi Running Puredata on the Raspberry Pi]
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup guide
| vertical-align:top; border:1px solid #aaa;" |
T3db0t
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |
===[http://raspi.tv/2012/mount-a-usb-flash-drive-on-raspberry-pi How to mount a USB flash drive on the Raspberry Pi]===
| vertical-align:top; border:1px solid #aaa;" |
Blog link: [http://raspi.tv/2012/mount-a-usb-flash-drive-on-raspberry-pi How to mount a USB flash drive on the Raspberry Pi]
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup guide, Linux
| vertical-align:top; border:1px solid #aaa;" |
Alex Eames
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |

===[http://raspi.tv/2012/how-to-mount-and-use-a-usb-hard-disk-with-the-raspberry-pi How to mount and use a USB Hard Disk Drive on the Raspberry Pi]===
| vertical-align:top; border:1px solid #aaa;" |
Blog link: [http://raspi.tv/2012/how-to-mount-and-use-a-usb-hard-disk-with-the-raspberry-pi How to mount a USB hard disk drive on the Raspberry Pi]
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup guide, Linux
| vertical-align:top; border:1px solid #aaa;" |
Alex Eames
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |

===[http://pihub.blogspot.co.uk/2012/06/raspberry-pi-power-supply-and-powered.html How to build a cheap powered USB hub]===
| vertical-align:top; border:1px solid #aaa;" |
Blog link: [http://pihub.blogspot.co.uk/2012/06/raspberry-pi-power-supply-and-powered.html How to build a cheap powered USB hub]

How to adapt a cheap unpowered USB hub and an existing mains adaptor to build a Raspberry Pi power supply and powered USB hub in one.
| vertical-align:top; border:1px solid #aaa;" |
Intermediate
| vertical-align:top; border:1px solid #aaa;" |
Hardware, USB hub
| vertical-align:top; border:1px solid #aaa;" |
Alan Thew
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |

===[[RPi_5V_PSU_construction| 5V Power Supply construction - How To]]===
| vertical-align:top; border:1px solid #aaa;" |
How to make a simple PSU for your Raspberry Pi - design and construction from scratch. Some experience with construction of electronic circuits is required.
| vertical-align:top; border:1px solid #aaa;" |
Intermediate
| vertical-align:top; border:1px solid #aaa;" |
Hardware, PSU
| vertical-align:top; border:1px solid #aaa;" |
Pinoccio
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |

===[http://chrisbaume.wordpress.com/2012/06/24/raspberry-pi-upnp-media-player/ Raspberry Pi UPnP Media Player]===
| vertical-align:top; border:1px solid #aaa;" |
Blog link: [http://chrisbaume.wordpress.com/2012/06/24/raspberry-pi-upnp-media-player/ Raspberry Pi UPnP Media Player]

A guide on using GMediaRender to set up a Raspberry Pi as a UPnP media renderer.
| vertical-align:top; border:1px solid #aaa;" |
Beginner
| vertical-align:top; border:1px solid #aaa;" |
Startup guide, Linux
| vertical-align:top; border:1px solid #aaa;" |
Chris Baume
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |

===[http://linuxtortures.blogspot.fr/2012/06/cross-compiling-and-cross-debugging-c.html Cross Compiling and Cross Debugging C++ with Eclipse from Debian Squeeze x64 to Debian Squeeze ARM (Raspberry Pi)]===
| vertical-align:top; border:1px solid #aaa;" |
Blog link: [http://linuxtortures.blogspot.fr/2012/06/cross-compiling-and-cross-debugging-c.html Cross Compiling and Cross Debugging C++ with Eclipse from Debian Squeeze x64 to Debian Squeeze ARM (Raspberry Pi)]

A guide on Cross-Compilation and Cross-Debugging C++ with Eclipse CDT.
| vertical-align:top; border:1px solid #aaa;" |
Intermediate
| vertical-align:top; border:1px solid #aaa;" |
Teaching, C++
| vertical-align:top; border:1px solid #aaa;" |
Javier Bravo
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |

===[http://pi.gadgetoid.co.uk/post/001-who-watches-the-watcher Setting up the Broadcom watchdog to reboot a hung Pi (Raspberry Pi)]===
| vertical-align:top; border:1px solid #aaa;" |
Blog link: [http://pi.gadgetoid.co.uk/post/001-who-watches-the-watcher Setting up the Broadcom watchdog to reboot a hung Pi (Raspberry Pi)]

A quick guide on setting up the watchdog process so that your Pi boots when it hangs or freezes. Adding "panic=20" is another good way of keeping your Pi running remotely.
| vertical-align:top; border:1px solid #aaa;" |
Intermediate
| vertical-align:top; border:1px solid #aaa;" |
Linux
| vertical-align:top; border:1px solid #aaa;" |
Philip Howard
| vertical-align:top; border:1px solid #aaa;" |
Available

|-
| vertical-align:top; border:1px solid #aaa;" |

===[http://linuxtortures.blogspot.fr/2012/07/communicating-with-raspberry-via-gsoap.html Communicating with RaspBerry via GSoap C++ Web Services]===
| vertical-align:top; border:1px solid #aaa;" |
Blog link: [http://linuxtortures.blogspot.fr/2012/07/communicating-with-raspberry-via-gsoap.html Communicating with RaspBerry via GSoap C++ Web Services]

A step by step guide about how to develop and deploy a C++ Web Service on our Raspberry using the open API GSoap.
| vertical-align:top; border:1px solid #aaa;" |
Intermediate
| vertical-align:top; border:1px solid #aaa;" |
Teaching, C++
| vertical-align:top; border:1px solid #aaa;" |
Javier Bravo
| vertical-align:top; border:1px solid #aaa;" |
Available

|}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Performance

2012-08-06T21:54:55Z

Lxndr: added references, template, category

{{Template:RPi_Software}}

=CPU=
==Linpack==

The Arm has been tested using the linpack benchmark from [http://www.netlib.org/benchmark/linpackc.new], built with gcc with -O3 (Optimisation level 3). Run with array size 200.

With software floating point

===Source===
[http://www.netlib.org/benchmark/linpackc.new]

===Compile/Run===
<pre>
cc -O3 -o linpack linpack.c -lm
linpack.c: In function ‘main’:
linpack.c:69: warning: return type of ‘main’ is not ‘int’
./linpack
Enter array size (q to quit) [200]: 200
</pre>

===Results===
Crippled
<pre>
Memory required: 315K.

LINPACK benchmark, Double precision.
Machine precision: 15 digits.
Array size 200 X 200.
Average rolled and unrolled performance:

Reps Time(s) DGEFA DGESL OVERHEAD KFLOPS
2 0.53 92.45% 1.89% 5.66% 5493.333
4 1.07 92.52% 2.80% 4.67% 5385.621
8 2.12 92.45% 2.36% 5.19% 5466.003
16 4.24 92.45% 2.83% 4.72% 5438.944
32 8.49 92.11% 2.71% 5.18% 5459.213
64 16.98 92.05% 2.89% 5.06% 5452.440
</pre>

Hardware floating point (-mfloat-abi=softfp)
<pre>
Memory required: 315K.
LINPACK benchmark, Double precision.
Machine precision: 15 digits.
Array size 200 X 200.
Average rolled and unrolled performance:

Reps Time(s) DGEFA DGESL OVERHEAD KFLOPS
8 0.51 90.20% 3.92% 5.88% 22888.889
16 1.02 89.22% 4.90% 5.88% 22888.889
32 2.05 90.24% 3.41% 6.34% 22888.889
64 4.08 91.42% 2.94% 5.64% 22829.437
128 8.16 91.54% 2.94% 5.51% 22799.827
256 16.31 91.35% 2.76% 5.89% 22903.800
</pre>

Full hardware floating point on Raspbian (-mfloat-abi=hard -mfpu=vfp) and arm_freq=700
<pre>
Memory required: 315K.
LINPACK benchmark, Double precision.
Machine precision: 15 digits.
Array size 200 X 200.
Average rolled and unrolled performance:

Reps Time(s) DGEFA DGESL OVERHEAD KFLOPS
16 0.58 89.66% 3.45% 6.90% 40691.358
32 1.17 87.18% 4.27% 8.55% 41071.651
64 2.32 88.36% 3.02% 8.62% 41459.119
128 4.67 88.22% 3.43% 8.35% 41071.651
256 9.33 88.85% 3.32% 7.82% 40880.620
512 18.63 89.00% 2.95% 8.05% 41047.675
</pre>

Full hardware floating point on Raspbian (-mfloat-abi=hard -mfpu=vfp) and arm_freq=1000 and core_freq=500
<pre>
Memory required: 315K.
LINPACK benchmark, Double precision.
Machine precision: 15 digits.
Array size 200 X 200.
Average rolled and unrolled performance:

Reps Time(s) DGEFA DGESL OVERHEAD KFLOPS
32 0.79 89.87% 0.00% 10.13% 61896.714
64 1.58 89.24% 1.27% 9.49% 61463.869
128 3.16 90.19% 1.90% 7.91% 60407.789
256 6.32 88.13% 3.80% 8.07% 60511.761
512 12.65 87.83% 3.56% 8.62% 60825.836

</pre>

Full hardware floating point on Gentoo with more compiler optimizations (gcc-4.6.3 -Ofast -fno-fast-math), default clocks
<pre>
Memory required: 315K.
LINPACK benchmark, Double precision.
Machine precision: 15 digits.
Array size 200 X 200.
Average rolled and unrolled performance:

Reps Time(s) DGEFA DGESL OVERHEAD KFLOPS
----------------------------------------------------
16 0.56 89.29% 1.79% 8.93% 43084.967
32 1.13 91.15% 4.42% 4.42% 40691.358
64 2.25 89.78% 3.56% 6.67% 41853.968
128 4.51 87.80% 4.21% 7.98% 42358.233
256 9.01 88.68% 3.88% 7.44% 42155.076
512 18.01 89.23% 2.78% 8.00% 42434.923

</pre>

==Whetstone/Dhrystone==

All code compiled with gcc options -float-abi=softfp -O3

===Source===
Code for these tests can be found here http://www.rowley.co.uk/arm/whet_dhry.zip.
Or if 404 this code might be analogous http://freespace.virgin.net/roy.longbottom/benchnt.zip

===Compile/Run===
<pre>
?
</pre>

===Results===
Dhrystone
<pre>
Microseconds for one run through Dhrystone: 1.2

Dhrystones per Second: 809061.5
</pre>

Whetstone Crippled
<pre>
Loops: 1000, Iterations: 10, Duration: 24 sec.

C Converted Double Precision Whetstones: 41.7 MIPS
</pre>

Rebuilding the Whetstone test code with 'gcc -mfpu -float-abi=softfp' gives better results:
<pre>

Loops: 1000, Iterations: 100, Duration: 106 sec.
C Converted Double Precision Whetstones: 94.3 MIPS
</pre>

However, the majority of compute time is spent in the SQRT function, which for the above test was built without -mfpu=vfp. Using a library with vfp give the following much improved result :
<pre>
Loops: 1000, Iterations: 100, Duration: 15 sec.
C Converted Double Precision Whetstones: 666.7 MIPS
</pre>

==OpenSSL==

===Source===
[http://www.openssl.org/source/]

===Compile/Run===
<pre>
openssl version;
openssl speed;
</pre>

===Results===
Assembly optimization disabled:
<pre>
OpenSSL 0.9.8o 01 Jun 2010
built on: Thu Aug 26 18:56:26 UTC 2010
options:bn(64,32) md2(int) rc4(ptr,int) des(idx,risc1,4,long) aes(partial) blowfish(idx)
compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DL_ENDIAN -DTERMIO -O2 -Wa,--noexecstack -g -Wall
available timing options: TIMES TIMEB HZ=100 [sysconf value]
timing function used: times
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
md2 148.81k 372.18k 624.81k 769.95k 832.90k
mdc2 0.00 0.00 0.00 0.00 0.00
md4 615.30k 2468.76k 7612.19k 16707.01k 28104.86k
md5 380.13k 1501.12k 4800.77k 11312.81k 21682.77k
hmac(md5) 1022.28k 3480.23k 9587.80k 17492.25k 25441.78k
sha1 303.72k 1092.39k 3106.50k 6302.57k 9852.39k
rmd160 244.29k 849.04k 2414.53k 4747.26k 7513.00k
rc4 14658.70k 16836.49k 17462.03k 17628.21k 17522.08k
des cbc 2913.17k 3221.30k 3289.77k 3360.09k 3367.21k
des ede3 1149.87k 1188.59k 1198.46k 1206.00k 1208.25k
idea cbc 0.00 0.00 0.00 0.00 0.00
seed cbc 0.00 0.00 0.00 0.00 0.00
rc2 cbc 2812.71k 3012.02k 3054.19k 3077.82k 3076.12k
rc5-32/12 cbc 0.00 0.00 0.00 0.00 0.00
blowfish cbc 6091.32k 7007.89k 7250.62k 7288.21k 7163.88k
cast cbc 5068.25k 6020.03k 6345.71k 6367.64k 6260.44k
aes-128 cbc 3205.76k 3497.72k 3616.00k 3652.49k 3665.85k
aes-192 cbc 2730.65k 2981.88k 3073.20k 3102.38k 3111.86k
aes-256 cbc 2383.90k 2596.12k 2659.91k 2702.13k 2732.50k
camellia-128 cbc 0.00 0.00 0.00 0.00 0.00
camellia-192 cbc 0.00 0.00 0.00 0.00 0.00
camellia-256 cbc 0.00 0.00 0.00 0.00 0.00
sha256 679.98k 1629.47k 2905.43k 3708.32k 4175.45k
sha512 41.02k 163.83k 232.63k 318.20k 353.81k
aes-128 ige 3089.03k 3579.08k 3698.68k 3689.14k 3578.18k
aes-192 ige 2641.68k 3019.45k 3111.38k 3144.95k 3035.70k
aes-256 ige 2334.50k 2632.35k 2705.04k 2735.69k 2687.74k
sign verify sign/s verify/s
rsa 512 bits 0.013747s 0.001193s 72.7 838.4
rsa 1024 bits 0.063481s 0.002742s 15.8 364.7
rsa 2048 bits 0.321250s 0.007378s 3.1 135.5
rsa 4096 bits 1.805000s 0.022528s 0.6 44.4
sign verify sign/s verify/s
dsa 512 bits 0.011690s 0.013597s 85.5 73.5
dsa 1024 bits 0.027233s 0.031683s 36.7 31.6
dsa 2048 bits 0.073897s 0.087304s 13.5 11.5
</pre>
Assembly optimization enabled:
<pre>
OpenSSL 1.0.1c 10 May 2012
built on: Sun Jul 29 00:43:16 CEST 2012
options:bn(64,32) rc4(ptr,char) des(idx,cisc,16,long) aes(partial) idea(int) blowfish(ptr)
compiler: armv6j-hardfloat-linux-gnueabi-gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN \
-DHAVE_DLFCN_H -DL_ENDIAN -DTERMIO -Wall -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM \
-DSHA512_ASM -DAES_ASM -DGHASH_ASM -O2 -march=armv6j -mfpu=vfp -mfloat-abi=hard -fno-strict-aliasing -Wa,--noexecstack
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
md2 0.00 0.00 0.00 0.00 0.00
mdc2 724.41k 933.06k 1024.68k 1063.59k 1075.88k
md4 2547.83k 9441.28k 27284.48k 51824.98k 69894.14k
md5 1954.05k 7217.96k 20805.95k 39365.29k 53226.15k
hmac(md5) 3075.61k 10241.88k 26669.65k 44729.00k 55386.11k
sha1 2115.34k 6823.83k 16264.45k 25053.18k 30121.35k
rmd160 1487.88k 4783.96k 10707.71k 15800.32k 19303.08k
rc4 34205.43k 39535.98k 41215.83k 41561.43k 41570.04k
des cbc 6251.12k 6605.08k 6686.81k 6713.01k 6707.54k
des ede3 2326.45k 2368.36k 2385.83k 2397.53k 2391.84k
idea cbc 8758.77k 9421.31k 9607.34k 9653.93k 9687.93k
seed cbc 8274.52k 9036.46k 9264.64k 9321.47k 9284.27k
rc2 cbc 6047.90k 6354.82k 6458.82k 6465.19k 6485.33k
rc5-32/12 cbc 16204.47k 18649.32k 19367.94k 19560.11k 19649.84k
blowfish cbc 11934.03k 13189.85k 13546.92k 13633.19k 13486.76k
cast cbc 10797.59k 11828.46k 12156.58k 12187.65k 12050.43k
aes-128 cbc 12978.72k 14708.69k 15387.40k 15472.93k 15529.06k
aes-192 cbc 11441.49k 12834.60k 13315.69k 13453.78k 13430.80k
aes-256 cbc 10267.01k 11409.83k 11744.41k 11812.86k 11859.64k
camellia-128 cbc 9312.98k 10278.89k 10572.46k 10646.19k 10657.82k
camellia-192 cbc 7541.38k 8140.71k 8325.63k 8370.18k 8361.30k
camellia-256 cbc 7513.97k 8138.65k 8297.98k 8351.40k 8347.65k
sha256 3598.03k 8377.26k 14605.57k 17979.39k 19300.35k
sha512 1080.74k 4322.82k 6151.85k 8416.32k 9418.07k
whirlpool 361.82k 729.24k 1186.42k 1425.38k 1512.79k
aes-128 ige 11702.57k 13853.45k 14429.53k 14671.38k 14057.47k
aes-192 ige 10468.67k 12165.24k 12628.24k 12743.72k 12331.69k
aes-256 ige 9505.78k 10831.25k 11205.36k 11333.43k 10982.74k
ghash 15681.70k 17279.32k 17770.84k 17894.06k 17940.48k
sign verify sign/s verify/s
rsa 512 bits 0.002185s 0.000217s 457.6 4611.1
rsa 1024 bits 0.011325s 0.000640s 88.3 1563.5
rsa 2048 bits 0.074296s 0.002289s 13.5 436.8
rsa 4096 bits 0.544211s 0.008741s 1.8 114.4
sign verify sign/s verify/s
dsa 512 bits 0.002157s 0.002262s 463.5 442.0
dsa 1024 bits 0.006234s 0.007123s 160.4 140.4
dsa 2048 bits 0.022247s 0.025884s 44.9 38.6
</pre>

=GPU=
The RaspberryPi appears to handle h264 1080p movie from USB to HDMI at least 4MB/s.

The Admin "JamesH" said it would handle "basically 1080p30, high profile, >40Mb/s." (5MB/s) in h264

And about WVGA(480p30) or 720p20 in VP8/WEBM

==ioquake3==

===Source===
https://github.com/raspberrypi/quake3

===Compile/Run===
- Download source, compile as delivered
- Start game
- Runs at display's native res, in my case 1280x1024
- Bitdepth stuck at 16bpp, not sure how to change, values in q3config.cfg seem to be ignored
- In-game console commands:
\timedemo 1
\demo four

===Results===
armel "driver info" : http://i.imgur.com/wtYhB.jpg
armel timedemo score: http://i.imgur.com/i2TkN.jpg
20.2fps

armhf "driver info" : http://i.imgur.com/8nqa1.jpg
armhf timedemo score: http://i.imgur.com/dUu0g.jpg
28.5fps

[[Category: RaspberryPi]]

=IO=

==USB bus==
*All IO uses the same bus so the combination of all IO can not exceed the the bus speed of an as yet hypothetical 60MB/s
*A test with a fast USB-Stick showed that Raspberry Pi can achieve about 30 MB/s:
<pre>root@raspberrypi:~# dd if=/dev/sda of=/dev/null bs=32M count=10 iflag=direct
10+0 records in
10+0 records out
335544320 bytes (336 MB) copied, 10.6428 s, 31.5 MB/s
</pre>

==SD card==
*TODO test

'''Note: the dd test should probably use i/oflags=direct for reads and writes. But that will change the results recorded to date'''
===Compile/Run===
<pre>
# write
dd if=/dev/zero of=~/test.tmp bs=500K count=1024
# read
dd if=~/test.tmp of=/dev/null bs=500K count=1024
# cleanup
rm ~/test.tmp
# find out which kernel you're running
uname -a
</pre>

===Results===
* Depends on SD card used http://elinux.org/RaspberryPiBoardVerifiedPeripherals#SD_cards

{| border="1" class="sortable"
! SD Card !! Read (MB/s) !! Write (MB/s) !! class="unsortable" | Distro !! class="unsortable" | Kernel !! class="unsortable" | Notes
|-
| ADATA 8GB SDHC Class 10 (ASDH8GCL10-R) || 19.6 || 18.8 || 2012-08-04 Debian Wheezy "Raspbian" || Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||
|-
| ADATA 32GB SDHC Class 10 (ASDH32GCL10-R) || 20.1 || 6.4 || 2012-06-18-wheezy-beta || Linux raspberrypi 3.1.9+ #152 PREEMPT Fri Jul 6 18:47:16 BST 2012 armv6l GNU/Linux ||
|-
| [http://amzn.com/B0058GH0LS AmazonBasics SDHC Class 10 8GB] || 19.3 || 8.6 || Debian Wheezy "Raspbian" || Linux massah 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||
|-
| [http://amzn.com/B0058GH0LS AmazonBasics SDHC Class 10 8GB] || 17 || 9.4 || Debian Wheezy "Raspbian" || Linux massah 3.1.9+ #202 PREEMPT Wed Jul 25 22:11:06 BST 2012 armv6l GNU/Linux || Same board and card as above, slightly newer kernel.
|-
| Extrememory SDHC 16GB class 10 || 4.7 || 4.5 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #52 ||
|-
| Extrememory SDHC 16GB class 10 || 11.3 || 5.4 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #101 || init_emmc_clock=200000000 in config.txt
|-
| Extrememory SDHC 16GB class 10 || 18.2 || 6.3 || Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ custom || kernel and firmware as of 17.06.2012, no extra option in config.txt
|-
| Extrememory SDHC 16GB class 10 (man:0x000012 oem:0x3456 name:F0F0F hwrev:0x1 fwrev:0x0) || 16.9 || 10.7 || archlinuxarm-13-06-2012 || Linux alarmpi 3.1.9-25-ARCH+ #1 PREEMPT ||
|-
| Extrememory SDHC 32GB class 10 (man:0x000003 oem:0x5344 name:SMI hwrev:0x1 fwrev:0x0) || 18.7 || 16.5 || archlinuxarm-13-06-2012 || Linux alarmpi 3.1.9-25-ARCH+ #1 PREEMPT ||
|-
| Fugi SDHC 32GB class 10 (P10NM00580A) || 12.7 || 19.8 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #168 || man:0x000073 oem:0x4247 name:NCard hwrev:0x1 fwrev:0x0
|-
| Integral SDHC 16GB class 10 ||17.7 || 19.6 || Debian Wheezy Raspbian || Linux raspbian 3.1.9+ #168 ||
|-
| Kingmax 8GB microSDHC Class 4 (KM08GMCSDHC41A) || 13.6 || 3.7 || Debian Wheezy Raspbian || Linux 3.1.9+ #242 PREEMPT Wed Aug 1 19:47:22 BST 2012 ||
|-
| Kingston SDHC 4GB class 4 ||4.5 ||4.1 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #52 Tue May 8 23:49:32 BST 2012 ||
|-
|Kingston SDHC 4GB class 4 ||4.2 ||2.5 ||archlinuxarm-19-04-2012 ||Linux alarmpi 3.1.9-13+ #6 Thu May 10 00:48:37 UTC 2012 ||Identical card to one above. One to look into, as I was expecting Arch to be faster...
|-
|Kingston uSDHC 4GB class 4 ||4.0 ||3.8 ||Debian Squeeze ||Linux 3.1.9+ #90 ||
|-
|Kingston uSDHC 8GB class 4 (SDC4/8GB) ||4.7 ||3.7 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/Kingston_uSD_8GB_CDM_Bench.zip CrystalDiskMark results (FAT32)] This is my only card that can be counted on to boot up on each plug-in.
|-
|Kingston SDHC 8GB class 4 (SD4/8GB) ||4.6 ||3.0 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/Kingston_SD4-8GB_CDM_Bench.zip CrystalDiskMark results (FAT32)]
|-
|Kingston SDHC 8GB class 4 (SD4/8GB) ||13.2 ||3.4 || Hexxeh Raspbian r3 ||Linux raspbian 3.1.9+ #202 PREEMPT Wed Jul 25 22:11:06 BST 2012 armv6l GNU/Linux || man:0x000002 oem:0x544d name:SA08G hwrev:0x1 fwrev:0x0
|-
|Kingston SDHC 32GB class 10 ||10.8 ||8.1 ||Fedora 17 ARM snapshot 07 May 2012 ||Linux fedora-arm 3.1.9 #1 ||mmc0: note - long write sync 1453000ns - 14608 its. - kernel/module problems?
|-
|Kingston SDHC 32GB class 10 ||4.7 ||4.1 ||Fedora 17 ARM nightly snapshot ||Linux fedora-arm 3.1.9+ #101 PREEMPT Mon Jun 4 17:19:44 BST 2012 ||custom kernel from raspberrypi github - no more mmc0 sync problems
|-
|Kingston SDHC 32GB class 10 ||4.6 ||3.5 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #90 ||
|-
|Panasonic SDHC 8GB class 6 ||4.8 ||4.4 || || ||
|-
|Panasonic SDHC 8GB class 4 ||11.1 || 9.7 || Debian Wheezy "Rasbpian" || Linux rpi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||
|-
|Patriot microSDHC 16GB Class 10 (PSF16GMSHC10) ||9.5 ||5.2 ||Fedora 14 ||Linux raspi 3.1.9+ #101 ||init_emmc_clock=200000000 in config.txt
|-
|Samsung SDHC 16GB Class 10 (MB-SPAGA) ||10.7 ||8.8 ||Fedora 17 ARM snapshot 07 May 2012 - GUI release ||Linux fedora-arm 3.1.9 #1 ||Had "long write sync" errors, slow boot times and then system instability using USB port on Macbook, switched to iPhone charger (5V 1A) and warning disappeared
|-
|Samsung SDHC 16GB Class 10 (MB-SPAGA) ||19.6 ||18.7 || Debian Wheezy "Raspbian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armvl GNU/Linux ||(Same user / card as above, definitely notable that Raspbian is superior)
|-
|Samsung microSDHC 16GB Class 10 (MB-MPAGA/US) || 19.8 || 15.8 || Debian Wheezy "Raspbian" || Linux pisces 3.1.9+ #155 PREEMPT Mon Jul 9 12:49:19 BST 2012 armv6l GNU/Linux || -
|-
|Samsung microSDHC 16GB Class 4 (MB-MS4GA/US) || 19.2 || 5.5 || Debian Wheezy "Raspbian" || ? || -
|-
|SanDisk microSD 2GB ||4.7 ||4.2 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/SanDisk_2GB_uSD_CDM_Bench.zip CrystalDiskMark results (FAT32)] Card has no serial/is likely a fake.
|-
|SanDisk Ultra SDHC 4GB class 4 ||4.7 ||4.4 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ #1 PREEMPT Wed Jun 6 16:26:14 CEST 2012 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SD04G hwrev:0x8 fwrev:0x0
|-
|SanDisk Ultra II SDHC 4GB class 4 (15 MB/s)||20.9 ||14.6 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ ||
|-
|SanDisk SDHC 8GB class 4 ||11.1 ||5.6 ||Raspbian Wheezy || Linux raspberrypi 3.1.9+ #202 PREEMPT || After Hexxeh rpi-update. man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0
|-
|SanDisk SDHC 8GB class 4 ||4.7 ||3.2 ||Debian Squeeze || ||
|-
|SanDisk Ultra SDHC I 8GB class 6 "30MB/s*" ||19.5 || 7.6 ||archlinuxarm || 3.1.9-22-ARCH+ #1 PREEMPT Sun Jun 17 13:54:30 UTC 2012 || "mmc0: error -84 whilst initialising SD card" at bootup, but works fine
|-
|SanDisk Ultra SDHC I 8GB class 10 "30MB/s*" ||19.3 || 3.2 ||Raspbian Wheezy || 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 ||
|-
|SanDisk Ultra SDHC I 8GB class 10 "30MB/s*" || 13.6 || 14.5 || raspbmc rc3 || Linux raspbmc 3.1.9-test-12-06 #1 PREEMPT Mon Jun 18 20:07:45 UTC 2012 armv6l GNU/Linux ||
|-
|SanDisk Ultra SDHC II 16GB class 2 "15MB/s*" ||16.7 || 16.2 || Raspbian Wheezy || 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 || man:0x000003 oem:0x5344 name:SD16G hwrev:0x8 fwrev:0x0
|-
|SanDisk Ultra SDHC 16GB class 10 UHS-1 "30Mb/s" (SDSDU-016G-U46) ||20.9 ||18.1 ||Raspbian Wheezy || Linux raspberrypi 3.1.9+ #202 PREEMPT || After Hexxeh rpi-update. man:0x000003 oem:0x5344 name:SU16G hwrev:0x8 fwrev:0x0
|-
|SanDisk Extreme SDHC I 4GB class 10 "30MB/s" || 19.7 || 21.0 || 2012-07-15-wheezy-raspbian || Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux || Only boots with images with new firmware, didn't boot with previous images.
|-
|SanDisk Extreme SDHC I 8GB class 10 "30MB/s" || 17.7 || 19.7 || Archlinuxarm 2012-06-13 || Linux raspi 3.1.9-28-ARCH+ #1 PREEMPT Fri Jul 6 23:07:26 UTC 2012 armv6l GNU/Linux ||
|-
|SanDisk SDHC 32GB class 6 ||4.6 ||4.8 || || ||
|-
|SanDisk uSDXC 64GB class 6 ||4.9 ||3.8 ||archlinuxarm-29-04-2012 ||Linux alarmpi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 ||[http://dl.dropbox.com/u/268147/rpi/SanDisk_64GB_uSDXC_CDM_Bench.zip CrystalDiskMark results (FAT32)]
|-
|TDK microSDHC 4GB, Class 4 (80-56-10301-004G) ||11.2 ||4.7 ||Debian Wheezy "Raspbian" (2012-07-15) ||3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 ||
|-
|Transcend SDHC 8GB class 6 ||5.8 ||5.8 || || || |
|-
|Transcend SDHC 8GB Class 6 (TS8GSDHC6) ||4.6 ||4.0 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #90 Wed Apr 18 18:23:05 BST 2012 armv61 GNU/Linux ||Tested with dd. Card doesn't maintain the promised minimum class speed.
|-
|Transcend SDHC 8GB Class 4 (TS8GSDHC4) ||11.1 ||8.1 ||Debian Wheezy "Rasbpian" ||Linux raspberrypi 3.1.9+ #168 PREEMPT Sat Jul 14 18:56:31 BST 2012 armv6l GNU/Linux ||man:0x000003 oem:0x5344 name:SD08G hwrev:0x8 fwrev:0x0
|-
|Transcend microSDHC 8GB Kit, Class 4 (TS8GUSDHC4)||4.7 ||3.7 ||Raspbian Wheezy || Linux raspberry-pi 3.1.9+ #1 PREEMPT Wed Jun 6 16:26:14 CEST 2012 armv6l GNU/Linux || man:0x000003 oem:0x5344 name:SU08G hwrev:0x8 fwrev:0x0
|-
|Transcend SDHC 4GB Class 6 ||9.8 ||8.8 ||Fedora Remix FC14 ||Linux raspi 3.1.9 #1 PREEMPT Sat Mar 3 21:58:00 UTC 2012 armv6l armv6l armv6l GNU/Linux ||Not sure why this setup is faster than others, test results repeatable.
|-
|Transcend SDHC 16GB Class 10 ||20.3 ||11.9 ||Debian Wheezy "Rasbpian" || Linux raspberry-pi 3.1.9-cutdown+ #173 ||
|-
|Transcend SDHC 32GB Class 10 (TS32GSDHC10E) || 20.3 || 15.3 || Debian Wheezy "Rasbpian" || Linux raspberrypi 3.1.9+ #242 PREEMPT Wed Aug 1 19:47:22 BST 2012 armv6l GNU/Linux || man:0x000074 oem:0x4a45 name:SDC hwrev:0x1 fwrev:0x0
|-
|Sandisk Extreme Pro SDHC 16GB Class 10 UHS-I (SDSDXPA-016G-A75) ||4.7 ||4.8 ||debian6-19-04-2012 ||Linux Raspi 3.1.9+ #66 Thu May 17 16:56:20 BST 2012 || Followed [http://www.element14.com/community/message/51493?tstart=0#51493 a forum post] to install newest kernel from git repo.
|-
|SanDisk Extreme Pro SDHC 16GB Class 10||20.8||18.6||Debian Wheezy "Raspbian"||Linux raspberrypi 3.1.9+ #125 PREEMPT Sun Jun 17 16:09:36 BST 2012 armv6l GNU/Linux||
|-
|Sandisk Ultra SDHC I Class 6 ("30MB/s") ||4.7 ||4.8 ||Debian Wheezy "Raspbian" ||3.2.18+ #3 PREEMPT ||Feels faster than my Kingston 4GB Class 4 card.
|-
|WINTEC FileMate Professional SDHC 16GB Class 10 (3FMSD16GBC10-R) ||4.6 ||4.5 ||Debian Squeeze "debian6-19-04-2012" ||Linux raspberrypi 3.1.9+ #95 PREEMPT Thu May 31 13:21:40 BST 2012 armv6l GNU/Linux ||After installing new kernel with rpi-update on 2012-06-01
|-
|Lexar SDHC 8GB Class 4 "Multi-use" ||18.9 ||6.8 ||Debian Wheezy "Raspbian" ||3.1.9+ #110 PREEMPT ||
|-
|Lexar SDHC 8GB Class 6 "PLATINUM II" ||19.7 ||10.1 ||Debian Wheezy "Raspbian" || 3.1.9+ #168 PREEMPT ||
|-
|Lexar SDHC 16GB Class 10 "PLATINUM II" ||5.3 ||4.8 ||Debian Wheezy/sid || Linux raspberrypi 3.2.19-rpi1+ #3 ||
|-
|Lexar SDHC 16GB Class 10 "PLATINUM II" ||18.9 ||9.0 ||Debian Wheezy "Raspbian" || Linux raspbian 3.1.9+ #168 PREEMPT || Same card as 'Lexar SDHC 16GB Class 10 "PLATINUM II"' above - imaged with Raspbian
|-
|Mushkin SDHC 16GB Class 10 MKNSDHCC10-16GB ||19.7 ||10.9 ||2012-07-15-wheezy-raspbian ||3.1.9+ #168 PREEMPT ||
|-
|Panasonic SDHC 4GB Class 10 UHS-I ||11.2 ||6.2 ||Debian Wheezy "Raspbian" ||3.1.9+ #144 PREEMPT || Panasonic RP-SDU04GE1K
|}

==NIC==

===Compile/Run===
On LAN server:
<pre>iperf -s</pre>

On Raspberry Pi:
<pre>iperf -t 60 -c <SERVER_IP_ADDRESS> -d</pre>

===Results===
{| border="1"
! Bandwidth (Mbit/s)
! CPU usage (top)
! Distro
! Kernel
! Notes
|-
|52.1 + 46.4
|5.1%us, 66.2%sy, 28.7%si
|Debian Squeeze "debian6-19-04-2012"
|Linux raspberrypi 3.1.9+ #95 PREEMPT
|
|-
|91.8 + 36.8
|1.6%us, 60.8%sy, 37.5%si
|Debian Wheezy "Raspbian"
|Linux raspbian 3.1.9+ #101 PREEMPT
|
|-
|65.1 + 48.8
|1.3%us, 61.9%sy, 36.8%si
|Arch Linux 2012-04-29
|Linux alarmpi 3.1.9-12+ #5 Sat Apr 28 04:49:38 UTC 2012 armv6l ARMv6-compatible processor rev 7 (v6l) BCM2708 GNU/Linux
|Remote host connected at gigabit
|-
|69.5 + 29.1
|0.6%us, 55.5%sy, 40.0%si
|Debian Wheezy "Raspbian"
|Linux rpi 3.1.9+ #168 PREEMPT
|Remote connected at gigabit, values for si between 30 and 55 %
|-
|90.8 + 91.4
|0.3%us, 62.2%sy, 37.5%si
|Gentoo Linux ARM
|Linux genpi 3.2.23-bootc #1
|Remote host connected at gigabit, vm.min_free_kbytes = 4096
|}

===Additional Observations===

Using netperf -H [netserver host IP] with Debian Wheezy and changing the CPU clock rate, the TCP performance increased linearly from 61 Mb/s at 500 MHz to 80.6 Mb/s at 900 MHz.

Performance seems to improve considerably by dropping MTU from the default 1500 to 1488. However, this has caused kernel instabilities with Debian Squeeze images (debian6-19-04-2012). It is unknown if this performance benefit is also gained on other images, or if these kernel instabilities have been resolved.

=Power=

This table lists how much power is drawn over the 5V power cable whilst performing various tasks.

{|class="wikitable"
! Task !! Power use (mA) !! Notes
|-
| Booting (without peripherals) || 120-400 || Taken from Agilent lab power supply readings. No composite/keyboard/mouse/network connected. HDMI was enabled but the cable was disconnected.
|-
| Idling (HDMI on, network on) || 370 || Taken from Agilent lab power supply readings. No composite/keyboard/mouse connected.
|-
| Idling (HDMI on, network off) || 320 || Taken from Agilent lab power supply readings. No composite/keyboard/mouse/network connected.
|-
| 1080p video playback || 750 || About 3h on 4 AA batteries
|-
| Text editing || - || Same as idling
|-
| Compiling C code || ? ||
|-
| Running a Python program || ? ||
|-
| Playing Quake III || ? ||
|}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Kernel Compilation

2012-08-06T21:54:38Z

Lxndr: added references, template, category

{{Template:RPi_Software}}

= Overview =

First, you are going to get and build the linux kernel and its modules using a suitable compiler (a "cross-compiler" if you aren't building it on the same hardware you will be running it on) and then you are going to create a kernel image from the uncompressed kernel (Image) to place on the sd, along with the modules you build alongside it.

See below for the various guides to get and compile a suitable kernel for your RPi, and then create a kernel.img according to the steps at the end.

= Raspberry PI kernel compilation =

You can compile the kernel on the board itself, but because of the limited resources it will take a lot of time. Alternatively you can crosscompile the kernel on another machine running Linux, Windows or OS X.

== Compiling on the Raspberry pi itself ==

=== Debian ===

apt-get update;
apt-get -y dist-upgrade;
apt-get -y install git tmux;
cd /opt/;
mkdir raspberrypi;
cd raspberrypi;
git clone --depth 1 https://github.com/raspberrypi/linux.git;
cd linux;
zcat /proc/config.gz > .config;
tmux new -s make;
nice make; nice make modules;
[Ctrl]+[B],[D]
############## … 5 hours later ...
tmux a -t m;
[Ctrl]+[D]
cp arch/arm/boot/Image /boot/kernel.img;
make ARCH=arm modules_install INSTALL_MOD_PATH=/
cd ../;
git clone --depth 1 https://github.com/raspberrypi/firmware/;
cd firmware/boot;
cp arm128_start.elf arm192_start.elf arm224_start.elf bootcode.bin loader.bin start.elf /boot/;
shutdown -r now;

=== Arch Linux ===

==== getting the compiler ====
You will need GIT to clone the kernel source tree from GitHub, compiler (gcc) and GNU Make:
pacman -S git gcc make

(NOTE: git might be omitted if you decide to download sources in compressed format; this is far faster)

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
(NOTE: git might fail due to memory constraints; in this case creation of swap file might help. Be warned - this takes ages! To omit the revision history and reduce the download, you can add "--depth 1" to the end of the git clone command.)

Alternatively, download ZIP or TAR.GZ version of the sources from:
https://github.com/raspberrypi/linux/downloads
unpack and enter the extracted directory (this is your kernel directory - its sources to be precise)

==== configuring the kernel ====
Next, the kernel options are configured. Either copy the cut down Raspberry Pi .config file from the kernel source configs directory:
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config

Or alternatively, to use the configuration from a currently running Raspberry Pi image, connect to the target and extract the .config file. Then copy the resultant .config file into the Linux kernel source root directory:
zcat /proc/config.gz > .config
cp .config <path to linux source root directory>

If needed - manual/additional configuration:
make menuconfig

==== compile the kernel ====
make

(NOTE: this will take around 6h; You might find GNU Screen useful)

==== build kernel.img so your RPi can boot from it ====

Finally you need to build a kernel.img for your Pi to boot from. For this, you need the mkimage tool from the raspberrypi github repository:

git clone https://github.com/raspberrypi/tools

Alternatively, download 'imagetool-uncompressed.py' and its dependencies from (this takes far less time and resources):
https://github.com/raspberrypi/tools/tree/master/mkimage

Before you can use this script you need Python v2 to be installed:
pacman -S python2

Once all above is set up you should have the following files (checklist):
* in the kernel folder you compiled a file: linux/arch/arm/boot/Image
* python2 executable (it should be located by default in /usr/bin/python2)
* imagetool-uncompressed.py script

If this is a case (you have all the above) convert your kernel image with the script:

python2 imagetool-uncompressed.py path/to/linux/arch/arm/boot/Image

This will create a file called kernel.img. Transfer this file into /boot directory (make sure the existing kernel.img in /boot directory gets replaced).

The last thing is to install kernel modules. To do this navigate to your kernel folder and execute:
make modules_install

This will install all compiled modules into /lib/modules and possibly some additional files into /lib/firmware folders.

Reboot your RPi and pray :)
reboot

TODO: verify & consolidate

== Cross compiling on a foreign machine==

=== Ubuntu Linux ===

==== getting the compiler ====

On Ubuntu Oneiric getting the arm cross compiler can be as easy as:

sudo apt-get install gcc-arm-linux-gnueabi make
sudo apt-get install git-core #jhauser14905 -- might as well state the obvious, you need git installed! -- it's git-core on ubuntu. --REW
sudo apt-get install ncurses-dev #MatthewEveritt -- Had to install this to use menuconfig.

(TODO: Is this the right one? More packages required? I did this a while ago! TODO: Other distributions?)

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

==== compiling ====

Next, the kernel options are configured. Either copy the cut down Raspberry Pi .config file from the kernel source configs directory:
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config

Or alternatively, to use the configuration from a currently running Raspberry Pi image, connect to the target and extract the .config file. Then copy the resultant .config file into the Linux kernel source root directory:
zcat /proc/config.gz > .config
cp .config <path to linux source root directory>

Configure the kernel with the copied .config file by running oldconfig:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig

If manual/additional configuration of kernel options are needed run menuconfig:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- menuconfig

Then build the kernel:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k

You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.

If you get the error messages that arm-linux-gnueabi-gcc cannot be found when running make, run the following command:

sudo apt-get install gcc-arm-linux-gnueabi

=== Gentoo Linux ===

==== getting the compiler ====

Build the cross toolchain:
crossdev -S -v -t arm-unknown-linux-gnueabi

theBuell: on 2012-05-06, cross -S -v -A gnueabi arm works just fine

This command should create a cross-toolchain using the latest stable versions of the required packages. If it fails, you can specify exact versions by removing the "-S" flag and adding the "--b", "--g", "--k" and "--l" flags. For the exact usage refer to the crossdev manpage. A good starting point for figuring out the right versions are those which are stable for the arm architecture.

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

==== compiling ====

Next you have to configure the kernel:
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig

Then building the kernel:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k

You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.

=== Arch Linux ===

==== getting the compiler ====
You will need GIT to clone the kernel source tree from GitHub:
pacman -S git

Build the cross toolchain:
arm-linux-gnueabi-gcc is on the AUR. If you use yaourt:

yaourt -S arm-linux-gnueabi-gcc

Yaourt is recommended as it will build all dependencies.

==== getting the sources ====

create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

==== compiling ====

Next you have to configure the kernel:
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- oldconfig

Then building the kernel:
make ARCH=arm CROSS_COMPILE=/usr/bin/arm-linux-gnueabi- -k

You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on.

=== Windows ===

TODO

=== OS X ===

==== getting the compiler ====
Ensure latest Xcode and command line tools are installed from [http://developer.apple.com/downloads Apple Developer Connection] then
Downoad and install an GNU ARM toolchain such as [http://www.yagarto.de/#downloadmac yagarto]

Another option is the MacPorts arm-none-eabi-*:

ARM gcc:

port install arm-none-eabi-gcc

binutils:

port install arm-none-eabi-binutils

==== getting the sources ====

The Kernel source requires a case-sensitive filesystem. If you do not have a HFS+ Case-sensitive partition that can be used, create a disk image with the appropriate format then clone the repository into the mounted image.

Otherwise, create a directory where you can work on the raspberry pi software. I called mine "raspberrypi". Then clone the git repository.

mkdir raspberrypi
cd raspberrypi
git clone https://github.com/raspberrypi/linux.git
cd linux

==== compiling ====

Next you have to configure the kernel: (the running kernel config can be found in <code>/proc/config.gz</code> on your RPi)
cp arch/arm/configs/bcmrpi_cutdown_defconfig .config
make ARCH=arm CROSS_COMPILE=/path/to/yagarto/bin/arm-none-eabi- oldconfig

or if you used the MacPorts
make ARCH=arm CROSS_COMPILE=/opt/local/bin/arm-none-eabi- oldconfig

Then building the kernel:
make ARCH=arm CROSS_COMPILE=/path/to/yagarto/bin/arm-none-eabi- -k

or if you used the MacPorts
make ARCH=arm CROSS_COMPILE=/opt/local/bin/arm-none-eabi- -k

You can use the "-j" flag to improve compilation time. If you have a dual core machine you can use "-j 3", for a quad core machine you can use "-j 6", and so on. (Don't use these for the oldconfig option because it messes up the input and output).

'''If you get an error message that elf.h is missing'''

install [http://guide.macports.org/#installing macports]
install libelf and symlink to /usr/libelf:
sudo port install libelf && sudo ln -s /opt/local/include/libelf /usr/include/libelf
copy [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elf.h?txt elf.h] and [http://opensource.apple.com/source/dtrace/dtrace-48/sys/elftypes.h?txt elftypes.h] to /usr/include

Edit elf.h and add
#define R_386_NONE 0
#define R_386_32 1
#define R_386_PC32 2
#define R_ARM_NONE 0
#define R_ARM_PC24 1
#define R_ARM_ABS32 2
#define R_MIPS_NONE 0
#define R_MIPS_16 1
#define R_MIPS_32 2
#define R_MIPS_REL32 3
#define R_MIPS_26 4
#define R_MIPS_HI16 5
#define R_MIPS_LO16 6

'''If you get a "SEGMENT_SIZE is undeclared" error'''

open the Makefile and change the line:

NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include)

to

NOSTDINC_FLAGS += -nostdinc -isystem $(shell $(CC) -print-file-name=include) -Dlinux

= Final step: Making the 'kernel.img' for your Pi =

Finally you need to build a kernel.img for your Pi to boot from. The next two sections describe how to do this, depending on which firmware/bootloader version you're using.

== Image Generation For Latest Firmware ==

With the latest firmware (available from https://github.com/raspberrypi/firmware), you no longer need to create an explicit kernel image; you can directly use Image (not zImage) from the kernel build process (under 'arch/arm/boot/' of the linux directory) as /boot/kernel.img.

cp linux/arch/arm/boot/Image /media/<boot-partition-of-SD-card>/kernel.img

If you just copied the "Image" file to "kernel.img" in the boot partition of your SD card and the Raspberry Pi doesn't boot (black screen, only red powerled on), then this might help:
* get the most recent firmware from github:

git clone https://github.com/raspberrypi/firmware/

* copy the files from ''firmware/boot/'' to the boot partition of your SD card

cd firmware/boot
cp arm128_start.elf arm192_start.elf arm224_start.elf bootcode.bin loader.bin start.elf /media/<boot-partition-of-SD-card>/

== Image Generation For Older Firmware ==

For this, you need the mkimage tool from the raspberrypi github repository:

git clone https://github.com/raspberrypi/tools

In tools/mkimage, you'll find a python script called 'imagetool-uncompressed.py':

usage : imagetool-uncompressed.py <kernel image>

After building your linux kernel, you'll find the kernel image you require in 'arch/arm/boot/Image' of the linux directory. Convert your kernel image with the script:

python imagetool-uncompressed.py path/to/linux/arch/arm/boot/Image

= Transferring The Image To The Raspberry Pi =

Then you have to transfer this img file to the /boot directory and install the compiled modules. Unfortunately the compiled modules are not in a single place, there are two options of installing them.

Boot your RaspberryPi and mount the <code>linux</code> directory over the network using sshfs:
cd /mnt
mkdir linux
sshfs <user>@<host>:<path/to/linux> linux
cd linux
make modules_install

If you got "Permission denied" when doing <code>cd linux</code>, try:
sudo sh -c "cd linux ; make modules_install"

If that is not an option, you can also install the modules into a temporary folder:
mkdir /tmp/modules
make ARCH=arm modules_install INSTALL_MOD_PATH=/tmp/modules

Now you have to copy the contents of that directory to /lib/modules on the SD card.

Once you've done those two steps, you are ready to put the SD card in and try booting your new system!

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Distributions

2012-08-06T21:54:21Z

Lxndr: added references, template, category

[[Category: Linux]]
[[Category:ARM Development Boards]]
[[Category: Broadcom]]
[[Category: Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]
{{Template:RPi_Software}}

=Available Distributions=

== What is armhf ==
The official Debian Squeeze image issued by the Raspberry Pi foundation uses "soft float" settings. The foundation found it necessary to use the existing Debian port for less capable ARM devices due to time and resource constraints during development of the Raspberry Pi. Therefore, it does not make use of the Pi's processor's floating point hardware - reducing the Pi's performance during floating point intensive applications - or the advanced instructions of the ARMv6 CPU.

Raspberry Pi distributions that are optimized for ARMV6 and are optimized for "hard float" should have better performance on certain CPU intensive tasks.

There are some info on the news groups that "hard float" optimization can speed up floating point operatins upto 10x, please read detailed discussion on Raspberry Pi forums - http://www.raspberrypi.org/phpBB3/viewtopic.php?p=61497#p61497

==Comparison==

{| class="sortable wikitable"
|+ Operational Systems for Raspberry Pi models A and B
|-
! Distribution
! Latest
! First
! Type
! License
! Memory footprint
! armhf
! Image/Installer
! Packages
! Username:Password
! default GUI
|-
| [http://archlinuxarm.org/ Arch Linux ARM]
| 2012-04-29
| 2012-03-01
| Linux
| [http://www.opensource.org/licenses/gpl-2.0.php OSI GPLv2]
|
| {{no}}
| [http://downloads.raspberrypi.org/download.php?file=/images/archlinuxarm/archlinuxarm-29-04-2012/archlinuxarm-29-04-2012.zip raw image]
| [http://archlinuxarm.org/arm/ {{formatnum:4416}}]?
| root:root
| none
|-
| [http://www.berryterminal.com/doku.php BerryTerminal]
| 2012-06-02
| 2012-06-02
| Linux
|
|
| {{no}}
| [http://www.berryterminal.com/dl/berryterminal-20120602.zip Image]
|
| N/A
| [http://www.ltsp.org/ ltsp]
|-
| [http://bodhilinux.com/ Bodhi Linux]
| 2012-06-12 (Wheezy)
| 2012-06-12 (Wheezy)
| Linux
| [http://www.debian.org/legal/licenses/ Core: OSI mixed] (GPLv2 BSD etc)
|
| {{no}}
| [http://sourceforge.net/projects/bodhilinux/files/ARM/RaspBerryPi/ img / tgz]
|
| pi/bodhilinux (sudo su root/bodhilinux)
| [http://www.enlightenment.org/ Enlightenment]
|-
| [http://www.debian.org/ports/arm/ Debian ARM]
| 2012-04-19 (Squeeze)
| 2012-02-16 (Squeeze)
| Linux
| [http://www.debian.org/legal/licenses/ Core: OSI mixed] (GPLv2 BSD etc)
|
| {{no}}
| [http://downloads.raspberrypi.org/images/debian/6/debian6-19-04-2012/debian6-19-04-2012.zip raw image]
| [http://packages.debian.org/stable/allpackages {{formatnum:20000}}+]
| pi:raspberry
| ?
|-
| [http://fedoraproject.org/wiki/Architectures/ARM Fedora Remix]
| 2012-07-07 (F14)
| 2012-07-07 (F14)
| Linux
| [http://fedoraproject.org/wiki/Licensing:Main OSI mixed] (GPLv2 BSD etc)
|
| {{no}}
| Fedora RPM: [http://files.velocix.com/c1410/fedora/installer/fedora/fedora-arm-installer-1.0.0-1.fc16.noarch.rpm installer] Windows Zip: [http://files.velocix.com/c1410/fedora/installer/windows/fedora-arm-installer-1.0.0.zip installer] Other Linux: [http://files.velocix.com/c1410/fedora/installer/source/faii-1.0.0.tar.gz Python script]
| [http://dl.fedoraproject.org/pub/fedora-secondary/releases/14/Everything/arm/os/Packages/ {{formatnum:16464}}]?
| root:fedoraarm
| gnome?
|-
| [http://www.gentoo.org/ Gentoo Linux]
| 2012-06-28
| 2012-04-27
| Linux
| [http://www.opensource.org/licenses/gpl-2.0.php GPLv2]
| ~23 MiB
| {{yes}}
| [http://distfiles.gentoo.org/releases/arm/autobuilds/current-stage3-armv6j_hardfp/ stage3] [http://wiki.gentoo.org/wiki/Raspberry_Pi Instructions]
|
| N/A
|
|-
| [http://planet.ipfire.org/post/ipfire-on-raspberry-pi-ready-to-first-test IPFire]
| 2012-06-27 (2.11)
| 2012-06-27 (2.11)
| Linux
| Open Source
| ~20 MiB
| {{no}}
| [http://people.ipfire.org/~arne_f/testing/RPi/ raw image]
| [http://wiki.ipfire.org/en/addons/all 144]
| N/A
| none
|-
| [http://wiki.meego.com/User:Vgrade#Raspberry_Pi Meego MER + XBMC]
| 2012-04-27 (0.2)
| 2012-04-11 (0.1)
| Linux (embedded)
| [http://www.opensource.org/licenses/index.html OSI mixed] (GPLv2 BSD etc)
| ~34 MiB + XBMC
| {{no}}
|
| [http://gitweb.merproject.org/gitweb/ ~{{formatnum:320}}] (core)
| N/A
| [http://www.xbmc.org XBMC]
|-
| [http://openelec.tv/component/k2/item/235-openelec-on-raspberry-pi-our-first-arm-device-supported OpenELEC]
| 2012-07-04
| 2012-05-10
| Linux (embedded)
| [http://www.opensource.org/licenses/index.html OSI mixed] (GPLv2 BSD etc)
| 70 MiB (inc. XBMC)
| {{yes}}
| [http://openelec.tv/component/k2/item/241-openelec-meets-raspberry-pi-part-1 build instructions] [http://openelec.tv/component/k2/item/242-openelec-meets-raspberry-pi-part-2 install instructions] [http://sources.openelec.tv/tmp/image/openelec-rpi/ official builds] [http://kvarley.co.uk/RaspberryPi/OpenELEC/ raw image (unofficial)]
| [https://github.com/OpenELEC/OpenELEC.tv/tree/master/packages ~{{formatnum:140}}] (+ [http://wiki.openelec.tv/index.php?title=OpenELEC_Addons_(official) 7] via xbmc)
| root:openelec (ssh only)
| [http://www.xbmc.org XBMC]
|-
| [http://www.pwnpi.net/index.html PwnPi]
| 2012-06-29 (Squeeze)
| 2012-05-26 (Squeeze)
| Linux
| GNU General Public License version 3.0
|
| {{no}}
| [http://sourceforge.net/projects/pwnpi/files/pwnpi-2.0-final.7z/download Image]
| [http://packages.debian.org/stable/allpackages {{formatnum:20000}}+]
| root:root
|[http://www.xfce.org/ xfce]
|-
| [http://wiki.qt-project.org/QtonPi QtonPi]
| 2012-05-27 (0.2)
| 2012-05-07 (0.1)
| Linux
|
|
| {{no}}
| [http://downloads.raspberrypi.org/images/qtonpi/qtonpi-0.02/qtonpi-0.2.tar.bz2 qt 5 sdk + sdcard image]
|
| root:rootme qtonpi:qtonpi
| ?
|-
| [http://www.raspbian.org/ Raspbian] Debian
| 2012-06-06 (Wheezy)
| 2012-05-28 (Wheezy)
| Linux
| [http://www.debian.org/legal/licenses/ Core: OSI mixed] (GPLv2 BSD etc)
| ~30 MiB w/o desktop
| {{yes}}
| [http://www.raspbian.org/RaspbianImages pi image list] [http://debian.raspbian.com/qemu/ qemu image]
| [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=66&t=4256&start=552 {{formatnum:35000}}+]
| root:hexxeh root:raspbian pi:raspberry
| [http://wiki.lxde.org/en/Openbox LXDE Openbox]
|-
| [http://www.raspbmc.com/ raspbmc]
| 2012-07-05 (Squeeze)
| 2012-06-30 (Squeeze)
| Linux
| [http://svn.stmlabs.com/svn/raspbmc/LICENSE custom]
|
| {{yes}}
| [http://raspbmc.com/downloads/bin/xbmc/nightlies/ nightlies] [http://svn.stmlabs.com/svn/raspbmc/testing/installers/python/install.py linux installer] [http://download.raspbmc.com/downloads/bin/installers/raspbmc-win32.zip windows installer]
| [http://packages.debian.org/stable/allpackages {{formatnum:20000}}+]
| pi:raspberry
| [http://www.xbmc.org XBMC]
|-
| [http://en.wikipedia.org/wiki/RISC_OS Risc OS]
| 2012-07-10 (5.19)
| 2012-07-09 (5.19)
| ARM RISC OS
| [http://www.riscosopen.org/content/documents/ssfaq Shared Source]
|
| {{no}}
| [http://www.riscosopen.org/content/downloads/other-zipfiles System Files] [http://www.riscosopen.org/forum/forums/1/topics/1098 Unofficial SD Card Image]
|
| N/A
| [http://en.wikipedia.org/wiki/WIMP_%28computing%29 wimp]
|-
| [http://www.slitaz.org/ SliTaz]
| 2012-05-29 (4.0)
| 2012-05-29 (4.0)
| Linux
| [http://www.opensource.org/licenses/gpl-2.0.php GPLv2]
| <~34 MiB
| {{no}}
| [http://kvarley.co.uk/RaspberryPi/SliTaz/ raw image]
|
| root:root
| Openbox
|}

==Fedora Remix==

The Raspberry Pi Fedora Remix is a Linux software distribution for the Raspberry Pi computer. It contains software packages from the Fedora Project (specifically, the Fedora ARM secondary architecture project), packages which have been specifically written for or modified for the Raspberry Pi, and proprietary software provided by the Raspberry Pi Foundation for device access.

* [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix wiki page]

==Debian (Squeeze/6.x)==

[http://www.debian.org/ports/arm/ http://www.debian.org/ports/arm/]

[http://www.debian.org/ Debian] was the default distribution on the Alpha boards. Boot time depends on width & speed of SD-card. Alpha board boot into Debian prompt (no GUI) was timed taking about 34 seconds.

The Debian distro for Raspberry Pi is the Cambridge reference filesystem, which is a fully functional Debian Squeeze installation containing LXDE (desktop) and Midori (browser); development tools; and sample code for accessing the multimedia functionality on the device.

==Arch==

[http://archlinuxarm.org Arch Linux ARM] is based on [http://www.archlinux.org/ Arch Linux], which aims for simplicity and full control to the end user. It provides a lightweight base structure that allows you to shape the system to your needs. For this reason, the Arch Linux ARM image for the Raspberry Pi does not come with a graphical user interface, though you can easily install one yourself. There is a [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=5&t=6000&p=79061&hilit=Arch#p79061 step-by-step guide] for installing Arch with the Enlightenment desktop. Please note that the Arch distribution may not be suitable for beginners.

Arch Linux ARM is on a rolling-release cycle that can be updated daily through small packages instead of huge updates every few months.

More information is available at http://archlinuxarm.org

==Raspbian==

Raspberry Pi + Debian = [http://www.raspbian.org Raspbian]. A project to create a hard float port of Debian Wheezy (7.x) armhf for the Raspberry Pi. The intent of Raspbian is to bring to the Raspberry Pi user 10,000s of pre-built Debian packages specifically tuned for optimal performance on the Raspberry Pi hardware. The project is still in it's early phases, but the major push to rebuild nearly all Debian packages for the Raspberry Pi is expected to be completed by early June, 2012 (only several hundred packages remain as of June 1st). After that, efforts will focus on making Raspbian the easiest to use, most stable and best performing Linux distribution available for the Raspberry Pi.

More information is available at http://www.raspbian.org

== IPFire ==

[http://www.ipfire.org IPFire] is an Open Source firewall distribution for x86 and ARM-based systems. It turns the Raspberry Pi computer into a small router for home networks and very small businesses. As the Raspberry Pi computer comes with only one NIC, it works perfectly as a 3G router without plugging in additional hardware.

The generally small system that provides essential services for networks can be enhanced by addons which add new features to IPFire. So the system can be turned into a file server and much more.

More information is available at http://www.ipfire.org

==OpenELEC==

OpenELEC is an embedded operating system built specifically to run [http://www.xbmc.org XBMC], the open source entertainment media hub. The idea behind OpenELEC is to allow people to use their Home Theatre PC (HTPC) like any other device you might have attached to your TV, like a DVD player or Sky box. Instead of having to manage a full operating system, configure it and install the packages required to turn it into a hybrid media center, OpenELEC is designed to be simple to install, manage and use, making it more like running a set-top box than a full-blown computer.

*[http://www.openelec.tv OpenELEC Mainsite]
*In February 2012, OpenELEC.tv announced their [http://openelec.tv/component/k2/item/235-openelec-on-raspberry-pi-our-first-arm-device-supported ARM port for Raspberry Pi]
*[http://openelec.tv/forum/90-miscellaneous/11763-raspberry-pi OpenELEC forum] thread
*[http://www.raspberrypi.org/forum/general-discussion/openelec RaspberryPi forum] thread
*[http://elinux.org/Rpi_openELEC Raspberry Pi build instructions for OpenELEC]

==Raspbmc==

Raspbmc is a minimal Linux distribution based on Debian that brings XBMC to your Raspberry Pi. This device has an excellent form factor and enough power to handle media playback, making it an ideal component in a low HTPC setup, yet delivering the same XBMC experience that can be enjoyed on much more costly platforms. Raspbmc is brought to you by the developer of the Crystalbuntu Linux Distribution, which brings XBMC and 1080p decoding to the 1st generation Apple TV.

*[http://www.raspbmc.com/ Main Site]

*[http://www.stmlabs.com/2012/06/24/network-issues/ Blog]
*[http://files.velocix.com/c1410/raspbmc/downloads/bin/ramdistribution/installer-testing.img.gz image]
*[http://download.raspbmc.com/downloads/bin/installers/raspbmc-win32.zip 1-click-Installer (Win)]
*[http://www.raspbmc.com/wiki/user/os-x-linux-installation/ Installation instructions (Mac/Lin)]
*[http://svn.stmlabs.com/listing.php?repname=raspbmc source]

==OpenWRT==

OpenWrt is described as a Linux distribution for embedded devices. Initial patches for the support against the latest development version "trunk" has been posted on the openwrt-devel mailing-list.

* http://thread.gmane.org/gmane.comp.embedded.openwrt.devel/14815
* http://www.zoobab.com/raspberry-pi-openwrt
* [https://forum.openwrt.org/viewtopic.php?pid=173937#p173937 openWRT Thread ] about Raspberry Pi status

==Bodhi==
Bodhi Linux is a small Linux distribution using the [ http://www.enlightenment.org/ Enlightenment] window manager and the ARM build is based on Debian.

If you hit any snags or find bugs with this image please let us know in the [http://forums.bodhilinux.com/index.php?/forum/30-raspberry-pi/ R_Pi section of our user forums] so we can improve this release.

* [http://jeffhoogland.blogspot.co.at/2012/07/bodhi-linux-raspberry-pi-beta.html?showComment=1343869408306#c8475812441665709126/ ARMHF ] announced for Bodhi Linux on R_Pi
*[http://jeffhoogland.blogspot.co.at/2012/06/bodhi-linux-arm-alpha-release-for.html Release Announcement] from Bodhi Developer Blog
*[http://sourceforge.net/projects/bodhilinux/files/ARM/RaspBerryPi/ Download] from sourceforge
*[http://forums.bodhilinux.com/index.php?/topic/2472-what-about-the-raspberry-pi/ what-about-the-raspberry-pi] Forum thread

Alpha Release [http://jeffhoogland.blogspot.co.at/2012/06/bodhi-linux-arm-alpha-release-for.html | Link Alpha Bodhi R_Pi])
User/Password: bodhi/bodhi root/raspberry

Beta Release [http://jeffhoogland.blogspot.co.at/2012/07/bodhi-linux-raspberry-pi-beta.html | Link Beta Bodhi R_Pi ]
User/Password: pi/bodhilinux Root: sudo su root/bodhilinux

==Gentoo==

[http://www.gentoo.org/ Gentoo Linux] is a source based rolling-release distribution which emphasizes choice and flexibility. [http://www.gentoo.org/proj/en/base/arm/ Gentoo ARM] aims to be the most up to date and fastest ARM distribution available.

A [http://wiki.gentoo.org/wiki/Raspberry_Pi guide] exists how to install Gentoo on the Raspberry Pi.

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=54&t=707 RaspberryPi forum] thread

=Announced distributions=

The following distributions have been announced and may have been publicly demonstrated but distributions are not generally available quite yet.

==NetBSD==
NetBSD is an operating system based off 4.3BSD and is geared towards embedded systems.
It is currently being actively ported, though there is no public release.

[http://mail-index.netbsd.org/port-arm/2012/07/13/msg001367.html Details about port]

==KidsRuby==

KidsRuby is what it sounds like – a Ruby for kids – and it’s running beautifully on the Raspberry Pi. This is exactly the sort of application we want to see on the device, and we’re really pleased to see it up and running. It looks like there will be some optimisation for speed before we launch, but what’s there already is very useable.

R.Pi blog entry: [http://www.raspberrypi.org/2011/09/kidsruby-on-raspberry-pi-another-video-demo/ http://www.raspberrypi.org/2011/09/kidsruby-on-raspberry-pi-another-video-demo/]
More info & Video: [http://confreaks.net/videos/637-gogaruco2011-kidsruby-think-of-the-children?player=html5 http://confreaks.net/videos/637-gogaruco2011-kidsruby-think-of-the-children?player=html5]

==Meego MER & XBMC==

The MeeGo MER project provides a Linux-based, open source software platform for the next generation of computing devices. The MeeGo MER software platform is designed to give developers the broadest range of device segments to target for their applications, including netbooks, handheld computing and communications devices, in-vehicle infotainment devices, smart TVs, tablets and more – all using a uniform set of APIs based on Qt. XBMC is an award-winning free and open source (GPL) software media player and entertainment hub for digital media. Meego TV 1.2 uses XBMC as a reference GUI (that is, a starting point for creating a custom GUI).

* [http://www.madeo.co.uk/?p=783 http://www.madeo.co.uk/?p=783]
* [http://www.madeo.co.uk/?page_id=605 http://www.madeo.co.uk/?page_id=605]
* [http://wiki.meego.com/User:Vgrade#Raspberry_Pi http://wiki.meego.com/User:Vgrade#Raspberry_Pi]
* [http://wiki.merproject.org/wiki/Community_Workspace/RaspberryPi http://wiki.merproject.org/wiki/Community_Workspace/RaspberryPi]
* [https://github.com/xbmc/xbmc-rbp https://github.com/xbmc/xbmc-rbp]

==Puppy==

[http://puppylinux.org/wikka/PARM Puppy] is the number one small Linux. [http://en.wikipedia.org/wiki/Puppy_Linux Puppy Linux] is going back to his roots. Designed to run from 256MB ram. Making every bit count. Join the [http://www.murga-linux.com/puppy/viewtopic.php?p=526#526 Puppy geek adventure] for 2012. Woof Woof

==RISC OS==

RISC OS is a fast and lightweight computer operating system designed in Cambridge, England by [http://en.wikipedia.org/wiki/Acorn_Computers Acorn]. First released in 1987, its origins can be traced back to the original team that developed the ARM microprocessor. RISC OS includes [http://en.wikipedia.org/wiki/BBC_BASIC BBC BASIC] which was primarily conceived to teach programming skills as part of the BBC computer literacy project.

*[http://www.riscosopen.org/ RISC OS Open] (ROOL) has released the sources. Community members have ported the OS to the BeagleBoard and similar hardware
*In November 2011, RISCOScode.com announced that [http://www.riscoscode.com/Pages/Item0113.html RISC OS will be available as an alternative OS] for Raspberry Pi <del>from launch</del>
*[http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=919 RaspberryPi forum] thread
*[http://www.riscosopen.org/forum/forums/5/topics/783 ROOL forum] thread

=Other Distributions=

These are other popular distributions that are often asked about for Raspberry Pi but are not available.

==Android==

[http://www.arm.com/community/software-enablement/google/solution-center-android/index.php http://www.arm.com/community/software-enablement/google/solution-center-android/index.php]

Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=144 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&t=144]

==GeeXboX ARM==

GeeXboX is a free and Open Source Media-Center purposed Linux distribution for embedded devices and desktop computers. GeeXboX is not an application, it’s a full-featured OS, that one can boot as a LiveCD, from a USB key, an SD/MMC card or install on its regular HDD. The GeeXboX distribution is lightweight and designed for one single goal: embed all major multimedia applications as to turn your computer into an HTPC.

[http://www.geexbox.org/category/arm/ http://www.geexbox.org/category/arm/]

==Ubuntu==

[http://www.ubuntu.com/ Ubuntu] was initially planned to be the default distribution, but the current version of Ubuntu only supports ARMv7 onwards, not the ARMv6 architecture used by the Raspberry Pi's processor. Therefore Ubuntu does not work on Raspberry Pi, and there is no further information about this changing in the near future.

A bug report on this subject was submitted to Ubuntu's bug tracker. The responses to that bug include an unofficial viewpoint from a Canonical employee, outlining the amount of work required to support ARMv6 (and therefore, potentially, Raspberry Pi). See [https://bugs.launchpad.net/ubuntu/+bug/848154 Bug 848154]

[https://wiki.ubuntu.com/ARM https://wiki.ubuntu.com/ARM]

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Cases

2012-08-06T21:53:56Z

Lxndr: added references, template, category

Back to [[RPi Hardware Basic Setup]].

{{Template:RPi_Hardware}}

As yet, the foundation does not provide cases for the Raspberry Pi. The small form factor or low power draw however, allow you to put it in almost everything.

==Lego Case==
[[File:R-Pi case, Lego, prototype.png|thumb|right|The Rpi Lego case, designed by forum user eric_baird]]

I just had a go at knocking up a quick Lego case prototype. Since I don't know the metrics of all the connections, it's a bit of a "proof of concept" right now, but since's it's not exactly difficult to take out any offending side-pieces and move them if they're in the way of a beloved connector, I'm assuming that this isn't a big deal.

Also, because of the thin side-walls, a bit of additional hacksawing or dremeling shouldn't be too difficult.

I've limited myself to only using pieces that are currently available from Lego's "Pick a Brick" shop, in red. :)

I've tried to fit everything into an 8*12 grid footprint, which will hopefully fit … but I don't have the specs of the thickness of the thin wall-pieces, so no guarantees. One thing that might screw things up is the height of the board's connectors: I don't know whether they'll all fit within the upper and lower lip of the side-wall pieces. If the board's "USB port stack" is too high, I guess the "roof" could be raised by a tile or two.

I knocked it up with Lego's Digital Designer program (free [http://ldd.lego.com/download/ download] from their site). The critical Lego piece is the repeated hollowed-out "side wall" ("[") brick ("wall element 1*2*2, w. window"), which you'll find on LDD's parts palette behind the little "door" symbol, or under the Pick a Brick page, as element #4507686, design #60032 (red), cost 8 pence each.

Feel free to hack, mangle or otherwise rework.

[[Media:Raspberry_Pi_Lego_Case.tgz|Download the Lego Digital Designer file for this case]]
{{clear}}

==Lego Case 2==
[[File:Rpilegocase.gif|thumb|right|100px|Another Rpi Lego case, designed by forum user kimondo]]

I had a bit of a play in lego designer with the idea of a vertical case – the USB / ethernet would emerge from the top, and the power usb would be on the bottom – possibly using a right angled usb connector. It's possible to alter the sides to allow for gaps for the various bits that stick out. There are lots of transparent bricks available – also includes a 2 x 2 brick to stick the raspberry pi sticker on.
{{clear}}

==ICEberg Case V3==

# First Case Aluminium with direct Coolling for CPU & LAN chipset
# Heat transfer with Silicon Thermal Pad
# Light LED Guide on the side
# 100% Aluminium machined CNC
# Case Design Pro
# GPU port available
# Upgrade with Vesa Mount
# Gloss finish
# Rubber foot

{|
|[[File:ICEberg-Case-vue-eclate-3D-264x300.png‎|thumb|center|200px|Exploded View ICEberg case]]
|[[File:ICEberg-V3-renderer.png|thumb|center|200px|A rendering of the case made by Moovika]]
|[[File:ICEberg-V3-renderer2.png|thumb|center|200px|Render 2]]
|[[File:ICEberg-V3-renderer4.png|thumb|center|200px|Render 3]]
|[[File:ICEberg-NewV32-300x298.jpg|thumb|center|200px|ICEberg V3 Production on the way !]]
|}

More information on BLOG [http://www.moovika.fr/raspberry-pi.fr/?cat=1 ICEberg Case]

Video V2 on youtube [http://www.youtube.com/watch?v=uZP5z4t30rQ ICEberg Case V2 Aluminium for Raspberry PI]

{{clear}}

==Marco Alici Case for Raspberry Pi==

Marco Alici, Italian Design Engineer, has designed this well appreciated clean enclosure to host the computer:

http://www.raspberrypi.org/forum/projects-and-collaboration-general/concept-for-a-case/
{|
|[[File:Raspberry-Pi-case_05c.jpg|thumb|center|200px|A rendering of the case made by MarcoA]]
|[[File:Raspberry-Pi-case_05d.jpg|thumb|center|200px|Another rendering made using [http://www.blender.org Blender] and [http://http://www.yafaray.org/ Yafaray]]]
|[[File:Raspberry-Pi-case_stacked_02.jpg|thumb|center|200px|A stackable version of the enclosure]]
|[[File:Prototype.jpg|thumb|center|200px|Raspberry Pi computer mounted into the first version of the enclosure 3D printed by [http://www.shapeways.com/shops/makeitreal Shapeways]]]
|}

This case is available for 3D printing [http://www.shapeways.com/model/486999 '''here'''] on [http://www.shapeways.com/shops/makeitreal Shapeways]. Everyone can buy it directly over there.

More infos on Marco's blog: http://marcoalici.wordpress.com
{{clear}}

==Printable Mylar Sheet Fold-up Case==

[[File:R-Pi_Mylar_Print-n-Fold_Case_Thick_Small.gif|right|200px|"tzj" Printable Mylar sheet case]]

[http://www.raspberrypi.org/forum/projects-and-collaboration-general/printable-cases-using-ohp-film RaspberryPi.org forum user "eric_baird"] thought of printing an outline of the walls of a case on a Mylar overhead projector (OHP) sheet or cardboard that could then be cut out and folded into a case. Multiple users have since
drawn such cases that can be printed on a Mylar sheet, thick paper, card stock, cardboard. The printed parts can be cut with a sharp knife or scissors and then folded/assembled into the case.

Multiple models are available:

[http://pdfcast.org/pdf/raspberry-pi-card-case-revision-1 The foldable case from "tzj"] (currently based on the model B beta board).

[http://elinux.org/images/0/0c/Raspberry-sandwich-1-0.pdf The foldable case from "alexisread"] originally posted [http://www.raspberrypi.org/forum/projects-and-collaboration-general/case-design-internal-mounting-raspberry-sandwich here].

[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=40&t=6500 The foldable case from "Andrew K"] is based on measurements of an actual Raspberry Pi model B and fits snugly.

[http://h2database.com/raspi The foldable case from Thomas Mueller] is (arguably) a bit more stylish. It stays closed without glue, and can be re-opened.

{{clear}}

==Laser-cut Clear Acrylic Case==
eBay UK seller guitarreriacom is offering a [http://www.ebay.co.uk/itm/360439728388 laser-cut clear acrylic case].
{|
|[[File:Laser-Cut_Clear_Acrylic_RasPi_Case.JPG|thumb|right|200px|Laser-cut Clear Acrylic Case on eBay]]
|[[File:Laser-Cut_Clear_Acrylic_RasPi_Case_Assembled.jpg|thumb|right|200px|Laser-cut Clear Acrylic Case on eBay]]
|}
{{clear}}
[http://www.adafruit.com/blog/2012/05/31/new-product-adafruit-pi-box-enclosure-for-raspberry-pi Adafruit Pi Box]

== BRAMBLE Pi - Laser-cut Finger Jointed Wooden Case ==
Etsy.com seller [http://www.etsy.com/people/Nhslzt Nhslzt] is offering a [https://www.etsy.com/listing/93162730/brambles-raspberry-pi-laser-cut-finger finger-jointed wooden case] for the Raspberry Pi for €12,00.
{|
|[[File:R-Pi Laser-cut Finger-jointed Wooden Case1.JPG|thumb|right|200px|Laser-cut finger-jointed wooden case on Etsy.com]]
|[[File:bramblepi1-1.jpg|thumb|right|200px|Laser-cut finger-jointed wooden case on Etsy.com]]
|[[File:R-Pi Laser-cut Finger-jointed Wooden Case2.JPG|thumb|right|200px|Laser-cut finger-jointed wooden case on Etsy.com]]
|}

=== Custom engraved Bramble Pi case ===
Etsy.com seller [http://www.etsy.com/people/Nhslzt Nhslzt] also offers a [https://www.etsy.com/listing/102467745/custom-engraved-bramble-pi-case Custom engraved Bramble Pi case] for the Raspberry Pi for €18,00.
{|
|[[File:custom-bramblepi-4.jpg|thumb|right|200px|Virtually any motif can be engraved!]]
|[[File:custom-bramblepi-1.jpg|thumb|right|200px|Linux's Tux.]]
|[[File:custom-bramblepi-2.jpg|thumb|right|200px|Ventilation ports are possible on the bottom plate (ad top) but also on both long sides.]]
|[[File:Bramblepi2-2.jpg|thumb|right|100px|Ventilation ports are possible on the bottom plate (ad top) but also on both long sides.]]
|}

{{clear}}

=== BRAMBLE Pi2 - laser engraved wooden case ===
[https://www.etsy.com/listing/103284715/bramble-pi2-raspberry-pi-laser-cut Bramble Pi2 - Raspberry Pi laser engraved wooden case] is also on sale on Etsy.com ([http://www.etsy.com/people/Nhslzt Nhslzt]). Laser cut and engraved with a bramble motif on both top and bottom.
{|
|[[File:bramblepi2-1.jpg|thumb|right|200px|Both bottom and top of the case are laser engraved.]]
|[[File:bramblepi2-2.jpg|thumb|right|100px|Ventilation ports are in the shape of the Raspberry Pi logo.]]
|[[File:bramblepi2-3.jpg|thumb|right|200px|Laser-cut finger-jointed wooden case on Etsy.com]]
|}

{{clear}}

==Raspberry Pi Board B Enclosure==

[[File:Raspberry-pi-board-b-enclosure.jpg|right|200px|solidworks prototype]]

A solidworks concept from http://solidworksbootcamp.com/raspberry-pi-board-b-enclosure/
{{clear}}

==Raspberry Pi air case==

[[File:Raspberry_air_case.jpg|right|200px|shape model]]

http://www.shapeways.com/model/434919/ and this is the [http://www.youtube.com/watch?v=NrLEiujfQh8 video]
{{clear}}

==Raspberry Pi fimo case==

[[File:Raspberry_pi_fimo_case.jpg|right|200px|fimo cover]]

The bijoux artist [http://www.annarellagioielli.com/ Annarella gioelli] has made her versione of case for raspberry pi usign fimo (a kind of polymer clay), there are a [http://annarellagioielli.blogspot.it/2012/04/tutorial-raspberry-pi-fimo-case-cover.html tutorial] and a [http://www.youtube.com/watch?v=77Ur56PB9iw video tutorial]
{{clear}}

==ModMyPi - Raspberry Topping Case==
[[File:Raspberry-Pi-Pokemon-case.jpg|thumb|right|200px|The red and white 'pokeball' case designed by ModMyPi
]]
ModMyPi LTD was founded in February 2012 following the public release of the ground breaking Raspberry Pi Model B. ModMyPi LTD specialise in the manufacture of unique, professional and high-quality cases for the Raspberry Pi. ModMyPi is offering mix and match colour customisable cases for sale on their [http://www.modmypi.com/ website].
{{clear}}

==Berry Box - The Lego compatible, transparent case for the Raspberry Pi==
[[File:Berry_box_case.png|right|200px|Berry Box]]
this is a [http://www.wefund.com/project/berry-box project] to make a case compatible with lego components, there's a [http://www.youtube.com/watch?v=CvuWAJ1Dn_o video]
{{clear}}

==RaspBerry Slice==
[[File:RaspBerry_Slice.jpg|right|200px|RaspBerry Slice]]
this is a project of the designer Brian Garvey, there a [http://www.indiegogo.com/projects/90582?c=home page] and a [http://www.youtube.com/watch?v=u6WcazMu8OQ video]
{{clear}}

==Raspberry Pi Cover - SK Pang electronics==
Developed in-house and manufactured in the UK. A range of laser cut acrylic covers for the Raspberry Pi.
[http://www.skpang.co.uk/catalog/raspberry-pi-c-240.html Link]
{|
|[[File:pi-cover-clr.jpg|thumb|right|200px|RaspBerry Cover]]
|[[File:pi_bboard.jpg|thumb|right|200px|RaspBerry Cover with Breadboard Area]]
|[[File:pi_dev_kit.jpg|thumb|right|200px|RaspBerry Cover with Breadboard Area]]
|}
{{clear}}

==Pi-Stack Raspberry Pi enclosure==
[[File:Pi-Stack.JPG|right|200px|RaspBerry Cover]]
Developed in-house and manufactured in the UK. One of a range of compatible acrylic products designed exclusively for the Raspberry Pi. While everyone else seems determined to "cover up his beauty from the world", the Pi-Stack exposes the Raspberry Pi elegantly from all 4 sides. Unlike some of the other designs the makers claim that this also allows access to all the GPIO pins. Currently available in "Gold", "Silver" and black with 10mm acrylic base and top. Currently sold in USA, Canada and Australia as well as the UK, via Ebay.
{{clear}}

==RepRap friendly cover for Raspberry Pi==
[[File:Pi-cover-reprap.png|right|200px|RepRap Pi Cover]]
The Rep-Rap we have is not very reliable and is only really able to produce basic designs so this is a 6 part case that has to be glued together.
There are 6 stl files [http://goo.gl/dqsvk here] with construction notes.
{{clear}}

==Mega Drive / Genesis Case for Raspberry Pi==
[[File:megadrivecase.jpg|right|200px|Mega Drive / Genesis Case by osholt]]
The design was thought up by osholt on the evening after receiving his Pi. The case is strictly DIY and an Instructable for it can be found at [http://www.instructables.com/id/Raspberry-Pi-Sega-Mega-DriveGenesis-II-Case/ the Instructables website]. The case is well suited to Green enthusiasts as it can easily be made with only reused or reclaimed parts as well as to emulation enthusiasts and to users with limited resources and design skill (you only need to know how to use a screwdriver to make the whole thing).
{{clear}}

==RPIBOX==
Our intention is to design a case for B model and provide that model of a functional protection, which all of us we will enjoy if you help me to achieve my objectives with your cooperation.

You can support al [http://www.lanzanos.com/proyectos/rpi-box/eng/apoyar/ RPIBOX project at lanzanos.com].
For more information visit [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=40&t=8710 at oficial forum] and [http://www.rpibox.net rpibox web]
[[File:RPIBOX_Black.jpg|right|200px|RPIBOX black case]]
[[File:RPIBOX_White.jpg|right|200px|RPIBOX white case]]
{{clear}}

==RaspBox==
[[File:raspbox.jpg|right|200px|The RaspBox, a minimalistic design.]]The RaspBox is made of two acrylic glass plates and four metallic spacers. All parts are hold together by eight screws. This minimalistic design comes from the Swiss company [http://www.yoctopuce.com Yoctopuce]. Originally, the RaspBox was just a pet-project, but as it was very appreciated within the company staff, the decision was made to bring it to the public. The design itself has been released under a Creative Commons Attribution-ShareAlike 3.0 License and can be downloaded from the [http://www.yoctopuce.com/EN/products/raspbox product page]. The finished product is also available from the [http://www.yoctopuce.com/EN/products/raspbox Yoctopuce shop].
{{clear}}

== Makerbot Cases ==
Two cases have been successfully printed on the makerbot so far. Both are vented for heat concerns. The main difference is one allows GPIO pin access directly.

[http://www.thingiverse.com/thing:24945 Design One]
{|
|[[File:P1010941_display_large.jpg|right|200px|Makerbot printed case with GPIO access]]
|[[File:Raspi_gpio_uncovered.jpg|right|200px]]
|[[File:Raspi_gpio_vent_covered.jpg|right|200px]]
|}

[http://www.thingiverse.com/thing:24721 Design Two]
{|
|[[File:RasPi_side.jpg|right|200px|Makerbot printed case]]
|[[File:RasPi_rear.jpg|right|200px]]
|[[File:RasPi_cover.jpg|right|200px]]
|[[File:RasPi_vent.jpg|right|200px]]
|}

==Tape Case==
Transparent cases for raspberry can be created using the case of a cassette tape.
Simply drill and cut the holes that are needed into the case using a dremel.

[[File:Tapecase.jpg|left|400px| Second version of the Tape Case]]

[http://imgur.com/a/AZIZN more images of the tape case]
{{clear}}

==DiscPi Case==
Easy DIY case made from a CD and plastic CD protectors.

[[File:DiscPi.jpg|right|200px| DiscPi case]]

[http://discpi.vkspartak.sk More images]

{{clear}}
== An 4€ RPi case ==
When having an RPi for 30€, buying a 15€ case is quit expensive. I decided to create this case. You just need :
# An 21x29.7 Art foam Cardboard
# Cutter
# Glues : sticker and gel

How to :

# Print the templates with the right scale
# Validate the sizes
# Glue the template on the board using the glue sticker
# Cut, assemble and glue using the glue gel
# If the RPi will stay powered for a long time. A few vent holes could be added

Final touch:

# Print a Raspberry Pi logo and glue it

The libreCad template files could be downloaded : [[File:Raspberry-pi-3mm-foamboard-case.dxf‎ | Raspberry Pi Foam Case]] and
the [[File:Raspberry-pi-3mm-foamboard-case-strips.dxf‎ | Raspberry Pi Foam Strips ]]

The 3d views of the case, thank you Hervé C. for this nice design :

[[File:FoamBoxBottomPlane.png|400px|thumb|left|FoamBoxBottomPlane.png]]
[[File:FoamBoxTopPlane.png|400px|thumb|center|FoamBoxTopPlane.png]]
[[File:FoamBoxBottom.png|400px|thumb|left|FoamBoxBottom.png]] 
[[File:FoamBoxCover.png|400px|thumb|center|FoamBoxCover.png]] 
[[File:FoamBoxBottomAndRaspberry.png|left|400px|thumb|FoamBoxBottomAndRaspberry.png]] 
[[File:FoamBox1.png|400px|thumb|center|FoamBox1.png]] 
[[File:FoamBox2.png|400px|thumb|left|FoamBox2.png]] 
[[File:FoamBox3.png|400px|thumb|center|FoamBox3.png]] 
[[File:FoamBox4.png|400px|thumb|left|FoamBox4.png]] 
{{clear}}

==Pibow==
[[File:Pibow.jpg|right|200px|Pibow Case]]
Made up of colorful layers sandwiched together between clear acrylic. [http://www.raspberrypi.org/archives/1640 Well received by the folks at the RaspberryPi foundation].
{{clear}}

==LCD Monitor Mount==
[[File:pilcdmount.jpg‎|thumb|right|200px|PI LCD Monitor Mount by PC Supplies]]

PI LCD Mount from PC Supplies Limited ([http://www.ebay.co.uk/itm/LCD-MOUNT-Case-for-Raspberry-Pi-PCSL-Deluxe-Wafer-LCD-VESA-100-Mount-/280921730684 eBay]), VESA 100 x 100 Standard Mount, Requires the 4xVESA Holes on your Monitor, Maybe not compatible if your monitor uses the VESA for the Base / Stand, Not compatible if you are already wall mounting your LCD Screen, Wafer Design, Motherboard is sandwiched between 2 wafers of clear shiny acrylic! Designed for Raspberry PI, Secured using 8 x M3 Nuts, Hex Spacers & Screws to allow you to build and unbuild, 4xM4 Spacers and 4xM4 Screws for the VESA Mounting. GPIO Compatible
{{clear}}

==Wafer Case==
[[File:piwafercase.jpg‎|thumb|right|200px|Wafer by PC Supplies]]

PI Wafer Case from PC Supplies Limited,
Wafer Design, Motherboard is sandwiched between 2 wafers of clear shiny acrylic!

Available from Amazon UK, Shipping throughout Europe [http://www.amazon.co.uk/PCSL-Brand-Raspberry-Professional-Delivery/dp/B008KPZADY Amazon UK]
{{clear}}

==PI Box Case==
[[File:pibox.jpg‎|thumb|right|200px|Pi Box by PC Supplies]]

Pi Box is the new Professional Case from PC Supplies Limited, Covers all sides of the motherboard for the ultimate protection. Unique Fit-together design with custom supplied 'PI Clips' Allows Access to SD Port / USB / Ethernet / Audio / Video / HDMI and PSU , No screws! and NO elastic bands! - "A true PRO design"

Available from Amazon UK, Shipping throughout Europe [http://www.amazon.co.uk/gp/product/B008DYNO6W Amazon UK]
{{clear}}

==PI Sandwich Case==
[[File:Sandwich3.png‎|thumb|right|200px|BUD PI Sandwich]]

BUD Industries is Proud to introduce The PI Sandwich Enclosure, designed for use with the Raspberry Pi microcomputer (not supplied) and to accommodate changes in component location on the board as well as the potential addition of components . The enclosures provide protection, flexibility and ease of access to all components with quick snap-in installation. This rectangular version is open on all four sides for direct access.

[[Media:BUD_Industries_is_Proud_to_introduce_The_PI_Sandwich_Enclosure.pdf | more details]]
{{clear}}

==Simple sandwich case==
[[File:Rpi-pc-case.jpg‎|thumb|right|200px|Sandwich case]]

Like me, most people do not have access to precision cutting tools like laser cutters. This makes it's rather difficult to do some of the intricate laser-cut case designs at home. So I decided to go with a simple sandwich case.

The case consists of:
* Two sheets of 75x120 mm polycarbonate
* Twelve 12 mm M5 countersunk hex screws
* Six 25 mm round spacers

The spacers have a notch at 6 mm which holds the board in place between the sheets of polycarbonate.
Sadly, my design isn't optimal since one of the spacers covers the GPIO pins.

This isn't the most beautiful case but I hope it inspires people to be creative and build their own case instead of just buying one. Building is fun!
{{clear}}

==Barch Designs Aluminum Engraved Case==

CNC Machined from Billet Aluminum. Mounting Holes in Bottom. Acts as a Heat Sink. LED Fiber Optics!

<h4><big>Features:</big></h4>
<ul>
<li> GPIO Port Access
<li> LED indicators
<li> True Heatsink Design
<li> Curved Sleek Look
<li> Mountable to a desk or wall
<li> Customizable!
<li> Nearly Indestructible
<li> Great Warranty
</ul>

[http://www.Raspberry-Pi-Case.com Manufacturing Website]

[http://www.PiHolder.com Official Store]

[[File:Raspberry-pi-case_LED3.jpg‎]]
[[File:Raspberry-pi-case_wired1.jpg‎‎]]
[[File:Raspberry-pi-case_bottom_cs.jpg‎]]
[[File:Raspberry-pi-case_GPIO3.jpg‎]]
[[File:Raspberry-pi-case_assembly4.jpg]]
[[File:Raspberry-pi-case_assembly3.jpg]]
{{clear}}

==Production Case==
[[File:R-Pi case, Production, case_small.png|thumb|right|Production quality Raspberry Pi case]]

This is a production quality case designed to meet most RPi owners needs. There is a [http://www.kickstarter.com/projects/250365370/raspberry-pi-case-0 Kickstarter project] trying to make this case available both with and without external screw terminal.

{{clear}}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Beginners

2012-08-06T21:53:11Z

Lxndr: added references, template, category

[[Category:RaspberryPi]]
{{Template:RPi_Startup}}

There is some restructuring going on , we are sorry for the inconvenience. '''

=Where to start?=
Any easy question to ask, but a very difficult one to answer!
# '''If you are looking for any information related to SD Cards and setup look [[RPi Easy SD Card Setup | here]]
# If you need to get a RPi, the see the [[RPi Buying Guide|Buying Guide]].
# If you need to know what equipment you will need and how to set it up, see the [[RPi Hardware Basic Setup|Basic Hardware Setup]] page.
# If you need to install/setup an SD card see the [[RPi Easy SD Card Setup|Preload your Card]] section.
# If something is not working, check the [[R-Pi_Troubleshooting|Troubleshooting]] section.
# If you need help with Debian, try the [http://wiki.debian.org/FrontPage Debian Wiki].
# If you have imaged a SD with the Debian Wheezy image and started your RPi here's some help with what you see first - the raspi-config menu [[RPi_raspi-config]]
# Help for Noob's with a quizical disposition and Wheezy or Raspbian instalations [[RPi_Noob_Guides_for_Wheezy_using_2012-16-18_beta|here]]
# If you don't have a composite monitor or HDMI then it may be worth you looking at [[RPi_A_Method_for_ssh_blind_login|Blind Login Method]]
# Build yourself a Wheezy [[RPi_A_Simple_Wheezy_LAMP_install|LAMP]] webserver.
# VNC connection for the monitorily challenged Noob [[RPi_Wheezy_VNC|VNC for a wheezy install]] (noobs that are using the Blind Login)
# If you've done all that, and you are wondering what next...'''welcome and read on!'''

References needed (idea for new section Living Without RPi, which can guide users or link to info to users who haven't got RPis)
Link to emulation builds or live linux cds setup for beginners (RacyPy2 for example)
If you don't have a Raspberry Pi yet, you can still try things out, see xxxx for details.

=What is Linux and why not use Windows?=
Linux is an operating system just like Windows, however, unlike Windows (which needs a set hardware requirement to run i.e. One Size fits or get different hardware), Linux comes in many varieties and configurations which means you can usually find a flavour (or Distribution) which fits your hardware big or small / fast or slow.

The Raspberry Pi is not suited to running Windows due to its hardware, but there are plenty of Linux Distributions which fit nicely. In addition to this, most Distributions of Linux are free, however Windows can cost many times the price of the Raspberry Pi itself.

Chances are you already have Linux running in your home without you even knowing it, since it is commonly used in modern TVs, Freeview and cable boxes to run things and ensure your recording of '''Inbetweeners''' or '''Prison Break''' gets done!

For more information about Linux see
[http://en.wikipedia.org/wiki/Linux Wikipedia]

Also see [[RPi_End-user_FAQ End-User|FAQ]]
And [[Will_RPi_Run|Running XXX on the RPi]]

=Basic Debian RPi Setup=
When you first turn on your Raspberry Pi with it's fresh Debian image on the SD card, you will likely want to tweak the system settings.

== Default login and password ==
See the ''Username:Password'' column of [[RPi_Distributions#Available Distributions|distributions table]] to access your Pi.

== Locale settings ==

By configuring the [[wikipedia:locale|locale]] settings, you can change the language and country settings (e.g. to get correct sorting behaviour) for much of the software available for the RPi. The default RPi locale is English/Great Britain ("en_GB").

You can alter this with

sudo dpkg-reconfigure locales

You will get a very long list of possible locales. You can enable/disable a locale by pressing the spacebar (not Enter), and scroll through the list using the arrow keys or PgUp/PgDn.

Selecting "All locales" will generate all possible locales, taking a very long time and using a great deal of space. Select only those you wish to use.

''It is highly recommended to stick to the UTF-8 locales'', and to leave the en_GB.UTF-8 locale enabled, in addition to any other locales you enable.

If you're unsure of which locale to pick, look up a [[wikipedia:List of ISO 639-1 codes|two-letter language code]] and a [[wikipedia:ISO 3166-1 alpha-2#Officially assigned code elements|two-letter country code]] on Wikipedia, and see if you can find a matching locale.

When you're done picking locale(s), press Enter. You will be prompted to select a default locale as well.

== Keyboard layout ==

If different letters appear on-screen from that which you typed, you need to reconfigure you keyboard settings. In Debian, from a command line type:

sudo dpkg-reconfigure keyboard-configuration

Follow the prompts.

'''Or:''' From the command line type:
sudo nano /etc/default/keyboard

Then find where it says

XKBLAYOUT="gb"

and change the gb to the [[wikipedia:ISO 3166-1 alpha-2#Officially assigned code elements|two-letter code]] for your country. [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=78325#p78325]

Also, see the [[R-Pi_Troubleshooting#Re-mapping_the_keyboard_with_Debian_Squeeze|Troubleshooting Guide]] for more information about remapping the keyboard.

You may need to restart for the changes to take effect.

If you get a very long delay during the keyboard mapping at startup, type the following once on the command line after you have logged in:

sudo setupcon

If the selected keyboard layout is not applied in the console (that is, when not running under X), try:

sudo apt-get install console-data

== Timezone ==

Unless you live in Great Britain, you'll have to change the default timezone:

sudo dpkg-reconfigure tzdata

Select geographic area - Europe, America or whatever. Etc gives UNIX compatible time zones including CUT, GMT, UTC

Select city

Follow the prompts to finish the config. The change should be immediate.

== Create a new user with sudo-privileges ==

You may want to create a new user account for yourself.

Type in following command in the terminal to create a new user:

sudo adduser username

Follow the steps.

To allow the newly created user to use the "sudo" command, type:
sudo visudo

Add following line under the "root ALL=(ALL) ALL" Line:

yourUsername ALL=(ALL) ALL

Now press CTRL+O, X to save and exit the editor.

Alternatively instead of adding the user to the sudoers list, you can add your user to the sudo group with the following command:

adduser <username> sudo

== Debian Wheezy, using raspi-config ==
Debian Wheezy has a menu that will do some of the above and more [[RPi_raspi-config]]

=Intro to the CLI (Command Line Interface)=
You will need to use the Command Line Interface at some point in your management of the RPi. The command line interface is a powerful way to interact with the Raspberry Pi and is well worth learning some basic commands to get started with.

For an introductory guide to some basic commands please see: [http://elinux.org/CLI_Spells Command Line Interface "Must Have" Commands]. Featured on the Raspberry Pi [http://www.raspberrypi.org/archives/1414 home page] was also a link to this site for [http://linuxcommand.org/learning_the_shell.php "learning the shell"]

Your SD card may boot into a GUI, if not and you are done with the text interface and want to use a graphical one instead, run:

startx

=Remote Access=
Your default install probably has a ssh (secure shell) "daemon" running.
This means that you can run everything on your Rpi with only the network attached. Provided you know which ip address it has. With appropriate software installed on your Winodws, Mac or Linux PC, you can also run a gui remotely.

Prior to your initial remote access it is recommended that you regenerate unique host public/private ID keys with the following command
rm /etc/ssh/ssh_host_* && dpkg-reconfigure openssh-server

More details about remote access (including remote GUI are at [[RPi Remote Access]]

=Adding more software to your Raspberry Pi=
You will probably want to add software to your Raspberry Pi. Here you can find out how to do it.
[http://elinux.org/Add_software Adding Software]

=Adding USB Storage to Your Raspberry Pi=
Sooner or later, you're going to run out of room on the SD card used to boot up your Raspberry Pi. For a tutorial on how to connect USB flash drives and hard drives to your Pi to expand storage, see: [http://elinux.org/RPi_Adding_USB_Drives Adding USB Drives to a Raspberry Pi]

=Beginner Projects=
Here are a few things you can try out with your Raspberry Pi, in most cases all you'll need is your SD Card loaded with a particular preconfigured OS Distribution.

It will be worth getting a few spare SD Cards if you think you will switch between setups regularly or become familiar with how to '''back up and restore''' your card.
Reference needed - a good guide on how to backup and restore cards or software to do this easily

==Backup your SD card==

For Windows users the 'Raw HDD Copy Tool' from HDD Guru works well to backup and restore your SD card between proejcts.
This can backup and restore the entire card sector by sector to/from an img file, and doesn't care which file system is on the card.

http://hddguru.com/software/HDD-Raw-Copy-Tool/

Linux users can use the dd tool that comes with most versions of Linux (including Raspbian) to save the contents of an SD card as an image file. Warning: be sure to use this tool carefully as accidentally choosing your hard drive as the output may destroy all data on it.

==Media Player==
With this configuration you will typically have the Raspberry Pi connected to a TV or large monitor and a source of videos/music/photos etc you wish to play (i.e. Internet/hard-drive/local network etc).

DesignSpark have written an article on this, which is worth a look, [http://www.designspark.com/content/raspberry-pi-goes-movies DesignSpark - Raspberry Pi goes to the movies]

You can download an installer from www.raspbmc.com which will install to your desktop (IOS, Windows, Linux) and write the latest install to your SD card. You then boot your Pi with the card and go through the config steps.

There is a breif video basic tutorial here: http://www.instructables.com/id/RaspberryPi-Media-center-XMBC/

''Reference needed - More information is needed on specific configuration choices for raspbmc, although raspbmc.com does have a wiki.''

==Play Games==
While there are not any commercial games for the Raspberry Pi (yet) there are plenty ways to play games on it.

Many distributions will have games built into them, and some may well support emulation of other platforms so you can run those games.

Also, a lot of Raspberry Pi users will be writing simple games which will be available for others to enjoy (and if desired added to or modified).

Reference needed - game section is empty at the moment!
''See the [[RPi Games|Games Section]] for more details''

==Introducing Young Children To Computers==
Reference needed - some kid friendly and fun stuff!

==Teaching==
There is a huge number of groups, links and resources available within the [[RPi Education|Education]] section.
Reference needed - links to the learning pages, education links and school/university groups

==Learn To Program==
There is a huge selection of [[RPi Programming|programming languages]] which you can use to write interesting programs, games, applications and utilities. There are also more great links within the [[RPi Education#Programming languages|Education]] section.

There is a huge selection to choose from (not just Python...) which should suit any ability and a range of purposes.

If you are new to programming, there are plenty of tutorials for getting started in the [[RPi Tutorials|Tutorials]] Section.

Books about programming can be found in the [[RPi Programming Books|Books]] Section.

In the latest Debian, Python (+Pygame) and MIT Scratch are pre-installed.

Reference needed - links to the learning pages, recommended books?

==Interface With Hardware==
# [[RPi Interfacing with hardware|Interfacing with Arduino]]

Reference needed - links to basic circuits tutorials and expansion boards

==Word Processing/Internet Browsing etc==
Yes, the Raspberry Pi can do the majority of the dull stuff too which other computers do.

'''Debian''' currently comes with Midori installed for web browsing and word processing programs be installed rather easily.

*Entering "sudo apt-get install chromium-browser" into a terminal will install Chromium which is generally a faster and more featured browser than Midori
*Entering "sudo apt-get install openoffice.org" into a terminal will install OpenOffice.org, a free Microsoft Office-like application suite
*Entering "sudo apt-get install abiword-common" into a terminal will install AbiWord, a lighter weight but still fully functional word processor
*Entering "sudo apt-get install gnumeric" into a terminal will install Gnumeric, a lighter weight but still fully functional spreadsheet

More information needed

==Your Own Pet Project!==
The sky is the limit really, with some time and effort any number of projects can be achieved.

Even if you don't have the skill to do it yourself, you can join like minded people by getting involved with one of the numerous groups in the [[RPi Community|Community Section]], also within the [[RPi Education|Education]] pages or learn what you need in from the [[RPi Guides |Guides]] & [[RPi Tutorials |Tutorials]] sections.

Of course, if you do anything interesting then please let us know in the [[RPi Projects |Projects]] section.

=Living Without RPi=
Even if you do not have any Raspberry Pi hardware there are a number things you can do to learn about linux, programming or even controlling hardware.

==Using Linux==
You can install a version of Linux on most computers, and many you will be able to "try out" Linux by using a "Live CD" - this will start your computer up running from a CD or DVD and run Linux (without installing anything to the computer itself).

RacyPy - This is a simple LiveCD of Puppy Linux which includes some basic programming languages and a light-weight graphical user interface (GUI).

You can get it from here:

[http://teampython.wordpress.com/2012/03/03/while-you-wait-for-your-raspberry-pi-why-not-use-racypy2/ teampython RacyPy]

==Trying Programming==
Many of the programming languages you can use on the Raspberry Pi can be installed on a Windows or Mac machine. Just visit the websites of the languages you are interested in and see if they have an installer for your operating system.

==Controlling Hardware==
As discussed in the [[RPi Tutorial Easy GPIO Hardware & Software | Easy GPIO Hardware & Software]] tutorials, there are lots of alternative hardware you can use to experiment with (some as little as $5).

=About This Page - For Contributors=

The intention of this page is to provide a '''starting point''' for beginners and to '''direct them to''' the kind of information a person would need in order to start doing something useful or interesting with a Raspberry Pi.

It is not intended to contain or replicate much of the information already available on-line or elsewhere in the wiki, however please create new wiki pages and link them here if there is information beginners will find useful (similarly any section which grows too much here, should be separated into new pages as and when needed)!

At the moment building up ideas of content of typical things beginners will want to know and the kind of things they will want to do first.

----

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Advanced Setup

2012-08-06T21:52:43Z

Lxndr: added references, template, category

[[Category: Linux]]
[[Category:ARM Development Boards]]
[[Category: Broadcom]]
[[Category:Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]
{{Template:RPi_Startup}}

=Notes=

'''WARNING: This page is not suitable for the average user. Information in this page is for experienced hackers only.'''

This page is a community work in progress in preparation for the first users. If something doesn't work or isn't covered in these guides, please feel free to ask on the [http://www.raspberrypi.org/?page_id=43 Forum]. But ''before'' you ask there, make sure you read the '''[http://www.raspberrypi.org/?page_id=8 FAQs]'''.

This page is based on [[BeagleBoardBeginners]] so the serial port info is appliable only under explained circumstances. Also, many Raspberry Pi users will buy pre-programmed SD cards and can skip to reading [[RPi Hardware Basic Setup]]. We expect that once Raspberry Pi boards become generally available helpful volunteers will update this page to match Raspberry Pi completely or point to better information elsewhere.

'''This page in a major work in progress!'''

=Finding hardware and setting up=
''Main article: see [[RPi Hardware Basic Setup]]''

You'll need to [[RPi Beginners#SD_card_setup | copy an image]] to a [[RPi_VerifiedPeripherals#SD_cards | suitable SD card]] (or [[RPi Beginners#Advanced_SD_card_setup | make your own image]]). You'll also need a USB keyboard, TV/Monitor (with HDMI/DVI/Composite/SCART input), and power supply (USB charger or a USB port from a powered USB Hub or another computer).

You'll likely also want a USB mouse, a case, and a USB Hub (a necessity for Model A). A powered USB Hub will reduce the demand on the RPi. To connect to the Internet, you'll need either an Ethernet/LAN cable (Model B) or a USB WiFi adaptor (either model). See [[RPi VerifiedPeripherals]] for more information on supported peripherals.

When setting up, it is advisable to connect the power after everything else is ready. ''See [[RPi_Hardware_Basic_Setup#Connecting_Together]].''

=Serial connection=

''For help setting up a serial connection with the Raspberry Pi, see [[RPi_Serial_Connection]].''

=Advanced SD card setup=

Now we want to use an SD card to install some GNU/Linux distro in it and get more space for our stuff. You can use either an SD or SDHC card. In the latter case of course take care that your PC card reader also supports SDHC.
Be aware that you are not dealing with an x86 processor, but instead a completely different architecture called ARM, so don't forget to install the ARM port for the distro you are planning to use.

Our first step will be the formatting of the SD card.

== Formatting the SD card via the mkcard.txt script ==
'''(to be completed)'''

# Download '''mkcard.txt''' from ???.
# <code>$ chmod +x mkcard.txt</code>
# <code>$ ./mkcard.txt /dev/sd</code>''x'', Where ''x'' is the letter of the card. You can find this by inserting your card and then running <code> dmesg | tail</code>. You should see the messages about the device being mounted in the log. Mine mounts as '''sdc'''.

Once run, your card should be formatted.

== Formatting the SD card via fdisk "Expert mode" ==

First, lets clear the partition table:

================================================================================
$ sudo fdisk /dev/sdb

Command (m for help): o
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
================================================================================

Print card info:

================================================================================
Command (m for help): p

Disk /dev/sdb: 128 MB, 128450560 bytes
....
================================================================================

Note card size in bytes. Needed later below.

Then go into "Expert mode":

================================================================================
Command (m for help): x
================================================================================

Now we want to set the geometry to 255 heads, 63 sectors and calculate the number of cylinders required for the particular SD/MMC card:

================================================================================
Expert command (m for help): h
Number of heads (1-256, default 4): 255

Expert command (m for help): s
Number of sectors (1-63, default 62): 63
Warning: setting sector offset for DOS compatiblity
================================================================================

NOTE: Be especially careful in the next step. First calculate the number of cylinders as follows:

* B = Card size in bytes (you got it before, in the second step when you printed the info out)
* C = Number of cylinders

C=B/255/63/512

When you get the number, you round it DOWN. Thus, if you got 108.8 you'll be using 108 cylinders.

================================================================================
Expert command (m for help): c
Number of cylinders (1-1048576, default 1011): 15
================================================================================

In this case 128MB card is used (reported as 128450560 bytes by fdisk above), thus 128450560 / 255 / 63 / 512 = 15.6 rounded down to 15 cylinders. Numbers there are 255 heads, 63 sectors, 512 bytes per sector.

So far so good, now we want to create two partitions. One for the boot image, one for our distro.

Create the FAT32 partition for booting and transferring files from Windows. Mark it as bootable.

================================================================================
Expert command (m for help): r
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-245, default 1): (press Enter)
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-245, default 245): +50

Command (m for help): t
Selected partition 1
Hex code (type L to list codes): c
Changed system type of partition 1 to c (W95 FAT32 (LBA))

Command (m for help): a
Partition number (1-4): 1
================================================================================

Create the Linux partition for the root file system.

================================================================================
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 2
First cylinder (52-245, default 52): (press Enter)
Using default value 52
Last cylinder or +size or +sizeM or +sizeK (52-245, default 245):(press Enter)
Using default value 245
================================================================================

Print and save the new partition records.

================================================================================
Command (m for help): p

Disk /dev/sdc: 2021 MB, 2021654528 bytes
255 heads, 63 sectors/track, 245 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sdc1 * 1 51 409626 c W95 FAT32 (LBA)
/dev/sdc2 52 245 1558305 83 Linux

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at the next reboot.

WARNING: If you have created or modified any DOS 6.x partitions, please see the fdisk
manual page for additional information.
Syncing disks.
================================================================================

Now we've got both partitions, next step is formatting them.

''NOTE'': If the partitions (/dev/sdc1 and /dev/sdc2) does not exist, you should unplug the card and plug it back in. Linux will now be able to detect the new partitions.

================================================================================
$ sudo mkfs.msdos -F 32 /dev/sdc1 -n LABEL
mkfs.msdos 2.11 (12 Mar 2005)

$ sudo mkfs.ext3 /dev/sdc2
mke2fs 1.40-WIP (14-Nov-2006)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
195072 inodes, 389576 blocks
19478 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=402653184
12 block groups
32768 blocks per group, 32768 fragments per group
16256 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912

Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information:
================================================================================

All done!

''NOTE'': For convenience, you can add the <tt>-L</tt> option to the <tt>mkfs.ext3</tt> command to assign a volume label to the new ext3 filesystem. If you do that, the new (automatic) mount point under <tt>/media</tt> when you insert that SD card into some Linux hosts will be based on that label. If there's no label, the new mount point will most likely be a long hex string, so assigning a label makes manual mounting on the host more convenient.

== Setting up the boot partition ==

The boot partition must contain the following files, get them from one of the official images:(bootable/fat32 partition)
* bootcode.bin : 2nd stage bootloader, starts with SDRAM disabled
* loader.bin : 3rd stage bootloader, starts with SDRAM enabled
* start.elf: The GPU binary firmware image, provided by the foundation.
* kernel.img: The OS kernel to load on the ARM processor. Normally this is Linux - see instructions for [[RPi Kernel Compilation |compiling a kernel]].
* cmdline.txt: Parameters passed to the kernel on boot.

Optional files:
* [[RPi config.txt|config.txt]]: A configuration file read by the GPU. Use this to override set the video mode, alter system clock speeds, voltages, etc.
* vlls directory: Additional GPU code, e.g. extra codecs. Not present in the initial release.

=== Additional files supplied by the foundation ===

These files are also present on the SD card images supplied by the foundation.

Additional kernels. Rename over kernel.img to use them (ensure you have a backup of the original kernel.img first!):
* kernel_emergency.img : kernel with busybox rootfs. You can use this to repair the main linux partition using e2fsck if the linux partition gets corrupted.

Additional GPU firmware images, copy over start.elf to use them:

the file called start.elf actually determines how much of the available 256MB of memory is assigned to the GPU.
The other splits are simply very similar files with a different filename, which are copied over the one called start.elf that is actually used, the others will have names like arm192_start.elf and such.

* arm128_start.elf : 128M ARM, 128M GPU split (use this for heavy 3D work, possibly also required for some video decoding)
* arm192_start.elf : 192M ARM, 64M GPU split (this is the default)
* arm224_start.elf : 224M ARM, 32M GPU split (use this for Linux only with no 3D or video processing. Its enough for the 1080p framebuffer, but not much else)

Note that actually there is no "default" split, the nature of the software determines what is the most suitable split. So a "distro" that is very heavy multimedia oriented will normally use the 128/128MB split as the GPU needs a lot of RAM, but a generic desktop distro will probably use the 64/192 MB split, and a game that doesn't use the GPU will probably use the 32/224MB split.



=Finally booting GNU/Linux=
== important steps ==
to be completed

== Setting up for remote access / headless operation ==
If you're anything like me (lazy, with a limited number of monitors), you'll want to get your Pi set up for remote access as soon as possible. Luckily, this is easy.
''These instructions assume you're using the official Debian distro for the Pi. Steps 0 & 1 based on info from [http://steve.dynedge.co.uk/2012/05/29/enabling-ssh-on-debian-raspberry-pi/ Steve Smith].''
* '''Step 0'''. Before you set up SSH, you might want to change the default password on the Pi, especially if it'll end up internet-facing. Do this on the Pi's console with the following command: <pre>passwd</pre>
* '''Step 1: Enable SSH''' with the following command:<pre>sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc</pre>This will enable sshd on the next boot. Restart the Pi. On reboot, you should see a line like the following:<pre>Starting OpenBSD Secure Shell server: sshd</pre> near the end of the boot sequence. This indicates that sshd is enabled, and you should be able to ssh into the Pi. You'll need the Pi's IP adress to do that; get that at the Pi's console with:<pre>ip addr</pre>You may also find it useful to copy an SSH key to the Pi so you don't need to enter a password each time you connect. To do that, first check if you've already got a public ssh keyfile:<pre>ls ~/.ssh/id_rsa.pub</pre>If you haven't, you can generate one with:<pre>ssh-keygen -t rsa -C "your_email@youremail.com"</pre>Finally, copy the keyfile to '''~/.ssh/authorized_keys''' on the Pi (there's a few different ways to do this, I used Transmit[http://panic.com/transmit/] to copy it over SFTP, since I'm a Mac user. Windows users have WinSCP[http://winscp.net/eng/index.php], and Linux users probably already know how to do it ;) ). This file contains '''all''' of the keys authorised to connect to the Pi, so will probably be blank or non-existent on a new Pi. If so, just copy '''id_rsa.pub''' to this location. If it already exists, add the key from '''id_rsa.pub''' to the end of the file.
* '''Step 2: IP address config.''' If your Pi is going to be always-on, or your network is set up in a such a way that devices always get the same IP, you can skip the step. However, if your Pi's IP is likely to change frequently (say, for instance, you're just powering it up every so often to play, and your network assigns IPs first-come first-served {like most home routers} ), it's a good idea to set up a consistent network address for your Pi. There's two ways to do this: the quick (but brittle) way and the more flexible way.
**'''The quick way: assign a static IP address to your Pi.''' This is simple, but runs the risk of clashing IP addresses with other devices on your network since your Pi's address will no longer be managed by DHCP. I haven't tried this myself, but here's some instructions from [http://blog.andrewmunsell.com/post/24830266512/setting-up-the-raspberry-pi-as-a-headless-device Andrew Munsell]. He's using '''192.168.1.222''' for his Pi, since that's outside the range assigned by his router. Change this address to whatever suits.<pre>You can do this in Debian Squeeze on the Raspberry by modifying the /etc/network/interfaces file.

I removed the original iface eth0 line and replaced it with the following:

iface eth0 inet static
address 192.168.1.222
netmask 255.255.255.0
gateway 192.168.1.1
</pre>On reboot, your Pi should now be using the static address specified in '''/etc/network/interfaces'''.
**'''The flexible way: set up avahi / zeroconf.''' Zeroconf is 'a set of techniques that automatically creates a usable Internet Protocol (IP) network without manual operator intervention or special configuration servers.'[http://en.wikipedia.org/wiki/Zero_configuration_networking]. Avahi is an implementation of zeroconf which 'ships with most Linux and *BSD distributions'[http://en.wikipedia.org/wiki/Avahi_(software)], but '''not''' the Pi's Debian distro. Zeroconf will be familiar to Apple users as '''Bonjour''', and is pretty clever tech which means that things Just Work when sharing stuff across computers on a network. In this context, it means that once we've set it up on the Pi, we'll be able to address it as: <pre>raspberrypi.local</pre> regardless of what IP address it's been assigned on your local network. This is handy if its IP is likely to change regularly, and even means we'll continue to be able to address it if we're on a different network (say, shuffling between home & work networks). ''Information in this section largely gathered from [http://4dc5.com/2012/06/12/setting-up-vnc-on-raspberry-pi-for-mac-access/ 4dc5]''.
#'''Install avahi''' with the following commands on the Pi: <pre>sudo apt-get install avahi-daemon</pre> and then on older Debian installs:<pre>sudo update-rc.d avahi-daemon defaults</pre>or on newer Raspbian installs:<pre>sudo insserv avahi-daemon</pre>(if in doubt, you're probably on the newer one).
# '''Create a configfile for Avahi''' at '''/etc/avahi/services/multiple.service'''. I did this with the following command:<pre>sudo pico /etc/avahi/services/multiple.service</pre>The contents of this file should be something like the following, courtesy of '''aXon''' on the [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=7795&p=94439&hilit=avahi#p94439 Rasperry Pi forums]:<pre><?xml version="1.0" standalone='no'?>
<!DOCTYPE service-group SYSTEM "avahi-service.dtd">
<service-group>
 <name replace-wildcards="yes">%h</name>
 <service>
 <type>_device-info._tcp</type>
 <port>0</port>
 <txt-record>model=RackMac</txt-record>
 </service>
 <service>
 <type>_ssh._tcp</type>
 <port>22</port>
 </service>
</service-group></pre>
# '''Apply the new configuration''' with:<pre>sudo /etc/init.d/avahi-daemon restart</pre>The Pi should now be addressable from other machines as '''raspberrypi.local''', for example: <pre>ssh pi@raspberrypi.local</pre>

= Software development/proving =

A supported platform for the Raspberry is Qt, which is already being worked on.
C/C++ is supported through a gcc cross-compiling toolchain. On Debian/Ubuntu systems, the packages gcc-4.6-arm-linux-gnueabi and g++-4.6-arm-linux-gnueabi provide suitable compilers. For other build platforms, [http://www.bootc.net/archives/2012/05/26/how-to-build-a-cross-compiler-for-your-raspberry-pi/#comment-22483 Chris has good instructions for building a cross-compiler] - this should also work in a Cygwin environment on Windows. MinGW may also be supported.

Python is being pushed forward by the foundation. (Status ??)

After compiling, using QEMU and a Linux VM would be one way of testing your apps (this also works on Windows).
Search the forum for the ready-made ARM images.

The choice of programming languages, IDEs and other tools on the R-Pi is only determined by:

1) The operating system compatibility (at the moment the specific Linux distro used)

2) The status of the respective ARM package repositories and their binary compatibility

3) The possibilty to build other software + its dependencies for the R-Pi from sources (depends on C cross-compiler ???)

What kind of software development and testing loop has been proven effective please (from someone who's been there and done it)?

For me (and others, hopefully) that would be very useful.

=Further reading=

The main Raspberry Pi resources are:

* Raspberry Pi Foundation-maintained [http://raspberrypi.org/ Raspberry Pi home]
* Raspberry Pi Foundation-maintained [http://raspberrypi.org/phpBB3 Raspberry Pi Forum]
* Community-maintained [[R-Pi_Hub|eLinux wiki]] (see [[:Category:RaspberryPi|wiki article overview]] for a list of existing articles)

An alternative startup guide for beginners can be found on h2g2: [http://h2g2.com/A13735596 Introducing the Raspberry Pi]

For more guides and projects involving the Raspberry Pi, see [[RPi Projects]].

=Thanks to=

* Nabax, _vlad, jkridner, ds2 and the other [[BeagleBoard]] wiki contributors on elinux.org for an excellent [[BeagleBoardBeginners]] resource, which we used as the template for this page.

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Easy SD Card Setup

2012-08-06T21:51:57Z

Lxndr: added references, template, category

[[Category: RaspberryPi]]
{{Template:RPi_Startup}}

=SD Card setup=
To boot the Raspberry Pi, you need an SD card installed with a bootloader and a suitable Operating System. Some Raspberry Pi kits will come with a ready-to-go card, but if you didn't receive one you will need to prepare your own:

Official images are available from http://www.raspberrypi.org/downloads and there is an overview of available distributions [[RPi_Distributions | here]].

Warning! When you write the Raspberry Pi image to your SD card you will lose all data that was on the card.

=Safest/Laziest way=
Buy a preloaded card from RS Components, element14 or [http://www.trendinguk.co.uk/sd-cards--operating-systems.html TrendingUK ]

=Easiest way=

* Use an installer program. The [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix_Installation#SD_Card_Installation_Using_the_Installer Fedora ARM Installer] will download and install Raspberry Pi Fedora Remix images, but it will also install other images if they are already downloaded and in uncompressed or .gz format.

* ('''Mac''') The [https://github.com/exaviorn/RasPiWrite RasPiWrite] utility is a python script which will walk you through the process of installing to SD card, it works with any Raspberry Pi compatible disk image, and can download one of the currently available distros if you don't have one.

=Easy way=

To write your SD card you start by downloading the SD image (the data you will write to the card). The best way to do this is using [http://en.wikipedia.org/wiki/BitTorrent_(protocol) BitTorrent]. This generally results in a faster download as it is a highly distributed system (you will be downloading the data from users who have previously downloaded it).

This guide assumes you have downloaded the Debian "squeeze" image, with name debian6-13-04-2012. Obviously, if you are downloading a different or newer version, use the name of the version you have downloaded.

==Copying the image to an SD Card on Windows==

# Download the image from a mirror or torrent. The remainder of this assumes you are using the Raspbian “wheezy” download 2012-07-15-wheezy-raspbian.zip
#* http://www.raspberrypi.org/downloads
# Extract the image file 2012-07-15-wheezy-raspbian.img from the downloaded .zip file.
# Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example G:) by looking in the left column of Windows Explorer. If the card is not new, you should format it; otherwise Win32DiskImager may hang.
# Download the [https://launchpad.net/win32-image-writer Win32DiskImager] utility. The download links are on the right hand side of the page, you want the binary zip.
# Extract the executable from the zip file and run the Win32DiskImager utility. You may need to run the utility as Administrator.
# Select the 2012-07-15-wheezy-raspbian.img image file you extracted earlier
# Select the drive letter of the SD card in the device box. Be careful to select the correct drive; if you get the wrong one you can destroy your computer's hard disk!
# Click Write and wait for the write to complete.
# Exit the imager and eject the SD card.
# Insert the card in the Raspberry Pi, power it on, and it should boot up. There is an option in the configure script that comes up to expand the partitions to use all of the SD card if you have used one larger than 4 GB
''In Windows the SD card will appear only to have a fairly small size - about 75 Mbytes. This is because most of the card has a partition that is formatted for the Linux operating system that the RPi uses and is not visible in Windows.
''

==Copying the image to an SD Card on Windows if first option isn't successful==
I wasn't able to choose device in Win32DiskImager on my notebook so I found a different way to achieve the same thing on windows machine..

# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Extract the image file debian6-19-04-2012.img from the debian6-19-04-2012 directory in the debian6-19-04-2012.zip
# Insert the SD card into your SD card reader and check what drive letter it was assigned. You can easily see the drive letter (for example H:) by looking in the left column of Windows Explorer.
# Download flashnul software from http://shounen.ru/soft/flashnul/ here is [http://translate.google.com/translate?u=http%3A%2F%2Fshounen.ru%2Fsoft%2Fflashnul%2F&hl=en&ie=UTF8&sl=ru&tl=en Translated version]
#* Download the latest version at the time of writing it was flashnul-1rc1.
#* Download and Extract the application from archive.
#* Click Start button > All Programs > Accessories > Command Prompt, right click on it and Run as Administrator.
#* Run the flashnul with argument:
C:/flashnul/flashnul.exe -p
#* Flashnul will tell you something like:

Avaible physical drives:
0 size = 250059350016 (232 Gb)
1 size = 1990197248 (1898 Mb)

Avaible logical disks:
C:\
D:\
F:\
G:\
H:\

Press ENTER to exit.

'''SDCARD number is on left! In my case it is number 1'''

#* Now we will use Load argument:
C:/flashnul/flashnul.exe 1 -L C:/debian6/debian6-19-04-2012.img
where '''<Path to flashnul directory>'''flashnul.exe '''<device number>''' -L '''<img file path>'''

#* Flashnul will give you a device summary and proceed caution, have a quick scan through the information to make sure you have selected the correct device, then type yes and press enter.
#* If you get a access denied error, try re-plugging the SD card. Also make sure to close all explorer windows or folders open for the device.
#* If you still get a access denied error, try substitute the device number with the drive letter followed by a colon. Eg:
C:/flashnul/flashnul.exe H: -L C:/debian6/debian6-19-04-2012.img
* If the device summary does not match Your card (the size is smaller, e.g. 75MB), but you are sure, that the letter is correct - please continue and then try again with the device number.

==Copying an image to the SD Card in Mac OS X==

'''Note''': Some users have [http://www.raspberrypi.org/phpBB3/search.php?keywords=extra+files&t=8226&sf=msgonly reported issues] with using OSX to create SD Cards.
#These commands and actions need to be performed from an account that has administrator privileges.
# Download the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Verify if the the hash key is the same (optional), in the terminal run:
#* '''shasum ~/Downloads/debian6-19-04-2012.zip'''
# Extract the image:
#* '''unzip ~/Downloads/debian6-19-04-2012.zip'''
#* ''(or: just double click the zip, it will extract automatically)''
# From the terminal run '''df -h'''
# Connect the sdcard reader with the sdcard inside
# Run '''df -h''' again and look for the new device that wasn't listed last time. Record the device name of the filesystem's partition, e.g. '''/dev/disk3s1'''
# Unmount the partition so that you will be allowed to overwrite the disk:
#* ‘’’sudo diskutil unmount /dev/disk3s1'''
#* ''(or: open Disk Utility and unmount the partition of the sdcard (do not eject it, or you have to reconnect it)
# Using the device name of the partition work out the raw device name for the entire disk, by omitting the final "s1" and replacing "disk" with "rdisk" ('''this is very important:''' you '''will''' lose all data on the hard drive on your computer if you get the wrong device name). Make sure the device name is the name of the whole SD card as described above, not just a partition of it (for example, rdisk3, not rdisk3s1 and '''definitely not''' rdisk1'''!!''' Similarly you might have another SD drive name/number like rdisk2 or rdisk4, etc. -- recheck by using the '''df -h''' command both before & after you insert your SD card reader into your Mac if you have any doubts!):
#* e.g. '''/dev/disk3s1''' => '''/dev/rdisk3'''
# In the terminal write the image to the card with this command, using the raw disk device name from above (read '''carefully''' the above step, to be sure you use the correct rdisk# here!):
#* '''sudo dd bs=1m if=~/Downloads/debian6-19-04-2012/debian6-19-04-2012.img of=/dev/rdisk3'''
#* if the above command report an error(dd: bs: illegal numeric value), please change bs=1M to bs=1m
#* (note that dd will not feedback any information until there is an error or it is finished, information will show and disk will re-mount when complete. However if you are curious as to the progresss - ctrl-T (SIGINFO, the status argument of your tty) will display some en-route statistics).
# After the dd command finishes, eject the card:
#* ‘’’sudo diskutil eject /dev/rdisk3'''
#* ''(or: open Disk Utility and eject the sdcard)''
# Insert it in the raspberry pi, and have fun

==Copying an image to the SD Card in Linux (command line)==

Please note that the use of the "dd" tool can overwrite any partition of your machine. If you specify the wrong device in the instructions below you could delete your primary Linux partition. Please be careful.

# Download the zip file containing the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Verify if the the hash key of the zip file is the same as shown on the downloads page (optional). Assuming that you put the zip file in your home directory (~/), in the terminal run:
#* '''sha1sum ~/debian6-19-04-2012.zip'''
#* This will print out a long hex number which should match the "SHA-1" line for the SD image you have downloaded
# Extract the image, with
#* '''unzip ~/debian6-19-04-2012.zip'''
# Run '''df -h''' to see what devices are currently mounted
# If your computer has a slot for SD cards, insert the card. If not, insert the card into an SD card reader, then connect the reader to your computer.
# Run '''df -h''' again. The device that wasn't there last time is your SD card. The left column gives the device name of your SD card. It will be listed as something like "/dev/mmcblk0p1" or "/dev/sdd1". The last part ("p1" or "1" respectively) is the partition number, but you want to write to the whole SD card, not just one partition, so you need to remove that part from the name (getting for example "/dev/mmcblk0" or "/dev/sdd") as the device for the whole SD card. Note that the SD card can show up more than once in the output of df: in fact it will if you have previously written a Raspberry Pi image to this SD card, because the RPi SD images have more than one partition.
# Now that you've noted what the device name is, you need to unmount it so that files can't be read or written to the SD card while you are copying over the SD image. So run the command below, replacing "/dev/sdd1" with whatever your SD card's device name is (including the partition number)
#* '''umount /dev/sdd1'''
#* If your SD card shows up more than once in the output of df due to having multiple partitions on the SD card, you should unmount all of these partitions.
# In the terminal write the image to the card with this command, making sure you replace the input file '''if=''' argument with the path to your .img file, and the "/dev/sdd" in the output file '''of=''' argument with the right device name ('''this is very important:''' you '''will''' lose all data on the hard drive on your computer if you get the wrong device name). Make sure the device name is the name of the whole SD card as described above, not just a partition of it (for example, sdd, not sdds1 or sddp1, or mmcblk0 not mmcblk0p1)
#* '''dd bs=1M if=~/debian6-19-04-2012/debian6-19-04-2012.img of=/dev/sdd'''
#* Note that if you are not logged in as root you will need to prefix this with '''sudo '''
#* The dd command does not give any information of its progress and so may appear to have frozen. It could take more than five minutes to finish writing to the card. If your card reader has an LED it may blink during the write process, or you can run '''pkill -USR1 -n -x dd''' in another terminal (prefixed with '''sudo''' if you are not logged in as root).
# As root run the command '''sync''' or if a normal user run '''sudo sync''' (this will ensure the write cache is flushed and that it is safe to unmount your SD card)
# Remove SD card from card reader, insert it in the Raspberry Pi, and have fun

==Copying an image to the SD Card in Linux (graphical interface)==
If you are using Ubuntu and hesitate to use the terminal, you can use the ImageWriter tool (nice graphical user interface) to write the .img file to the SD card.

# Download the zip file containing the image from a mirror or torrent
#* http://www.raspberrypi.org/downloads
# Right click the zip file and select "Extract here"
#* '''ATTENTION''': As of this writing (15 June 2012), there is a bug in the ImageWriter program that causes it to fail if the filename of the image file or its path (i.e. all the names of any parent folders that you extract the image file into) contain any space characters. Before going any further, ensure that neither the file name of the image you're using or the path contain any spaces (or other odd characters, for that matter). A bug has been opened for this issue: https://bugs.launchpad.net/usb-imagewriter/+bug/1013834 Once the issue is fixed, edit this page to advise people to use an updated/patched version of ImageWriter.
# Insert the SD card into your computer or connect the SD card reader with the SD card inside
# Install the ImageWriter tool from the Ubuntu Software Center
# Launch the ImageWriter tool (it needs your administrative password)
# Select the image file (example debian6-19-04-2012.img) to be written to the SD card (note: because you started ImageWriter as administrator the starting point when selecting the image file is the administrator's home folder so you need to change to your own home folder to select the image file)
# Select the target device to write the image to (your device will be something like "/dev/mmcblk0" or "/dev/sdc")
# Click the "Write to device" button
# Wait for the process to finish and then insert the SD card in the Raspberry Pi

=Manually resizing the SD card partitions (Optional)=
The SD card image is sized for a 2GB card. The Fedora Remix will automatically resize the partitions on the card during the first boot. The Debian version won't, so you'll have to do it manually. It's much easier if you do this on another machine, as the SD card can't be mounted when you do this.

Look [[RPi_Resize_Flash_Partitions|here]] for instructions.

=Adding a data partition (Optional)=
If you would rather not resize the partition on another machine as described above, either because you do not have another working Linux machine or you wish to keep your data on another partition to your operating system, you can instead create a new data partition and have that mount automatically at boot.

*First you need to become root and install parted (I did all of this from the boot command prompt, although if you feel safer in a GUI, you can do all of this in a terminal window):
sudo su -
apt-get install parted
*Then you need to run parted on your SD card, mine is /dev/mmcblk0, ymmv:
parted /dev/mmcblk0
*Once running, set the display units to something usable and then print your partition table
unit chs
print
*You should see something like this:
Model: SD SD08G (sd/mmc)
Disk /dev/mmcblk0: 121279,3,31
Sector size (logical/physical): 512B/512B
BIOS cylinder,head,sector geometry: 121280,4,32. Each cylinder is 65.5kB.
Partition Table: msdos
Number Start End Type File system Flags
1 16,0,0 1215,3,31 primary fat32 lba
2 1232,0,0 26671,3,31 primary ext4
3 26688,0,0 29743,3,31 primary linux-swap(v1)
*Now you need to create your data partition - you need to choose one more than the end of partition 3 with ,0,0 as your start and use the number from the line that starts with Disk as your end:
mkpart primary 29744,0,0 121279,3,31
print
*That should show your new partition:
Number Start End Type File system Flags
1 16,0,0 1215,3,31 primary fat32 lba
2 1232,0,0 26671,3,31 primary ext4
3 26688,0,0 29743,3,31 primary linux-swap(v1)
4 29744,0,0 121279,3,31 primary
*Now quit and format the partition (again, ymmv with the specific device name, try ls /dev for some clues), and then label it:
quit
mkfs.ext4 /dev/mmcblk0p4
e2label /dev/mmcblk0p4 data
*Now we need to make sure that the partition is mounted automatically when the system boots (maybe don't use vi if you never have before, try nano):
vi /etc/fstab
*Enter a line exactly like this at the end of the file and save and quit your text editor:
/dev/mmcblk0p4 /data ext4 defaults 1 2
*Create the mount point:
mkdir /data
*Now mount the partition:
mount /data
cd /data
ls
Your new partition has been created!

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

CLI Spells for the Raspberry Pi

2012-08-06T21:50:30Z

Lxndr: added references, template, category

[[Category:RaspberryPi]]
This Page is a Quickstart for Command Line Interface on the Raspberry PI.--[[User:Brian|Brian]] 09:13, 20 April 2012 (UTC)
[http://elinux.org/RPi_Beginners Back to Beginners Page]

== Why Do I Need the CLI? ==

(CLI-Command Line Interface)

The Raspberry Pi operating systems that you can download for your SD card are all versions of Linux. A graphical user interface (GUI) for Linux is provided by the X Windowing System, together with a window manager. There are lots of different window managers, for example the one being used at time of writing with the Debian "squeeze" OS is LXDE. For some OS distributions, the windowing system is started up automatically when the machine starts up, but if not then you are in the Command Line Interface, which allows you to type commands and get information back. Most of us will immediately type "startx" to bring up the GUI, but even when you are using the GUI you can still get a CLI in the form of a terminal window. You can bring this up from the start menu; usually it is called something like X Terminal.

You need the CLI because there are many things that either can't be be done using GUIs, or are much easier using the CLI. In addition there are situations when you would rather not run the X Windowing system, because it takes up a lot of processor power and memory. Also a Raspberry Pi doing some task or other may well have no screen at all, and you may manage it remotely using a remote log in to a terminal.

Windows and Mac users are generally guided away from the CLI hence this Quick start Guide.
The commands here have mostly been described and tested using debian linux which at the time of writing (April 2012) was the version of linux that was most active in the RPi world. It is not meant to advocate this distribution in particular. The author ([[User:Brian|Brian]] 09:27, 30 May 2012 (UTC)) is actually a Fedora user most of the time.

The quick answer to "why do I need the CLI?" then, is that the CLI is going to be a very useful tool for Raspberry Pi users.

== Commands are just programs ==
When you type into the terminal you are running programs. Most of the commands listed here run programs that give you the ability to command the system to do something. When you add programs to your pi, you will be able to run more commands. This means that if a command you run and expect to work returns the message
$ bash: foo: command not found...

It just means that you have not installed "foo" yet. Most of the commands described in this page are the kind of house keeping commands that come with bash. Each program has an original author who is acknowledged at the bottom of the man page.

To use the CLI you need to know commands and the default command set is contained in the "shell" you are using. There are Lots of shells out there and the one on this Raspberry Pi is Bash [http://en.wikipedia.org/wiki/Bash Wikipedia Bash Entry].

To find the syntax for a command do an Internet search for the command or find a Bash Quick Reference Card. In this wiki entry, each command has a link to the Wikipedia entry for that command.

If you want to know how to use commands without using the Internet then use man (short for manual).

$ man <command>
or
$ info <command>

from the CLI to be sent to a page of guidance.

The guidance given by "man" is sometimes a bit formal to the point that it could be said, "if you think you know a command then go to the command's man page in order to find out that you don't really".

== General Syntax of Commands ==

Commands take the form

<Command> | -<Switches> | <Parameters> | <Target>

<tt><nowiki><></nowiki></tt> are often used in Syntax guides to indicate that the <tt><nowiki><></nowiki></tt> surround a place for a command rather than an actual command.
<tt><nowiki>|</nowiki></tt> is used to denote OR or Optional so in the line above we read that a Command can be used on its own but may be followed by
Switches (single letters, preceded by a hyphen that adjust what the command does),
Parameters (Things that the command needs to know in order to work) and a
Target (The thing that the command will be applied to).

e.g. "<tt>ls -l /home/brian</tt>" means List in Long Format (the <tt>-l</tt> switch) the directory (target) <tt>/home/brian</tt>

mount -F smbfs //workgroup;fred:foo@192.168.1.99/homes /mnt/net

Means use the username <tt>fred</tt> and password <tt>foo</tt> (parameters) to make the shared drive called <tt>homes</tt> on the Windows server at <tt>192.168.1.99</tt> (parameter) appear in the directory tree at the point <tt>/mnt/net</tt> (target) using the Server Message Block Filing System (the <tt>-F</tt> switch). (BTW, this assumes that you have the samba client software installed on your pi)

== Task [http://en.wikipedia.org/wiki/Cd_%28command%29 $ cd]. Navigating the file system using "cd" ==
The file system in Linux is Hierarchical with nested directories. (Often called Folders) in a "Tree".
The top of the directory structure is "<tt>/</tt>" and Directories underneath <tt>/</tt> are referred to using "Paths" just like urls in a web browser. To go to a particular place in the directory structure you use ''<tt>cd</tt>''.
''e.g.''
cd /
will take you to the top of the Directory Tree

To go to a particular place use cd followed by the location in the tree.
cd /home/brian/Documents
will take you to "<tt>brian</tt>'s" home directory <tt>Documents</tt> Folder. '''File & Directory Names are Case Sensitive in Linux'''

To go one Directory "Up" the tree then do
cd ..

== Task [http://en.wikipedia.org/wiki/Ls $ ls]. Listing the files and Folders in a particular place ==
$ ls
list all the file in the current directory.
$ ls -l
list all the file in the current directory and display the long version of the information about each file or directory.
The output may be colour coded depending on the terminal preferences that you have set. <tt>ls -l</tt> tells you (amongst other stuff) the size, owner and security setting on each file.
Other useful invocations are
ls -R
Recursive. i.e. list contents of sub-directories as well as this directory.
ls -A
Show "Hidden" Files. ie. Hidden files are file names that start with a dot which in Unix GUI file navigators are (by default) hidden.

Examples.

$ ls

An_Gott_und_meine_Mutter.mid Domestic Programming Test.mid

An_Gott_und_meine_Mutter.mscz Engineering Quantum Physics Tutoring

appliances FluidR3_GM.ins School Windaz

...

$ ls -l

total 336

-rw-rw-r--. 1 brian brian 2429 Apr 2 20:27 An_Gott_und_meine_Mutter.mid

-rw-rw-r--. 1 brian brian 4085 Apr 2 19:52 An_Gott_und_meine_Mutter.mscz

drwxrwxr-x. 4 brian brian 4096 Apr 2 20:38 appliances

-rw-rw-r--. 1 brian brian 10919 Apr 2 19:52 brotplot.odt

.....

== Task [http://en.wikipedia.org/wiki/Chown $ chown] Change Ownership of directories and files ==

In the Long List above, the files are owned by Brian and are also in the Brian Group.
$ chown fred brotplot.odt
after executing <tt>ls -l</tt> will result in
-rw-rw-r--. 1 fred brian 10919 Apr 2 19:52 brotplot.odt

The file is still in group <tt>brian</tt> but is owned by <tt>fred</tt>

$chown foo:foo brotplot.odt
will result in

-rw-rw-r--. 1 foo foo 10919 Apr 2 19:52 brotplot.odt

The group has changed also. See Also <tt>[http://en.wikipedia.org/wiki/Chgrp chgrp]</tt>

== Task [http://en.wikipedia.org/wiki/Chmod $ chmod] Change Access to directories and files ==
When long list files, the left hand column takes the form <tt>xuuugggwww</tt>.
<tt>x</tt> is a letter describing what kind of thing the list entry is and can be various things but most commonly is <tt>d</tt>, <tt>l</tt> or <tt>-</tt>.
<tt>d</tt> stands for directory, <tt>l</tt> for link <tt>-</tt> for a file.

The <tt>uuugggwww</tt> describe access rights for the owner (user), group and the world. (i.e. everyone not in the set owner or group).
In each triplet, the order is <tt>rwx</tt>, <tt>r</tt> for ability to read, <tt>w</tt> for ability to write and <tt>x</tt> for ability to execute. If the <tt>x</tt>flag is not set then the file will not run as a program.

This line from above tells us that fred and the group called students both have read and write access where everyone else has read access only.

-rw-rw-r--. 1 fred students 10919 Apr 2 19:52 brotplot.odt

There are various ways of <tt>chmod</tt> use but probably the easiest is to consider the groups <tt>u</tt> for user-owner, <tt>g</tt> for group, <tt>o</tt> for other(everyone else) and a for all three.

Use chmod as follows
chmod o+w brotplot.odt
means add write access for the other group to brotplot.odt
chmod a-r brotplot.odt
means remove read access for the all three (user, group and other) from brotplot.odt
chmod u+x brotplot.odt
means add execute access for the user/owner to brotplot.odt

== Task [http://en.wikipedia.org/wiki/Sudo $ sudo]. Invoking commands as an admin user ==
This command introduces the SuperUser or root user. Many commands are only permissible to the root user and by invoking sudo before a command, you are saying "do the following command as the root user". When you do this, you will be asked for your password and if you have system permissions (commonly called being in the admin group) to be a root user then the command will be run. If you do not then a message will tell you so.

<tt>root</tt> is the name for the main administrator of a Unix like system. The default Debian distribution has no <tt>root</tt> passwd set and you do privileged commands by prepending the command with <tt>sudo</tt>.

Example
adduser brian
adduser: Only root may add a user or group to the system.

sudo adduser brian
# You now enter a sript that sets up a new user called brian

Anytime you get an "<tt>Only root can ....</tt>" message, try the <tt>sudo</tt> command.

There is another way of doing things as <tt>root</tt> user and that is by using

== Task [http://en.wikipedia.org/wiki/Su_%28Unix%29 $ su -] Becoming the admin user ==
which stands for "substitute user" (or "switch user") and as invoked here means "become the <tt>root</tt> user". From this point on, all commands run as the super user. Invoking this command will cause you to be asked for the <tt>root</tt> password. Some systems do not allow this to happen in a default install in which case you have to enable the root user.
To enable the root user issue
passwd root
(You will have to enter a new passwd). You will be asked twice for the password and assuming you can manage to enter the same password twice, you now have a root user and you can issue

su -

When you enter passwords in Unix like systems, you will not see asterisks or anything at the prompt but the password is being entered nevertheless.
If you habitually do everything as the <tt>root</tt> user, you shouldn't. Eventually you will do something both educational and disastrous. For example, you could invoke

rm -r -f /*
and delete all the files in the whole system.

$ rm -r -f ./*
would just delete the files in the current directory. You do not usually get warnings as <tt>root</tt> user. (Other than this one).

== Task [http://en.wikipedia.org/wiki/Touch_%28Unix%29 $ touch]. Create a new empty file ==
Go to where you want the file to be and invoke

$ touch <filename>

== Task [http://en.wikipedia.org/wiki/Mkdir $ mkdir]. Create a new empty directory ==
Go to where you want the directory to be and invoke

$ mkdir <Directory Name>

== Task [http://en.wikipedia.org/wiki/Rm_%28Unix%29 $ rm]. Remove a file ==
Go to where you want the directory to be and invoke

$ rm filename

== Task [http://en.wikipedia.org/wiki/Rm_%28Unix%29 $ rmdir]. Remove a Directory ==
Go to where you want the directory to be removed. The directory will already need to be empty of all contents.
rmdir

If the directory is not yet empty
$ rm -r -f <Directory Name>

This will remove the directory, all its contents and also any sub directories and their contents.

== Task [http://en.wikipedia.org/wiki/Mount_%28Unix%29 $ mount] Connect to a device or Filing System ==

<tt>mount</tt> is the way in which you connect a Unix system to external devices. There is no "C" drive as in Windows. What happens in Linux (and FreeBSD/OS X) is that a device is mounted in the filing system somewhere and when you navigate to that place. The items offered by the device will appear at that point.

This is a complex command. The switches, parameters and target of the Mount command will vary according to the protocol of the system being mounted. Some things will automount. This is why, when you plug a SDcard into a modern Linux, the filing system will automatically pick it up.

Manual Mounting requires a "Mount Point". That means a directory which will be filled with the mounted device when it is mounted. Often, this is in the directory <tt>/mnt/</tt> somewhere.

Generally, first ensure there is a mount point, if not then create a directory at the point needed.
e.g.
$ mkdir /mnt/netfolder

Then issue <tt>mount</tt> with the necessary switches, parameters and directories.

e.g. From above.

mount -F smbfs //workgroup;fred:foo@192.168.1.99/homes /mnt/net

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

R-Pi ConfigurationFile

2012-08-06T21:50:02Z

Lxndr: added references, template, category

[[Category:RaspberryPi]]

How to edit the boot configuration file for Raspberry Pi

=A quick overview=

While booting up, the Raspberry Pi reads some configuration parameters from the SD card.
These parameters are stored in a file named [[RPi_config.txt|config.txt]]. This file is within the part of the SD card which
is visible to Windows PCs. Therefore, you can edit this configuration file from a Windows PC, from a Mac,
from a Linux PC, or from within the Raspberry Pi itself.

This configuration file contains instructions which are necessary to setup the display.
If you have severe problems with the display, you will need to connect the SD card to a PC so that
you can edit the configuration file. If the display is working but you wish to make minor adjustments,
you may find it more convenient to edit the file from within the Raspberry Pi itself.

=How to edit from a Windows PC=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.

*Put the SD card in your PC's card reader and wait for the folder to open automatically.

*If the folder does not open automatically, open "My Computer" and then open the drive marked "SD".

*Look to see if there is a file called config (or possibly config.txt).

*If this file exists, open it with Notepad. If not, create the file with Notepad.
(One way to do this, in XP, is to right-click where you see the other files, select New and then Text document.
Then change "New Text Document" to "config").

*Open config.txt using Notepad, and add the necessary configuration parameters.

*Save the file (menu item File, Save)

*Exit Notepad

*In Windows Explorer, go to "My Computer". Right-click on the SD card and select "Safely Remove".

*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from OSX=
This method is most useful if you cannot see anything on the display of the Raspberry Pi.

*Shut down your Raspberry Pi, remove the power and remove the SD card.
*Put the SD card in your Mac's card reader and wait for the card to appear on the Desktop.
*Open the card in Finder.
*Look to see if there is a file called config (or possibly config.txt).
*If this file exists, open it with TextEdit. If not, create a new file in Textedit as Plain Text format.
*Add the necessary configuration parameters.
*Save the file as "config" and quit TextEdit.
*In Finder eject the SD card by dragging it to the Trash or clicking the eject button in the Finder window.
*Remove the SD card from the PC and insert it in the Raspberry Pi.

=How to edit from the Raspberry Pi=
This method is most useful if you can see the display of the Raspberry Pi and you wish to make minor adjustments.

*Reboot the Raspberry Pi and enter your username and password.

*To edit the configuration file, enter the command
sudo nano /boot/config.txt

*Type in the necessary configuration parameters

*Save the edited file
Press Control-x
Press y
Press [enter]

*After exiting the editor, restart using the command
sudo reboot

'''NOTE:''' You may find that your changes to config.txt disappear after a reboot. This is a very rare problem and seems to depend on the type of SD card. In this case, use a Windows/Linux/OSX PC to edit the file, see instructions above.

=An example configuration file=

This example show how to reduce the size of the display to prevent text spilling off the edge of the screen.

<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

=What configuration options are available?=
For a list of all the configuration options available, click [http://elinux.org/RPi_config.txt here]

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

R-Pi Troubleshooting

2012-08-06T21:49:38Z

Lxndr: added references, template, category

[[Category:RaspberryPi]]

Back to the [[R-Pi Hub|Hub]].

This page lists the most common problems and suggests some solutions.

See [[RPi_Bugs]] for problems that are bugs.

==Power / Start-up==
A good power supply that will supply 5V is vital. There is more information about See [[#Troubleshooting_power_problems]].
===Red power LED does not light, nothing on display===
The power is not properly connected.

===Red power LED is blinking===
The red power LED should never blink, because it is hard-wired to the 3.3V power supply rail. If it is blinking, as one user has reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7528</ref> it means the 5V power supply is dropping out. Use a different power supply.

===Red power LED is on, green LED does not flash, nothing on display===
*The Raspberry Pi cannot find a valid image on the SD card. Check card is inserted correctly. Check that you have correctly written a Raspberry Pi image to the card. Insert the SD card into a Windows machine and you should see bootcode.bin, loader.bin and start.elf amongst others. See also, [[RPi_VerifiedPeripherals#SD_cards|Known SD Cards]].
*Try with no cables connected except the USB power lead, and SD card inserted. You should see flashing of the OK light for ~20 seconds. If that helps, plug in cables one at a time to identify which is interfering with boot.
*The voltage is too low (below 5 V), try a different power supply and/or cable. The R-Pi needs a supply rated for 700 mA or more. Some supplies labeled as such cannot actually provide their rated current while maintaining 5V. See also, [[#Troubleshooting_power_problems]].
*There is a bug in the distributed version of bootcode.bin which causes problems with some sdcards. Try this version: https://github.com/raspberrypi/firmware/blob/234c19de7cbaaf4997671d61df20a05759066295/boot/bootcode.bin. Please let us know if it "fixes" your non-working SD card (or, more importantly, if it doesn't). This can also manifest itself as intermittent booting, or only booting when cold.
*''(unlikely)'' hardware abuse, for example by connecting a 7 V supply to a 3v3 GPIO output pin<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5096&p=76503#p76503</ref> or powering up the board after a solder splash shorts some traces<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5096&p=76654#p76654</ref>.

===Green LED blinks in a specific pattern===

With recent firmware, according to [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8725#p103338 this forum post] the green light will blink in a specific pattern to indicate some types of errors:

* 3 flashes: <tt>loader.bin</tt> not found
* 4 flashes: <tt>loader.bin</tt> not launched
* 5 flashes: <tt>start.elf</tt> not found
* 6 flashes: <tt>start.elf</tt> not launched

===Coloured splash screen===
[[File:Debug-screen.jpg]]

With recent firmware, a coloured splash screen is displayed after firmware (start.elf) is loaded. This should be replaced by linux console a second later.
However if the coloured screen remains, it suggests the kernel.img file is failing to boot. Try replacing it with a known good one.

===Kernel Panic on boot ===
Text appears on screen, but then hangs with debug messages. This can be caused by USB devices such as keyboards.
Try again with nothing in the USB.

===Raspberry Pi shuts down soon after booting up===
This is caused by a power supply producing too low a voltage. See [[#Troubleshooting_power_problems]].

===Pi boots sometimes but not always===
With a known good power supply and known good SD card, the R-Pi boots occasionally, but other times shows only a tiny green flicker from the "OK" LED and it fails to start, even with no USB devices and no Ethernet. This has been reported several times<ref>http://www.raspberrypi.org/forum/troubleshooting/will-not-boot-consistently-any-suggestions-before-i-send-my-pi-back</ref>
<ref>http://www.raspberrypi.org/forum/troubleshooting/booted-once-wont-work-again</ref>
<ref>http://www.raspberrypi.org/forum/troubleshooting/possible-fault-pi-boots-sometimes-but-not-always</ref> and remains an open issue. Low voltage or an improper SD card can cause it. Some SD cards will work until they warm up slightly, and then fail<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5900&p=79008#p79008</ref>. When exposed to 21 C room temperature the warmest part of an uncased working R-Pi should be 41 C<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=6&t=5900&p=78973#p78973</ref>. The wiki has a [[RPi_VerifiedPeripherals#SD_cards | list of working SD cards]]. Buy from a reliable vendor as it has been [http://www.petapixel.com/2011/05/20/one-third-of-the-sandisk-memory-cards-on-earth-are-counterfeit/ claimed] that 1/3 of all "Sandisk" labelled memory cards are counterfeit.

==Keyboard / Mouse / Input Devices==

===R-Pi does not respond to key presses / Keyboard randomly repeats key presses===
This is caused by inadequate power. Use a good power supply and a good power cable. Some cheap cables that work with a cell phone, cannot fully power the R-Pi. Some USB devices require a lot of power: most will have a label showing the voltage and mA requirements. They should be 5v 100mA each max, any more than this they must be used with a powered USB hub. Try unplugging every USB device except the keyboard (you should also note that some keyboards have built in hubs and can try to draw 150mA (Pi can only handle 100mA per USB slot without a hub)).
Also, use the latest software. Forum user MrEngman [http://www.raspberrypi.org/forum/absolute-beginners/using-a-powered-usb-port-to-power-a-rpi#p76485 reported] some keyboard repeats and wireless hangs until [http://www.raspberrypi.org/downloads upgrading] to the debian6-19-04-2012 kernel, which he reports stable with no problems even with a low [[R-Pi_Troubleshooting#Troubleshooting_power_problems | TP1-TP2 voltage]] of 4.65 - 4.68 volts.

===Keyboard / Mouse interferes with USB WiFi device===
Connecting a keyboard and/or mouse while a USB WiFi device is connected, may cause one or both devices to malfunction. On April 30 2012, there was a bugfix<ref>https://github.com/raspberrypi/linux/commit/e09244e60881148431ecd016ccc42f1fa0678556</ref> relating to USB sharing between high-speed (eg. WiFi) and full/low-speed devices (eg. keyboard/mouse). User spennig<ref>http://www.raspberrypi.org/forum/troubleshooting/usb-power-hub-wifi/page-4#p74609</ref><ref>http://www.raspberrypi.org/forum/troubleshooting/success-with-kb-mouse-wifi?value=3761&type=8&include=1&search=1</ref> reports this patch did not fix the Mouse/WiFi conflict. On 2012-05-12, user spennig was pleased to confirm that wifi was working with a USB keyboard and mouse, as long as the Raspberry Pi had a good PSU and a powered hub. Even so, some experimentation was needed, e.g. USB mouse connected to the device, and the keyboard and mouse connected to the powered hub. Some experimentation may be necessary to find a working combination; however a good power supply is essential.

===Wireless Keyboard trouble===
Some wireless keyboards, for example the Microsoft Wireless Keyboard 800 are reported to fail<ref>http://www.raspberrypi.org/forum/troubleshooting/display-and-keyboard-issues-on-a-real-pi#p74816</ref> even though the current drawn by the wireless adaptor is within the R-Pi USB spec limit of 100 mA. This may be a software driver problem.

===Re-mapping the keyboard with Debian Squeeze===
If different letters appear on-screen from that which you typed, you need to reconfigure you keyboard settings. In Debian, from a command line type:
sudo dpkg-reconfigure keyboard-configuration
Follow the prompts. Then restart your RasPi. '''Or:''' From the command line type:
sudo nano /etc/default/keyboard
Then find where it says <blockquote>XKBLAYOUT=”gb”</blockquote>and change the gb to the two letter code for your country. [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=78325#p78325]

===Slow keyboard mapping===
If you have remapped your keyboard and get a very long delay during the keyboard mapping at startup, type the following once on the command line after you have logged in:
sudo setupcon

===No USB device works, with known good PS, SD card, KB===
There has been more than one report<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7533</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p77576</ref><ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5766#p80995</ref> of a R-Pi booting but not getting USB input, using a known-good power supply, SD card, and keyboard. The more common cause for no USB devices working is [[#Troubleshooting_power_problems|low power supply voltage]] from bad PSU, cable, or USB hub, but in this case the problem was no clock signal present at the LAN9512 USB/Ethernet chip "IC3", and the solution was to reflow the solder on the 25 MHz crystal "X1" on the bottom side of the board.
Or return the board for a replacement, but before making this conclusion, confirm known good peripherals. A significant number of
[[RPi_VerifiedPeripherals#USB_Keyboards| USB keyboards]] are not compatible with R-Pi. As of June 1 2012, Eben reported<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=6822&p=89589&hilit=eben#p89513</ref> that only about 1 in 1000 shipped R-Pi boards have been found to have a hardware fault of any kind.

== Updating firmware ==
=== Check your firmware version ===
Using the latest firmware version may help various problems with SD card and display compatibility. Check the kernel version with:
uname -a
Linux RPi 3.1.19 #1 PREEMPT Fri Jun 1 14:16:38 CEST 2012 armv6l GNU/Linux

And the GPU firmware with:
/opt/vc/bin/vcgencmd version
May 31 2012 13:35:03
Copyright (c) 2012 Broadcom
version 317494 (release)

=== Get the latest firmware version ===
The GPU firmware and kernel can be updated with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update tool].

However this requires the Pi to be successfully booted. With sdcard problems, you may not get that far, so can try a manual udpate.
If you have a Linux machine, rpi-update can be run on that in an offline mode, and will update your sdcard from the Linux machine.

Otherwise, on a Windows computer, you will see the "/boot" partition appear as the contents of SD card.
You can download the latest GPU firmware version [https://github.com/raspberrypi/firmware/blob/master/boot/start.elf here].
Click on '''view raw''', then save it, and put the new start.elf file on the sdcard replacing the existing one. Similarly, the latest kernel is [https://github.com/raspberrypi/firmware/tree/master/boot/kernel.img here].
After updating these files you should be able to boot. You still need to run rpi-update to update the kernel modules (in /lib/modules) and the GPU libraries (in /opt/vc).

=== Choosing the right ARM/GPU memory split ===
There is a choice of how the 256M of RAM is divided between the ARM and GPU:
arm224_start.elf : 224M ARM, 32M GPU split : Maximum ARM memory. Good for ARM desktop use. No accelerated video or 3D possible.
arm192_start.elf : 192M ARM, 64M GPU split : Reasonable ARM memory. Simple video (omxplayer) or 3D (quake) is possible. This is the default.
arm128_start.elf : 128M ARM, 128M GPU split : Use this for heavy 3D work, or 3D plus video. Needed for XBMC.

To switch replace start.elf with one of the above files and reboot. E.g.
sudo cp /boot/arm224_start.elf /boot/start.elf && sudo reboot

== SD cards ==

* If you have problems, check you have latest firmware version (described above)
* Some SD cards do not work on the R-Pi, so check the [[RPi_VerifiedPeripherals#SD_cards|list of known SD cards]].
* If you are having problems setting up your SD card you might want to start by erasing it completely - especially if it has been used elsewhere and still contains data / partitions.
** Windows and Mac users can download a formatting tool from the SD Association: https://www.sdcard.org/downloads/formatter_3/
* Reformatting cards is also easy to do in a digital camera.
* After writing the image to the SD card, verify that you can see the boot partition when you insert the SD card into your computer. The partition should contain a number of files, including ''start.elf'' and ''kernel.img''. If you do not see these files on the SD card, you have made an error writing the image file.
* If you are manually preparing your SD card on Linux or Mac OS using the ''dd'' command, this operation will completely erase any existing data and partitions. Make sure you write to the whole card (e.g. <tt>/dev/sdd</tt>) and not to an existing partition (e.g. <tt>/dev/sdd1</tt>).
* If you have an sdcard that doesn't work with latest firmware, head over [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=6093 here].
* If you put the SD card into your PC in an attempt to write the R-Pi operating system onto it, and the PC tells you the card is write-protected, even with the write-protect tab in the correct, forward position, then you may have a faulty SD-card rewriter. There's a common fault with many SD-card rewriters - The write-protect tab is detected by a very thin, narrow metal strip, that is part of a switch. When the card is inserted, the write-protect tab is supposed to push the strip and make/break the contact, as needed. Unfortunately, these strips have a habit of getting stuck, because they are mounted in a thin plastic channel, and only need to be deformed slightly sideways to get jammed.
Luckily, if you have this problem, most built-in card readers are easy to pull apart and repair; some users have even reported succesfully unjamming the switch with a blast of compressed air from a can into the SD-card slot without having to dismantle anything.
You may also be able to temporarily get round the problem by putting the write-protect tab in a half-way position - this pushes on a different part of the strip and may break the contact - it's worth trying a few, slightly different positions. You could also use a USB-SD card adaptor, which are cheap to buy.

==Networking==

===Ethernet connection is lost when a USB device is plugged in===
This is caused by inadequate power. Use a good power supply and a good power cable. Some cheap cables that work with a cell phone, cannot fully power the R-Pi. Some USB devices require a lot of power (>100 mA), so they must be used with a powered USB hub. Some cheap USB hubs suck power from the Raspberry Pi even if a USB power supply is connected.

There is an ongoing issue with the Ethernet connection being lost when mouse and / or keyboard are connected via a powered USB hub. The simplest way to solve this is to connect your mouse and keyboard directly into the 2 USB ports on the R-Pi.

===Ethernet connects at 10M instead of 100M===
The LED in the corner of the board labelled "10M" is mislabeled. When that LED is on, the R-Pi is actually connected at 100 Mbps. You can confirm the true transfer rate using a network benchmark such as iperf. You can also read the current network speed with
cat /sys/class/net/eth0/speed

===Cannot ssh in to Pi===

In the Debian image, ssh is disabled by default. Boot commands are taken from /boot/boot.rc if that file present. There is an example file named '''boot_enable_ssh.rc''' that enables ssh. So:

sudo mv /boot/boot_enable_ssh.rc /boot/boot.rc

and reboot should enable ssh. (password as below)

===Network/USB chip gets too hot to touch===

This is normal. In open air at 24 C, the LAN9512 Ethernet/USB chip reaches about 52 C after some time. This is too hot to touch for more than a few seconds, but it is not unusually hot for the chip.

The
[http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf LAN9512 data sheet] in Table 4.1 on p.40 says it comes in two versions, rated for operation at an ambient temperature in still air (Ta) of 70 C (commercial) or 85 C (industrial). It uses 763 mW at 3.3V with maximum traffic on 100baseT and both USB ports (Table 4.3.4, p. 42).

There is a study of RasPi heat profiles by "Remy" at [http://www.geektopia.es/es/technology/2012/06/22/articulos/se-calienta-el-ordenador-raspberry-pi-estudio-de-sus-temperaturas-en-funcionamiento.html ¿Se calienta el ordenador Raspberry Pi? Estudio de sus temperaturas en funcionamiento] (''Is the Raspberry Pi computer getting hot? A study of its operational temperature.'') The Spanish article has numerous color temperature images of RasPi in various operational modes, with the highest LAN9512 case temperature measured as 64.5 C.

===Networking no longer works when changing SD card between two Raspberry Pis===

In some distributions, /etc/udev/rules.d/70-persistent-net.rules remembers which MAC address is associated with eth0, so each new device will be assigned as a different interface (eth1, eth2, etc.) due to the different MAC addresses. Editing /etc/udev/rules.d/70-persistent-net.rules to remove the invalid rules and rebooting may help fix the problem.

==Passwords==
===I do not know the password to login===
Please check the page [http://www.raspberrypi.org/downloads http://www.raspberrypi.org/downloads] for the correct username and password for each image.

Here are the most common username/password combinations:
*Debian after Feb 2012: pi/raspberry
*Debian 17 Feb 2012: pi/suse
*Arch: root/root

===Some programs refuse to accept my password===
While using Debian, some programs may ask for your password but refuse to accept a valid password.

This is a fault in some Debian images and will be fixed soon. If you are using an image with this fault, enter the following command on the command line.
gconftool-2 --type bool --set /apps/gksu/sudo-mode true
Please enter this command carefully, the spaces are important. The command should be accepted without any response or errors.

===I don't know the root password===

There is no root password set by default on Debian. You are expected to do everything through sudo. You can set one with "sudo passwd root" - just make sure you know what you are doing with a root account.

==Sound==
===Sound does not work with an HDMI monitor===
This is caused by some computer monitors which select DVI mode even if an HDMI cable is connected. This fix may be necessary even if other HDMI devices work perfectly on the same monitor (or TV)!

Edit the configuration file - see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file:
hdmi_drive=2

This will force it to select HDMI mode.

===Sound does not work at all, or in some applications===
In Debian Squeeze, sound is disabled by default because the ALSA sound driver is still "alpha" (not fully tested) on the R-Pi. To try out sound, from the command prompt ''before'' "startx", type

sudo apt-get install alsa-utils
sudo modprobe snd_bcm2835

On Debian Wheezy, snd_bm2835 is enabled, by default, do that step is not necessary. Next try:

sudo aplay /usr/share/sounds/alsa/Front_Center.wav

By default output will be automatic (hdmi if hdmi supports audio, otherwise analogue). You can force it with:

sudo amixer cset numid=3 <n>

where n is 0=auto, 1=headphones, 2=hdmi.

With recent firmware, you can build hello_audio with:
cd /opt/vc/src/hello_pi/
./rebuild.sh
cd hello_audio

With older firmware
cd /opt/vc/src/hello_pi/hello_audio
make

to test analogue output:
./hello_audio.bin
and:
./hello_audio.bin 1
to test HDMI.

Also note that you may have to add your user to the 'audio' group to get permission to access the sound card.

==Display==
===Startx fails to start===
If you just get errors instead of a desktop when typing
startx
you may be out of storage space on the SD card. By default there are only a few hundred MB free in the 2 GB main partition, which can quickly fill up if you download files. Make sure there is some space free (gparted can expand a partition, if the SD card is > 2GB). Also, installing some software may incorrectly create or modify a .Xauthority file in your home directory, causing startx to fail, according to [http://www.raspberrypi.org/forum/troubleshooting/startx-fails-worked-yesterday this thread]. Temporarily renaming, moving, or deleting that file may fix the problem.

===Video does not play or plays very slowly===
The only hardware-accelerated video player is in the [http://www.raspberrypi.org/forum/general-discussion/openelec-meets-raspberry-pi-part-1-xbmc XBMC distribution] and its command line variant [[omxplayer]]. H264 is the only hardware-accelerated codec, for playback. No hardware encoding is supported. Additional codecs were not purchased as licensing fees would have increased the R-Pi's price.

===Can only get 800x480 resolution in LXDE (Arch linux)===
Known issue with distro package as of 17th April 2012 - there's some missing boot config information. Creating a suitable cmdline.txt fixes it - type the following at the Raspberry Pi command line:

<pre>
sudo echo "dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 root=/dev/mmcblk0p2 rootfstype=ext3 rootwait" >/boot/cmdline.txt
</pre>

===Big black borders around small image on HD monitors===

Out of the box, R-Pi graphics don't necessarily fill the whole screen. This is due to something called "Underscan", and it can be fixed easily.

Note: the best solution is to disable overscan in display menu options (it may be called "just scan", "screen fit", "HD size", "full pixel", "unscaled", "dot by dot", "native" or "1:1"), then use the disable_overscan=1 option.

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following lines to the configuration file...

If your display has no overscan:

<pre>

disable_overscan=1

</pre>

or if your display has some overscan:

<pre>

overscan_left=-20

overscan_right=-20

overscan_top=-20

overscan_bottom=-20

</pre>

Making the R-Pi graphics fill the screen is a matter of experimenting with the numbers you put in the config.txt file. Change the numbers – try jumps of 5 or 10 at a time. Bigger negative numbers reduce the black borders (so -40 means less black border than -20). The numbers do not all have to be the same; you can use this feature to centre the display on the screen.

===Writing spills off the screen on HD monitors===

Out of the box, R-Pi graphics may be larger than the 1080p (ie Full HD) screen. This is due to something called "Overscan", and it can be fixed easily by creating a simple text file on the R-Pi SD card by using Notepad on your PC.

Follow the instructions in the section "Big black borders around small image on HD monitors", but use positive numbers for the overscan settings, for example
<pre>

overscan_left=20

overscan_right=20

overscan_top=20

overscan_bottom=20

</pre>

===Interference visible on a HDMI or DVI monitor===
This may be caused by loss of signal on long video cables. The signal level may be increased by changing a configuration parameter.

[[File:RPi_HDMI_interference.jpg|600px]]

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
config_hdmi_boost=4

You may experiment with different values of config_hdmi_boost. Value 1 is used for very short cables, value 7 is used for very long cables.

This option can also help when there is no display output at all, the display periodically blanks, or colours are wrong/inverted.

This symptom can also be caused by RasPi +5V (measured from TP1 to TP2) falling too low. See "Troubleshooting Power Problems".

===No HDMI output at all===
First make sure the display is powered on and switched to the right input before booting Pi.

If you have the [http://www.raspberrypi.org/archives/1435 Wheezy] image (recommended) then try
hdmi_safe=1

Otherwise, try adding the following line to the configuration file (similar to interference case above)
config_hdmi_boost=4

Your monitor/cable may not be asserting the hotplug signal. You can override this with:
hdmi_force_hotplug=1

Also [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=7513 try] the following video options:
hdmi_group=2
hdmi_mode=4
which resolved an issue with DVI monitor reporting "input signal out of range"

As a last resort, try deleting (rename to keep backup) config.txt from the SD card.

Also check that the RasPi +5V voltage (measured from TP1 to TP2) is in the correct range. One user found that his DVI-D monitor blanked out when +5V was too low. See "Troubleshooting Power Problems".

===Composite displays only back and white or no image===
The output display will default to HDMI if a HDMI display is connected, and composite if not. Make sure there isn't a HDMI cable connected when you want to use composite output.

The composite display defaults to NTSC (American) output. Most TVs will show an image with that, but older PAL (European) televisions may display only back and white or no image. To fix this:

Edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

Add the following line to the configuration file
sdtv_mode=2

(You can try other values: 0 is NTSC, 1 is Japanese NTSC, 2 is PAL, 3 is Brazilian PAL)

==GPIO==
Remember that the GPIO pins are 3.3V logic level only, and are NOT 5V tolerant.

If you momentarily shorted the two end GPIO pins together (+3.3V and +5V), or a supply pin to ground, and the Pi appears to be dead, don't panic. The input polyfuse may have tripped. It is self-resetting after it cools down and the polymer re-crystallizes, which can take several hours. Set the Pi aside and try again later.

The GPIO pins connect directly into the core of the ARM processer, and are static-sensitive, so you should avoid touching the pins wherever possible. If you are carrying a static charge, for example by taking off an acrylic pullover, or walking across a nylon carpet, touching the GPIO pins could destroy your R-Pi, so always earth yourself before touching the pins or anything connected to them.

==General==
===The time is incorrect===
If the clock is off by a series of hours, in the command line type:
sudo dpkg-reconfigure tzdata

The R-Pi has no real-time clock, so unless it can access a timeserver over the network at boot, or time is manually entered by the user, the time/date will restart counting from the last logged time in the previous session.

===A part broke off===

The silver cylinder near the microUSB power input is a 220 uF capacitor ("C6" on schematic). It sticks up and due to the small surface-mount pads, it is easy to break off; several people have done so. This is a power supply filter capacitor which reduces any noise and spikes on the input +5V power. If you like, you can solder it back on, or just leave it off. If you do solder it back on, take care to observe the correct polarity with the black stripe towards the board edge. This part, C6 is a "just in case" component which is good design practice to include, but [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&t=4926| as it turns out] most power supplies still work OK without this part installed. This part is also [http://elinux.org/RPi_Hardware#Capacitor_C6 discussed here].

===Unable to install new software===
When trying to install a software package (using the command sudo apt-get install xxxx) you may see the error
Package yyyy is not available
This means that your software list is out of date. Before attempting to install software, you should always make sure that you are using the latest software list by using the command
sudo apt-get update

==Troubleshooting power problems==

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

Use a multimeter which is set to the range 20 volts DC (or 20v =). You should see a voltage between 4.75 and 5.25 volts. Anything outside this range indicates that you have a problem with your power supply or your power cable.

If you have not used a multimeter before, see these [[http://www.sparkfun.com/tutorials/202 basic instructions]]

Note: Even if the multimeter shows the correct voltage, you may have some power supply problems. A multimeter only displays the average voltage. If there are very short-lived dips or spikes in the voltage, these will not be shown by the multimeter. It is best to measure voltage when Pi is busy.

If your voltage is low, it could be:
* The power supply produces too low a voltage
* The power supply cannot supply enough current, which results in a voltage drop. Make sure Power supply is labelled as at least 700mA. (Some cheap power supplies don't deliver what is labelled).
* The USB power cable is low quality. See: [[On_the_RPi_usb_power_cable]]
* Attached USB devices want too much power. The Pi is only designed for up to 100mA USB devices. A USB device wanting more that that will cause a voltage drop.
Note: keyboards with LCD displays, built in USB hubs, backlights, etc are likely to be problematic. Try to use a basic one. Wifi dongles are also unlikely to work when directly connected. Connect high powered USB devices to a powered USB hub.

Try booting without HDMI, ethernet or USB deviced plugged in, and see if the voltage improves.
See also: [[RPi_Hardware#Power_Supply_Problems| Power Supply Problems]]

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following tables try to help you identify your board for better troubleshooting.

Look for the date of manufacturing printed with the year and week. In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

For '''Board ver'''. we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")

Model A:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
|
|
|
|
|
|}

Model B:
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! Front
! Back
|-
| BS12xx
| Samsung
| SMSC
| [[File:RaspberryPi-Board_A-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|200px|thumb|center]]
|-
| BH12xx
| Hynix
| SMSC
| [[File:RaspberryPi-Board_B-Front.JPG|200px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|200px|thumb|center]]
|}

<big>See a '''complete list''' and user feedback here: [[RaspberryPi Boards]]</big>

=References=
<references/>

{{Template:Raspberry Pi}}

[[Category:RaspberryPi]]

RPi Framebuffer

2012-08-06T21:48:16Z

Lxndr: added references, template, category

== Introduction ==
The aim of this page is to provide some documentation on BCM2835's frame buffer, as this is not publicly documented by Broadcom, and is necessary to write a basic OS for the Raspberry Pi.
Most of this was worked out by reading the Linux source code (mostly drivers/video/bcm2708_fb.c and arch/arm/mach-bcm2708/) and experimentation. Note: At times I have used a different naming convention to that used by Broadcom's kernel source, partially because I used slightly different semantics where the kernel source is either unclear or seemed confusing.
A working (more or less) example code for the frame buffer can be found [http://people.pwf.cam.ac.uk/nst25/rpi/2012062301.tar.gz here] (note: this page includes corrections to the large comment in fb.c).

== Basic procedure to get stuff on screen ==
The basic procedure to get a frame buffer is:
# Set up a structure with the frame buffer specification (resolution, etc)
# Tell the GPU about this structure by writing to the mailbox
# Wait by reading from the mailbox for the GPU to modify this structure
# Write to the frame buffer at the pointer we got in stage 3

=== Notes ===
* Only step 4 is required for subsequent writes to the frame buffer.
* Currently, I do not know how to enable the HDMI output, so this will always operate the composite, and not the HDMI (there have been suggestions that this might be achieved using a combination of config.txt, parameters specified by the GPU, and appropriate resolution settings).
* The two conditions for successfully acquiring a frame buffer are:
** The 28 bits of data read from the mailbox is zero
** The pointer in the structure is non-zero after the mailbox read
* For some reason (that I haven't discovered yet), the code sometimes fails (not meeting one of the two criteria above) unless it is retried. Hence steps 1-3 of the basic procedure are tried in a loop until success.
* Once we have the frame buffer, we can just write to it. The pixels (in 24 bit mode) are RGB ordered by y then x coordinate. The address of a subpixel is given by: y * pitch + x * 3 + rgb_channel, where rgb_channel is 0 for red, 1 for green, and 2 for blue.

== Memory mapped registers ==
The bus address for the mailbox memory mapped registers is 0x7E00B880.
This corresponds to an ARM physical address of 0x2000B880 (the address we use from the ARM processor, and hence here). We use three registers from the mail box:
* MAIL0_READ
* MAIL0_WRITE
* MAIL0_STATUS

=== Partial Memory Map at Address 0x7E00B880 ===
{| border="1"
|'''Offset Address'''
|'''Name''' ''(as used on this page)''
|'''Description'''
|-
|0x00
|MAIL0_READ
|The read register for mailbox 0 at offset (the Linux source mentions something of "and the next 4 words", but I've found it sufficient to read only from this address)
|-
|0x10
|MAIL0_PEAK
|Read from the mailbox without removing data from it.
|-
|0x14
|MAIL0_SENDER
|Sender ID (bottom 2 bits only)
|-
|0x18
|MAIL0_STATUS
|The status register for mailbox 0
|-
|0x1C
|MAIL0_CONFIG
|The configuration register for mailbox 0
|-
|0x20
|MAIL0_WRITE
|The write register for mailbox 0 (this is actually the read register for mailbox 1).
|}

=== Format of MAIL0_READ ===
{| border="1"
|'''Bits'''
|'''Name''' ''(as used on this page)''
|'''Description'''
|-
|0-3
|channel
|The mailbox channel number from which the data originated
|-
|4-31
|data
|The 28 bits of data sent to the CPU
|}

=== Format of the MAIL0_STATUS ===
{| border="1"
|'''Bits'''
|'''Name''' ''(as used on this page)''
|'''Description'''
|-
|0-29
|N/A
|Not documented here. Unused?
|-
|30
|MAIL_FULL
|Set if the mailbox is empty, and thus no more data is available to be read from it.
|-
|31
|MAIL_EMPTY
|Set if the mailbox is full, and thus no more data can be written to it.
|}

=== Format of the MAIL0_WRITE ===
{| border="1"
|'''Bits'''
|'''Name''' ''(as used on this page)''
|'''Description'''
|-
|0-3
|channel
|The mailbox channel number to which the data is to be sent
|-
|4-31
|data
|The 28 bits of data to be sent to the destination
|}

== Mailbox operations ==
Read/write operatitons on the mailbox consist of transfering data via a
32 bit register. 28 bits of this 32 bit register are the data to be sent
to the receiver, while the lower 4 bits specify the channel (channel 1 is
the frame buffer, but there are others).

=== Procedure to Send Via the Mailbox ===
# Wait for space in the mailbox
## Execute a memory barrier
## Read MAIL0_STATUS
## Goto step 1 if MAIL_FULL bit is set
# Write channel and data to MAIL0_WRITE
# Execute a memory barrier

=== Procedure to Receive Via the Mailbox ===
# Wait for the mailbox to be non-empty
## Execute a memory barrier
## Read MAIL0_STATUS
## Goto step 1 if MAIL_EMPTY bit is set
# Execute a memory barrier
# Read from MAIL0_READ
# Check the channel (lowest 4 bits) of the read value for the correct channel
# If the channel is not the one we wish to read from (i.e: 1), go to step 1
# Return the data (i.e: the read value >> 4)

=== Mailbox Channels ===
{| border="1"
|'''Channel Number'''
|'''Description'''
|-
|0
|Power management interface
|-
|1
|Framebuffer
|-
|2
|Virtual UART
|-
|3
|VCHIQ interface
|-
|4
|LEDs interface
|-
|5
|Buttons interface
|-
|6
|Touch screen interface
|}

=== Notes ===
* The read procedure will not work if we're interested in reading from more than one channel as it does not handle the reception of other channels' data
* The address of the frame buffer structure must be at least a multiple of 16 (in order to be accurately transmitted in the 28 bits available in the mailbox). I used (1 << 22) as the address of this structure.

== Format of GPU Framebuffer Structure ==
The structure expected by the GPU for initializing the frame buffer is as follows:
{| border="1"
|'''Bytes'''
|'''Name''' ''(as used on this page)''
|'''Description'''
|-
|0-3
|width
|Width of the requested frame buffer. My code uses a value of 640 here.
|-
|4-7
|height
|Height of the requested frame buffer. My code uses a value of 480 here.
|-
|8-11
|virtual_width
|Virtual Width -- easiest thing to do is to set this to width. I'm not entirely certain what this does (perhaps rescales?).
|-
|12-15
|virtual_height
|Virtual Height -- easiest thing to do is to set this to height. I'm not entirely certain what this does (perhaps rescales?).
|-
|16-19
|pitch
|Number of bytes between each row of the frame buffer. This is set by the GPU; in my code, I set it to zero before passing the structure to the GPU.
|-
|20-23
|depth
|The number of bits per pixel of the requested frame buffer. I have not managed to make this work with anything other than a value of 24, however the Linux source seems to use 16 bit?!
|-
|24-27
|x_offset
|Offset in the x direction. The easiest thing to do is to set this to zero. I'm not entirely certain exactly what this does.
|-
|28-31
|y_offset
|Offset in the y direction. The easiest thing to do is to set this to zero. I'm not entirely certain exactly what this does.
|-
|32-35
|pointer
|The pointer to the frame buffer into which your code should write. This is set by the GPU. I set this to zero before passing the structure to the GPU.
|-
|36-39
|size
|The size of the frame buffer. Set by the GPU. I set this to zero before passing the structure to the GPU.
|}
Each of the 32-bit values should be little endian (i.e: that of the included ARM processor). Hence a simple C struct with a data type of uint32_t for each of these fields will suffice.

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPiconfig

2012-08-06T21:47:17Z

Lxndr: changed notes to references

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

And here is another example file, containing extended documentation of features: [http://elinux.org/images/c/ca/Raspi_documented_config.txt link].

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''sdtv_disable_colourburst''' disables colour burst on composite output. The picture will be monochrome, but possibly sharper
sdtv_disable_colourburst=1 colour burst is disabled

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility.
hdmi_safe=1 (this does: hdmi_force_hotplug=1, config_hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0)

'''hdmi_ignore_edid''' Enables the ignoring of EDID/display data if your display is a crappy Chinese one
hdmi_ignore_edid=0xa5000080

'''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
hdmi_force_edid_audio=1

'''hdmi_ignore_cec''' Pretends CEC is not supported by TV. Avoids bringing (CEC enabled) TV out of standby and channel switch when rebooting.
hdmi_ignore_cec=1

'''hdmi_force_hotplug''' Pretends HDMI hotplug signal is asserted so it appears a HDMI display is attached
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_ignore_hotplug''' Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type

Not specifying the group, or setting to 0 will use the preferred group reported by the edid.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''
*Enter the following commands to dump more detailed information from your monitor
'''/opt/vc/bin/tvservice -d edid.dat'''
'''/opt/vc/bin/edidparser edid.dat'''
The edid.dat should also be provided when troubleshooting problems with the default HDMI mode

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''ramfsaddr''' address to load ramfs file at

'''initramfs''' (string address) ramfs file and adress to load it at (it's like ramfsfile+ramfsaddr in one option). NOTE: this option uses different syntax than all other options - you should not use "=" character here. Example:
initramfs initramf.gz 0x00800000

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

'''avoid_safe_mode''' If set to one, [[RPI_safe_mode|safe_mode]] boot won't be enabled.

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. It have an impact on ARM performance since it drives L2 cache. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

== Clocks relationship ==

ARM, SDRAM and GPU each have their own PLLs and can have unrelated frequencies<ref name=freq_relationship>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=125#p126308</ref>.
The GPU core, h264, v3d and isp share a PLL, so need to have related frequencies. PLL will be set to:
pll_freq = core_freq * 2^n, for smallest n satisfying pll_freq > 600MHz.

GPU core, h264, v3d and isp should all be integer divisors of pll_freq.
So core_freq=480 sets pll_freq=960. That would allow a v3d_freq/h264_freq/v3d_freq of 320 with an integer divider of 3.

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|750 ||255 || || || || ||450 || ||
|-
|900 ||250 || || || || ||500 || ||
|-
|900 ||275 || || || || ||500 || ||
|-
|900 || ||450 || || || ||450 || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||450 ||6 ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Configuration

2012-08-06T21:46:49Z

Lxndr: changed notes to references

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

And here is another example file, containing extended documentation of features: [http://elinux.org/images/c/ca/Raspi_documented_config.txt link].

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''sdtv_disable_colourburst''' disables colour burst on composite output. The picture will be monochrome, but possibly sharper
sdtv_disable_colourburst=1 colour burst is disabled

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility.
hdmi_safe=1 (this does: hdmi_force_hotplug=1, config_hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0)

'''hdmi_ignore_edid''' Enables the ignoring of EDID/display data if your display is a crappy Chinese one
hdmi_ignore_edid=0xa5000080

'''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
hdmi_force_edid_audio=1

'''hdmi_ignore_cec''' Pretends CEC is not supported by TV. Avoids bringing (CEC enabled) TV out of standby and channel switch when rebooting.
hdmi_ignore_cec=1

'''hdmi_force_hotplug''' Pretends HDMI hotplug signal is asserted so it appears a HDMI display is attached
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_ignore_hotplug''' Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type

Not specifying the group, or setting to 0 will use the preferred group reported by the edid.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''
*Enter the following commands to dump more detailed information from your monitor
'''/opt/vc/bin/tvservice -d edid.dat'''
'''/opt/vc/bin/edidparser edid.dat'''
The edid.dat should also be provided when troubleshooting problems with the default HDMI mode

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''ramfsaddr''' address to load ramfs file at

'''initramfs''' (string address) ramfs file and adress to load it at (it's like ramfsfile+ramfsaddr in one option). NOTE: this option uses different syntax than all other options - you should not use "=" character here. Example:
initramfs initramf.gz 0x00800000

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

'''avoid_safe_mode''' If set to one, [[RPI_safe_mode|safe_mode]] boot won't be enabled.

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Overclocking

2012-08-06T21:46:16Z

Lxndr: /* Notes */ changed to references

=Overclocking configuration=
'''WARNING:''' Setting any (of the below) parameters which could potentially over-volt your Raspberry Pi, will set a ''permanent bit'' within the SOC, voiding your warranty. So if you care about the warranty on your Raspberry Pi do NOT adjust any voltages!

Also at your own risk, you can try the display [[RPi_config_for_your_TV|overscan settings]] from our wiki. These overscan-settings were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum, but are not confimed to work...

==Overclocking options==

These settings are also documented in one of the example configuration files mentioned on [[RPi_config.txt|the config page]].

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. It have an impact on ARM performance since it drives L2 cache. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

== Clocks relationship ==

ARM, SDRAM and GPU each have their own PLLs and can have unrelated frequencies<ref name=freq_relationship>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=125#p126308</ref>.
The GPU core, h264, v3d and isp share a PLL, so need to have related frequencies. PLL will be set to:
pll_freq = core_freq * 2^n, for smallest n satisfying pll_freq > 600MHz.

GPU core, h264, v3d and isp should all be integer divisors of pll_freq.
So core_freq=480 sets pll_freq=960. That would allow a v3d_freq/h264_freq/v3d_freq of 320 with an integer divider of 3.

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|750 ||255 || || || || ||450 || ||
|-
|900 ||250 || || || || ||500 || ||
|-
|900 ||275 || || || || ||500 || ||
|-
|900 || ||450 || || || ||450 || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||450 ||6 ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|}

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Wiki Best Practice

2012-08-06T21:45:55Z

Lxndr: /* Keep basic structure */ amended to 'end of page'

[[Category:RaspberryPi]]

=This is not your private wiki=

Respect the rules and prepare for a possible wiki migration !

=Get involved =

Need help ? Look here: [[Help:Contents]].
 
AND: ''' DICUSS ''' - Use the discussion pages ! 
TIP: If you leave a message on the page, use this signature : <nowiki> ~~~~ </nowiki>.
After saving , it will look like this : [[User:Ghans|Ghans]] 16:47, 18 March 2012 (UTC)

=Keep basic structure=
'''Please reapply the category RaspberryPi to existing articles !'''
* prefix article name with RPi (RPi_Name)
* add <nowiki> [[Category:RaspberryPi]] </nowiki> to each of your articles and uploads
* put this at the end of your page :
<nowiki>
=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]
</nowiki>

=Make it safe=
Make it clear to which audience the current page is aimed at , as seen here [[RPi Advanced Setup]]

Keep the beginners in mind.
The news of CE marking shows that a load of boards will get into the hans of ''' end-users ''' .
There is no way to influence this , therefore , ADAPT.

* Do not expect torough knowledge of the subject.
* Simple language
* Clear intructions
* Clean and understandable structure - much room for improvement there.

=Think of others=

Goes hand in hand with Tip # 3. DO NOT BREAK LINKS. See [[Help:Moving_a_page]] and [[Help:Deleting_a_page]].
When the wiki gets more and more imortant over the time , we should avoid breaking old (and older) links.
If you are unsure wheter your goal cannot achieved otherwise (logical link loop) , discuss with others first.

=Use templates=

'''Use the templates - this is not a recommendation !'''

[[RPi_List_of_Templates]]

Do not arbitarily extend and change them. They are specificially made for a better (BASIC) overview.
Use Categories instead (Tip #2).

=Keep it modular=

If you see big lists and code listing cropping up , create a new article for them .

Bad Example : [[RPi Buying Guide]] had all the information now moved to [[RPi Buying Links By Country]] within a single page.

Please use the preview and see what monster you have created.

=References=
<references/>

Talk:RPi Wiki Best Practice

2012-08-06T21:44:16Z

Lxndr: /* Keep Basic Structure >> Rename R-Pi to RPi */ new section

Obviously , this needs your input.

== references query ==

Is the example in this page of how to include a references section broken. It seems to do nothing when I add it to [[Wheezy_raspi-config]]. Unfortunately I cannot find anything in the wiki help pages about references. [[User:KenT|KenT]] 10:33, 11 July 2012 (UTC)

== Official elinux.org guidelines discussion ==
Just found this a minute ago : [[Volunteer_editor_tasks]] [[User:Ghans|Ghans]]

==This is not your private wiki ==

For a general overview about eLinux.org , read this first: [[Help:About]] 
ADMINS ?? So far i managed to come up with this : http://elinux.org/Special:ListUsers/sysop 

[[User:Wmat]] seems to be the site founder. 
More background info here : [[Embedded_Wiki_Task_Force_Conference_Call]] .

What do next ?? [[User:Ghans|Ghans]] 14:36, 4 April 2012 (UTC)

:Hi - my name is [[User:TimBird|Tim Bird]], and I'm one of the founders of the elinux wiki. The administrator for the site is [[User:wmat|Bill Traynor]]. This wiki originated with the merger of two separate wikis - one devoted to hardware and run by Tim Riker, and the other devoted to embedded use of the Linux kernel, run by me. It is sponsored by the Consumer Electronics working group of the Linux Foundation, and hosted at the Oregon State University Open Source Lab (OSUOSL), which hosts many open source projects and resources. I am very happy to host Raspberry Pi pages on this site. The RPi material, covering hardware, software, community and learning resources is exactly what this site exists for. Please don't hesitate to contact me if you have any questions. Also, please use one of the [[ELinuxWiki:Mailing List|Mailing list]]s for general discussion of policies, administration, etc. Thanks [[User:Tim Bird|Tim Bird]] 17:15, 12 April 2012 (UTC)
 
: Wow - thank you very much for the info. This wiki is a great tool for the RPi community. Thank you for giving us space ! I'll let this stay for some days , then move this to the discussion page. And i will subscribe to the mailing list - shouldn't have neglected that. [[User:Ghans|Ghans]] 17:02, 15 April 2012 (UTC)

== Keep Basic Structure >> Rename R-Pi to RPi ==

I feel we should start a renaming effort (by means of 'move page'?) to 'rename' all "R-Pi_Blablabla" pages to "RPi_Blablabla"

RPi Hub

2012-08-06T21:39:38Z

Lxndr: /* R-Pi Model B 3D CAD files */

{{TOC right}}{{Template:Hub_Flags}} 
{{Clear}}
'''The Raspberry Pi wiki pages on this site are a community work - the Raspberry Pi Foundation is not responsible for content on these pages.'''

==Now shipping to customers==
Premier Farnell and RS Components have started shipping to customers. Congratulations to those at the front of the queue!.

Work is ongoing to clear the backlog of orders, with both distributors now manufacturing them in serial production. Farnell/Element14 have stated that all people worldwide who ordered their Raspberry Pi through them on or before April 18th should receive theirs by the end of June.

Update: In the US, on 2012 July 24, Newark/Element 14 is quoting five '''weeks''' and Allied is still quoting 12 weeks. An order placed by Rick Seiden on July 19, 2012 at Newark/Element 14 shipped July 31, 2012, indicating a less than five week wait time.

See the [[RPi Buying Guide | Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]

==About==
[[File:RpiFront.jpg|300px|thumb|right|The Rpi beta board (model B)]]

The Raspberry Pi (short: RPi or RasPi) is an ultra-low-cost credit-card sized Linux computer which was conceived with the primary goal of teaching computer programming to children. It was developed by the [http://www.raspberrypi.org Raspberry Pi Foundation], which is a UK registered charity (Registration Number 1129409). The foundation exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. The device is expected to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).

Raspberry Pi is manufactured and sold in partnership with the worldwide industrial distributors [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components].

* You can get the latest news from the [http://www.raspberrypi.org Foundation Home Page], the [http://twitter.com/intent/user?screen_name=Raspberry_Pi Twitter Feed] or in the [http://www.raspberrypi.org/forum/general-discussion/news-articles-and-blog-posts-about-raspberry-pi forums].
* For Raspberry Pi frequently asked questions see the [[R-Pi FAQ]] or the [http://www.raspberrypi.org/?page_id=8 Raspberry Pi Foundation's FAQ] page.
* Both manufacturing partners provide community areas for more technically focused discussions, articles, FAQs and related information:
:* Premier Farnell: [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group]
:* RS-Components: [http://www.designspark.com/theme/raspberrypi DesignSpark - Raspberry Pi]
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant<ref>http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet</ref>. In common with all Electronic and Electrical products the Raspberry Pi should not be disposed of in household waste. Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.
* Price: 25USD Model A, 35USD for Model B, excluding taxes, postage and packaging. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].

===History===
* Confused about seeing different versions of the board? Visit the [[Rpi HardwareHistory | History of the Raspberry Pi Hardware]] for information about the past versions.

* RegHardware's very detailed analysis is [http://www.reghardware.com/2011/11/28/raspberry_pi/ well worth a read]. Wikipedia also has [http://en.wikipedia.org/wiki/Raspberry_Pi an entry].

* Russell Davis (aka forum admin ukscone) has a series of blog articles recording his perspective of the [http://russelldavis.org/2012/01/14/the-raspberry-pi-part-one/ Raspberry Pi story] in several parts from the beginning.

* You will often hear mention of the BBC Micro Computer when people talk about the purpose of the Raspberry Pi Foundation. See this article on the [http://www.reghardware.com/2011/11/30/bbc_micro_model_b_30th_anniversary/ history of the BBC Micro Computer].

* Here's a video from the Financial Times, with three different groups evaluating the raspberry pi: http://video.ft.com/v/1498254373001/Taste-testing-the-Raspberry-Pi (March 2012)

==Getting Started==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa;" |
===[[Buying RPi |Buying Guide]]===
----
Where can I get one and for how much?
* Raspberry Pi can only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.

* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop].

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

===[[RPi Hardware Basic Setup | Basic Setup]]===
----
First little Raspberry Pi Steps...
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]
* Note: On the Debian OS after you log in you need to type startx at the prompt to get a graphic desktop.

* '''Having problems? Try the [http://elinux.org/R-Pi_Troubleshooting Troubleshooting] page.'''

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

===[[RPi Beginners | Beginners Guide]]===
----
You've just got your new Raspberry Pi device - what now?
* [[RPi Beginners | Beginners Guide]]

* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.

* Get started with some basic projects and tutorials:
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials] 
[http://www.youtube.com/user/RaspberryPiBeginners Another set of video tutorials]

[[RPi Tutorial Easy GPIO Hardware & Software | Easy GPIO Hardware & Software]] - in-progress at the moment
Example projects/tuts which can be linked from here
(or from within a beginners guide page perhaps):
Setup XBMC media centre
Programming tutorials (Liams YouTube etc)
Easy GPIO (when complete or similar thing).
Also links to some basic linux user guides.

* Take a look through the [[R-Pi_Hub#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.

|}

==Resources==
{| border="1" style="background:transparent;"

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Hardware|Hardware]] & [[RPi VerifiedPeripherals|Peripherals]]===
----

*The Model B is more advanced than the Model A - see [[RPi Hardware]].
*The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].
*The unit will support a range of [[RPi VerifiedPeripherals |devices, peripherals and accessories]].
*The [[Rpi Low-level peripherals| Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.
*For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].
*[[RPi Peripherals|Setting up peripherals - examples/HowTos]]
*[[RaspberryPi Boards|List of boards and user feedback]]
*[[RPi 5V PSU construction|Power Supply construction - HowTo]]
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[Rpi_Software|Software]] & [[RPi_Distributions|OS Distributions]]===
----
The Raspberry Pi will run a range of OS Distributions and run a variety of software.
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/Puppi Puppi] from Puppy Linux.
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]] or [[RPi_Performance|test the Pi's performance]].
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.
*Information about installing specific [[RPi_applications|applications]] is available through the link.
*Extensive (boot) configuration info (config.txt) is available [[RPi_config.txt|here]].

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Documentation|Documentation]]===
----
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].

[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]

Example documents which can be linked from here (or sub page):
Official Datasheets
White Papers
User Manuals
Recommended books (perhaps)

=== RPi Troubleshooting ===

Head over to the [[R-Pi Troubleshooting|troubleshooting page]] for help fixing common problems.

=== RPi Bugs ===

Head over to the [[RPi_Bugs|bugs page]] for a list of known bugs.

=== RPi Model B 3D CAD files ===
Theses are various 3D CAD Versions in both RAR and ZIP.

* CATIA V5 RAR http://sdrv.ms/JqdhMb
* CATIA V5 ZIP http://sdrv.ms/LjyLGD
* ProE RAR http://sdrv.ms/KCv1hZ
* ProE ZIP http://sdrv.ms/KCvhxq
* STEP RAR http://sdrv.ms/KCvv7T
* STEP ZIP http://sdrv.ms/JMhv18
* SketchUp http://scc.jezmckean.com/item/581
|}

==Community==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Projects |Projects]], [[RPi Guides |Guides]] & [[RPi Tutorials |Tutorials]]===
----
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].
*Knowledgeable users may want to review and help out with the [[RPi Tasks |Tasks page]].
*Get started by following some of the many [[RPi Tutorials | Tutorials]].
*Common tasks and useful tips are available through the [[RPi Guides | Guides page]].
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[Rpi Education|Schools, Universities, Clubs & Groups]]===
----
*The Raspberry Pi Foundation's aims include encouraging education. Several groups including [http://www.computingatschool.org.uk/ Computing At School] aim to bring Computing Science back into schools.
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |
===[[RPi Community |Supporting Communities]]===
----
The [[RPi Community |Raspberry Pi Community]] is steadily growing:
*[http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]

*[http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group], community site of Premier Farnell

*[http://www.designspark.com/theme/raspberrypi DesignSpark], community site of RS-Components

*[http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]

*[http://www.raspberrymod.com/ Raspberrymod] and [http://www.raspberrypiforums.com/forum RPiforums] Un-Official Raspberry Pi Discussion Boards

*[http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]

*[http://www.worldofpi.com/ World Of Pi] A forum based on all things Raspberry Pi.

*[[RPi Community Magazine]] - User contributed eMagazine, get involved!

*[[RaspberryPi Osdev]] - Hardware specific OS-development community, sitting in freenode.net#raspberrypi-osdev.

|}

==About the RPi Wiki==

'''Do not be afraid to add your bit, content is vital for the wiki to function.'''

[[File:Rasp_turn_around.gif|200px|thumb|right|A 3D rendering of the Raspberry Pi logo by forum user Antario. [http://www.raspberrypi.org/forum/projects-and-collaboration-general/raspberry-pi-3d-logo-animation Source]]]
This wiki is '''open''' for the community. You are encouraged to sign up and add your own projects, guides and correct anything within it. It is important that users like you continue to add to and grow this wiki, that way others will be able to come and do the same making the wiki a valuable resource. See [[Help:Editing | Help Editing The Wiki]] and the [[Special:Upload | Upload File]] link (on the left sidebar) to reference images.
Have a look at our [[RPi Wiki Best Practice|Guidelines]] and then you are free to go !

=== Translations ===

The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:

* English: [[R-Pi Hub]]
* French: [[FR:R-Pi Hub]]
* German: [[DE:R-Pi Hub]]
* Greek: [[EL:R-Pi Hub]]
* Hungarian: [[HU:R-Pi Hub]]
* Japanese: [[JP:R-Pi_Hub]]
* Polish: [[PL:R-Pi_Hub]]
* Portugese: [[pt-BR:Raspberry Pi Board]]
* Romanian: [[RO:R-Pi_Hub]]
* Russian: [[RU:RaspberryPiBoard]]
* Українська: [[UA:R-Pi Hub]]
* Spanish: [[ES:R-Pi Hub]]
* Italiano: [[IT:R-Pi Hub]]
* Chinese:[[CH:R-Pi Hub]]
* Hebrew:[[HE:R-Pi Hub]]
* 한국어:[[KR:R-Pi Hub]]

Any help translating would be greatly appreciated. Thank you to those who have already contributed!

===Admins/Contributors===

Please see the [[Talk:R-Pi_Hub|Talk]] page for outstanding issues and discussions regarding the RPi Hub and related pages. 
Also , have look at [[RPi Wiki Best Practice]]. You can discuss the recommendations
[[Talk:RPi Wiki Best Practice | here ]] .

To share your thoughts, comments, thanks and interesting articles, see our [[RPi Visitor Book |Visitor Book]].

''Big thanks to elinux.org and their groups for the wiki space and content from which these pages have been grown.''

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Hub

2012-08-06T21:39:29Z

Lxndr: /* R-Pi Bugs */

{{TOC right}}{{Template:Hub_Flags}} 
{{Clear}}
'''The Raspberry Pi wiki pages on this site are a community work - the Raspberry Pi Foundation is not responsible for content on these pages.'''

==Now shipping to customers==
Premier Farnell and RS Components have started shipping to customers. Congratulations to those at the front of the queue!.

Work is ongoing to clear the backlog of orders, with both distributors now manufacturing them in serial production. Farnell/Element14 have stated that all people worldwide who ordered their Raspberry Pi through them on or before April 18th should receive theirs by the end of June.

Update: In the US, on 2012 July 24, Newark/Element 14 is quoting five '''weeks''' and Allied is still quoting 12 weeks. An order placed by Rick Seiden on July 19, 2012 at Newark/Element 14 shipped July 31, 2012, indicating a less than five week wait time.

See the [[RPi Buying Guide | Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]

==About==
[[File:RpiFront.jpg|300px|thumb|right|The Rpi beta board (model B)]]

The Raspberry Pi (short: RPi or RasPi) is an ultra-low-cost credit-card sized Linux computer which was conceived with the primary goal of teaching computer programming to children. It was developed by the [http://www.raspberrypi.org Raspberry Pi Foundation], which is a UK registered charity (Registration Number 1129409). The foundation exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. The device is expected to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).

Raspberry Pi is manufactured and sold in partnership with the worldwide industrial distributors [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components].

* You can get the latest news from the [http://www.raspberrypi.org Foundation Home Page], the [http://twitter.com/intent/user?screen_name=Raspberry_Pi Twitter Feed] or in the [http://www.raspberrypi.org/forum/general-discussion/news-articles-and-blog-posts-about-raspberry-pi forums].
* For Raspberry Pi frequently asked questions see the [[R-Pi FAQ]] or the [http://www.raspberrypi.org/?page_id=8 Raspberry Pi Foundation's FAQ] page.
* Both manufacturing partners provide community areas for more technically focused discussions, articles, FAQs and related information:
:* Premier Farnell: [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group]
:* RS-Components: [http://www.designspark.com/theme/raspberrypi DesignSpark - Raspberry Pi]
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant<ref>http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet</ref>. In common with all Electronic and Electrical products the Raspberry Pi should not be disposed of in household waste. Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.
* Price: 25USD Model A, 35USD for Model B, excluding taxes, postage and packaging. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].

===History===
* Confused about seeing different versions of the board? Visit the [[Rpi HardwareHistory | History of the Raspberry Pi Hardware]] for information about the past versions.

* RegHardware's very detailed analysis is [http://www.reghardware.com/2011/11/28/raspberry_pi/ well worth a read]. Wikipedia also has [http://en.wikipedia.org/wiki/Raspberry_Pi an entry].

* Russell Davis (aka forum admin ukscone) has a series of blog articles recording his perspective of the [http://russelldavis.org/2012/01/14/the-raspberry-pi-part-one/ Raspberry Pi story] in several parts from the beginning.

* You will often hear mention of the BBC Micro Computer when people talk about the purpose of the Raspberry Pi Foundation. See this article on the [http://www.reghardware.com/2011/11/30/bbc_micro_model_b_30th_anniversary/ history of the BBC Micro Computer].

* Here's a video from the Financial Times, with three different groups evaluating the raspberry pi: http://video.ft.com/v/1498254373001/Taste-testing-the-Raspberry-Pi (March 2012)

==Getting Started==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa;" |
===[[Buying RPi |Buying Guide]]===
----
Where can I get one and for how much?
* Raspberry Pi can only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.

* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop].

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

===[[RPi Hardware Basic Setup | Basic Setup]]===
----
First little Raspberry Pi Steps...
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]
* Note: On the Debian OS after you log in you need to type startx at the prompt to get a graphic desktop.

* '''Having problems? Try the [http://elinux.org/R-Pi_Troubleshooting Troubleshooting] page.'''

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

===[[RPi Beginners | Beginners Guide]]===
----
You've just got your new Raspberry Pi device - what now?
* [[RPi Beginners | Beginners Guide]]

* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.

* Get started with some basic projects and tutorials:
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials] 
[http://www.youtube.com/user/RaspberryPiBeginners Another set of video tutorials]

[[RPi Tutorial Easy GPIO Hardware & Software | Easy GPIO Hardware & Software]] - in-progress at the moment
Example projects/tuts which can be linked from here
(or from within a beginners guide page perhaps):
Setup XBMC media centre
Programming tutorials (Liams YouTube etc)
Easy GPIO (when complete or similar thing).
Also links to some basic linux user guides.

* Take a look through the [[R-Pi_Hub#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.

|}

==Resources==
{| border="1" style="background:transparent;"

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Hardware|Hardware]] & [[RPi VerifiedPeripherals|Peripherals]]===
----

*The Model B is more advanced than the Model A - see [[RPi Hardware]].
*The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].
*The unit will support a range of [[RPi VerifiedPeripherals |devices, peripherals and accessories]].
*The [[Rpi Low-level peripherals| Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.
*For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].
*[[RPi Peripherals|Setting up peripherals - examples/HowTos]]
*[[RaspberryPi Boards|List of boards and user feedback]]
*[[RPi 5V PSU construction|Power Supply construction - HowTo]]
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[Rpi_Software|Software]] & [[RPi_Distributions|OS Distributions]]===
----
The Raspberry Pi will run a range of OS Distributions and run a variety of software.
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/Puppi Puppi] from Puppy Linux.
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]] or [[RPi_Performance|test the Pi's performance]].
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.
*Information about installing specific [[RPi_applications|applications]] is available through the link.
*Extensive (boot) configuration info (config.txt) is available [[RPi_config.txt|here]].

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Documentation|Documentation]]===
----
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].

[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]

Example documents which can be linked from here (or sub page):
Official Datasheets
White Papers
User Manuals
Recommended books (perhaps)

=== RPi Troubleshooting ===

Head over to the [[R-Pi Troubleshooting|troubleshooting page]] for help fixing common problems.

=== RPi Bugs ===

Head over to the [[RPi_Bugs|bugs page]] for a list of known bugs.

=== R-Pi Model B 3D CAD files ===
Theses are various 3D CAD Versions in both RAR and ZIP.

* CATIA V5 RAR http://sdrv.ms/JqdhMb
* CATIA V5 ZIP http://sdrv.ms/LjyLGD
* ProE RAR http://sdrv.ms/KCv1hZ
* ProE ZIP http://sdrv.ms/KCvhxq
* STEP RAR http://sdrv.ms/KCvv7T
* STEP ZIP http://sdrv.ms/JMhv18
* SketchUp http://scc.jezmckean.com/item/581
|}

==Community==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Projects |Projects]], [[RPi Guides |Guides]] & [[RPi Tutorials |Tutorials]]===
----
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].
*Knowledgeable users may want to review and help out with the [[RPi Tasks |Tasks page]].
*Get started by following some of the many [[RPi Tutorials | Tutorials]].
*Common tasks and useful tips are available through the [[RPi Guides | Guides page]].
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[Rpi Education|Schools, Universities, Clubs & Groups]]===
----
*The Raspberry Pi Foundation's aims include encouraging education. Several groups including [http://www.computingatschool.org.uk/ Computing At School] aim to bring Computing Science back into schools.
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |
===[[RPi Community |Supporting Communities]]===
----
The [[RPi Community |Raspberry Pi Community]] is steadily growing:
*[http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]

*[http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group], community site of Premier Farnell

*[http://www.designspark.com/theme/raspberrypi DesignSpark], community site of RS-Components

*[http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]

*[http://www.raspberrymod.com/ Raspberrymod] and [http://www.raspberrypiforums.com/forum RPiforums] Un-Official Raspberry Pi Discussion Boards

*[http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]

*[http://www.worldofpi.com/ World Of Pi] A forum based on all things Raspberry Pi.

*[[RPi Community Magazine]] - User contributed eMagazine, get involved!

*[[RaspberryPi Osdev]] - Hardware specific OS-development community, sitting in freenode.net#raspberrypi-osdev.

|}

==About the RPi Wiki==

'''Do not be afraid to add your bit, content is vital for the wiki to function.'''

[[File:Rasp_turn_around.gif|200px|thumb|right|A 3D rendering of the Raspberry Pi logo by forum user Antario. [http://www.raspberrypi.org/forum/projects-and-collaboration-general/raspberry-pi-3d-logo-animation Source]]]
This wiki is '''open''' for the community. You are encouraged to sign up and add your own projects, guides and correct anything within it. It is important that users like you continue to add to and grow this wiki, that way others will be able to come and do the same making the wiki a valuable resource. See [[Help:Editing | Help Editing The Wiki]] and the [[Special:Upload | Upload File]] link (on the left sidebar) to reference images.
Have a look at our [[RPi Wiki Best Practice|Guidelines]] and then you are free to go !

=== Translations ===

The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:

* English: [[R-Pi Hub]]
* French: [[FR:R-Pi Hub]]
* German: [[DE:R-Pi Hub]]
* Greek: [[EL:R-Pi Hub]]
* Hungarian: [[HU:R-Pi Hub]]
* Japanese: [[JP:R-Pi_Hub]]
* Polish: [[PL:R-Pi_Hub]]
* Portugese: [[pt-BR:Raspberry Pi Board]]
* Romanian: [[RO:R-Pi_Hub]]
* Russian: [[RU:RaspberryPiBoard]]
* Українська: [[UA:R-Pi Hub]]
* Spanish: [[ES:R-Pi Hub]]
* Italiano: [[IT:R-Pi Hub]]
* Chinese:[[CH:R-Pi Hub]]
* Hebrew:[[HE:R-Pi Hub]]
* 한국어:[[KR:R-Pi Hub]]

Any help translating would be greatly appreciated. Thank you to those who have already contributed!

===Admins/Contributors===

Please see the [[Talk:R-Pi_Hub|Talk]] page for outstanding issues and discussions regarding the RPi Hub and related pages. 
Also , have look at [[RPi Wiki Best Practice]]. You can discuss the recommendations
[[Talk:RPi Wiki Best Practice | here ]] .

To share your thoughts, comments, thanks and interesting articles, see our [[RPi Visitor Book |Visitor Book]].

''Big thanks to elinux.org and their groups for the wiki space and content from which these pages have been grown.''

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Hub

2012-08-06T21:39:18Z

Lxndr: /* R-Pi Troubleshooting */

{{TOC right}}{{Template:Hub_Flags}} 
{{Clear}}
'''The Raspberry Pi wiki pages on this site are a community work - the Raspberry Pi Foundation is not responsible for content on these pages.'''

==Now shipping to customers==
Premier Farnell and RS Components have started shipping to customers. Congratulations to those at the front of the queue!.

Work is ongoing to clear the backlog of orders, with both distributors now manufacturing them in serial production. Farnell/Element14 have stated that all people worldwide who ordered their Raspberry Pi through them on or before April 18th should receive theirs by the end of June.

Update: In the US, on 2012 July 24, Newark/Element 14 is quoting five '''weeks''' and Allied is still quoting 12 weeks. An order placed by Rick Seiden on July 19, 2012 at Newark/Element 14 shipped July 31, 2012, indicating a less than five week wait time.

See the [[RPi Buying Guide | Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]

==About==
[[File:RpiFront.jpg|300px|thumb|right|The Rpi beta board (model B)]]

The Raspberry Pi (short: RPi or RasPi) is an ultra-low-cost credit-card sized Linux computer which was conceived with the primary goal of teaching computer programming to children. It was developed by the [http://www.raspberrypi.org Raspberry Pi Foundation], which is a UK registered charity (Registration Number 1129409). The foundation exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. The device is expected to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).

Raspberry Pi is manufactured and sold in partnership with the worldwide industrial distributors [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components].

* You can get the latest news from the [http://www.raspberrypi.org Foundation Home Page], the [http://twitter.com/intent/user?screen_name=Raspberry_Pi Twitter Feed] or in the [http://www.raspberrypi.org/forum/general-discussion/news-articles-and-blog-posts-about-raspberry-pi forums].
* For Raspberry Pi frequently asked questions see the [[R-Pi FAQ]] or the [http://www.raspberrypi.org/?page_id=8 Raspberry Pi Foundation's FAQ] page.
* Both manufacturing partners provide community areas for more technically focused discussions, articles, FAQs and related information:
:* Premier Farnell: [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group]
:* RS-Components: [http://www.designspark.com/theme/raspberrypi DesignSpark - Raspberry Pi]
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant<ref>http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet</ref>. In common with all Electronic and Electrical products the Raspberry Pi should not be disposed of in household waste. Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.
* Price: 25USD Model A, 35USD for Model B, excluding taxes, postage and packaging. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].

===History===
* Confused about seeing different versions of the board? Visit the [[Rpi HardwareHistory | History of the Raspberry Pi Hardware]] for information about the past versions.

* RegHardware's very detailed analysis is [http://www.reghardware.com/2011/11/28/raspberry_pi/ well worth a read]. Wikipedia also has [http://en.wikipedia.org/wiki/Raspberry_Pi an entry].

* Russell Davis (aka forum admin ukscone) has a series of blog articles recording his perspective of the [http://russelldavis.org/2012/01/14/the-raspberry-pi-part-one/ Raspberry Pi story] in several parts from the beginning.

* You will often hear mention of the BBC Micro Computer when people talk about the purpose of the Raspberry Pi Foundation. See this article on the [http://www.reghardware.com/2011/11/30/bbc_micro_model_b_30th_anniversary/ history of the BBC Micro Computer].

* Here's a video from the Financial Times, with three different groups evaluating the raspberry pi: http://video.ft.com/v/1498254373001/Taste-testing-the-Raspberry-Pi (March 2012)

==Getting Started==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa;" |
===[[Buying RPi |Buying Guide]]===
----
Where can I get one and for how much?
* Raspberry Pi can only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.

* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop].

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

===[[RPi Hardware Basic Setup | Basic Setup]]===
----
First little Raspberry Pi Steps...
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]
* Note: On the Debian OS after you log in you need to type startx at the prompt to get a graphic desktop.

* '''Having problems? Try the [http://elinux.org/R-Pi_Troubleshooting Troubleshooting] page.'''

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

===[[RPi Beginners | Beginners Guide]]===
----
You've just got your new Raspberry Pi device - what now?
* [[RPi Beginners | Beginners Guide]]

* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.

* Get started with some basic projects and tutorials:
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials] 
[http://www.youtube.com/user/RaspberryPiBeginners Another set of video tutorials]

[[RPi Tutorial Easy GPIO Hardware & Software | Easy GPIO Hardware & Software]] - in-progress at the moment
Example projects/tuts which can be linked from here
(or from within a beginners guide page perhaps):
Setup XBMC media centre
Programming tutorials (Liams YouTube etc)
Easy GPIO (when complete or similar thing).
Also links to some basic linux user guides.

* Take a look through the [[R-Pi_Hub#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.

|}

==Resources==
{| border="1" style="background:transparent;"

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Hardware|Hardware]] & [[RPi VerifiedPeripherals|Peripherals]]===
----

*The Model B is more advanced than the Model A - see [[RPi Hardware]].
*The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].
*The unit will support a range of [[RPi VerifiedPeripherals |devices, peripherals and accessories]].
*The [[Rpi Low-level peripherals| Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.
*For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].
*[[RPi Peripherals|Setting up peripherals - examples/HowTos]]
*[[RaspberryPi Boards|List of boards and user feedback]]
*[[RPi 5V PSU construction|Power Supply construction - HowTo]]
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[Rpi_Software|Software]] & [[RPi_Distributions|OS Distributions]]===
----
The Raspberry Pi will run a range of OS Distributions and run a variety of software.
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/Puppi Puppi] from Puppy Linux.
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]] or [[RPi_Performance|test the Pi's performance]].
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.
*Information about installing specific [[RPi_applications|applications]] is available through the link.
*Extensive (boot) configuration info (config.txt) is available [[RPi_config.txt|here]].

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Documentation|Documentation]]===
----
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].

[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]

Example documents which can be linked from here (or sub page):
Official Datasheets
White Papers
User Manuals
Recommended books (perhaps)

=== RPi Troubleshooting ===

Head over to the [[R-Pi Troubleshooting|troubleshooting page]] for help fixing common problems.

=== R-Pi Bugs ===

Head over to the [[RPi_Bugs|bugs page]] for a list of known bugs.

=== R-Pi Model B 3D CAD files ===
Theses are various 3D CAD Versions in both RAR and ZIP.

* CATIA V5 RAR http://sdrv.ms/JqdhMb
* CATIA V5 ZIP http://sdrv.ms/LjyLGD
* ProE RAR http://sdrv.ms/KCv1hZ
* ProE ZIP http://sdrv.ms/KCvhxq
* STEP RAR http://sdrv.ms/KCvv7T
* STEP ZIP http://sdrv.ms/JMhv18
* SketchUp http://scc.jezmckean.com/item/581
|}

==Community==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Projects |Projects]], [[RPi Guides |Guides]] & [[RPi Tutorials |Tutorials]]===
----
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].
*Knowledgeable users may want to review and help out with the [[RPi Tasks |Tasks page]].
*Get started by following some of the many [[RPi Tutorials | Tutorials]].
*Common tasks and useful tips are available through the [[RPi Guides | Guides page]].
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[Rpi Education|Schools, Universities, Clubs & Groups]]===
----
*The Raspberry Pi Foundation's aims include encouraging education. Several groups including [http://www.computingatschool.org.uk/ Computing At School] aim to bring Computing Science back into schools.
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |
===[[RPi Community |Supporting Communities]]===
----
The [[RPi Community |Raspberry Pi Community]] is steadily growing:
*[http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]

*[http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group], community site of Premier Farnell

*[http://www.designspark.com/theme/raspberrypi DesignSpark], community site of RS-Components

*[http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]

*[http://www.raspberrymod.com/ Raspberrymod] and [http://www.raspberrypiforums.com/forum RPiforums] Un-Official Raspberry Pi Discussion Boards

*[http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]

*[http://www.worldofpi.com/ World Of Pi] A forum based on all things Raspberry Pi.

*[[RPi Community Magazine]] - User contributed eMagazine, get involved!

*[[RaspberryPi Osdev]] - Hardware specific OS-development community, sitting in freenode.net#raspberrypi-osdev.

|}

==About the RPi Wiki==

'''Do not be afraid to add your bit, content is vital for the wiki to function.'''

[[File:Rasp_turn_around.gif|200px|thumb|right|A 3D rendering of the Raspberry Pi logo by forum user Antario. [http://www.raspberrypi.org/forum/projects-and-collaboration-general/raspberry-pi-3d-logo-animation Source]]]
This wiki is '''open''' for the community. You are encouraged to sign up and add your own projects, guides and correct anything within it. It is important that users like you continue to add to and grow this wiki, that way others will be able to come and do the same making the wiki a valuable resource. See [[Help:Editing | Help Editing The Wiki]] and the [[Special:Upload | Upload File]] link (on the left sidebar) to reference images.
Have a look at our [[RPi Wiki Best Practice|Guidelines]] and then you are free to go !

=== Translations ===

The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:

* English: [[R-Pi Hub]]
* French: [[FR:R-Pi Hub]]
* German: [[DE:R-Pi Hub]]
* Greek: [[EL:R-Pi Hub]]
* Hungarian: [[HU:R-Pi Hub]]
* Japanese: [[JP:R-Pi_Hub]]
* Polish: [[PL:R-Pi_Hub]]
* Portugese: [[pt-BR:Raspberry Pi Board]]
* Romanian: [[RO:R-Pi_Hub]]
* Russian: [[RU:RaspberryPiBoard]]
* Українська: [[UA:R-Pi Hub]]
* Spanish: [[ES:R-Pi Hub]]
* Italiano: [[IT:R-Pi Hub]]
* Chinese:[[CH:R-Pi Hub]]
* Hebrew:[[HE:R-Pi Hub]]
* 한국어:[[KR:R-Pi Hub]]

Any help translating would be greatly appreciated. Thank you to those who have already contributed!

===Admins/Contributors===

Please see the [[Talk:R-Pi_Hub|Talk]] page for outstanding issues and discussions regarding the RPi Hub and related pages. 
Also , have look at [[RPi Wiki Best Practice]]. You can discuss the recommendations
[[Talk:RPi Wiki Best Practice | here ]] .

To share your thoughts, comments, thanks and interesting articles, see our [[RPi Visitor Book |Visitor Book]].

''Big thanks to elinux.org and their groups for the wiki space and content from which these pages have been grown.''

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

Community

2012-08-06T21:37:53Z

Lxndr: /* Hardware-Specific Communities */ added Raspberry Pi

This page is for information about the embedded Linux and open source community.
== Netiquette ==

'''Please read [[Netiquette]] before interacting with the Open Source Communities'''

* [[Patch_Submission_HOWTO]]

== Community sites ==

=== General Portals ===

* [http://meld.org Meld] - An embedded Linux developer community site, designed to enable developers, ISVs, and hardware manufacturers to share, connect, and design, sponsored by [[MontaVista | MontaVista Software]]
* [http://www.linux.com Linux.com] - Linux community portal sponsored by the [http://www.linuxfoundation.org Linux Foundation]
* [http://www.linuxdevices.com LinuxDevices.com] - the canonical (no pun intended) place for news about embedded Linux
* [http://www.linux.org Linux.org] - an excellent starting place for all things linux

=== Hardware-Specific Communities ===

* [http://www.arm.linux.org.uk/ ARM Linux] - the central place for Linux on ARM, this is where you find Russell Kings patch tracker for example
* [http://www.beagleboard.org Beagle Board community] - portal for the Beagle Board community, sponsored by TI
* [http://www.opensourcemid.org OpenSourceMID.org community] - portal for the K7 OMAP3530 MID community
* [http://www.pandaboard.org PandaBoard community] - portal for the PandaBoard community, sponsored by TI
* [http://www.raspberrypi.org Rapsberry Pi community] - portal for the Raspberry Pi community, an ARM GNU/Linux box for $25. Take a byte!
* [http://www.igloocommunity.org Snowball community] - Portal for the Snowball community

=== Software-Specific Communities ===

* [http://www.moblin.org Moblin community] - portal for the Moblin community (merged with Maemo to form Meego - see next item)
* [http://www.meego.com Meego community] - portal for the Meego community
* [http://www.yoctoproject.org Yocto Project] - portal for the Yocto project

=== Communities for beginners ===

* http://kernelnewbies.org/ - General site for people getting started developing on the Linux kernel
* http://jp.kernelnewbies.org/webresources - Japanese site for kernel newbies
* [http://www.embedded-systems-portal.com/CTB Embedded Systems Common Technical Baseline] - Although not directly related to Linux this site is an excellent overview of what embedded systems are seen from various angles (hardware, software, design methods, etc...)
* [[Community Participation Guides]] - Resources for how to participate in Open Source Communities.

== People ==
This section lists inviduals who are "movers and shakers" in embedded Linux:
For more Information be sure to checkout [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=MAINTAINERS;hb=master MAINTAINERS]
=== Linux kernel ===
==== Important kernel figures ====
* Linus Torvalds - Linux kernel initiator and head maintainer
* Andrew Morton - maintains an important secondary (staging) tree
* David Woodhouse - Embedded Linux Maintainer
* Matt Mackall - Embedded Linux Maintainer, originator of Linux-tiny patch set (author of SLOB allocator), author of kpagemap and smem
* Greg Kroah-Hartman - Initiator and Maintainer of the Linux Driver Project / Staging Tree and quite a handyman.
* Stephen Rothwell - Maintainer of the Linux-Next-Tree, most stuff goes in there before getting merged into Linus' tree-

==== Kernel arch maintainers ====
* Russell King - ARM kernel maintainer
* Paul Mundt - SH kernel maintainer
* Ralf Baechle - MIPS kernel maintainer
* Greg Ungerer - uCLinux kernel maintainer
* Arnd Bergman - CELL kernel maintainer
* Thomas Gleixner - x86 kernel maintainer, author of clock events
* Haavard Skinnemoen - avr32 kernel Maintainer (Atmel)

==== Feature developers/maintainers ====
* David Woodhouse - MTD/jffs2 author - Embedded Linux kernel maintainer
* Andi Kleen - author of bloat-o-meter
* Ingo Molnar - author of RT-preempt patch set, kernel scheduler maintainer
* Phillip Lougher - author of [[Squash FS]]

=== Interview candidates ===
The following page has a list of people we'd like to interview for an eLinux.org feature:
* [[Interviews]]

== Foundations and Forums ==
* [http://www.embedinfo.com/cforum/arm_forum_find.asp?bid=6 ARM Development Discussion Forum] launched by [http://armkits.com Embest]
* [http://www.embedinfo.com/cforum/arm_forum_find.asp?bID=7 Embest Product User Forum]
* [[CE Linux Forum]]
** [[ELC_Presentations|ELF Conference Presentations]]
** [http://www.celinuxforum.org/ CELF home page]
* [http://www.linuxfoundation.org/ Linux Foundation]

== Communities for beginners ==
* http://kernelnewbies.org/ - General site for people getting started developing on the Linux kernel
* http://jp.kernelnewbies.org/webresources - Japanese site for kernel newbies

== Linux User Groups ==
One way to get involved with a bunch of like-minded Linux enthusiasts is to participate in a local Linux users group. The following site has a good database of Linux users groups:
* [http://www.linux.org/groups/ www.linux.org/groups]
* [http://www.cluecan.ca/flexinode/table/1 CLUE LUG List] - Canadian User Group listing.
* [[BeagleBoard/bangalore_user_meet | Bangalore Beagle User Group Meet]]

== Development Model ==
* [http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ The Cathedral and the Bazaar]
* FIXTHIS - add more links to papers and articles about the development model
=== Reasons for contributing to open source ===
* [[Open Source ROI Model]] - a page about return on investment from open source contributions

== Quality Assurance ==
This section has links to aspects of the development model designed to provide quality assurance.
=== Certificate of Origin ===
Developers who contribute code to the Linux kernel agree to the [[Developer Certificate Of Origin]] by signing
their code, with a "Signed Off By" line.

------
[[Category:NeedsEditing]]

[[Category:Community| ]]

User:Lxndr

2012-08-06T21:34:49Z

Lxndr: Created page with "New-born Raspberry Pi user :)"

New-born Raspberry Pi user :)

RPi Hardware Basic Setup

2012-08-06T21:34:09Z

Lxndr: /* Prepared Operating System SD Card */ added configuration page to the bullet list

[[Category:RaspberryPi]]
{{Template:RPi_Startup}}

=Typical Hardware You Will Need=
While the RPi can be used without any additional hardware (except perhaps a power supply of some kind), it won't be much use as a general computer. As with any normal PC, it is likely you will need some additional hardware.

'''IMPORTANT''' For USB devices other than a mouse and a simple wired keyboard (for USB devices drawing more than 100mA) a powered USB hub is strongly recommended. A technical discussion as to why can be found [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5830 here]. Specifically the RPI's built in USB hub is designed only for "Single current unit" USB devices.

The following are more or less essential:

* [[RPi Buying Guide|Raspberry Pi board]]
* [[#Prepared Operating System SD Card|Prepared Operating System SD Card]]
* [[#Keyboard & Mouse|USB keyboard]]
* [[#Display|Display]] (with HDMI, DVI, Composite or SCART input)
* [[#Power Supply|Power Supply]]
* [[#Cables|Cables]]

Highly suggested extras include:

* [[#Keyboard & Mouse|USB mouse]]
* [[#Additional Peripherals|Internet connectivity]] - a USB WiFi adaptor (Model A/B) or a LAN cable (Model B)
* [[#Additional Peripherals|Powered USB Hub]]
* [[#Additional Peripherals|Case]]
* [[#Additional Peripherals|SD card reader]] - if you need to prepare your own SD card

==Prepared Operating System SD Card==
As the RPi has no internal storage or built-in [[RPi Distributions|operating system]] it requires an SD-Card that is set up to boot the RPi.

* Have a look at [[RPi Easy SD Card Setup]] to create your own preloaded SD Card.
* If you want an extensive technical explanation, look here : ''Create your own preloaded card using any [[RPi VerifiedPeripherals#SD_cards]] card you have and this [[RPi Beginners#SD_card_setup| HowTo]] . ''
* Preloaded SD cards will be available from the [http://www.raspberrypi.com RPi Shop] , [http://www.trendinguk.co.uk/sd-cards--operating-systems.html TrendingUK] or [http://www.ebay.co.uk/itm/330743733755 eBay].
* For configuration of boot options and extensive graphic modes, look at the [[RPi_Configuration|Configuration]] page.

NOTE: An RPi SD card can only be used to boot an RPi. A normal PC will refuse to boot from an RPi SD card.

This guide will assume you have a preloaded SD card.

''To check your SD card is compatible with Linux, see [[RPi VerifiedPeripherals#SD_cards]].''

==Keyboard & Mouse==
Most standard USB keyboards and mice will work with the RPi. Wireless keyboard/mice should also function, and only require a single USB port for an RF dongle. In order to use a Bluetooth keyboard or mouse you would need to use a Bluetooth dongle, which again uses a single port.

Remember that the Model A has a single USB port and the Model B only has two (typically a keyboard and mouse will use a USB port each) - see [[RPi_Hardware_Basic_Setup#USB-Hub | USB Hub]] below.

''To check your mouse and keyboard are compatible with Linux, see [[RPi VerifiedPeripherals | RPi Verified Peripherals]].''

==Display==
There are two main connection options for the RPi display, ''HDMI'' (high definition) and ''Composite'' (low definition).

* HD TVs and most LCD Monitors can be connected using a full-size 'male' HDMI cable, and with an inexpensive adaptor if DVI is used. HDMI versions 1.3 and 1.4 are supported, and a version 1.4 cable is recommended. The RPi outputs audio and video via HMDI, but does not support HDMI input.

* Most older TVs can be connected using Composite (a yellow-to-yellow cable). PAL and NTSC TVs are supported. Note that the RCA output is composite video, not RF, so it cannot be connected directly to the antenna input of a TV, you need to connected it the the yellow video input connector, or to the SCART input using a RCA to SCART plug, (adapter).

When using composite video, audio is available from a 3.5mm (1/8 inch) socket, and can be sent to your TV, or to an amplifier. To send audio to your TV, you will need a cable which adapts from 3.5mm to double (red and white) RCA connectors. These red and white can go into the red and white RCA plug inputs of a TV, or a stereo set, or to the above mentioned RCA to SCART plug. Another option for audio (when not using HDMI) is to connect the 3.5mm jackplug to an amplified speakerset. Do not connect the 3.5 mm jack directly to a headset, as the 3.5 mm audio output isn't suitable to drive headsets, only amplifier inputs. Attaching a low impedance load, (such as a headset) to the stereo audio output may lead to distorted sound.

'''Note: There is no VGA output available, so older VGA monitors will require an expensive adaptor.'''

Using an HDMI to DVI-D (digital) adaptor plus a DVI to VGA adaptor will not work. HDMI does not supply the DVI-A (analogue) needed to convert to VGA - converting an HDMI or DVI-D source to VGA (or component) needs an active converter. (It can work out cheaper to buy a new monitor.) The lack of VGA has been acknowledged as a priority issue. In a [http://interviews.slashdot.org/story/11/09/14/1554243/Eben-Upton-Answers-Your-Questions Q/A with Slashdot] Eben said that they plan to look into providing some form of add-on.

''For detailed information see [[Rpi Screens]].''

==Power Supply==
The unit uses a Micro USB connection to power itself (only the power pins are connected - so it will not transfer data over this connection). A standard modern phone charger with a micro-USB connector will do, but needs to produce at least 700mA at 5 volts. Check your power supply's ratings carefully, and [http://www.raspberrypi.org/forum/general-discussion/power-supply-warning beware cheap knock-offs!]. Suitable mains adaptors will be available from the [http://www.raspberrypi.com RPi Shop] as well as [http://www.trendinguk.co.uk/micro-usb-power-supply-for-the-raspberry-pi.html TrendingUK] or [http://www.ebay.co.uk/itm/330757401271 eBay] and are recommended if you are unsure what to use.

You can use a range of other power sources (assuming they are able to provide enough current ~700mA):
* Computer USB Port or powered USB hub (will depend on power output)
* Special wall warts with USB ports
* Mobile Phone Backup Battery (will depend on power output) (in theory - needs confirmation)
* Modern TV with built-in USB (for example, it has been shown to work with the Sony KDL-40HX723 and KDL-55NX813)
* Internet Routers with USB Ports (the BT Home Hub 3 seems to run the Pi nicely)

To use the above, you'll need a USB A 'male' to USB micro 'male' cable - these are often shipped as data cables with mobile phones.

''For detailed information about power requirements see [[Rpi_Hardware#Power | RPi Hardware - Power]].''

==Cables==
You will probably need a number of cables in order to connect your RPi up.
# Micro-B USB Power Cable (see above) [http://en.wikipedia.org/wiki/File:MicroB_USB_Plug.jpg picture]. This has to be a [[On the RPi usb power cable|high quality one]].
# HDMI-A [http://en.wikipedia.org/wiki/File:HDMI.jpg picture] or Composite cable [http://en.wikipedia.org/wiki/File:Composite-video-cable.jpg picture], plus DVI adaptor [http://en.wikipedia.org/wiki/File:Adapter_dvi_hdmi_S7302224_wp.jpg picture] or SCART adaptor [http://en.wikipedia.org/wiki/File:Multiconnector-scart-chti.jpg picture] if required, to connect your RPi to the Display/Monitor/TV of your choice.
# Audio cable [http://en.wikipedia.org/wiki/File:Audio-TRS-Mini-Plug.jpg picture], this is not needed if you use a HDMI TV/monitor.
# Ethernet/LAN Cable (see below) [http://en.wikipedia.org/wiki/File:Ethernet_RJ45_connector_p1160054.jpg picture].

The price you pay for an HDMI cable can very wildly and under most circumstances a low-cost cable from a reputable online or local supplier will be absolutely fine, but the definition of what constitutes 'low cost' can vary wildly - for example, in the UK, a 1m cable can be purchased for anything between £1 and £24.99.
If, however, you want to drive a display some distance from the RPi (say greater than the ubiquitous 1.8m/6ft), or you are using a video switch to share a display between several devices, then higher quality cables might be wise - for example, a pair of 1m HDMI cables purchased in a UK 'pound shop' worked fine when directly connected between the RPi and a display, but would not give a stable picture when used via an HDMI switch. Replacing the £1 1m cable with a 1.5m cable bought online for £1.30 fixed the problem.
For more insight: [http://www.techradar.com/news/video/why-you-dont-need-to-spend-more-than-2-on-an-hdmi-cable-1071343 Why you don't need to spend more than £2 on an HDMI cable]

==Additional Peripherals==
You may decide you want to use various other devices with your RPi, such as Flash Drives/Portable Hard Drives, Speakers etc.

''For detailed information see [[RPi VerifiedPeripherals | RPi Verified Peripherals]].''

===Internet Connectivity===

This may be an Ethernet/LAN cable (standard RJ45 connector) or a USB WiFi adaptor. The RPi ethernet port is auto-sensing which means that it may be connected to a router or directly to another computer (without the need for a crossover cable<ref name=autoMDIX>[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]</ref>).

''Support for USB WiFi adaptors will vary - see [[RPi VerifiedPeripherals | RPi Verified Peripherals]].''

===USB-Hub===
In order to connect additional devices to the RPi, you may want to obtain a USB Hub, which will allow multiple devices to be used.

It is nearly a requirement that a '''powered''' hub is used - this will provide any additional power to the devices without affecting the RPi itself. The USB ports are fused at about 140ma each without an additional external power source. This not enough to power a hard drive, and you may even have trouble powering wireless adapters and other peripherals. There is enough current out there, however, for mice and most keyboards. (see [[Rpi_Hardware#Power | RPi Hardware - Power]] section).

USB version 2.0 is recommended. USB version 1.1 is fine for keyboards and mice, but may not be fast enough for other accessories.

===Heatsink===
Not a vital accessory for your RPi, but will help to reduce the CPU's temperature whilst under load. Via [http://www.trendinguk.co.uk/heatsink-for-the-raspberry-pi.html TrendingUK] or [http://www.ebay.co.uk/itm/330758220781 eBay]

===Case===
Since the RPi is supplied without a case, it will be important to ensure that you do not use it in places where it will come into contact with conductive metal or liquids, unless suitably protected. Some form of [[Rpi Cases | case]] should be considered, and there is a [http://www.raspberrypi.org/forum/general-discussion/cases-for-the-raspberry-pi Rpi case thread] on the forum.

''For detailed information see [[Rpi Cases]].''

===SD card reader===
If you will not use a preloaded SD card to boot from, you will need an SD card reader to prepare an SD card.

Note that the SD card reader will be connected to a traditional PC, not to the RPi. You may use an SD card reader integrated into your PC, or you may use a dedicated USB-connected SD card reader. Note that several peripherals may also be used as an SD card reader, for example cameras, smartphones, camcorders and GPS units.

===Expansion & Low Level Peripherals===
If you plan on making use of the low level interfaces available on the RPi, then ensure you have suitable header pins for the GPIO (and if required JTAG) suitable for your needs.

Also if you have a particular low-level project in mind, then ensure you design in suitable protection circuits to keep your RPi safe (details will be made available within the [[RaspberryPiBoardProjects | RPi Projects, Guides & Tutorials]] section).

''For detailed information see [[Rpi Low-level peripherals | Rpi Low-level Peripherals]].''

=Connecting Together=

[[File:Raspi-Model-AB-Mono-1-699x1024.png|200px|thumb|right|A diagram denoting the places of the different components on the Rpi, made by Paul Beech. Click to enlarge.]]
You can use the diagram to connect everything together, or use the following instructions:

# Plug the preloaded SD Card into the Pi.
# Plug the USB keyboard and mouse into the Pi, perhaps via a USB Hub. Connect the Hub to power, if necessary.
# Plug the video cable into the screen (TV) and into the Pi.
# Plug your extras into the Pi (USB WiFi, Ethernet cable, hard drive etc.). This is where you may really need a USB Hub.
# Ensure that your USB Hub (if any) and screen are working.
# Plug the power source into the main socket.
# With your screen on, plug the other end of the power source into the Pi.
# The Pi should boot up and display messages on the screen.

It is always recommended to connect the MicroUSB Power to the unit last (while most connections can be made live, it is best practice to connect items such as displays and other connections with the power turned off).

If you use both a R-PI power supply and a powered hub, its recommended you connect them to the same switched power bar, and use the switch on the power bar to switch off both the R-PI and hub at the exact same time.

Also, always shutdown using the software shutdown function, not by pulling the plug. When not using a GUI, (with a GUI use the GUI command) you can use the command "shutdown -h now", and power off when all the LED's on the board (except the power LED) go off. This is especially important the first time you boot, as in the process the R-PI modifies the content of the SD-card, without a clean shutdown the contents of the card may be damaged.

The RPi may take a long time to boot when powered-on for the first time, so be patient, and cleanly shutdown afterwards, as described above!

=External Links=

For a verbose guide aimed at absolute beginners, see [http://h2g2.com/A13413584 Peripherals You'll Need] and [http://h2g2.com/A9143796 Getting Started] in h2g2's 'Introducing the Raspberry Pi'.

=References=
<references/>
{{Template:Raspberry Pi}}

RPi Configuration

2012-08-06T21:31:21Z

Lxndr: Started a separate configuration page, with more extensive and beginner friendly documentation as RPi_config.txt, including links to example configs

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

And here is another example file, containing extended documentation of features: [http://elinux.org/images/c/ca/Raspi_documented_config.txt link].

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''sdtv_disable_colourburst''' disables colour burst on composite output. The picture will be monochrome, but possibly sharper
sdtv_disable_colourburst=1 colour burst is disabled

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility.
hdmi_safe=1 (this does: hdmi_force_hotplug=1, config_hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0)

'''hdmi_ignore_edid''' Enables the ignoring of EDID/display data if your display is a crappy Chinese one
hdmi_ignore_edid=0xa5000080

'''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
hdmi_force_edid_audio=1

'''hdmi_ignore_cec''' Pretends CEC is not supported by TV. Avoids bringing (CEC enabled) TV out of standby and channel switch when rebooting.
hdmi_ignore_cec=1

'''hdmi_force_hotplug''' Pretends HDMI hotplug signal is asserted so it appears a HDMI display is attached
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_ignore_hotplug''' Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type

Not specifying the group, or setting to 0 will use the preferred group reported by the edid.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''
*Enter the following commands to dump more detailed information from your monitor
'''/opt/vc/bin/tvservice -d edid.dat'''
'''/opt/vc/bin/edidparser edid.dat'''
The edid.dat should also be provided when troubleshooting problems with the default HDMI mode

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''ramfsaddr''' address to load ramfs file at

'''initramfs''' (string address) ramfs file and adress to load it at (it's like ramfsfile+ramfsaddr in one option). NOTE: this option uses different syntax than all other options - you should not use "=" character here. Example:
initramfs initramf.gz 0x00800000

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

'''avoid_safe_mode''' If set to one, [[RPI_safe_mode|safe_mode]] boot won't be enabled.

= Notes =
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Overclocking

2012-08-06T21:28:33Z

Lxndr: added references, template, category

=Overclocking configuration=
'''WARNING:''' Setting any (of the below) parameters which could potentially over-volt your Raspberry Pi, will set a ''permanent bit'' within the SOC, voiding your warranty. So if you care about the warranty on your Raspberry Pi do NOT adjust any voltages!

Also at your own risk, you can try the display [[RPi_config_for_your_TV|overscan settings]] from our wiki. These overscan-settings were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum, but are not confimed to work...

==Overclocking options==

These settings are also documented in one of the example configuration files mentioned on [[RPi_config.txt|the config page]].

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. It have an impact on ARM performance since it drives L2 cache. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

== Clocks relationship ==

ARM, SDRAM and GPU each have their own PLLs and can have unrelated frequencies<ref name=freq_relationship>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=125#p126308</ref>.
The GPU core, h264, v3d and isp share a PLL, so need to have related frequencies. PLL will be set to:
pll_freq = core_freq * 2^n, for smallest n satisfying pll_freq > 600MHz.

GPU core, h264, v3d and isp should all be integer divisors of pll_freq.
So core_freq=480 sets pll_freq=960. That would allow a v3d_freq/h264_freq/v3d_freq of 320 with an integer divider of 3.

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|750 ||255 || || || || ||450 || ||
|-
|900 ||250 || || || || ||500 || ||
|-
|900 ||275 || || || || ||500 || ||
|-
|900 || ||450 || || || ||450 || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||450 ||6 ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|}

= Notes =
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPi Overclocking

2012-08-06T21:26:54Z

Lxndr: Started a separate overclocking page as most users either want detailed info or should stay away from it, will adjust RPi_Configuration accordingly.

RPiconfig

2012-08-06T21:14:06Z

Lxndr: /* File format */ added more documented example config file

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

And here is another example file, containing extended documentation of features: [http://elinux.org/images/c/ca/Raspi_documented_config.txt link].

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''sdtv_disable_colourburst''' disables colour burst on composite output. The picture will be monochrome, but possibly sharper
sdtv_disable_colourburst=1 colour burst is disabled

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility.
hdmi_safe=1 (this does: hdmi_force_hotplug=1, config_hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0)

'''hdmi_ignore_edid''' Enables the ignoring of EDID/display data if your display is a crappy Chinese one
hdmi_ignore_edid=0xa5000080

'''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
hdmi_force_edid_audio=1

'''hdmi_ignore_cec''' Pretends CEC is not supported by TV. Avoids bringing (CEC enabled) TV out of standby and channel switch when rebooting.
hdmi_ignore_cec=1

'''hdmi_force_hotplug''' Pretends HDMI hotplug signal is asserted so it appears a HDMI display is attached
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_ignore_hotplug''' Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type

Not specifying the group, or setting to 0 will use the preferred group reported by the edid.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''
*Enter the following commands to dump more detailed information from your monitor
'''/opt/vc/bin/tvservice -d edid.dat'''
'''/opt/vc/bin/edidparser edid.dat'''
The edid.dat should also be provided when troubleshooting problems with the default HDMI mode

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''ramfsaddr''' address to load ramfs file at

'''initramfs''' (string address) ramfs file and adress to load it at (it's like ramfsfile+ramfsaddr in one option). NOTE: this option uses different syntax than all other options - you should not use "=" character here. Example:
initramfs initramf.gz 0x00800000

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

'''avoid_safe_mode''' If set to one, [[RPI_safe_mode|safe_mode]] boot won't be enabled.

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. It have an impact on ARM performance since it drives L2 cache. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

== Clocks relationship ==

ARM, SDRAM and GPU each have their own PLLs and can have unrelated frequencies<ref name=freq_relationship>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=125#p126308</ref>.
The GPU core, h264, v3d and isp share a PLL, so need to have related frequencies. PLL will be set to:
pll_freq = core_freq * 2^n, for smallest n satisfying pll_freq > 600MHz.

GPU core, h264, v3d and isp should all be integer divisors of pll_freq.
So core_freq=480 sets pll_freq=960. That would allow a v3d_freq/h264_freq/v3d_freq of 320 with an integer divider of 3.

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|750 ||255 || || || || ||450 || ||
|-
|900 ||250 || || || || ||500 || ||
|-
|900 ||275 || || || || ||500 || ||
|-
|900 || ||450 || || || ||450 || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||450 ||6 ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|}

= Notes =
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

File:Raspi documented config.txt

2012-08-06T21:12:25Z

Lxndr: Suggested replacement for current /boot/config.txt with extensive documentation based on elinux.org pages etc. Rename to config.txt and save to /boot

Suggested replacement for current /boot/config.txt with extensive documentation based on elinux.org pages etc. Rename to config.txt and save to /boot

RPiconfig

2012-08-06T21:09:45Z

Lxndr:

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''sdtv_disable_colourburst''' disables colour burst on composite output. The picture will be monochrome, but possibly sharper
sdtv_disable_colourburst=1 colour burst is disabled

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility.
hdmi_safe=1 (this does: hdmi_force_hotplug=1, config_hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0)

'''hdmi_ignore_edid''' Enables the ignoring of EDID/display data if your display is a crappy Chinese one
hdmi_ignore_edid=0xa5000080

'''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
hdmi_force_edid_audio=1

'''hdmi_ignore_cec''' Pretends CEC is not supported by TV. Avoids bringing (CEC enabled) TV out of standby and channel switch when rebooting.
hdmi_ignore_cec=1

'''hdmi_force_hotplug''' Pretends HDMI hotplug signal is asserted so it appears a HDMI display is attached
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_ignore_hotplug''' Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type

Not specifying the group, or setting to 0 will use the preferred group reported by the edid.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''
*Enter the following commands to dump more detailed information from your monitor
'''/opt/vc/bin/tvservice -d edid.dat'''
'''/opt/vc/bin/edidparser edid.dat'''
The edid.dat should also be provided when troubleshooting problems with the default HDMI mode

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''ramfsaddr''' address to load ramfs file at

'''initramfs''' (string address) ramfs file and adress to load it at (it's like ramfsfile+ramfsaddr in one option). NOTE: this option uses different syntax than all other options - you should not use "=" character here. Example:
initramfs initramf.gz 0x00800000

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

'''avoid_safe_mode''' If set to one, [[RPI_safe_mode|safe_mode]] boot won't be enabled.

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. It have an impact on ARM performance since it drives L2 cache. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

== Clocks relationship ==

ARM, SDRAM and GPU each have their own PLLs and can have unrelated frequencies<ref name=freq_relationship>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=125#p126308</ref>.
The GPU core, h264, v3d and isp share a PLL, so need to have related frequencies. PLL will be set to:
pll_freq = core_freq * 2^n, for smallest n satisfying pll_freq > 600MHz.

GPU core, h264, v3d and isp should all be integer divisors of pll_freq.
So core_freq=480 sets pll_freq=960. That would allow a v3d_freq/h264_freq/v3d_freq of 320 with an integer divider of 3.

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|750 ||255 || || || || ||450 || ||
|-
|900 ||250 || || || || ||500 || ||
|-
|900 ||275 || || || || ||500 || ||
|-
|900 || ||450 || || || ||450 || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||450 ||6 ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|}

= Notes =
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]

RPiconfig

2012-08-06T21:08:41Z

Lxndr: /* Notes */ added the template box at the bottom

[[Category: RaspberryPi]]

The Raspberry Pi config.txt file is read by the GPU before the ARM core is initialised. It can be used to set various system configuration parameters.

This file is an optional file on the boot partition. It would normally be accessible as /boot/config.txt from Linux.

To edit the configuration file, see the instructions at [[R-Pi_ConfigurationFile]].

=File format=

The format is "property=value". value is an integer. You may specify only one option per line. Comments may be added by starting a line with the '#' character.

Here is an example file
'''# Set stdv mode to PAL (as used in Europe)
sdtv_mode=2
# Force the monitor to HDMI mode so that sound will be sent over HDMI cable
hdmi_drive=2
# Set monitor mode to DMT
hdmi_group=2
# Set monitor resolution to 1024x768 XGA 60Hz (HDMI_DMT_XGA_60)
hdmi_mode=16
# Make display smaller to stop text spilling off the screen
overscan_left=20
overscan_right=12
overscan_top=10
overscan_bottom=10'''

=Video mode configuration=
==Video mode options==
'''sdtv_mode''' defines the TV standard for composite output (default=0)
sdtv_mode=0 Normal NTSC
sdtv_mode=1 Japanese version of NTSC – no pedestal
sdtv_mode=2 Normal PAL
sdtv_mode=3 Brazilian version of PAL – 525/60 rather than 625/50, different subcarrier

'''sdtv_aspect''' defines the aspect ratio for composite output (default=1)
sdtv_aspect=1 4:3
sdtv_aspect=2 14:9
sdtv_aspect=3 16:9

'''sdtv_disable_colourburst''' disables colour burst on composite output. The picture will be monochrome, but possibly sharper
sdtv_disable_colourburst=1 colour burst is disabled

'''hdmi_safe''' Use "safe mode" settings to try to boot with maximum hdmi compatibility.
hdmi_safe=1 (this does: hdmi_force_hotplug=1, config_hdmi_boost=4, hdmi_group=1, hdmi_mode=1, disable_overscan=0)

'''hdmi_ignore_edid''' Enables the ignoring of EDID/display data if your display is a crappy Chinese one
hdmi_ignore_edid=0xa5000080

'''hdmi_force_edid_audio''' Pretends all audio formats are supported by display, allowing passthrough of DTS/AC3 even when not reported as supported.
hdmi_force_edid_audio=1

'''hdmi_ignore_cec''' Pretends CEC is not supported by TV. Avoids bringing (CEC enabled) TV out of standby and channel switch when rebooting.
hdmi_ignore_cec=1

'''hdmi_force_hotplug''' Pretends HDMI hotplug signal is asserted so it appears a HDMI display is attached
hdmi_force_hotplug=1 Use HDMI mode even if no HDMI monitor is detected

'''hdmi_ignore_hotplug''' Pretends HDMI hotplug signal is not asserted so it appears a HDMI display is not attached
hdmi_ignore_hotplug=1 Use composite mode even if HDMI monitor is detected

'''hdmi_drive''' chooses between HDMI and DVI modes
hdmi_drive= 1 Normal DVI mode (No sound)
hdmi_drive= 2 Normal HDMI mode (Sound will be sent if supported and enabled)

'''hdmi_group''' defines the HDMI type

Not specifying the group, or setting to 0 will use the preferred group reported by the edid.

hdmi_group=1 CEA
hdmi_group=2 DMT

'''hdmi_mode''' defines screen resolution in CEA or DMT format

'''These values are valid if hdmi_group=1 (CEA)'''
hdmi_mode=1 VGA
hdmi_mode=2 480p 60Hz
hdmi_mode=3 480p 60Hz H
hdmi_mode=4 720p 60Hz
hdmi_mode=5 1080i 60Hz
hdmi_mode=6 480i 60Hz
hdmi_mode=7 480i 60Hz H
hdmi_mode=8 240p 60Hz
hdmi_mode=9 240p 60Hz H
hdmi_mode=10 480i 60Hz 4x
hdmi_mode=11 480i 60Hz 4x H
hdmi_mode=12 240p 60Hz 4x
hdmi_mode=13 240p 60Hz 4x H
hdmi_mode=14 480p 60Hz 2x
hdmi_mode=15 480p 60Hz 2x H
hdmi_mode=16 1080p 60Hz
hdmi_mode=17 576p 50Hz
hdmi_mode=18 576p 50Hz H
hdmi_mode=19 720p 50Hz
hdmi_mode=20 1080i 50Hz
hdmi_mode=21 576i 50Hz
hdmi_mode=22 576i 50Hz H
hdmi_mode=23 288p 50Hz
hdmi_mode=24 288p 50Hz H
hdmi_mode=25 576i 50Hz 4x
hdmi_mode=26 576i 50Hz 4x H
hdmi_mode=27 288p 50Hz 4x
hdmi_mode=28 288p 50Hz 4x H
hdmi_mode=29 576p 50Hz 2x
hdmi_mode=30 576p 50Hz 2x H
hdmi_mode=31 1080p 50Hz
hdmi_mode=32 1080p 24Hz
hdmi_mode=33 1080p 25Hz
hdmi_mode=34 1080p 30Hz
hdmi_mode=35 480p 60Hz 4x
hdmi_mode=36 480p 60Hz 4xH
hdmi_mode=37 576p 50Hz 4x
hdmi_mode=38 576p 50Hz 4x H
hdmi_mode=39 1080i 50Hz reduced blanking
hdmi_mode=40 1080i 100Hz
hdmi_mode=41 720p 100Hz
hdmi_mode=42 576p 100Hz
hdmi_mode=43 576p 100Hz H
hdmi_mode=44 576i 100Hz
hdmi_mode=45 576i 100Hz H
hdmi_mode=46 1080i 120Hz
hdmi_mode=47 720p 120Hz
hdmi_mode=48 480p 120Hz
hdmi_mode=49 480p 120Hz H
hdmi_mode=50 480i 120Hz
hdmi_mode=51 480i 120Hz H
hdmi_mode=52 576p 200Hz
hdmi_mode=53 576p 200Hz H
hdmi_mode=54 576i 200Hz
hdmi_mode=55 576i 200Hz H
hdmi_mode=56 480p 240Hz
hdmi_mode=57 480p 240Hz H
hdmi_mode=58 480i 240Hz
hdmi_mode=59 480i 240Hz H
H means 16:9 variant (of a normally 4:3 mode).
2x means pixel doubled (i.e. higher clock rate, with each pixel repeated twice)
4x means pixel quadrupled (i.e. higher clock rate, with each pixel repeated four times)

'''These values are valid if hdmi_group=2 (DMT)'''
hdmi_mode=1 640x350 85Hz
hdmi_mode=2 640x400 85Hz
hdmi_mode=3 720x400 85Hz
hdmi_mode=4 640x480 60Hz
hdmi_mode=5 640x480 72Hz
hdmi_mode=6 640x480 75Hz
hdmi_mode=7 640x480 85Hz
hdmi_mode=8 800x600 56Hz
hdmi_mode=9 800x600 60Hz
hdmi_mode=10 800x600 72Hz
hdmi_mode=11 800x600 75Hz
hdmi_mode=12 800x600 85Hz
hdmi_mode=13 800x600 120Hz
hdmi_mode=14 848x480 60Hz
hdmi_mode=15 1024x768 43Hz DO NOT USE
hdmi_mode=16 1024x768 60Hz
hdmi_mode=17 1024x768 70Hz
hdmi_mode=18 1024x768 75Hz
hdmi_mode=19 1024x768 85Hz
hdmi_mode=20 1024x768 120Hz
hdmi_mode=21 1152x864 75Hz
hdmi_mode=22 1280x768 reduced blanking
hdmi_mode=23 1280x768 60Hz
hdmi_mode=24 1280x768 75Hz
hdmi_mode=25 1280x768 85Hz
hdmi_mode=26 1280x768 120Hz reduced blanking
hdmi_mode=27 1280x800 reduced blanking
hdmi_mode=28 1280x800 60Hz
hdmi_mode=29 1280x800 75Hz
hdmi_mode=30 1280x800 85Hz
hdmi_mode=31 1280x800 120Hz reduced blanking
hdmi_mode=32 1280x960 60Hz
hdmi_mode=33 1280x960 85Hz
hdmi_mode=34 1280x960 120Hz reduced blanking
hdmi_mode=35 1280x1024 60Hz
hdmi_mode=36 1280x1024 75Hz
hdmi_mode=37 1280x1024 85Hz
hdmi_mode=38 1280x1024 120Hz reduced blanking
hdmi_mode=39 1360x768 60Hz
hdmi_mode=40 1360x768 120Hz reduced blanking
hdmi_mode=41 1400x1050 reduced blanking
hdmi_mode=42 1400x1050 60Hz
hdmi_mode=43 1400x1050 75Hz
hdmi_mode=44 1400x1050 85Hz
hdmi_mode=45 1400x1050 120Hz reduced blanking
hdmi_mode=46 1440x900 reduced blanking
hdmi_mode=47 1440x900 60Hz
hdmi_mode=48 1440x900 75Hz
hdmi_mode=49 1440x900 85Hz
hdmi_mode=50 1440x900 120Hz reduced blanking
hdmi_mode=51 1600x1200 60Hz
hdmi_mode=52 1600x1200 65Hz
hdmi_mode=53 1600x1200 70Hz
hdmi_mode=54 1600x1200 75Hz
hdmi_mode=55 1600x1200 85Hz
hdmi_mode=56 1600x1200 120Hz reduced blanking
hdmi_mode=57 1680x1050 reduced blanking
hdmi_mode=58 1680x1050 60Hz
hdmi_mode=59 1680x1050 75Hz
hdmi_mode=60 1680x1050 85Hz
hdmi_mode=61 1680x1050 120Hz reduced blanking
hdmi_mode=62 1792x1344 60Hz
hdmi_mode=63 1792x1344 75Hz
hdmi_mode=64 1792x1344 120Hz reduced blanking
hdmi_mode=65 1856x1392 60Hz
hdmi_mode=66 1856x1392 75Hz
hdmi_mode=67 1856x1392 120Hz reduced blanking
hdmi_mode=68 1920x1200 reduced blanking
hdmi_mode=69 1920x1200 60Hz
hdmi_mode=70 1920x1200 75Hz
hdmi_mode=71 1920x1200 85Hz
hdmi_mode=72 1920x1200 120Hz reduced blanking
hdmi_mode=73 1920x1440 60Hz
hdmi_mode=74 1920x1440 75Hz
hdmi_mode=75 1920x1440 120Hz reduced blanking
hdmi_mode=76 2560x1600 reduced blanking
hdmi_mode=77 2560x1600 60Hz
hdmi_mode=78 2560x1600 75Hz
hdmi_mode=79 2560x1600 85Hz
hdmi_mode=80 2560x1600 120Hz reduced blanking
hdmi_mode=81 1366x768 60Hz
hdmi_mode=82 1080p 60Hz
hdmi_mode=83 1600x900 reduced blanking
hdmi_mode=84 2048x1152 reduced blanking
hdmi_mode=85 720p 60Hz
hdmi_mode=86 1366x768 reduced blanking

'''overscan_left''' number of pixels to skip on left

'''overscan_right''' number of pixels to skip on right

'''overscan_top''' number of pixels to skip on top

'''overscan_bottom''' number of pixels to skip on bottom

'''framebuffer_width''' console framebuffer width in pixels. Default is display width minus overscan.

'''framebuffer_height''' console framebuffer height in pixels. Default is display height minus overscan.

'''framebuffer_depth''' console framebuffer depth in bits per pixel. Default is 16. 8bit is valid, but default RGB palette makes an unreadable screen. 24bit looks better but has corruption issues as of 20120615. 32bit has no corruption issues but needs framebuffer_ignore_alpha=1 and shows the wrong colors as of 20120615.

'''framebuffer_ignore_alpha''' set to 1 to disable alpha channel. Helps with 32bit.

'''test_mode''' enable test sound/image during boot for manufacturing test.

'''disable_l2cache''' disable arm access to GPU's L2 cache. Needs corresponding L2 disabled kernel. Default is 0.

'''disable_overscan''' set to 1 to disable overscan.

'''config_hdmi_boost''' configure the signal strength of the HDMI interface. Default is 0. Try 4 if you have interference issues with hdmi. 7 is the maximum.

==Which values are valid for my monitor?==
Your HDMI monitor may support only a limited set of formats. To find out which formats are supported, use the following method.

*Set the output format to VGA 60Hz (hdmi_group=1 hdmi_mode=1) and boot up the Raspberry Pi
*Enter the following command to give a list of CEA supported modes
'''/opt/vc/bin/tvservice -m CEA'''
*Enter the following command to give a list of DMT supported modes
'''/opt/vc/bin/tvservice -m DMT'''
*Enter the following command to show your current state
'''/opt/vc/bin/tvservice -s'''
*Enter the following commands to dump more detailed information from your monitor
'''/opt/vc/bin/tvservice -d edid.dat'''
'''/opt/vc/bin/edidparser edid.dat'''
The edid.dat should also be provided when troubleshooting problems with the default HDMI mode

=Boot options=
'''disable_commandline_tags''' Stops start.elf from filling in ATAGS (memory from 0x100) before launching kernel

'''cmdline''' (string) Command line parameters. Can be used instead of cmdline.txt file

'''kernel''' (string) Alternative name to use when loading kernel.

'''kernel_address''' address to load kernel.img file at

'''ramfsfile''' (string) ramfs file to load

'''ramfsaddr''' address to load ramfs file at

'''initramfs''' (string address) ramfs file and adress to load it at (it's like ramfsfile+ramfsaddr in one option). NOTE: this option uses different syntax than all other options - you should not use "=" character here. Example:
initramfs initramf.gz 0x00800000

'''device_tree_address''' address to load device_tree at

'''init_uart_baud''' initial uart baud rate. Default 115200

'''init_uart_clock''' initial uart clock. Default 3000000

'''init_emmc_clock''' initial emmc clock. Default 50000000 (50mhz default. increasing this can speedup your SD-card)

'''boot_delay''' Waits for given number of seconds in start.elf before loading kernel.img.

'''avoid_safe_mode''' If set to one, [[RPI_safe_mode|safe_mode]] boot won't be enabled.

=Overclocking configuration=
'''WARNING:''' Setting any of the parameters which over volt your Raspberry Pi will set a permanent bit within the SOC and your warranty is void. So If you care about the warranty do not adjust voltage.

Also at your own risk you can try [[RPi_config_for_your_TV|overscan settings]] from our wiki. These were [http://www.raspberrypi.org/forum/features-and-requests/should-we-make-a-wiki-page-for-overscan-settings posted] on the forum and are not confimed to work.
==Overclocking options==

{| cellpadding="2"
!Option !! Description
|-
!align="right"|arm_freq
| frequency of ARM in MHz. Default 700.
|-
!align="right"|gpu_freq
| Sets core_freq, h264_freq, isp_freq, v3d_freq together.
|-
!align="right"|core_freq
| frequency of GPU processor core in MHz. It have an impact on ARM performance since it drives L2 cache. Default 250.
|-
!align="right"|h264_freq
| frequency of hardware video block in MHz. Default 250.
|-
!align="right"|isp_freq
| frequency of image sensor pipeline block in MHz. Default 250.
|-
!align="right"|v3d_freq
| frequency of 3D block in MHz. Default 250.
|-
!align="right"|sdram_freq
| frequency of SDRAM in MHz. Default 400.
|-
!align="right"|over_voltage
| ARM/GPU core voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages>What this means is that you can specify -16 and expect about 0.8V as the GPU/core voltage. This is 0.4V below the normal value of 1.2. If you specify 16, you'd get 0.4V ABOVE the normal value of 1.2V, or 1.6V. The fact that someone carefully specified "8" and "1.4V" as the upper limit in the examples leads me to think that it is likely to shorten the life of your raspberry pi significantly if you would specify values above "8". So: don't specify values above zero, but if you do, don't go above 8.</ref>
|-
!align="right"|over_voltage_sdram
| Sets over_voltage_sdram_c, over_voltage_sdram_i, over_voltage_sdram_p together
|-
!align="right"|over_voltage_sdram_c
| SDRAM controller voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V) <ref name=voltages />
|-
!align="right"|over_voltage_sdram_i
| SDRAM I/O voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|-
!align="right"|over_voltage_sdram_p
| SDRAM phy voltage adjust. [-16,8] equates to [0.8V,1.4V] with 0.025V steps. Default 0 (1.2V)<ref name=voltages />
|}

== Clocks relationship ==

ARM, SDRAM and GPU each have their own PLLs and can have unrelated frequencies<ref name=freq_relationship>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=29&t=6201&start=125#p126308</ref>.
The GPU core, h264, v3d and isp share a PLL, so need to have related frequencies. PLL will be set to:
pll_freq = core_freq * 2^n, for smallest n satisfying pll_freq > 600MHz.

GPU core, h264, v3d and isp should all be integer divisors of pll_freq.
So core_freq=480 sets pll_freq=960. That would allow a v3d_freq/h264_freq/v3d_freq of 320 with an integer divider of 3.

==Tested values==
The following table shows some successfull attempts of overclocking. These settings may not work on every device and can shorten the life of the Broadcom SoC. '''Warranty will be voided if overvoltage is used.'''
{| border="1"
! arm_freq !! gpu_freq !! core_freq !! h264_freq !! isp_freq !! v3d_freq !! sdram_freq !! over_voltage !! over_voltage_sdram
|-
|750 ||255 || || || || ||450 || ||
|-
|900 ||250 || || || || ||500 || ||
|-
|900 ||275 || || || || ||500 || ||
|-
|900 || ||450 || || || ||450 || ||
|-
|930 ||350 || || || || ||500 || ||
|-
|1000 || ||500 || || || ||450 ||6 ||
|-
|1000 || ||500 || || || ||500 ||6 ||
|}

= Notes =
<references>
{{Template:Raspberry Pi}}

RPi Hub

2012-08-06T21:07:23Z

Lxndr: /* Software & OS Distributions */ added link to RPi_config.txt as it is hard to find

{{TOC right}}{{Template:Hub_Flags}} 
{{Clear}}
'''The Raspberry Pi wiki pages on this site are a community work - the Raspberry Pi Foundation is not responsible for content on these pages.'''

==Now shipping to customers==
Premier Farnell and RS Components have started shipping to customers. Congratulations to those at the front of the queue!.

Work is ongoing to clear the backlog of orders, with both distributors now manufacturing them in serial production. Farnell/Element14 have stated that all people worldwide who ordered their Raspberry Pi through them on or before April 18th should receive theirs by the end of June.

Update: In the US, on 2012 July 24, Newark/Element 14 is quoting five '''weeks''' and Allied is still quoting 12 weeks. An order placed by Rick Seiden on July 19, 2012 at Newark/Element 14 shipped July 31, 2012, indicating a less than five week wait time.

See the [[RPi Buying Guide | Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]

==About==
[[File:RpiFront.jpg|300px|thumb|right|The Rpi beta board (model B)]]

The Raspberry Pi (short: RPi or RasPi) is an ultra-low-cost credit-card sized Linux computer which was conceived with the primary goal of teaching computer programming to children. It was developed by the [http://www.raspberrypi.org Raspberry Pi Foundation], which is a UK registered charity (Registration Number 1129409). The foundation exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. The device is expected to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).

Raspberry Pi is manufactured and sold in partnership with the worldwide industrial distributors [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components].

* You can get the latest news from the [http://www.raspberrypi.org Foundation Home Page], the [http://twitter.com/intent/user?screen_name=Raspberry_Pi Twitter Feed] or in the [http://www.raspberrypi.org/forum/general-discussion/news-articles-and-blog-posts-about-raspberry-pi forums].
* For Raspberry Pi frequently asked questions see the [[R-Pi FAQ]] or the [http://www.raspberrypi.org/?page_id=8 Raspberry Pi Foundation's FAQ] page.
* Both manufacturing partners provide community areas for more technically focused discussions, articles, FAQs and related information:
:* Premier Farnell: [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group]
:* RS-Components: [http://www.designspark.com/theme/raspberrypi DesignSpark - Raspberry Pi]
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant<ref>http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet</ref>. In common with all Electronic and Electrical products the Raspberry Pi should not be disposed of in household waste. Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.
* Price: 25USD Model A, 35USD for Model B, excluding taxes, postage and packaging. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].

===History===
* Confused about seeing different versions of the board? Visit the [[Rpi HardwareHistory | History of the Raspberry Pi Hardware]] for information about the past versions.

* RegHardware's very detailed analysis is [http://www.reghardware.com/2011/11/28/raspberry_pi/ well worth a read]. Wikipedia also has [http://en.wikipedia.org/wiki/Raspberry_Pi an entry].

* Russell Davis (aka forum admin ukscone) has a series of blog articles recording his perspective of the [http://russelldavis.org/2012/01/14/the-raspberry-pi-part-one/ Raspberry Pi story] in several parts from the beginning.

* You will often hear mention of the BBC Micro Computer when people talk about the purpose of the Raspberry Pi Foundation. See this article on the [http://www.reghardware.com/2011/11/30/bbc_micro_model_b_30th_anniversary/ history of the BBC Micro Computer].

* Here's a video from the Financial Times, with three different groups evaluating the raspberry pi: http://video.ft.com/v/1498254373001/Taste-testing-the-Raspberry-Pi (March 2012)

==Getting Started==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa;" |
===[[Buying RPi |Buying Guide]]===
----
Where can I get one and for how much?
* Raspberry Pi can only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.

* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop].

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

===[[RPi Hardware Basic Setup | Basic Setup]]===
----
First little Raspberry Pi Steps...
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]
* Note: On the Debian OS after you log in you need to type startx at the prompt to get a graphic desktop.

* '''Having problems? Try the [http://elinux.org/R-Pi_Troubleshooting Troubleshooting] page.'''

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

===[[RPi Beginners | Beginners Guide]]===
----
You've just got your new Raspberry Pi device - what now?
* [[RPi Beginners | Beginners Guide]]

* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.

* Get started with some basic projects and tutorials:
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials] 
[http://www.youtube.com/user/RaspberryPiBeginners Another set of video tutorials]

[[RPi Tutorial Easy GPIO Hardware & Software | Easy GPIO Hardware & Software]] - in-progress at the moment
Example projects/tuts which can be linked from here
(or from within a beginners guide page perhaps):
Setup XBMC media centre
Programming tutorials (Liams YouTube etc)
Easy GPIO (when complete or similar thing).
Also links to some basic linux user guides.

* Take a look through the [[R-Pi_Hub#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.

|}

==Resources==
{| border="1" style="background:transparent;"

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Hardware|Hardware]] & [[RPi VerifiedPeripherals|Peripherals]]===
----

*The Model B is more advanced than the Model A - see [[RPi Hardware]].
*The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].
*The unit will support a range of [[RPi VerifiedPeripherals |devices, peripherals and accessories]].
*The [[Rpi Low-level peripherals| Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.
*For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].
*[[RPi Peripherals|Setting up peripherals - examples/HowTos]]
*[[RaspberryPi Boards|List of boards and user feedback]]
*[[RPi 5V PSU construction|Power Supply construction - HowTo]]
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[Rpi_Software|Software]] & [[RPi_Distributions|OS Distributions]]===
----
The Raspberry Pi will run a range of OS Distributions and run a variety of software.
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/Puppi Puppi] from Puppy Linux.
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]] or [[RPi_Performance|test the Pi's performance]].
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.
*Information about installing specific [[RPi_applications|applications]] is available through the link.
*Extensive (boot) configuration info (config.txt) is available [[RPi_config.txt|here]].

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Documentation|Documentation]]===
----
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].

[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]

Example documents which can be linked from here (or sub page):
Official Datasheets
White Papers
User Manuals
Recommended books (perhaps)

=== R-Pi Troubleshooting ===

Head over to the [[R-Pi Troubleshooting|troubleshooting page]] for help fixing common problems.

=== R-Pi Bugs ===

Head over to the [[RPi_Bugs|bugs page]] for a list of known bugs.

=== R-Pi Model B 3D CAD files ===
Theses are various 3D CAD Versions in both RAR and ZIP.

* CATIA V5 RAR http://sdrv.ms/JqdhMb
* CATIA V5 ZIP http://sdrv.ms/LjyLGD
* ProE RAR http://sdrv.ms/KCv1hZ
* ProE ZIP http://sdrv.ms/KCvhxq
* STEP RAR http://sdrv.ms/KCvv7T
* STEP ZIP http://sdrv.ms/JMhv18
* SketchUp http://scc.jezmckean.com/item/581
|}

==Community==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[RPi Projects |Projects]], [[RPi Guides |Guides]] & [[RPi Tutorials |Tutorials]]===
----
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].
*Knowledgeable users may want to review and help out with the [[RPi Tasks |Tasks page]].
*Get started by following some of the many [[RPi Tutorials | Tutorials]].
*Common tasks and useful tips are available through the [[RPi Guides | Guides page]].
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

===[[Rpi Education|Schools, Universities, Clubs & Groups]]===
----
*The Raspberry Pi Foundation's aims include encouraging education. Several groups including [http://www.computingatschool.org.uk/ Computing At School] aim to bring Computing Science back into schools.
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |
===[[RPi Community |Supporting Communities]]===
----
The [[RPi Community |Raspberry Pi Community]] is steadily growing:
*[http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]

*[http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group], community site of Premier Farnell

*[http://www.designspark.com/theme/raspberrypi DesignSpark], community site of RS-Components

*[http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]

*[http://www.raspberrymod.com/ Raspberrymod] and [http://www.raspberrypiforums.com/forum RPiforums] Un-Official Raspberry Pi Discussion Boards

*[http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]

*[http://www.worldofpi.com/ World Of Pi] A forum based on all things Raspberry Pi.

*[[RPi Community Magazine]] - User contributed eMagazine, get involved!

*[[RaspberryPi Osdev]] - Hardware specific OS-development community, sitting in freenode.net#raspberrypi-osdev.

|}

==About the RPi Wiki==

'''Do not be afraid to add your bit, content is vital for the wiki to function.'''

[[File:Rasp_turn_around.gif|200px|thumb|right|A 3D rendering of the Raspberry Pi logo by forum user Antario. [http://www.raspberrypi.org/forum/projects-and-collaboration-general/raspberry-pi-3d-logo-animation Source]]]
This wiki is '''open''' for the community. You are encouraged to sign up and add your own projects, guides and correct anything within it. It is important that users like you continue to add to and grow this wiki, that way others will be able to come and do the same making the wiki a valuable resource. See [[Help:Editing | Help Editing The Wiki]] and the [[Special:Upload | Upload File]] link (on the left sidebar) to reference images.
Have a look at our [[RPi Wiki Best Practice|Guidelines]] and then you are free to go !

=== Translations ===

The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:

* English: [[R-Pi Hub]]
* French: [[FR:R-Pi Hub]]
* German: [[DE:R-Pi Hub]]
* Greek: [[EL:R-Pi Hub]]
* Hungarian: [[HU:R-Pi Hub]]
* Japanese: [[JP:R-Pi_Hub]]
* Polish: [[PL:R-Pi_Hub]]
* Portugese: [[pt-BR:Raspberry Pi Board]]
* Romanian: [[RO:R-Pi_Hub]]
* Russian: [[RU:RaspberryPiBoard]]
* Українська: [[UA:R-Pi Hub]]
* Spanish: [[ES:R-Pi Hub]]
* Italiano: [[IT:R-Pi Hub]]
* Chinese:[[CH:R-Pi Hub]]
* Hebrew:[[HE:R-Pi Hub]]
* 한국어:[[KR:R-Pi Hub]]

Any help translating would be greatly appreciated. Thank you to those who have already contributed!

===Admins/Contributors===

Please see the [[Talk:R-Pi_Hub|Talk]] page for outstanding issues and discussions regarding the RPi Hub and related pages. 
Also , have look at [[RPi Wiki Best Practice]]. You can discuss the recommendations
[[Talk:RPi Wiki Best Practice | here ]] .

To share your thoughts, comments, thanks and interesting articles, see our [[RPi Visitor Book |Visitor Book]].

''Big thanks to elinux.org and their groups for the wiki space and content from which these pages have been grown.''

=References=
<references/>

{{Template:Raspberry Pi}}
[[Category:RaspberryPi]]