<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://elinux.org/skins/common/feed.css?303"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://elinux.org/api.php?action=feedcontributions&amp;user=Md84419&amp;feedformat=atom</id>
		<title>eLinux.org - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="http://elinux.org/api.php?action=feedcontributions&amp;user=Md84419&amp;feedformat=atom"/>
		<link rel="alternate" type="text/html" href="http://elinux.org/Special:Contributions/Md84419"/>
		<updated>2013-05-19T14:43:52Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.21alpha</generator>

	<entry>
		<id>http://elinux.org/RPi_VerifiedPeripherals</id>
		<title>RPi VerifiedPeripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_VerifiedPeripherals"/>
				<updated>2012-05-08T18:56:58Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Linux]]&lt;br /&gt;
[[Category: ARM Development Boards]]&lt;br /&gt;
[[Category: Broadcom]]&lt;br /&gt;
[[Category: Development Boards]]&lt;br /&gt;
[[Category: RaspberryPi]]&lt;br /&gt;
[[Category: Education]]&lt;br /&gt;
{{Template: RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
&lt;br /&gt;
19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the default Debian distribution unless stated otherwise. A suggested suffix markup scheme is as follows:&lt;br /&gt;
&lt;br /&gt;
* (A) - Relates to model A production board&lt;br /&gt;
* (B) - Relates to model B production board&lt;br /&gt;
* (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different&lt;br /&gt;
* No markup - relates to all production boards&lt;br /&gt;
&lt;br /&gt;
''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247]''&lt;br /&gt;
&lt;br /&gt;
If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}&lt;br /&gt;
&lt;br /&gt;
== Powered USB Hubs ==&lt;br /&gt;
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.&lt;br /&gt;
&lt;br /&gt;
===Working USB Hubs===&lt;br /&gt;
*'''Targus'''&lt;br /&gt;
** ACH81xx 7-port powered hub. 5V 3A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wifi Dongles)&lt;br /&gt;
*'''Newlink'''&lt;br /&gt;
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5V 1A&lt;br /&gt;
*'''Logik'''&lt;br /&gt;
** LP4HUB10 4-Port USB Hub&lt;br /&gt;
&lt;br /&gt;
===Problem USB Hubs===&lt;br /&gt;
*'''Unbranded / Multiple Brands'''&lt;br /&gt;
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably''due to an inadequate power supply.&lt;br /&gt;
** Generic 7-port black hub with Genesys Logic GL850A chipset&lt;br /&gt;
&lt;br /&gt;
== USB Remotes ==&lt;br /&gt;
* [https://www.google.com/search?q=tranksung+TS-Y150 Tranksung TS-Y150] USB RF Keyboard and air mouse (B)&lt;br /&gt;
&lt;br /&gt;
== USB Keyboards ==&lt;br /&gt;
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work.  &lt;br /&gt;
=== Working USB Keyboards ===&lt;br /&gt;
The following is a list of specific keyboards known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* '''Acer'''&lt;br /&gt;
** Compact Keyboard KU-0906 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Apple'''&lt;br /&gt;
** Apple Keyboard (109 keys) A1048&lt;br /&gt;
&lt;br /&gt;
* '''Cerulian''' &lt;br /&gt;
** Mini wireless keyboard and mouse deskset (B)&lt;br /&gt;
&lt;br /&gt;
* '''Dell'''&lt;br /&gt;
** SK-8135 (B)&lt;br /&gt;
** SK-8115 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Fujitsu Siemens''' &lt;br /&gt;
**KB SC USB UK (!)&lt;br /&gt;
&lt;br /&gt;
* '''Genius'''&lt;br /&gt;
** KB-06XE (K639) (B)&lt;br /&gt;
&lt;br /&gt;
* '''Lenovo'''&lt;br /&gt;
** SK-8825 UK (B)&lt;br /&gt;
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)&lt;br /&gt;
&lt;br /&gt;
* '''Logitech''' &lt;br /&gt;
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)&lt;br /&gt;
** Wii wireless keyboard KG-0802 (!)&lt;br /&gt;
** C-BG17-Dual Wireless keyboard and mouse with wired USB received (B)&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
**Comfort Curve Keyboard 2000 v1.0 (Debian 13-Apr-2012 on Production Model B)&lt;br /&gt;
&lt;br /&gt;
*'''Riitek'''&lt;br /&gt;
**RT-MWK03 mini wireless keyboard &amp;amp; trackpad&lt;br /&gt;
&lt;br /&gt;
*'''Tesco'''&lt;br /&gt;
**Value Keyboard VK109 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Trust'''&lt;br /&gt;
** Trust 17916 Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Xenta'''&lt;br /&gt;
** 2.5Ghz Wireless Multimedia Entertainment Keyboard with Touchpad (B)&lt;br /&gt;
&lt;br /&gt;
===Problem USB Keyboards===&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (!)&lt;br /&gt;
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)&lt;br /&gt;
* '''Novatech'''&lt;br /&gt;
** (B)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
* '''Unbranded'''&lt;br /&gt;
** model no. HK-6106 (B) &amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
* '''Levono/IBM'''&lt;br /&gt;
** 04b3:301b IBM Corp. SK-8815 Keyboard, [http://www.element14.com/community/docs/DOC-44703 conflicting behavior] with USB wifi adapters (B)&lt;br /&gt;
* '''Logitech'''&lt;br /&gt;
** model K120, [http://www.element14.com/community/docs/DOC-44703 conflicting behavior] with USB wifi adapters (B)&lt;br /&gt;
&lt;br /&gt;
== USB Mouse devices ==&lt;br /&gt;
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.  &lt;br /&gt;
&lt;br /&gt;
===Working USB Mouse Devices===&lt;br /&gt;
The following is a list of specific mouse devices known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* '''Dell'''&lt;br /&gt;
** M-UVDEL1 (B)&lt;br /&gt;
** M056U0A (B)&lt;br /&gt;
&lt;br /&gt;
* '''Genius'''&lt;br /&gt;
** GM-04003A (B)&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
** Compact optical mouse 500 V2.0 (B)&lt;br /&gt;
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)&lt;br /&gt;
** Microsoft Intellimouse Optical Mouse&lt;br /&gt;
&lt;br /&gt;
* '''Logitech'''&lt;br /&gt;
** M505 USB wireless laser, model no: 910-001324 (B)&lt;br /&gt;
** M-BJ79 (B)&lt;br /&gt;
** LX-700 Cordless Desktop Receiver (B)&lt;br /&gt;
&lt;br /&gt;
* '''Tesco'''&lt;br /&gt;
** Wired optical mouse M211 (B)&lt;br /&gt;
&lt;br /&gt;
== USB WiFi Adapters ==&lt;br /&gt;
&lt;br /&gt;
See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing&lt;br /&gt;
&lt;br /&gt;
There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.&lt;br /&gt;
&lt;br /&gt;
===Working USB Wifi Adapters===&lt;br /&gt;
&lt;br /&gt;
These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.&lt;br /&gt;
&lt;br /&gt;
* '''3COM'''&lt;br /&gt;
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)&lt;br /&gt;
* '''Asus'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 USB-N10] USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix &amp;amp; Arch, must compile if Debian, requires firmware-realtek; todo: test with mouse (B)&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 USB-N13] USB ID 0b05:17ab, using compiled manufacturer driver for RTL8192CU; todo: test with mouse (B)&lt;br /&gt;
* '''D-Link'''&lt;br /&gt;
** AirPlus G DWL-G122 (rev. E). USB ID 07d1:3c0f, Ralink RT2870. On Debian requires the &amp;lt;code&amp;gt;firmware-ralink&amp;lt;/code&amp;gt; package from the &amp;lt;code&amp;gt;squeeze-firmware&amp;lt;/code&amp;gt; non-free repository.&lt;br /&gt;
* '''Edimax'''&lt;br /&gt;
** [http://www.edimax.co.uk/en/produce_detail.php?pd_id=328&amp;amp;pl1_id=1&amp;amp;pl2_id=44 EW-7811Un] USB ID 7392:7811, RTL8192CU, use driver for &amp;lt;code&amp;gt;Asus USB-N13&amp;lt;/code&amp;gt; above (same chipset), driver blob [http://www.electrictea.co.uk/rpi/8192cu.tar.gz download] via [http://www.element14.com/community/docs/DOC-44703 Element14], works with WPA2-AES-CCMP (B)&lt;br /&gt;
* '''IOGear'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix &amp;amp; Arch, must compile if Debian, requires firmware-realtek; warning: conflict with mouse (B)&lt;br /&gt;
* '''Netgear''' &lt;br /&gt;
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the &amp;lt;code&amp;gt;firmware-atheros&amp;lt;/code&amp;gt; package from the &amp;lt;code&amp;gt;squeeze-backports&amp;lt;/code&amp;gt; non-free repository  (!)&lt;br /&gt;
** WG111v2: Realtek rtl8187 chipset (!)&lt;br /&gt;
* '''Sempre'''&lt;br /&gt;
** Sempre Wireless USB stick WU300-2: USB ID 0bda:8172, Realtek r8712u driver + firmware-realtek package. Module is not shipped in Debian image, but can be found here: http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/&lt;br /&gt;
* '''Tenda''' &lt;br /&gt;
** USB 11n adapter on a G network: Ralink  2870/3070 driver (!)&lt;br /&gt;
* '''TP-Link'''&lt;br /&gt;
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw) (B)&lt;br /&gt;
&lt;br /&gt;
* '''ZyXEL'''&lt;br /&gt;
** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)&lt;br /&gt;
* '''Generic'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter] USB ID 148f:2573, tested on debian; must install firmware-ralink package (B)&lt;br /&gt;
** Ralink Technology, Corp. RT5370 Wireless Adapter (USB ID 148f:5370)&lt;br /&gt;
&lt;br /&gt;
===Problem USB Wifi Adapters===&lt;br /&gt;
&lt;br /&gt;
These adapters were tested and found to have issues the Raspberry Pi.&lt;br /&gt;
&lt;br /&gt;
* '''Trendnet'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 TEW-424UB] USB ID: 0bda:8189; tested on Debian, Fedora &amp;amp; Arch; rtl8187 driver; conflicts with some keyboards (B)&lt;br /&gt;
* '''BlueProton'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 BT3] USB ID: 0bda:8187; tested on Debian, Fedora &amp;amp; Arch; rtl8187 driver; conflicts with some keyboards (B)&lt;br /&gt;
* '''TP-Link'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 TL-WN821N] USB ID: 0cf3:7015; tested on Debian; requires [http://linuxwireless.org/download/htc_fw/1.3/htc_7010.fw htc_7010.fw] firmware; ath9k_htc driver; conflicts with some keyboards (B)&lt;br /&gt;
&lt;br /&gt;
== USB Bluetooth adapters ==&lt;br /&gt;
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)&lt;br /&gt;
&lt;br /&gt;
== USB Ethernet adapters ==&lt;br /&gt;
&lt;br /&gt;
== USB IR Receivers==&lt;br /&gt;
&lt;br /&gt;
== USB TV Tuners==&lt;br /&gt;
*August&lt;br /&gt;
**DVB-T205, based on rtl2832u chipset, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD &amp;amp; SD.&lt;br /&gt;
&lt;br /&gt;
== USB Webcam ==&lt;br /&gt;
&lt;br /&gt;
== USB UART adapters ==&lt;br /&gt;
The USB UART adapter is used to access the serial console of the Raspberry Pi from a development host such as a laptop or desktop PC.  The USB end connects to the PC and the UART header end connects to the USB.  While it is possible to connect the USB end to another Raspberry Pi, this configuration has not been tested unless explicitly mentioned against an individual entry below.&lt;br /&gt;
&lt;br /&gt;
== Power adapters ==&lt;br /&gt;
The Raspberry Pi uses a standard MicroUSB power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.&lt;br /&gt;
&lt;br /&gt;
===Wired Adaptors===&lt;br /&gt;
* '''All HTC mobile phone adaptors'''&lt;br /&gt;
** TCP-300 Single port USB mains phone charger 5v 1A (B)&lt;br /&gt;
* '''Blackberry'''&lt;br /&gt;
** Charger for Pearl Flip 8220, Bold 9600 (B)&lt;br /&gt;
** Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003, Output 700mA @ 5V (B)&lt;br /&gt;
* '''Samsung'''&lt;br /&gt;
** Charger for Galaxy SII 5V 0.7A&lt;br /&gt;
* '''Maplin Electronics'''&lt;br /&gt;
** 5v 1000mA dual USB power supply, model number H25B-MT-K2&lt;br /&gt;
&lt;br /&gt;
===External Batteries===&lt;br /&gt;
* ''' New Trent'''&lt;br /&gt;
** iCurve IMP70D 7000mAh (Approx 12hrs from full charge)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Display adapters ==&lt;br /&gt;
While technically there shouldn't be a difference between one (for example) HDMI-&amp;gt;DVI adapter and another, it would be nice to have a list of working ones so if necessary, you can just buy a recommended one (contributors should give links) instead of hunting around. This section could contain information about verified HDMI-&amp;gt;DVI, CompositeRCA-&amp;gt;SCART, CompositeRCA-&amp;gt;VGA ''boxes/chipsets'', and HDMI-&amp;gt;VGA ''boxes/chipsets''.&lt;br /&gt;
&lt;br /&gt;
===HDMI-&amp;gt;DVI-D===&lt;br /&gt;
None explicitly mentioned &lt;br /&gt;
===HDMI-&amp;gt;VGA converter boxes===&lt;br /&gt;
According to user &amp;quot;asb&amp;quot; -- http://www.amazon.co.uk/gp/product/B007KEIRNG -- the Neewer HDMI to VGA adapter works with the Pi.&lt;br /&gt;
&lt;br /&gt;
This adapter (from Kanaan) -- http://www.amazon.co.uk/KanaaN-Adapter-Converter-Cable-Resolutions/dp/B007QT0NNW -- is working. Quality not wonderful, but certainly usable, on 1400x900 monitor.&lt;br /&gt;
&lt;br /&gt;
===Composite-&amp;gt;SCART===&lt;br /&gt;
None explicitly mentioned &lt;br /&gt;
===Composite-&amp;gt;VGA converter boxes===&lt;br /&gt;
None explicitly mentioned, and they are pricey so the chances of someone buying one to test functionality is low&lt;br /&gt;
== SD cards ==&lt;br /&gt;
&lt;br /&gt;
Note that manufacturers change their designs over time, even as the specs stay the same. (E.g. an ACME 8 GB class 4 card manufactured in 2011 might work, while one manufactured in 2012 might not.)&lt;br /&gt;
For this reason, please specify product numbers in the lists below, when possible.&lt;br /&gt;
&lt;br /&gt;
===Working SD Cards===&lt;br /&gt;
* '''Adata''' &lt;br /&gt;
** Class 10 8GB (AUSDH8GCL10-R)&lt;br /&gt;
* '''Dane-Elec''' &lt;br /&gt;
** 16Gb class 4&lt;br /&gt;
* '''Integral''' &lt;br /&gt;
** Ultima Pro 16GB Class 10 (20MB/s)&lt;br /&gt;
* '''Kingston''' &lt;br /&gt;
** SD 2GB (no class mentioned)&lt;br /&gt;
** SDHC 8GB class 4&lt;br /&gt;
** SDHC 8GB class 10 (ultimateX 120X)&lt;br /&gt;
* '''Kodak''' &lt;br /&gt;
** SDHC 8GB Class 4&lt;br /&gt;
* '''Lexar''' &lt;br /&gt;
** 4GB SDHC Class4 (Boots consistently and no error messages in log after 1/2 hour use )&lt;br /&gt;
** 8GB SDHC Class4&lt;br /&gt;
** 4GB Platinum II SDHC Class 6 (from [http://www.microcenter.com/single_product_results.phtml?product_id=0350735 Microcenter])&lt;br /&gt;
** 8GB Platinum II SDHC Class 6&lt;br /&gt;
* '''Microcenter Brand (sold in bins at checkout)'''&lt;br /&gt;
** [http://www.microcenter.com/single_product_results.phtml?product_id=0349728 8GB SDHC Class 10]&lt;br /&gt;
** [http://www.microcenter.com/single_product_results.phtml?product_id=0289508 8GB SDHC Class 4]&lt;br /&gt;
* '''MyMemory''' &lt;br /&gt;
** 8GB SDHC class 10 (MYMESDH8G10) [http://www.mymemory.co.uk/SDHC/MyMemory/MyMemory-8GB-SD-Card-%28SDHC%29---Class-10 MyMemory 8GB class 10]&lt;br /&gt;
* '''Panasonic''' &lt;br /&gt;
** 8GB SDHC class6 (~4.8MB/s read, ~4.4MB/s write, following [[RPi_Performance#SD_card]])&lt;br /&gt;
* '''Peak''' &lt;br /&gt;
** 4GB microSDHC class4 (MMBTR04GUBCA-ME) tested with Arch&lt;br /&gt;
* '''PNY''' &lt;br /&gt;
** 4GB SDHC Class 4&lt;br /&gt;
* '''Samsung''' &lt;br /&gt;
** SDHC 4GB&lt;br /&gt;
** SDHC 8GB&lt;br /&gt;
** SDHC 16GB Class 6 (MB-SSAGAEU)&lt;br /&gt;
* '''SanDisk''' &lt;br /&gt;
** Ultra 2GB Class 4 (15MB/s)&lt;br /&gt;
** Ultra II SD 2GB class 4&lt;br /&gt;
** Ultra II SDHC 4GB class 4&lt;br /&gt;
** 2GB (non SDHC but with a circle 2 --probably class 2), writes at 3.5 Mb/s&lt;br /&gt;
** 2GB, white &amp;quot;SanDisk for Wii&amp;quot; branded, no class mentioned&lt;br /&gt;
** Ultra SDHC 4GB class 6 (SDSDH-004G-U46 - BH1136121837G, BH1130521822D)&lt;br /&gt;
** Ultra SDHC 8GB class 6 (SDSDH-008G-U46 - BI1131222083D) (could be problematic, see below)&lt;br /&gt;
** 4/8GB Micro SDHC (with Sandisk MicroSD =&amp;gt; SD adaptor) Class 4&lt;br /&gt;
** 4GB Micro SDHC (with Sandisk MicroSD =&amp;gt; SD adaptor) Class 2&lt;br /&gt;
** 4GB SHDC (class 4)&lt;br /&gt;
** 8GB SDHC (class 4); writes at ~1.5MB/s&lt;br /&gt;
** 16GB SDHC (class 4)&lt;br /&gt;
** 32GB SDHC Class 6&lt;br /&gt;
** Extreme III 2GB (BE0715105083B)&lt;br /&gt;
* '''Sony'''&lt;br /&gt;
** SDHC 4GB class 4 (SF-4B4)&lt;br /&gt;
* '''Transcend''' &lt;br /&gt;
** SDHC 16GB class 10&lt;br /&gt;
** SDHC 8GB class 10 (TS8GSDHC10) [http://www.mymemory.co.uk/SDHC/Transcend/Transcend-8GB-SD-Card-%28SDHC%29---Class-10- Transcend 8G class 10]&lt;br /&gt;
** SDHC 8GB class 6 (~5.8 MB/s read/write following [[RPi_Performance#SD_card]])&lt;br /&gt;
** SDHC 4GB class 4 - we've found these to work without any errors and offer reasonable performance&lt;br /&gt;
** SDHC 4GB class 4 (TS4GSDHC4 - BH1130821915G)&lt;br /&gt;
** SDHC 4GB class 6 (TS4GSDHC6) - no problems. &lt;br /&gt;
** SDHC 8GB class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)&lt;br /&gt;
** SDHC 16GB class 6 (TS16GSDHC6)&lt;br /&gt;
** SDHC 8GB class 4&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).&lt;br /&gt;
&lt;br /&gt;
===Problem SD Cards===&lt;br /&gt;
&lt;br /&gt;
There are issues with most Class 10 SDHC cards, apparently due to a bug in the Broadcom bootloader.[http://www.raspberrypi.org/forum/general-discussion/class-10-sd-cards-on-the-production-boards/page-3/#p39181]&lt;br /&gt;
&lt;br /&gt;
This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.&lt;br /&gt;
&lt;br /&gt;
* '''Panasonic''' &lt;br /&gt;
** Class 10 8GB (RP-SDU08GD1K) mmc0: timeout waiting for hardware interrupt [http://www.mymemory.co.uk/SDHC/Panasonic/Panasonic-8GB-UHS-1-London-2012-Collection-SDHC-Card---Class-10 Panasonic 8GB Class 10]&lt;br /&gt;
* '''Patriot''' &lt;br /&gt;
** Class 10 8GB (PSF8GSDHC10)&lt;br /&gt;
* '''SanDisk''' &lt;br /&gt;
** Ultra SDHC Class 4 4GB (BH1028516076D) - Intermitant booting ( 1/50 power on ), random timeout messages when it does boot.&lt;br /&gt;
** Ultra Class 6 8GB (B11201421964G)&lt;br /&gt;
** Ultra SDHC I 8GB Class 6 (BI1201221964G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )&lt;br /&gt;
** Ultra SDHC 8GB class 6 (SDSDH-008G-U46 - BI1131222083D) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )&lt;br /&gt;
** Mobile Ultra microSDHC 4 GB Class 6 - Boots kernel but won't run init ( mmc timeout waiting for interrupt )&lt;br /&gt;
** Ultra Class 6 16GB (BL1202021933G)&lt;br /&gt;
** Extreme Class 6 4Gb (BH0822411730D)&lt;br /&gt;
** Extreme Class 6 8GB (BI1101116253G)&lt;br /&gt;
** Extreme Class 10 8GB (BI1108716254G)&lt;br /&gt;
** Extreme Pro Class 10 8GB - Boots kernel but won't run init ( mmc timeout waiting for interrupt )&lt;br /&gt;
* '''Kingston''' &lt;br /&gt;
** SDHC 4GB class 4 (works but gets mmc errors: mmc0: final write to SD card still running) Russel King might have a kernel patch for this problem.&lt;br /&gt;
* '''Integral'''&lt;br /&gt;
** Ultima Pro 16GB SDHC Class 6 (SH016GAA2BB)&lt;br /&gt;
&lt;br /&gt;
The usual warnings against less reputable sellers (such as Ebay merchants) apply.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):&lt;br /&gt;
&lt;br /&gt;
 mmc0: timeout waiting for hardware interrupt&lt;br /&gt;
&lt;br /&gt;
=== Benchmarks ===&lt;br /&gt;
&lt;br /&gt;
* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html&lt;br /&gt;
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11&lt;br /&gt;
&lt;br /&gt;
== Foreign Language Translations ==&lt;br /&gt;
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references&amp;gt;&lt;br /&gt;
&amp;lt;/references&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_schematic_errata</id>
		<title>RPi schematic errata</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_schematic_errata"/>
				<updated>2012-05-07T09:28:34Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
Back to [[RPi_Hardware#Components]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Raspberry Pi schematic errata =&lt;br /&gt;
&lt;br /&gt;
The (partial) datasheet was published here: [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf | at raspberrypi.org] and [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf | a mirror]&lt;br /&gt;
&lt;br /&gt;
It has a couple of typos. Some more serious than others. &lt;br /&gt;
&lt;br /&gt;
Let's gather those schematic typos and errors here. &lt;br /&gt;
&lt;br /&gt;
The quality of the schematic is high. It looks like it contains the information that designers need. &lt;br /&gt;
&lt;br /&gt;
==Schematic v1.0 (Model B)==&lt;br /&gt;
&lt;br /&gt;
===Unverified typos===&lt;br /&gt;
&lt;br /&gt;
* On sheet 3, area C9, should that not be a (B) instead of (A) under the “IC3?”&lt;br /&gt;
* Also D10 close by&lt;br /&gt;
* R22,23,24,25 &amp;amp; C28 all missing (B) designation&lt;br /&gt;
* Also on sheet 3: R38 (area B8), R28 (area H5), C49 (area A1) and C29 (area A2) also appear to be missing (B) designation&lt;br /&gt;
* [[RPi_Hardware#Components]] says that D5 is yellow, but the schematic says D5 is green. Could somebody who actually has a production board check? -&amp;gt; The OK led is definitively GREEN. -- REW. &lt;br /&gt;
* Sheet 4 D6: DSI0 should be DSI1&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* there is an extra line drawn across R22-R25.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Verified typos===&lt;br /&gt;
&lt;br /&gt;
* Possible silk-screen typo rather than schematic typo: According to both the schematic and the LAN9512 datasheet, D9 (yellow LED) is ON if the link-speed is 100Mbs. But on the silk-screen it's labelled as &amp;quot;10M&amp;quot; rather than &amp;quot;100M&amp;quot; ? -&amp;gt; YES it is marked 10M due to space constraints. 100M wouldn't have fit. -- REW &amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/ethernet-10m-only&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_schematic_errata</id>
		<title>RPi schematic errata</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_schematic_errata"/>
				<updated>2012-05-07T09:27:39Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Schematic v1.0 (Model B) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
Back to [[RPi_Hardware#Components]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Raspberry Pi schematic errata =&lt;br /&gt;
&lt;br /&gt;
The (partial) datasheet was published here: [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf | at raspberrypi.org] and [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf | a mirror]&lt;br /&gt;
&lt;br /&gt;
It has a couple of typos. Some more serious than others. &lt;br /&gt;
&lt;br /&gt;
Let's gather those schematic typos and errors here. &lt;br /&gt;
&lt;br /&gt;
The quality of the schematic is high. It looks like it contains the information that designers need. &lt;br /&gt;
&lt;br /&gt;
==Schematic v1.0 (Model B)==&lt;br /&gt;
&lt;br /&gt;
===Unverified typos===&lt;br /&gt;
&lt;br /&gt;
* On sheet 3, area C9, should that not be a (B) instead of (A) under the “IC3?”&lt;br /&gt;
* Also D10 close by&lt;br /&gt;
* R22,23,24,25 &amp;amp; C28 all missing (B) designation&lt;br /&gt;
* Also on sheet 3: R38 (area B8), R28 (area H5), C49 (area A1) and C29 (area A2) also appear to be missing (B) designation&lt;br /&gt;
* [[RPi_Hardware#Components]] says that D5 is yellow, but the schematic says D5 is green. Could somebody who actually has a production board check? -&amp;gt; The OK led is definitively GREEN. -- REW. &lt;br /&gt;
* Sheet 4 D6: DSI0 should be DSI1&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* there is an extra line drawn across R22-R25.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Verified typos===&lt;br /&gt;
&lt;br /&gt;
* Possible silk-screen typo rather than schematic typo: According to both the schematic and the LAN9512 datasheet, D9 (yellow LED) is ON if the link-speed is 100Mbs. But on the silk-screen it's labelled as &amp;quot;10M&amp;quot; rather than &amp;quot;100M&amp;quot; ? -&amp;gt; YES it is marked 10M due to space constraints. 100M wouldn't have fit. -- REW &amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/ethernet-10m-only&amp;lt;/ref&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hardware</id>
		<title>RPi Hardware</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hardware"/>
				<updated>2012-05-06T17:48:56Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Power */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]&lt;br /&gt;
The first product is the size of a credit card, and is designed to plug into a TV or HDMI monitor. It comes in two variants, model A and B, with B having more features. The expected price is $25 for model A and $35 for model B. The [[Rpi Low-level peripherals| GPIO pins]] on each board allow the use of optional [[Rpi expansion boards|expansion boards]].&lt;br /&gt;
&lt;br /&gt;
Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].&lt;br /&gt;
&lt;br /&gt;
==Specifications==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!&lt;br /&gt;
! Model A&lt;br /&gt;
! Model B&lt;br /&gt;
|-&lt;br /&gt;
| Target price:&amp;lt;ref name=&amp;quot;faq&amp;quot; &amp;gt;http://www.raspberrypi.org/faqs&amp;lt;/ref&amp;gt;&lt;br /&gt;
| US$25 (GBP £16)&lt;br /&gt;
| US$35 (GBP £22)&lt;br /&gt;
|-&lt;br /&gt;
| System-on-a-chip (SoC):&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom BCM2835 (CPU + GPU + SDRAM)&lt;br /&gt;
|-&lt;br /&gt;
| CPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 700&amp;amp;nbsp;MHz ARM11 ARM1176JZF-S core&lt;br /&gt;
|-&lt;br /&gt;
| GPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode &lt;br /&gt;
|-&lt;br /&gt;
| Memory (SDRAM)iB&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 256 MiB (previously listed as 128MiB for model A, but an upgrade to 256MiB was announced on 29 Feb 2012)&lt;br /&gt;
|-&lt;br /&gt;
| USB 2.0 ports:&lt;br /&gt;
| 1(provided by the BCM2835)&lt;br /&gt;
| 2 (via integrated USB hub)&lt;br /&gt;
|-&lt;br /&gt;
| Video outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Composite video|Composite RCA, HDMI (not at the same time)&lt;br /&gt;
|-&lt;br /&gt;
| Audio outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | TRS connector|3.5 mm jack, HDMI&lt;br /&gt;
|-&lt;br /&gt;
| Audio inputs:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | none, but a USB mic or sound-card could be added&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Storage:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Secure Digital|SD / MMC / SDIO card slot&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Network:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| None&lt;br /&gt;
| 10/100 wired Ethernet RJ45&lt;br /&gt;
|-&lt;br /&gt;
| Low-level peripherals:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S&amp;lt;ref name=&amp;quot;i2s&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;, Universal asynchronous receiver/transmitter (UART)&lt;br /&gt;
|-&lt;br /&gt;
| Real-time clock:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | None&lt;br /&gt;
|-&lt;br /&gt;
| Power ratings (provisional, from alpha board):&lt;br /&gt;
| 500mA, (2.5 Watt) &amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| 700mA, (3.5 Watt)&lt;br /&gt;
|-&lt;br /&gt;
| Power source:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 5V via Micro USB or GPIO header&lt;br /&gt;
|-&lt;br /&gt;
| Size:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 85.60mm x 53.98mm&amp;lt;ref&amp;gt;[http://www.raspberrypi.org/archives/344 Final PCB artwork]&amp;lt;/ref&amp;gt; (3.370 × 2.125 inch)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Components==&lt;br /&gt;
[[File:Raspi-Model-AB-Mono-2-699x1024.png|400px|thumb|right|A diagram denoting the places of the different components on the Rpi, made by Paul&lt;br /&gt;
Beech, edited to show 256MB ram for both boards]]&lt;br /&gt;
(Provisional - some of the expansion interfaces won't be available on production boards)&lt;br /&gt;
(PCB IDs are those of the Model B Beta board) &lt;br /&gt;
&lt;br /&gt;
* SoC: [http://www.broadcom.com/products/BCM2835 Broadcom BCM2835 media processor] ([http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf datasheet], [[BCM2835 datasheet errata]], [[RPi_BCM2835_Pinout|unofficial pinout]]) system-on-chip featuring:&lt;br /&gt;
** CPU core: [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0301h/DDI0301H_arm1176jzfs_r0p7_trm.pdf ARM1176JZF-S] ARM11 core clocked at 700MHz; ARM VFP.  The ARM11 core implements the ARMv6 Architecture.  For details on ARM instruction sets and naming conventions, see [http://en.wikipedia.org/wiki/ARM_architecture ARM architecture] and [http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores List of ARM microprocessor cores].&lt;br /&gt;
** GPU core: a Broadcom [http://en.wikipedia.org/wiki/Videocore VideoCore] IV GPU providing OpenGL ES 1.1, OpenGL ES 2.0, hardware-accelerated OpenVG 1.1, Open EGL, OpenMAX and 1080p30 H.264 high-profile decode.  There are 24 GFLOPS of general purpose compute and a bunch of texture filtering and DMA infrastructure.  Eben worked on the architecture team for this and the Raspberry Pi team are looking at how they can make some of the proprietary features available to application programmers&lt;br /&gt;
** DSP core: There is a DSP, but there isn't currently a public API (Liz thinks the BC team are keen to make one available at some point)&lt;br /&gt;
** 256MiB of ([http://www.hynix.com/products/mobile/view.jsp?info.ramKind=28&amp;amp;info.serialNo=H9TKNNN2GDMPLR&amp;amp;posMap=MobileDDR2 Hynix MobileDDR2]) SDRAM.  The RAM is physically stacked on top of the Broadcom media processor (package-on-package technology)&lt;br /&gt;
* LAN9512 ([http://www.smsc.com/media/Downloads_Public/Data_Briefs/9512db.pdf Data Brief] | [http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf Data Sheet])'''(Model B)''' providing:&lt;br /&gt;
** 10/100Mb Ethernet (Auto-MDIX)&amp;lt;ref name=autoMDIX&amp;gt;[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]&amp;lt;/ref&amp;gt;&lt;br /&gt;
** 2x USB 2.0 &lt;br /&gt;
* S1: Micro USB power jack (5v - Power Only)&lt;br /&gt;
* S2: [http://www.mipi.org/specifications/display-interface DSI] interface.  15-pin surface mounted flat flex connector, providing two data lanes, one clock lane, 3.3V and GND.&lt;br /&gt;
* S3: HDMI connector providing type A HDMI 1.3a out&lt;br /&gt;
* S4: Composite Video connector: RCA&lt;br /&gt;
* S5: MIPI [http://www.mipi.org/specifications/camera-interface CSI-2] interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S6: Audio connector: 3.5mm stereo jack (output only)&lt;br /&gt;
* S8: SD/MMC/SDIO memory card slot (underside)&lt;br /&gt;
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''&lt;br /&gt;
* P1: 26-pin 2.54mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]&lt;br /&gt;
** 8 GPIOs at 3v3&lt;br /&gt;
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3&lt;br /&gt;
** I2C interface (3v3); or 2 GPIOs at 3v3&lt;br /&gt;
** SPI interface (3v3); or 5 GPIOs at 3v3&lt;br /&gt;
** 3v3, 5v and GND supply pins&lt;br /&gt;
** ARM JTAG (if pins are reconfigured in software)&lt;br /&gt;
** Second I2C interface (3v3) (if pins are reconfigured in software)&lt;br /&gt;
** I2S interface (if pins are reconfigured in software, hardware hack may be required&amp;lt;ref name=&amp;quot;i2s&amp;quot;/&amp;gt;)&lt;br /&gt;
** 6 pins reserved for future use&lt;br /&gt;
* P2 8-pin 2.54mm header expansion providing GPU JTAG (ARM11 pinout, pin 7 is nofit for locating)&lt;br /&gt;
* P3: 7-pin 2.54mm header expansion (header not fitted), providing LAN9512 JTAG (pin 6 is nofit for locating)&lt;br /&gt;
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''&lt;br /&gt;
* TP1 and TP2: Test Points giving access to +5V and GND respectively&lt;br /&gt;
* 5 Status LEDs&amp;lt;ref name=&amp;quot;PCBs&amp;quot;&amp;gt;[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDs&amp;quot;&amp;gt;[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDsGPIO&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/what-do-the-status-indicator-leds-indicate-the-status-of Forum:What do the status indicator LEDs indicate the status of?]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;OKGreen&amp;quot;&amp;gt;[[RPi_schematic_errata]]&amp;lt;/ref&amp;gt;:&lt;br /&gt;
** D5(Green) - OK  - SDCard Access (via GPIO16)&lt;br /&gt;
** D6(Red) - PWR - 3.3V Power&lt;br /&gt;
** D7(Green) - FDX - Full Duplex (LAN) '''(Model B)'''&lt;br /&gt;
** D8(Green) - LNK - Link/Activity (LAN) '''(Model B)'''&lt;br /&gt;
** D9(Yellow) - 10M - 10/100Mbit (LAN) '''(Model B)'''&lt;br /&gt;
&lt;br /&gt;
* Board size: 85.60mm x 53.98mm.  Overall height expected to be less than 25mm. &amp;lt;ref name=&amp;quot;artwork&amp;quot;&amp;gt;http://www.raspberrypi.org/archives/344&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Weight: &amp;lt;40g? (Alpha board weighs ~55g &amp;lt;ref&amp;gt;http://www.raspberrypi.org/?page_id=43&amp;amp;mingleforumaction=viewtopic&amp;amp;t=285.0&amp;lt;/ref&amp;gt;)&lt;br /&gt;
* 6 layer PCB &amp;lt;ref name=&amp;quot;artwork&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Schematic / Layout==&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot]&lt;br /&gt;
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot, labelled version]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1-300x225.jpg Low-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back-300x225.jpg Low-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1.jpg High-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back.jpg High-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://www.andrewscheller.co.uk/bare_pcb.xcf GIMP project containing properly aligned versions of the high-res PCB photos and Gerbers on separate layers (94MB)]&lt;br /&gt;
* [[Media:RPi beta xray.jpg|&amp;quot;Xray style&amp;quot; image of the beta board, created from the above GIMP project]] | [[RPi_xray_wallpapers|desktop wallpapers]]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official schematics PDF] | [[RPi_schematic_errata|errata]] | [[RPi_schematics_breakdown|breakdown]]&lt;br /&gt;
&lt;br /&gt;
==Power==&lt;br /&gt;
&lt;br /&gt;
The board takes fixed 5V input, (with the 1V2 core voltage generated directly from the input using the internal switch-mode supply on the BCM2835 die). &lt;br /&gt;
This permits adoption of the micro USB form factor, which, in turn, prevents the user from inadvertently plugging in out-of-range power inputs; that would be dangerous, since the 5V would go straight to HDMI and output USB ports, even though the problem should be mitigated by some protections applied to the input power: The board provides a polarity protection diode, a voltage clamp, and a self-resetting semiconductor fuse.&lt;br /&gt;
&lt;br /&gt;
Premier Farnell recommend the following power supplies:&lt;br /&gt;
* Model A: 5V dc, 500-700mA&lt;br /&gt;
* Model B: 5V dc, 700-1200mA&lt;br /&gt;
&lt;br /&gt;
Power consumption of the Raspberry Pi device is&lt;br /&gt;
&lt;br /&gt;
* Board A: 5V, 500 mA (2.5W) '''without any devices connected''' (e.g. USB, Ethernet, HDMI)&lt;br /&gt;
* Board B: 5V, 700 mA (3.5W) '''without any devices connected''' (e.g. USB, Ethernet, HDMI) (Is this correct? These [http://www.raspberrypi.org/forum/troubleshooting/usb-hub-sending-power-to-raspberry-pi-through-usb-port/#p68382] links [http://www.raspberrypi.org/forum/general-discussion/raspberry-pi-power-requirements/page-2/#p68224] suggest that the 700mA is only required if &amp;quot;using networking and high-current USB peripherals&amp;quot; [http://www.raspberrypi.org/archives/260].)&lt;br /&gt;
&lt;br /&gt;
You will need to provide a power supply that can provide enough current to power the device plus any connected peripherals, and taking into account inefficiencies of the supply itself and the cable between the power supply and Raspberry Pi.  The community advises opting for a power supply that can supply at least 1A if using USB peripherals or Pi plates that draw more than a few tens of milliamps of current.&lt;br /&gt;
&lt;br /&gt;
*As the 5V rail is brought out in the [[Rpi_Low-level_peripherals | GPIO pins]], you can power the Rpi from there too. You should mind however, that those are ''behind'' the power protection circuitry , so you should provide your own.&lt;br /&gt;
* It is possible to power the Rpi from a powered USB hub the Rpi controls, but only on 'dumb' devices, that allow the port to supply the full current without waiting for the usb device to ask for it[http://www.raspberrypi.org/forum/general-discussion/power-pi-from-usb-hub-connected-to-pi]. As the power input of the Rpi doesn't have its data leads connected, there is no chance for a communication loop of some sorts.&lt;br /&gt;
* POE ([http://nl.wikipedia.org/wiki/Power_over_Ethernet power over ethernet]) is currently not available for the Rpi (but nobody stops you from taking your soldering iron and doing it yourself)&lt;br /&gt;
&lt;br /&gt;
===Power Supply Problems===&lt;br /&gt;
&lt;br /&gt;
There have been a number of problems reported that seem to be caused by inadequate power, this is an attempt to explain what is needed and the consequences of not having enough power.&lt;br /&gt;
&lt;br /&gt;
The power required by the Pi will vary depending on how busy it is and what peripherals are connected.&lt;br /&gt;
* Running a GUI will take more power.&lt;br /&gt;
* The USB devices and Ethernet connection will take power.&lt;br /&gt;
* Running software will take power.&lt;br /&gt;
&lt;br /&gt;
This means that it's difficult to say exactly how much power is needed.  People have reported current requirements of between 300mA and 550mA. But it could in reality take more, especially for short periods. A simple multimeter will not show short surges on the power requirement. A surge in the power requirement for a few milliseconds will not be detectable by a meter but will be enough to cause problems.&lt;br /&gt;
If the board does not get enough power the voltage will drop. If it drops enough parts of the system will run unreliably because data can get corrupted.  The USB IC runs on 5V and handles the USB and Ethernet ports so it's likely that this will be the first thing to fail. Problems seen are unreliable Ethernet connection and unreliable operation of the Keyboard and/or mouse. Each USB port on the Pi has a fuse rated at 140 mA, so any connected USB devices should draw less than this amount of current. Some USB WiFi dongles are known to draw more than 150 mA when configured and active.&lt;br /&gt;
&lt;br /&gt;
There are several reasons why the power to the board may be inadequate:&lt;br /&gt;
* The PSU may not deliver enough power.  Although the maximum power requirement is said to be 700mA, that is with no peripherals connected (USB, Ethernet etc), so a 1000mA PSU should be regarded as a minimum.  This allows some leeway in case the power supply cannot deliver it's full power without the voltage dropping.&lt;br /&gt;
* The PSU is not regulated.&lt;br /&gt;
* The cable connecting the PSU to the Pi may not be good. People have reported cables with 4 ohms resistance on the power connections. At 500mA drain this would reduce a 5V supply to 3V.&lt;br /&gt;
&lt;br /&gt;
====How Can I tell if the power supply is inadequate?====&lt;br /&gt;
&lt;br /&gt;
Common symptoms of an inadequate power supply are&lt;br /&gt;
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.&lt;br /&gt;
* SD card errors at start up seems to be another symptom of poor power.&lt;br /&gt;
&lt;br /&gt;
If you think you have a problem with your power supply, it is a good idea to check the actual voltage&lt;br /&gt;
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board&lt;br /&gt;
to facilitate voltage measurements.&lt;br /&gt;
&lt;br /&gt;
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.  Anything inside, but close to the limits, of this range ''may'' indicate a problem.&lt;br /&gt;
&lt;br /&gt;
[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]&lt;br /&gt;
&lt;br /&gt;
====Things that can cause problems====&lt;br /&gt;
* A USB connection on a TV or PC. The USB power supply specification is for up to 500mA and if the TV implements this then it can cause problems.  The system may work initially but be unreliable because as it becomes more active the power requirement increases.&lt;br /&gt;
* A single supply from a powered hub.  Most hubs seem to deliver more than the specified current but there's no guarantee.  Check the power supply rating, it must be enough to supply everything that's connected to the hub.&lt;br /&gt;
* A power supply that is rated for less than 700mA may work some of the time.&lt;br /&gt;
* Adding a USB hard disk drive. A HDD will take quite a lot of power as it starts, maybe an amp or more. It the power supply for this also supplies the Pi then this could overload things and cause trouble.&lt;br /&gt;
* Some complex keyboards have been reported to take a considerable amount of power, maybe up to 500mA.  The Pi cannot deliver this amount of power.  Simpler budget keyboards may be better. If the system works with no keyboard attached but not with a keyboard then it's worth trying a different, simpler, keyboard.&lt;br /&gt;
&lt;br /&gt;
====Summary====&lt;br /&gt;
&lt;br /&gt;
* If you are having unreliable operation the first thing to do is check your power supply.&lt;br /&gt;
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).&lt;br /&gt;
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.&lt;br /&gt;
* Not all power supplies will deliver what they claim.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_VerifiedPeripherals</id>
		<title>RPi VerifiedPeripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_VerifiedPeripherals"/>
				<updated>2012-05-06T17:07:29Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Working SD Cards */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Linux]]&lt;br /&gt;
[[Category: ARM Development Boards]]&lt;br /&gt;
[[Category: Broadcom]]&lt;br /&gt;
[[Category: Development Boards]]&lt;br /&gt;
[[Category: RaspberryPi]]&lt;br /&gt;
[[Category: Education]]&lt;br /&gt;
{{Template: RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
&lt;br /&gt;
19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the default Debian distribution unless stated otherwise. A suggested suffix markup scheme is as follows:&lt;br /&gt;
&lt;br /&gt;
* (A) - Relates to model A production board&lt;br /&gt;
* (B) - Relates to model B production board&lt;br /&gt;
* (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different&lt;br /&gt;
* No markup - relates to all production boards&lt;br /&gt;
&lt;br /&gt;
''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247]''&lt;br /&gt;
&lt;br /&gt;
If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}&lt;br /&gt;
&lt;br /&gt;
== Powered USB Hubs ==&lt;br /&gt;
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.&lt;br /&gt;
&lt;br /&gt;
===Working USB Hubs===&lt;br /&gt;
*'''Targus'''&lt;br /&gt;
** ACH81xx 7-port powered hub. 5V 3A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wifi Dongles)&lt;br /&gt;
*'''Newlink'''&lt;br /&gt;
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5V 1A&lt;br /&gt;
&lt;br /&gt;
===Problem USB Hubs===&lt;br /&gt;
*'''Unbranded / Multiple Brands'''&lt;br /&gt;
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably''due to an inadequate power supply.&lt;br /&gt;
&lt;br /&gt;
== USB Keyboards ==&lt;br /&gt;
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work.  &lt;br /&gt;
=== Working USB Keyboards ===&lt;br /&gt;
The following is a list of specific keyboards known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* '''Acer'''&lt;br /&gt;
** Compact Keyboard KU-0906 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Apple'''&lt;br /&gt;
** Apple Keyboard (109 keys) A1048&lt;br /&gt;
&lt;br /&gt;
* '''Cerulian''' &lt;br /&gt;
** Mini wireless keyboard and mouse deskset (B)&lt;br /&gt;
&lt;br /&gt;
* '''Dell'''&lt;br /&gt;
** SK-8135 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Fujitsu Siemens''' &lt;br /&gt;
**KB SC USB UK (!)&lt;br /&gt;
&lt;br /&gt;
* '''Genius'''&lt;br /&gt;
** KB-06XE (K639) (B)&lt;br /&gt;
&lt;br /&gt;
* '''Lenovo'''&lt;br /&gt;
** SK-8825 UK (B)&lt;br /&gt;
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)&lt;br /&gt;
&lt;br /&gt;
* '''Logitech''' &lt;br /&gt;
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)&lt;br /&gt;
** Wii wireless keyboard KG-0802 (!)&lt;br /&gt;
** C-BG17-Dual Wireless keyboard and mouse with wired USB received (B)&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
**Comfort Curve Keyboard 2000 v1.0 (Debian 13-Apr-2012 on Production Model B)&lt;br /&gt;
&lt;br /&gt;
*'''Tesco'''&lt;br /&gt;
**Value Keyboard VK109 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Trust'''&lt;br /&gt;
** Trust 17916 Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Xenta'''&lt;br /&gt;
** 2.5Ghz Wireless Multimedia Entertainment Keyboard with Touchpad (B)&lt;br /&gt;
&lt;br /&gt;
===Problem USB Keyboards===&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (!)&lt;br /&gt;
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)&lt;br /&gt;
* '''Novatech'''&lt;br /&gt;
** (B)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
* '''Unbranded'''&lt;br /&gt;
** model no. HK-6106 (B) &amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
* '''Levono/IBM'''&lt;br /&gt;
** 04b3:301b IBM Corp. SK-8815 Keyboard, [http://www.element14.com/community/docs/DOC-44703 conflicting behavior] with USB wifi adapters (B)&lt;br /&gt;
* '''Logitech'''&lt;br /&gt;
** model K120, [http://www.element14.com/community/docs/DOC-44703 conflicting behavior] with USB wifi adapters (B)&lt;br /&gt;
&lt;br /&gt;
== USB Mouse devices ==&lt;br /&gt;
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.  &lt;br /&gt;
&lt;br /&gt;
===Working USB Mouse Devices===&lt;br /&gt;
The following is a list of specific mouse devices known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* '''Dell'''&lt;br /&gt;
** M-UVDEL1 (B)&lt;br /&gt;
** M056U0A (B)&lt;br /&gt;
&lt;br /&gt;
* '''Genius'''&lt;br /&gt;
** GM-04003A (B)&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
** Compact optical mouse 500 V2.0 (B)&lt;br /&gt;
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)&lt;br /&gt;
** Microsoft Intellimouse Optical Mouse&lt;br /&gt;
&lt;br /&gt;
* '''Logitech'''&lt;br /&gt;
** M505 USB wireless laser, model no: 910-001324 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Tesco'''&lt;br /&gt;
** Wired optical mouse M211 (B)&lt;br /&gt;
&lt;br /&gt;
== USB WiFi Adapters ==&lt;br /&gt;
&lt;br /&gt;
See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing&lt;br /&gt;
&lt;br /&gt;
There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.&lt;br /&gt;
&lt;br /&gt;
===Working USB Wifi Adapters===&lt;br /&gt;
&lt;br /&gt;
These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.&lt;br /&gt;
&lt;br /&gt;
* '''3COM'''&lt;br /&gt;
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)&lt;br /&gt;
* '''Asus'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 USB-N10] USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix &amp;amp; Arch, must compile if Debian, requires firmware-realtek; todo: test with mouse (B)&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 USB-N13] USB ID 0b05:17ab, using compiled manufacturer driver for RTL8192CU; todo: test with mouse (B)&lt;br /&gt;
* '''D-Link'''&lt;br /&gt;
** AirPlus G DWL-G122 (rev. E). USB ID 07d1:3c0f, Ralink RT2870. On Debian requires the &amp;lt;code&amp;gt;firmware-ralink&amp;lt;/code&amp;gt; package from the &amp;lt;code&amp;gt;squeeze-firmware&amp;lt;/code&amp;gt; non-free repository.&lt;br /&gt;
* '''IOGear'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix &amp;amp; Arch, must compile if Debian, requires firmware-realtek; warning: conflict with mouse (B)&lt;br /&gt;
* '''Netgear''' &lt;br /&gt;
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the &amp;lt;code&amp;gt;firmware-atheros&amp;lt;/code&amp;gt; package from the &amp;lt;code&amp;gt;squeeze-backports&amp;lt;/code&amp;gt; non-free repository  (!)&lt;br /&gt;
** WG111v2: Realtek rtl8187 chipset (!)&lt;br /&gt;
* '''Sempre'''&lt;br /&gt;
** Sempre Wireless USB stick WU300-2: USB ID 0bda:8172, Realtek r8712u driver + firmware-realtek package. Module is not shipped in Debian image, but can be found here: http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/&lt;br /&gt;
* '''Tenda''' &lt;br /&gt;
** USB 11n adapter on a G network: Ralink  2870/3070 driver (!)&lt;br /&gt;
* '''TP-Link'''&lt;br /&gt;
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw) (B)&lt;br /&gt;
&lt;br /&gt;
* '''ZyXEL'''&lt;br /&gt;
** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)&lt;br /&gt;
* '''Generic'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter] USB ID 148f:2573, tested on debian; must install firmware-ralink package (B)&lt;br /&gt;
** Ralink Technology, Corp. RT5370 Wireless Adapter (USB ID 148f:5370)&lt;br /&gt;
&lt;br /&gt;
===Problem USB Wifi Adapters===&lt;br /&gt;
&lt;br /&gt;
These adapters were tested and found to have issues the Raspberry Pi.&lt;br /&gt;
&lt;br /&gt;
* '''Trendnet'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 TEW-424UB] USB ID: 0bda:8189; tested on Debian, Fedora &amp;amp; Arch; rtl8187 driver; conflicts with some keyboards (B)&lt;br /&gt;
* '''BlueProton'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 BT3] USB ID: 0bda:8187; tested on Debian, Fedora &amp;amp; Arch; rtl8187 driver; conflicts with some keyboards (B)&lt;br /&gt;
* '''TP-Link'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 TL-WN821N] USB ID: 0cf3:7015; tested on Debian; requires [http://linuxwireless.org/download/htc_fw/1.3/htc_7010.fw htc_7010.fw] firmware; ath9k_htc driver; conflicts with some keyboards (B)&lt;br /&gt;
&lt;br /&gt;
== USB Bluetooth adapters ==&lt;br /&gt;
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)&lt;br /&gt;
&lt;br /&gt;
== USB Ethernet adapters ==&lt;br /&gt;
&lt;br /&gt;
== USB IR Receivers==&lt;br /&gt;
&lt;br /&gt;
== USB TV Tuners==&lt;br /&gt;
*August&lt;br /&gt;
**DVB-T205, based on rtl2832u chipset, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD &amp;amp; SD.&lt;br /&gt;
&lt;br /&gt;
== USB Webcam ==&lt;br /&gt;
&lt;br /&gt;
== USB UART adapters ==&lt;br /&gt;
The USB UART adapter is used to access the serial console of the Raspberry Pi from a development host such as a laptop or desktop PC.  The USB end connects to the PC and the UART header end connects to the USB.  While it is possible to connect the USB end to another Raspberry Pi, this configuration has not been tested unless explicitly mentioned against an individual entry below.&lt;br /&gt;
&lt;br /&gt;
== Power adapters ==&lt;br /&gt;
The Raspberry Pi uses a standard MicroUSB power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.&lt;br /&gt;
&lt;br /&gt;
===Wired Adaptors===&lt;br /&gt;
* '''All HTC mobile phone adaptors'''&lt;br /&gt;
** TCP-300 Single port USB mains phone charger 5v 1A (B)&lt;br /&gt;
* '''Blackberry'''&lt;br /&gt;
** Charger for Pearl Flip 8220, Bold 9600 (B)&lt;br /&gt;
** Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003, Output 700mA @ 5V (B)&lt;br /&gt;
* '''Stontronics'''&lt;br /&gt;
** S2097ST switching PSU, 7.5V 1.6A (!) '''Note that the power connector and voltage requirements for production boards are completely different'''&lt;br /&gt;
* '''Samsung'''&lt;br /&gt;
** Charger for Galaxy SII 5V 0.7A&lt;br /&gt;
&lt;br /&gt;
===External Batteries===&lt;br /&gt;
* ''' New Trent'''&lt;br /&gt;
** iCurve IMP70D 7000mAh (Approx 12hrs from full charge)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Display adapters ==&lt;br /&gt;
While technically there shouldn't be a difference between one (for example) HDMI-&amp;gt;DVI adapter and another, it would be nice to have a list of working ones so if necessary, you can just buy a recommended one (contributors should give links) instead of hunting around. This section could contain information about verified HDMI-&amp;gt;DVI, CompositeRCA-&amp;gt;SCART, CompositeRCA-&amp;gt;VGA ''boxes/chipsets'', and HDMI-&amp;gt;VGA ''boxes/chipsets''.&lt;br /&gt;
&lt;br /&gt;
===HDMI-&amp;gt;DVI-D===&lt;br /&gt;
None explicitly mentioned &lt;br /&gt;
===HDMI-&amp;gt;VGA converter boxes===&lt;br /&gt;
According to user &amp;quot;asb&amp;quot; -- http://www.amazon.co.uk/gp/product/B007KEIRNG -- the Neewer HDMI to VGA adapter works with the Pi.&lt;br /&gt;
&lt;br /&gt;
===Composite-&amp;gt;SCART===&lt;br /&gt;
None explicitly mentioned &lt;br /&gt;
===Composite-&amp;gt;VGA converter boxes===&lt;br /&gt;
None explicitly mentioned, and they are pricey so the chances of someone buying one to test functionality is low&lt;br /&gt;
== SD cards ==&lt;br /&gt;
&lt;br /&gt;
Note that manufacturers change their designs over time, even as the specs stay the same. (E.g. an ACME 8 GB class 4 card manufactured in 2011 might work, while one manufactured in 2012 might not.)&lt;br /&gt;
For this reason, please specify product numbers in the lists below, when possible.&lt;br /&gt;
&lt;br /&gt;
===Working SD Cards===&lt;br /&gt;
* '''Adata''' &lt;br /&gt;
** Class 10 8GB (AUSDH8GCL10-R)&lt;br /&gt;
* '''Dane-Elec''' &lt;br /&gt;
** 16Gb class 4&lt;br /&gt;
* '''Integral''' &lt;br /&gt;
** Ultima Pro 16GB Class 10 (20MB/s)&lt;br /&gt;
* '''Kingston''' &lt;br /&gt;
** SD 2GB (no class mentioned)&lt;br /&gt;
** SDHC 8GB class 4&lt;br /&gt;
** SDHC 8GB class 10 (ultimateX 120X)&lt;br /&gt;
* '''Kodak''' &lt;br /&gt;
** SDHC 8GB Class 4&lt;br /&gt;
* '''Lexar''' &lt;br /&gt;
** 4GB SDHC Class4 (Boots consistently and no error messages in log after 1/2 hour use )&lt;br /&gt;
** 8GB SDHC Class4&lt;br /&gt;
** 4GB Platinum II SDHC Class 6 (from [http://www.microcenter.com/single_product_results.phtml?product_id=0350735 Microcenter])&lt;br /&gt;
* '''Microcenter Brand (sold in bins at checkout)'''&lt;br /&gt;
** [http://www.microcenter.com/single_product_results.phtml?product_id=0349728 8GB SDHC Class 10]&lt;br /&gt;
** [http://www.microcenter.com/single_product_results.phtml?product_id=0289508 8GB SDHC Class 4]&lt;br /&gt;
* '''MyMemory''' &lt;br /&gt;
** 8GB SDHC class 10 (MYMESDH8G10) [http://www.mymemory.co.uk/SDHC/MyMemory/MyMemory-8GB-SD-Card-%28SDHC%29---Class-10 MyMemory 8GB class 10]&lt;br /&gt;
* '''Panasonic''' &lt;br /&gt;
** 8GB SDHC class6 (~4.8MB/s read, ~4.4MB/s write, following [[RPi_Performance#SD_card]])&lt;br /&gt;
* '''Peak''' &lt;br /&gt;
** 4GB microSDHC class4 (MMBTR04GUBCA-ME) tested with Arch&lt;br /&gt;
* '''PNY''' &lt;br /&gt;
** 4GB SDHC Class 4&lt;br /&gt;
* '''Samsung''' &lt;br /&gt;
** SDHC 4GB&lt;br /&gt;
** SDHC 8GB&lt;br /&gt;
** SDHC 16GB Class 6 (MB-SSAGAEU)&lt;br /&gt;
* '''SanDisk''' &lt;br /&gt;
** Ultra 2GB Class 4 (15MB/s)&lt;br /&gt;
** Ultra II SD 2GB class 4&lt;br /&gt;
** Ultra II SDHC 4GB class 4&lt;br /&gt;
** 2GB (non SDHC but with a circle 2 --probably class 2), writes at 3.5 Mb/s&lt;br /&gt;
** 2GB, white &amp;quot;SanDisk for Wii&amp;quot; branded, no class mentioned&lt;br /&gt;
** Ultra SDHC 4GB class 6 (SDSDH-004G-U46 - BH1136121837G, BH1130521822D)&lt;br /&gt;
** Ultra SDHC 8GB class 6 (SDSDH-008G-U46 - BI1131222083D)&lt;br /&gt;
** 4/8GB Micro SDHC (with Sandisk MicroSD =&amp;gt; SD adaptor) Class 4&lt;br /&gt;
** 4GB Micro SDHC (with Sandisk MicroSD =&amp;gt; SD adaptor) Class 2&lt;br /&gt;
** 4GB SHDC (class 4)&lt;br /&gt;
** 8GB SDHC (class 4); writes at ~1.5MB/s&lt;br /&gt;
** 16GB SDHC (class 4)&lt;br /&gt;
** 32GB SDHC Class 6&lt;br /&gt;
** Extreme III 2GB (BE0715105083B)&lt;br /&gt;
* '''Transcend''' &lt;br /&gt;
** SDHC 16GB class 10&lt;br /&gt;
** SDHC 8GB class 10 (TS8GSDHC10) [http://www.mymemory.co.uk/SDHC/Transcend/Transcend-8GB-SD-Card-%28SDHC%29---Class-10- Transcend 8G class 10]&lt;br /&gt;
** SDHC 8GB class 6 (~5.8 MB/s read/write following [[RPi_Performance#SD_card]])&lt;br /&gt;
** SDHC 4GB class 4 - we've found these to work without any errors and offer reasonable performance&lt;br /&gt;
** SDHC 4GB class 4 (TS4GSDHC4 - BH1130821915G)&lt;br /&gt;
** SDHC 4GB class 6 (TS4GSDHC6) - no problems. &lt;br /&gt;
** SDHC 8GB class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)&lt;br /&gt;
** SDHC 8GB class 4&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).&lt;br /&gt;
&lt;br /&gt;
===Problem SD Cards===&lt;br /&gt;
&lt;br /&gt;
There are issues with most Class 10 SDHC cards, apparently due to a bug in the Broadcom bootloader.[http://www.raspberrypi.org/forum/general-discussion/class-10-sd-cards-on-the-production-boards/page-3/#p39181]&lt;br /&gt;
&lt;br /&gt;
This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.&lt;br /&gt;
&lt;br /&gt;
* '''Panasonic''' &lt;br /&gt;
** Class 10 8GB (RP-SDU08GD1K) mmc0: timeout waiting for hardware interrupt [http://www.mymemory.co.uk/SDHC/Panasonic/Panasonic-8GB-UHS-1-London-2012-Collection-SDHC-Card---Class-10 Panasonic 8GB Class 10]&lt;br /&gt;
* '''Patriot''' &lt;br /&gt;
** Class 10 8GB (PSF8GSDHC10)&lt;br /&gt;
* '''SanDisk''' &lt;br /&gt;
** Ultra SDHC Class 4 4GB (BH1028516076D) - Intermitant booting ( 1/50 power on ), random timeout messages when it does boot.&lt;br /&gt;
** Ultra Class 6 8GB (B11201421964G)&lt;br /&gt;
** Ultra SDHC I 8GB Class 6 (BI1201221964G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )&lt;br /&gt;
** Ultra Class 6 16GB (BL1202021933G)&lt;br /&gt;
** Extreme Class 6 8GB (BI1101116253G)&lt;br /&gt;
** Extreme Class 10 8GB (BI1108716254G)&lt;br /&gt;
** Extreme Pro Class 10 8GB - Boots kernel but won't run init ( mmc timeout waiting for interrupt )&lt;br /&gt;
* '''Kingston''' &lt;br /&gt;
** SDHC 4GB class 4 (works but gets mmc errors: mmc0: final write to SD card still running) Russel King might have a kernel patch for this problem.&lt;br /&gt;
* '''Integral'''&lt;br /&gt;
** Ultima Pro 16GB SDHC Class 6 (SH016GAA2BB)&lt;br /&gt;
&lt;br /&gt;
The usual warnings against less reputable sellers (such as Ebay merchants) apply.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):&lt;br /&gt;
&lt;br /&gt;
 mmc0: timeout waiting for hardware interrupt&lt;br /&gt;
&lt;br /&gt;
=== Benchmarks ===&lt;br /&gt;
&lt;br /&gt;
* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html&lt;br /&gt;
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11&lt;br /&gt;
&lt;br /&gt;
== Foreign Language Translations ==&lt;br /&gt;
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references&amp;gt;&lt;br /&gt;
&amp;lt;/references&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_VerifiedPeripherals</id>
		<title>RPi VerifiedPeripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_VerifiedPeripherals"/>
				<updated>2012-05-06T17:03:55Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Wired Adaptors */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Linux]]&lt;br /&gt;
[[Category: ARM Development Boards]]&lt;br /&gt;
[[Category: Broadcom]]&lt;br /&gt;
[[Category: Development Boards]]&lt;br /&gt;
[[Category: RaspberryPi]]&lt;br /&gt;
[[Category: Education]]&lt;br /&gt;
{{Template: RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
&lt;br /&gt;
19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the default Debian distribution unless stated otherwise. A suggested suffix markup scheme is as follows:&lt;br /&gt;
&lt;br /&gt;
* (A) - Relates to model A production board&lt;br /&gt;
* (B) - Relates to model B production board&lt;br /&gt;
* (!) - Information from alpha and beta board days -- beta board verified peripherals should still apply to production boards for the most part, but the alpha board is fairly different&lt;br /&gt;
* No markup - relates to all production boards&lt;br /&gt;
&lt;br /&gt;
''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247]''&lt;br /&gt;
&lt;br /&gt;
If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}&lt;br /&gt;
&lt;br /&gt;
== Powered USB Hubs ==&lt;br /&gt;
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.&lt;br /&gt;
&lt;br /&gt;
===Working USB Hubs===&lt;br /&gt;
*'''Targus'''&lt;br /&gt;
** ACH81xx 7-port powered hub. 5V 3A power supply, with 2 high power ports. (possible conflicting behaviour with USB keyboard / Wifi Dongles)&lt;br /&gt;
*'''Newlink'''&lt;br /&gt;
** NLUSB2-224P 4 port USB 2.0 Mini hub with PSU 5V 1A&lt;br /&gt;
&lt;br /&gt;
===Problem USB Hubs===&lt;br /&gt;
*'''Unbranded / Multiple Brands'''&lt;br /&gt;
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra' -- This is ''probably''due to an inadequate power supply.&lt;br /&gt;
&lt;br /&gt;
== USB Keyboards ==&lt;br /&gt;
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work.  &lt;br /&gt;
=== Working USB Keyboards ===&lt;br /&gt;
The following is a list of specific keyboards known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* '''Acer'''&lt;br /&gt;
** Compact Keyboard KU-0906 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Apple'''&lt;br /&gt;
** Apple Keyboard (109 keys) A1048&lt;br /&gt;
&lt;br /&gt;
* '''Cerulian''' &lt;br /&gt;
** Mini wireless keyboard and mouse deskset (B)&lt;br /&gt;
&lt;br /&gt;
* '''Dell'''&lt;br /&gt;
** SK-8135 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Fujitsu Siemens''' &lt;br /&gt;
**KB SC USB UK (!)&lt;br /&gt;
&lt;br /&gt;
* '''Genius'''&lt;br /&gt;
** KB-06XE (K639) (B)&lt;br /&gt;
&lt;br /&gt;
* '''Lenovo'''&lt;br /&gt;
** SK-8825 UK (B)&lt;br /&gt;
** Lenovo Enhanced Multimedia Remote with backlit keyboard N5902 (US)&lt;br /&gt;
&lt;br /&gt;
* '''Logitech''' &lt;br /&gt;
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)&lt;br /&gt;
** Wii wireless keyboard KG-0802 (!)&lt;br /&gt;
** C-BG17-Dual Wireless keyboard and mouse with wired USB received (B)&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
**Comfort Curve Keyboard 2000 v1.0 (Debian 13-Apr-2012 on Production Model B)&lt;br /&gt;
&lt;br /&gt;
*'''Tesco'''&lt;br /&gt;
**Value Keyboard VK109 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Trust'''&lt;br /&gt;
** Trust 17916 Compact Wireless Entertainment Keyboard http://www.trust.com/products/product.aspx?artnr=17916 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Xenta'''&lt;br /&gt;
** 2.5Ghz Wireless Multimedia Entertainment Keyboard with Touchpad (B)&lt;br /&gt;
&lt;br /&gt;
===Problem USB Keyboards===&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
** Wireless Desktop 800 - Keyboard has 'sticky' keys. (!)&lt;br /&gt;
** Wireless Optical Desktop 1000 - Keyboard has 'sticky' keys (B)&lt;br /&gt;
* '''Novatech'''&lt;br /&gt;
** (B)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
* '''Unbranded'''&lt;br /&gt;
** model no. HK-6106 (B) &amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
* '''Levono/IBM'''&lt;br /&gt;
** 04b3:301b IBM Corp. SK-8815 Keyboard, [http://www.element14.com/community/docs/DOC-44703 conflicting behavior] with USB wifi adapters (B)&lt;br /&gt;
* '''Logitech'''&lt;br /&gt;
** model K120, [http://www.element14.com/community/docs/DOC-44703 conflicting behavior] with USB wifi adapters (B)&lt;br /&gt;
&lt;br /&gt;
== USB Mouse devices ==&lt;br /&gt;
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.  &lt;br /&gt;
&lt;br /&gt;
===Working USB Mouse Devices===&lt;br /&gt;
The following is a list of specific mouse devices known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* '''Dell'''&lt;br /&gt;
** M-UVDEL1 (B)&lt;br /&gt;
** M056U0A (B)&lt;br /&gt;
&lt;br /&gt;
* '''Genius'''&lt;br /&gt;
** GM-04003A (B)&lt;br /&gt;
&lt;br /&gt;
* '''Microsoft''' &lt;br /&gt;
** Compact optical mouse 500 V2.0 (B)&lt;br /&gt;
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)&lt;br /&gt;
** Microsoft Intellimouse Optical Mouse&lt;br /&gt;
&lt;br /&gt;
* '''Logitech'''&lt;br /&gt;
** M505 USB wireless laser, model no: 910-001324 (B)&lt;br /&gt;
&lt;br /&gt;
* '''Tesco'''&lt;br /&gt;
** Wired optical mouse M211 (B)&lt;br /&gt;
&lt;br /&gt;
== USB WiFi Adapters ==&lt;br /&gt;
&lt;br /&gt;
See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing&lt;br /&gt;
&lt;br /&gt;
There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.&lt;br /&gt;
&lt;br /&gt;
===Working USB Wifi Adapters===&lt;br /&gt;
&lt;br /&gt;
These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.&lt;br /&gt;
&lt;br /&gt;
* '''3COM'''&lt;br /&gt;
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)&lt;br /&gt;
* '''Asus'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 USB-N10] USB ID 0b05:1786, r8712u staging driver, included on Fedora Remix &amp;amp; Arch, must compile if Debian, requires firmware-realtek; todo: test with mouse (B)&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 USB-N13] USB ID 0b05:17ab, using compiled manufacturer driver for RTL8192CU; todo: test with mouse (B)&lt;br /&gt;
* '''D-Link'''&lt;br /&gt;
** AirPlus G DWL-G122 (rev. E). USB ID 07d1:3c0f, Ralink RT2870. On Debian requires the &amp;lt;code&amp;gt;firmware-ralink&amp;lt;/code&amp;gt; package from the &amp;lt;code&amp;gt;squeeze-firmware&amp;lt;/code&amp;gt; non-free repository.&lt;br /&gt;
* '''IOGear'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u staging driver, included on Fedora Remix &amp;amp; Arch, must compile if Debian, requires firmware-realtek; warning: conflict with mouse (B)&lt;br /&gt;
* '''Netgear''' &lt;br /&gt;
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the &amp;lt;code&amp;gt;firmware-atheros&amp;lt;/code&amp;gt; package from the &amp;lt;code&amp;gt;squeeze-backports&amp;lt;/code&amp;gt; non-free repository  (!)&lt;br /&gt;
** WG111v2: Realtek rtl8187 chipset (!)&lt;br /&gt;
* '''Sempre'''&lt;br /&gt;
** Sempre Wireless USB stick WU300-2: USB ID 0bda:8172, Realtek r8712u driver + firmware-realtek package. Module is not shipped in Debian image, but can be found here: http://www.t3node.com/blog/sempre-wireless-usb-stick-wu300-2-on-raspberry-pi/&lt;br /&gt;
* '''Tenda''' &lt;br /&gt;
** USB 11n adapter on a G network: Ralink  2870/3070 driver (!)&lt;br /&gt;
* '''TP-Link'''&lt;br /&gt;
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw) (B)&lt;br /&gt;
&lt;br /&gt;
* '''ZyXEL'''&lt;br /&gt;
** [http://www.element14.com/community/message/50015#50015/l/re-installing-kernel-headers-on-the-pi NWD2105] USB ID: 0586:341e, RT3070 chipset, rt2800usb driver (B)&lt;br /&gt;
* '''Generic'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter] USB ID 148f:2573, tested on debian; must install firmware-ralink package (B)&lt;br /&gt;
** Ralink Technology, Corp. RT5370 Wireless Adapter (USB ID 148f:5370)&lt;br /&gt;
&lt;br /&gt;
===Problem USB Wifi Adapters===&lt;br /&gt;
&lt;br /&gt;
These adapters were tested and found to have issues the Raspberry Pi.&lt;br /&gt;
&lt;br /&gt;
* '''Trendnet'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 TEW-424UB] USB ID: 0bda:8189; tested on Debian, Fedora &amp;amp; Arch; rtl8187 driver; conflicts with some keyboards (B)&lt;br /&gt;
* '''BlueProton'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 BT3] USB ID: 0bda:8187; tested on Debian, Fedora &amp;amp; Arch; rtl8187 driver; conflicts with some keyboards (B)&lt;br /&gt;
* '''TP-Link'''&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 TL-WN821N] USB ID: 0cf3:7015; tested on Debian; requires [http://linuxwireless.org/download/htc_fw/1.3/htc_7010.fw htc_7010.fw] firmware; ath9k_htc driver; conflicts with some keyboards (B)&lt;br /&gt;
&lt;br /&gt;
== USB Bluetooth adapters ==&lt;br /&gt;
* Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) - (USB ID 0a12:0001)&lt;br /&gt;
&lt;br /&gt;
== USB Ethernet adapters ==&lt;br /&gt;
&lt;br /&gt;
== USB IR Receivers==&lt;br /&gt;
&lt;br /&gt;
== USB TV Tuners==&lt;br /&gt;
*August&lt;br /&gt;
**DVB-T205, based on rtl2832u chipset, working with [https://github.com/ambrosa/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0 this driver]. Tested with Saorview (Irish DTT service), both HD &amp;amp; SD.&lt;br /&gt;
&lt;br /&gt;
== USB Webcam ==&lt;br /&gt;
&lt;br /&gt;
== USB UART adapters ==&lt;br /&gt;
The USB UART adapter is used to access the serial console of the Raspberry Pi from a development host such as a laptop or desktop PC.  The USB end connects to the PC and the UART header end connects to the USB.  While it is possible to connect the USB end to another Raspberry Pi, this configuration has not been tested unless explicitly mentioned against an individual entry below.&lt;br /&gt;
&lt;br /&gt;
== Power adapters ==&lt;br /&gt;
The Raspberry Pi uses a standard MicroUSB power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.&lt;br /&gt;
&lt;br /&gt;
===Wired Adaptors===&lt;br /&gt;
* '''All HTC mobile phone adaptors'''&lt;br /&gt;
** TCP-300 Single port USB mains phone charger 5v 1A (B)&lt;br /&gt;
* '''Blackberry'''&lt;br /&gt;
** Charger for Pearl Flip 8220, Bold 9600 (B)&lt;br /&gt;
** Model PSM04R-0500CHW1(M), RIM Part Number HDW-17957-003, Output 700mA @ 5V (B)&lt;br /&gt;
* '''Stontronics'''&lt;br /&gt;
** S2097ST switching PSU, 7.5V 1.6A (!) '''Note that the power connector and voltage requirements for production boards are completely different'''&lt;br /&gt;
* '''Samsung'''&lt;br /&gt;
** Charger for Galaxy SII 5V 0.7A&lt;br /&gt;
&lt;br /&gt;
===External Batteries===&lt;br /&gt;
* ''' New Trent'''&lt;br /&gt;
** iCurve IMP70D 7000mAh (Approx 12hrs from full charge)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Display adapters ==&lt;br /&gt;
While technically there shouldn't be a difference between one (for example) HDMI-&amp;gt;DVI adapter and another, it would be nice to have a list of working ones so if necessary, you can just buy a recommended one (contributors should give links) instead of hunting around. This section could contain information about verified HDMI-&amp;gt;DVI, CompositeRCA-&amp;gt;SCART, CompositeRCA-&amp;gt;VGA ''boxes/chipsets'', and HDMI-&amp;gt;VGA ''boxes/chipsets''.&lt;br /&gt;
&lt;br /&gt;
===HDMI-&amp;gt;DVI-D===&lt;br /&gt;
None explicitly mentioned &lt;br /&gt;
===HDMI-&amp;gt;VGA converter boxes===&lt;br /&gt;
According to user &amp;quot;asb&amp;quot; -- http://www.amazon.co.uk/gp/product/B007KEIRNG -- the Neewer HDMI to VGA adapter works with the Pi.&lt;br /&gt;
&lt;br /&gt;
===Composite-&amp;gt;SCART===&lt;br /&gt;
None explicitly mentioned &lt;br /&gt;
===Composite-&amp;gt;VGA converter boxes===&lt;br /&gt;
None explicitly mentioned, and they are pricey so the chances of someone buying one to test functionality is low&lt;br /&gt;
== SD cards ==&lt;br /&gt;
&lt;br /&gt;
Note that manufacturers change their designs over time, even as the specs stay the same. (E.g. an ACME 8 GB class 4 card manufactured in 2011 might work, while one manufactured in 2012 might not.)&lt;br /&gt;
For this reason, please specify product numbers in the lists below, when possible.&lt;br /&gt;
&lt;br /&gt;
===Working SD Cards===&lt;br /&gt;
* '''Adata''' &lt;br /&gt;
** Class 10 8GB (AUSDH8GCL10-R)&lt;br /&gt;
* '''Dane-Elec''' &lt;br /&gt;
** 16Gb class 4&lt;br /&gt;
* '''Integral''' &lt;br /&gt;
** Ultima Pro 16GB Class 10 (20MB/s)&lt;br /&gt;
* '''Kingston''' &lt;br /&gt;
** SD 2GB (no class mentioned)&lt;br /&gt;
** SDHC 8GB class 4&lt;br /&gt;
** SDHC 8GB class 10 (ultimateX 120X)&lt;br /&gt;
* '''Kodak''' &lt;br /&gt;
** SDHC 8GB Class 4&lt;br /&gt;
* '''Lexar''' &lt;br /&gt;
** 4GB SDHC Class4 (Boots consistently and no error messages in log after 1/2 hour use )&lt;br /&gt;
** 8GB SDHC Class4&lt;br /&gt;
** 4GB Platinum II SDHC Class 6 (from [http://www.microcenter.com/single_product_results.phtml?product_id=0350735 Microcenter])&lt;br /&gt;
* '''Microcenter Brand (sold in bins at checkout)'''&lt;br /&gt;
** [http://www.microcenter.com/single_product_results.phtml?product_id=0349728 8GB SDHC Class 10]&lt;br /&gt;
** [http://www.microcenter.com/single_product_results.phtml?product_id=0289508 8GB SDHC Class 4]&lt;br /&gt;
* '''MyMemory''' &lt;br /&gt;
** 8GB SDHC class 10 (MYMESDH8G10) [http://www.mymemory.co.uk/SDHC/MyMemory/MyMemory-8GB-SD-Card-%28SDHC%29---Class-10 MyMemory 8GB class 10]&lt;br /&gt;
* '''Panasonic''' &lt;br /&gt;
** 8GB SDHC class6 (~4.8MB/s read, ~4.4MB/s write, following [[RPi_Performance#SD_card]])&lt;br /&gt;
* '''Peak''' &lt;br /&gt;
** 4GB microSDHC class4 (MMBTR04GUBCA-ME) tested with Arch&lt;br /&gt;
* '''PNY''' &lt;br /&gt;
** 4GB SDHC Class 4&lt;br /&gt;
* '''Samsung''' &lt;br /&gt;
** SDHC 4GB&lt;br /&gt;
** SDHC 8GB&lt;br /&gt;
** SDHC 16GB Class 6 (MB-SSAGAEU)&lt;br /&gt;
* '''SanDisk''' &lt;br /&gt;
** Ultra 2GB Class 4 (15MB/s)&lt;br /&gt;
** Ultra II SD 2GB class 4&lt;br /&gt;
** Ultra II SDHC 4GB class 4&lt;br /&gt;
** 2GB (non SDHC but with a circle 2 --probably class 2), writes at 3.5 Mb/s&lt;br /&gt;
** 2GB, white &amp;quot;SanDisk for Wii&amp;quot; branded, no class mentioned&lt;br /&gt;
** Ultra SDHC 4GB class 6 (SDSDH-004G-U46 - BH1136121837G, BH1130521822D)&lt;br /&gt;
** Ultra SDHC 8GB class 6 (SDSDH-008G-U46 - BI1131222083D)&lt;br /&gt;
** 8GB SDHC (class 4); writes at ~1.5MB/s&lt;br /&gt;
** 4/8GB Micro SDHC (with Sandisk MicroSD =&amp;gt; SD adaptor) Class 4&lt;br /&gt;
** 4GB Micro SDHC (with Sandisk MicroSD =&amp;gt; SD adaptor) Class 2&lt;br /&gt;
** 16GB SDHC (class 4)&lt;br /&gt;
** 32GB SDHC Class 6&lt;br /&gt;
** Extreme III 2GB (BE0715105083B)&lt;br /&gt;
* '''Transcend''' &lt;br /&gt;
** SDHC 16GB class 10&lt;br /&gt;
** SDHC 8GB class 10 (TS8GSDHC10) [http://www.mymemory.co.uk/SDHC/Transcend/Transcend-8GB-SD-Card-%28SDHC%29---Class-10- Transcend 8G class 10]&lt;br /&gt;
** SDHC 8GB class 6 (~5.8 MB/s read/write following [[RPi_Performance#SD_card]])&lt;br /&gt;
** SDHC 4GB class 4 - we've found these to work without any errors and offer reasonable performance&lt;br /&gt;
** SDHC 4GB class 4 (TS4GSDHC4 - BH1130821915G)&lt;br /&gt;
** SDHC 4GB class 6 (TS4GSDHC6) - no problems. &lt;br /&gt;
** SDHC 8GB class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)&lt;br /&gt;
** SDHC 8GB class 4&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).&lt;br /&gt;
&lt;br /&gt;
===Problem SD Cards===&lt;br /&gt;
&lt;br /&gt;
There are issues with most Class 10 SDHC cards, apparently due to a bug in the Broadcom bootloader.[http://www.raspberrypi.org/forum/general-discussion/class-10-sd-cards-on-the-production-boards/page-3/#p39181]&lt;br /&gt;
&lt;br /&gt;
This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.&lt;br /&gt;
&lt;br /&gt;
* '''Panasonic''' &lt;br /&gt;
** Class 10 8GB (RP-SDU08GD1K) mmc0: timeout waiting for hardware interrupt [http://www.mymemory.co.uk/SDHC/Panasonic/Panasonic-8GB-UHS-1-London-2012-Collection-SDHC-Card---Class-10 Panasonic 8GB Class 10]&lt;br /&gt;
* '''Patriot''' &lt;br /&gt;
** Class 10 8GB (PSF8GSDHC10)&lt;br /&gt;
* '''SanDisk''' &lt;br /&gt;
** Ultra SDHC Class 4 4GB (BH1028516076D) - Intermitant booting ( 1/50 power on ), random timeout messages when it does boot.&lt;br /&gt;
** Ultra Class 6 8GB (B11201421964G)&lt;br /&gt;
** Ultra SDHC I 8GB Class 6 (BI1201221964G) - Boots kernel but won't run init ( mmc timeout waiting for interrupt )&lt;br /&gt;
** Ultra Class 6 16GB (BL1202021933G)&lt;br /&gt;
** Extreme Class 6 8GB (BI1101116253G)&lt;br /&gt;
** Extreme Class 10 8GB (BI1108716254G)&lt;br /&gt;
** Extreme Pro Class 10 8GB - Boots kernel but won't run init ( mmc timeout waiting for interrupt )&lt;br /&gt;
* '''Kingston''' &lt;br /&gt;
** SDHC 4GB class 4 (works but gets mmc errors: mmc0: final write to SD card still running) Russel King might have a kernel patch for this problem.&lt;br /&gt;
* '''Integral'''&lt;br /&gt;
** Ultima Pro 16GB SDHC Class 6 (SH016GAA2BB)&lt;br /&gt;
&lt;br /&gt;
The usual warnings against less reputable sellers (such as Ebay merchants) apply.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):&lt;br /&gt;
&lt;br /&gt;
 mmc0: timeout waiting for hardware interrupt&lt;br /&gt;
&lt;br /&gt;
=== Benchmarks ===&lt;br /&gt;
&lt;br /&gt;
* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html&lt;br /&gt;
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11&lt;br /&gt;
&lt;br /&gt;
== Foreign Language Translations ==&lt;br /&gt;
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references&amp;gt;&lt;br /&gt;
&amp;lt;/references&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hub</id>
		<title>RPi Hub</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hub"/>
				<updated>2012-05-02T23:39:07Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* About */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC right}}{{Template:Hub_Flags}} &amp;lt;!-- please edit template to alter banner and flag display on all hubs --&amp;gt;&lt;br /&gt;
{{Clear}}&lt;br /&gt;
'''The Raspberry Pi wiki pages on this site are a community work - the Raspberry Pi Foundation is not responsible for content on these pages.'''&lt;br /&gt;
&lt;br /&gt;
==Now shipping to customers==&lt;br /&gt;
Premier Farnell and RS Components have started shipping to customers. Congratulations to those at the front of the queue!.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
See the [[RPi Buying Guide | Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]&lt;br /&gt;
&lt;br /&gt;
==About==&lt;br /&gt;
[[File:RpiFront.jpg|300px|thumb|right|The Rpi beta board (model B)]]&lt;br /&gt;
&lt;br /&gt;
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. We expect this computer to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
* 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.&lt;br /&gt;
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant&amp;lt;ref&amp;gt;http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet&amp;lt;/ref&amp;gt;.  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.&lt;br /&gt;
* 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]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===History===&lt;br /&gt;
* Confused about seeing different versions of the board? Visit the [[Rpi HardwareHistory | History of the Raspberry Pi Hardware]] for information about the past versions.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
&lt;br /&gt;
* 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)&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
===[[Buying RPi |Buying Guide]]===&lt;br /&gt;
----&lt;br /&gt;
Where can I get one and for how much?&lt;br /&gt;
* Raspberry Pi can only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.&lt;br /&gt;
&lt;br /&gt;
* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop].&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Hardware Basic Setup | Basic Setup]]===&lt;br /&gt;
----&lt;br /&gt;
First little Raspberry Pi Steps...&lt;br /&gt;
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.&lt;br /&gt;
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.&lt;br /&gt;
* 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]]&lt;br /&gt;
&lt;br /&gt;
* '''Having problems? Try the [http://elinux.org/R-Pi_Troubleshooting Troubleshooting] page.'''&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Beginners | Beginners Guide]]===&lt;br /&gt;
----&lt;br /&gt;
You've just got your new Raspberry Pi device - what now?&lt;br /&gt;
* [[RPi Beginners | Beginners Guide]]&lt;br /&gt;
&lt;br /&gt;
* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.&lt;br /&gt;
&lt;br /&gt;
* Get started with some basic projects and tutorials:&lt;br /&gt;
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials]&lt;br /&gt;
&lt;br /&gt;
[[RPi Tutorial Easy GPIO Hardware &amp;amp; Software | Easy GPIO Hardware &amp;amp; Software]] - in-progress at the moment&lt;br /&gt;
 Example projects/tuts which can be linked from here&lt;br /&gt;
 (or from within a beginners guide page perhaps):&lt;br /&gt;
  Setup XBMC media centre&lt;br /&gt;
  Programming tutorials (Liams YouTube etc)&lt;br /&gt;
  Easy GPIO (when complete or similar thing).&lt;br /&gt;
  Also links to some basic linux user guides.&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Hardware|Hardware]] &amp;amp; [[RPi VerifiedPeripherals|Peripherals]]===&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
*The Model B is more advanced than the Model A - see [[RPi Hardware]].&lt;br /&gt;
*The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].&lt;br /&gt;
*The unit will support a range of [[RPi VerifiedPeripherals |USB devices, peripherals and accessories]].&lt;br /&gt;
*The [[Rpi Low-level peripherals| Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.&lt;br /&gt;
*For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].&lt;br /&gt;
*[[RPi Peripherals|Setting up peripherals - examples/HowTos]]&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[Rpi_Software|Software]] &amp;amp; [[RPi_Distributions|OS Distributions]]===&lt;br /&gt;
----&lt;br /&gt;
The Raspberry Pi will run a range of OS Distributions and run a variety of software.&lt;br /&gt;
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.&lt;br /&gt;
*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.&lt;br /&gt;
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]] or [[RPi_Performance|test the Pi's performance]].&lt;br /&gt;
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.&lt;br /&gt;
*Information about installing specific [[RPi_applications|applications]] is available through the link.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Documentation|Documentation]]===&lt;br /&gt;
----&lt;br /&gt;
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].&lt;br /&gt;
&lt;br /&gt;
[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]&lt;br /&gt;
&lt;br /&gt;
 Example documents which can be linked from here (or sub page):&lt;br /&gt;
  Official Datasheets&lt;br /&gt;
  White Papers&lt;br /&gt;
  User Manuals&lt;br /&gt;
  Recommended books (perhaps)&lt;br /&gt;
&lt;br /&gt;
===[[R-Pi Troubleshooting|How to fix common problems]]===&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Community==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Projects |Projects]], [[RPi Guides |Guides]] &amp;amp; [[RPi Tutorials |Tutorials]]===&lt;br /&gt;
----&lt;br /&gt;
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].&lt;br /&gt;
*Knowledgeable users may want to review and help out with the [[RPi Tasks |Tasks page]].&lt;br /&gt;
*Get started by following some of the many [[RPi Tutorials | Tutorials]].&lt;br /&gt;
*Common tasks and useful tip are available through the [[RPi Guides | Guides page]]. &lt;br /&gt;
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[Rpi Education|Schools, Universities, Clubs &amp;amp; Groups]]===&lt;br /&gt;
----&lt;br /&gt;
*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.&lt;br /&gt;
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
===[[RPi Community |Supporting Communities]]===&lt;br /&gt;
----&lt;br /&gt;
The [[RPi Community |Raspberry Pi Community]] is steadily growing: &lt;br /&gt;
*[http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]&lt;br /&gt;
&lt;br /&gt;
*[http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]&lt;br /&gt;
&lt;br /&gt;
*[http://www.raspberrymod.com/ Raspberrymod] and [http://www.raspberrypiforums.com/forum RPiforums] Un-Official Raspberry Pi Discussion Boards&lt;br /&gt;
&lt;br /&gt;
*[http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]&lt;br /&gt;
&lt;br /&gt;
*[http://www.worldofpi/com/ World Of Pi] A forum based on all things Raspberry Pi.&lt;br /&gt;
&lt;br /&gt;
*[[RPi Community Magazine]] - User contributed eMagazine, get involved!&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==About the RPi Wiki==&lt;br /&gt;
&lt;br /&gt;
'''Do not be afraid to add your bit, content is vital for the wiki to function.'''&lt;br /&gt;
&lt;br /&gt;
[[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]]]&lt;br /&gt;
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.&lt;br /&gt;
Have a look at our [[RPi Wiki Best Practice|Guidelines]] and then you are free to go !&lt;br /&gt;
&lt;br /&gt;
=== Translations ===&lt;br /&gt;
&lt;br /&gt;
The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:&lt;br /&gt;
&lt;br /&gt;
* English: [[R-Pi Hub]]&lt;br /&gt;
* French: [[FR:R-Pi Hub]]&lt;br /&gt;
* German: [[DE:R-Pi Hub]]&lt;br /&gt;
* Greek: [[EL:R-Pi Hub]]&lt;br /&gt;
* Hungarian: [[HU:R-Pi Hub]]&lt;br /&gt;
* Japanese: [[JP:R-Pi_Hub]]&lt;br /&gt;
* Polish: [[PL:R-Pi_Hub]]&lt;br /&gt;
* Portugese: [[pt-BR:Raspberry Pi Board]]&lt;br /&gt;
* Romanian: [[RO:R-Pi_Hub]]&lt;br /&gt;
* Russian: [[RU:RaspberryPiBoard]]&lt;br /&gt;
* Spanish: [[ES:R-Pi Hub]]&lt;br /&gt;
* Italiano: [[IT:R-Pi Hub]]&lt;br /&gt;
* Chinese:[[CH:R-Pi Hub]]&lt;br /&gt;
&lt;br /&gt;
Any help translating would be greatly appreciated. Thank you to those who have already contributed!&lt;br /&gt;
&lt;br /&gt;
===Admins/Contributors===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Talk:R-Pi_Hub|Talk]] page for outstanding issues and discussions regarding the RPi Hub and related pages. &amp;lt;br&amp;gt;&lt;br /&gt;
Also , have look at [[RPi Wiki Best Practice]]. You can discuss the recommendations &lt;br /&gt;
[[Talk:RPi Wiki Best Practice | here ]] . &lt;br /&gt;
&lt;br /&gt;
To share your thoughts, comments, thanks and interesting articles, see our [[RPi Visitor Book |Visitor Book]].&lt;br /&gt;
&lt;br /&gt;
''Big thanks to elinux.org and their groups for the wiki space and content from which these pages have been grown.''&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;br /&gt;
[[Category:RaspberryPi]]&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-30T22:52:44Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Basic}}&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
The Raspberry PI device is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
=The Ten Reasons=&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;  Home PC systems are no longer supplied with programming tools&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Barriers to entrance: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed.  Others (for example games consoles) are locked down so only authorised companies can write software for them&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring, the equivilent of teaching children how to read but not how to write&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot; &amp;quot;the dot-com bubble has burst&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_List_of_Templates</id>
		<title>RPi List of Templates</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_List_of_Templates"/>
				<updated>2012-04-30T22:52:21Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Templates which should be locked */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=Templates which should be locked=&lt;br /&gt;
* [[Template:Raspberry Pi]] for the main pages&lt;br /&gt;
* [[Template:RPi_Startup]] very important pages&lt;br /&gt;
* [[Template:RPi_Basic]] pages that don't fit into another category, such as for the page [[RPi Philosophy]]&lt;br /&gt;
&amp;lt;br&amp;gt; because: KISS&lt;br /&gt;
&lt;br /&gt;
=Useful templates=&lt;br /&gt;
* [[Template:Hub_Flags]]&lt;br /&gt;
* [[Template:RPi_Hardware]]&lt;br /&gt;
* [[Template:RPi_Software]]&lt;br /&gt;
* [[Template:RPi_Learning]]&lt;br /&gt;
* [[Template:RPi Resources]]&lt;br /&gt;
* [[Template:RPi_Tutorials]]&lt;br /&gt;
&lt;br /&gt;
[[Category:RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=References= &lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/Template:RPi_Basic</id>
		<title>Template:RPi Basic</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/Template:RPi_Basic"/>
				<updated>2012-04-30T22:50:40Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: Created page with &amp;quot;{{TOC right}} Back to the Hub.&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC right}}&lt;br /&gt;
Back to the [[R-Pi Hub|Hub]].&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-30T22:49:09Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Startup}}&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
The Raspberry PI device is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
=The Ten Reasons=&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;  Home PC systems are no longer supplied with programming tools&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Barriers to entrance: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed.  Others (for example games consoles) are locked down so only authorised companies can write software for them&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring, the equivilent of teaching children how to read but not how to write&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot; &amp;quot;the dot-com bubble has burst&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-30T22:47:28Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
The Raspberry PI device is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
=The Ten Reasons=&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;  Home PC systems are no longer supplied with programming tools&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Barriers to entrance: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed.  Others (for example games consoles) are locked down so only authorised companies can write software for them&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring, the equivilent of teaching children how to read but not how to write&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot; &amp;quot;the dot-com bubble has burst&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-30T07:16:38Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
The Raspberry PI device is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
=The Ten Reasons=&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;  Home PC systems are no longer supplied with programming tools&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Barriers to entrance: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed.  Others (for example games consoles) are locked down so only authorised companies can write software for them&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring, the equivilent of teaching children how to read but not how to write&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot; &amp;quot;the dot-com bubble has burst&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-30T07:10:45Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
The Raspberry PI device is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
=The Ten Reasons=&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;  Home PC systems are no longer supplied with programming tools&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed.  Others (for example games consoles) are locked down so only authorised companies can write software for them&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring, the equivilent of teaching children how to read but not how to write&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot; &amp;quot;the dot-com bubble has burst&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-30T07:00:06Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
The Raspberry PI device is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
=The Ten Reasons=&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring, the equivilent of teaching children how to read but not how to write&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T20:32:15Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
=The Ten Reasons=&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring, the equivilent of teaching children how to read but not how to write&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T10:47:27Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
==The Ten Reasons==&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring, the equivilent of teaching children how to read but not how to write&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T10:45:34Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
==The Ten Reasons==&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;&amp;lt;ref&amp;gt;https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T10:44:24Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Success */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
==The Ten Reasons==&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of [https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;].&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T10:43:46Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
==The Ten Reasons==&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of [https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;].&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks' pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T10:42:55Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
==The Ten Reasons==&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of [https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;].&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks pocket money - and making devices easy to recover or reset to their default state - it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T10:42:20Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
==The Ten Reasons==&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers:&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of [https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;].&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. By driving the price down to the point where devices and associated software can be purchased with a few weeks pocket money - and making devices easy to recover or reset to their default state, it should be possible to mitigate reasons 2, 3 and 4 above.  The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T10:36:15Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* The Ten Reasons */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
==The Ten Reasons==&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers.&lt;br /&gt;
&lt;br /&gt;
# No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
# Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
# Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
# Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
# Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
# Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
# Computing is “just more ICT” as presently taught in UK schools – boring&lt;br /&gt;
# Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
# Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
# Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of [https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;].&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-29T10:34:19Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Landmarks and minor drivers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
==The Ten Reasons==&lt;br /&gt;
&lt;br /&gt;
The Foundation (and educators in general&amp;lt;ref&amp;gt;http://www.computingatschool.org.uk/&amp;lt;/ref&amp;gt;) believe there are ten reasons why we aren't educating programmers.&lt;br /&gt;
&lt;br /&gt;
#. No examples/mentors/role models: &amp;quot;I don't know anyone who codes&amp;quot;&lt;br /&gt;
#. Access: About 20% of UK people do not own a computer (source OFCOM 2008) Those that do are often discouraged from experimenting. In other countries, or in the lower socio economic groups access is even more limited&lt;br /&gt;
#. Expense: &amp;quot;Development systems cost hundreds of pounds, and are hard to use&amp;quot;&lt;br /&gt;
#. Fear: &amp;quot;If I type the wrong thing I might break it&amp;quot; &amp;quot;We can’t let students write or run their own code on the schools system, as they might introduce a virus&amp;quot;&lt;br /&gt;
#. Complexity: The learning curve to get started, for example to program in VB on a PC is quite steep. Some systems (for example Android) cannot be natively programmed&lt;br /&gt;
#. Culture: &amp;quot;Coding is only for propeller heads/boys/geeks&amp;quot; &amp;quot;Computer people are all like the IT crowd&amp;quot;&lt;br /&gt;
#. Computing is “just more ICT” as presently taught in UK schools – boring&lt;br /&gt;
#. Lack of skills base in schools: &amp;quot;I know more about computers than my ICT teacher, who usually teaches PE and RI&amp;quot; &amp;quot;I don’t know where to start and my teacher can’t help&amp;quot;&lt;br /&gt;
#. Perceived difficulty: &amp;quot;I can't write anything significant on my own - it takes a big team&amp;quot;&lt;br /&gt;
#. Perceived career prospects: &amp;quot;Coding leads to low paid jobs&amp;quot; &amp;quot;Coding jobs are all offshore&amp;quot; &amp;quot;The school points system/University entrance doesn’t value Computing&amp;quot;&lt;br /&gt;
&lt;br /&gt;
These are roughly in the inverse order to the [http://en.wikipedia.org/wiki/Technological_change#Innovation ACCTO criteria] (Advantage, Complexity, Compatibility, Trialability, Observability) criteria of [https://www.google.com/search?q=Everett+Rogers+diffusion+of+innovation Everett Rogers given in his book &amp;quot;Diffusion of Innovation&amp;quot;].&lt;br /&gt;
&lt;br /&gt;
The the Raspberry Pi Device solves exactly one of those problems: that computers are too expensive. The Foundation believes that they may eventually be able to do something about the first 5&amp;lt;ref&amp;gt;http://www.raspberrypi.org/phpBB3/viewtopic.php?f=2&amp;amp;t=324&amp;amp;start=270&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Landmarks and tenets=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-22T15:16:52Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination.&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/about Back story: 'About Us' page on raspberrypi.org]&lt;br /&gt;
* [http://www.raspberrypi.org/contact-us Contacting the Raspberry Pi Foundation]&lt;br /&gt;
&lt;br /&gt;
=Landmarks and minor drivers=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-22T14:25:40Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Landmarks and minor drivers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Landmarks and minor drivers=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
[1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!  A school textbook typically costs $75-125 and has an average lifespan of three to five years before needing to be replaced due to wear or curriculum changes, although some schools keep some course textbooks for much longer.&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-22T13:56:25Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Landmarks and minor drivers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Landmarks and minor drivers=&lt;br /&gt;
&lt;br /&gt;
* It should be possible to equip a class with Raspberry Pis for no more than the average annual spend on subject (say, chemistry) textbooks for an equivilent sized class [1]&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
([1] Eben originally said that Raspberry Pi devices should cost no more than what he thought a school textbook costs.  It turns out that it has been some time since Eben purchased a school textbook!)&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hardware</id>
		<title>RPi Hardware</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hardware"/>
				<updated>2012-04-22T13:07:34Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* How Can I tell if the power supply is inadequate? */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]&lt;br /&gt;
The first product is the size of a credit card, and is designed to plug into a TV or HDMI monitor. It comes in two variants, model A and B, with B having more features. The expected price is $25 for model A and $35 for model B. The [[Rpi Low-level peripherals| GPIO pins]] on each board allow the use of optional [[Rpi expansion boards|expansion boards]].&lt;br /&gt;
&lt;br /&gt;
Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].&lt;br /&gt;
&lt;br /&gt;
==Specifications==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!&lt;br /&gt;
! Model A&lt;br /&gt;
! Model B&lt;br /&gt;
|-&lt;br /&gt;
| Target price:&amp;lt;ref name=&amp;quot;faq&amp;quot; &amp;gt;http://www.raspberrypi.org/faqs&amp;lt;/ref&amp;gt;&lt;br /&gt;
| US$25 (GBP £16)&lt;br /&gt;
| US$35 (GBP £22)&lt;br /&gt;
|-&lt;br /&gt;
| System-on-a-chip (SoC):&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom BCM2835 (CPU + GPU + SDRAM)&lt;br /&gt;
|-&lt;br /&gt;
| CPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 700&amp;amp;nbsp;MHz ARM11 ARM1176JZF-S core&lt;br /&gt;
|-&lt;br /&gt;
| GPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode &lt;br /&gt;
|-&lt;br /&gt;
| Memory (SDRAM)iB&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 256 MiB (previously listed as 128MiB for model A, but an upgrade to 256MiB was announced on 29 Feb 2012)&lt;br /&gt;
|-&lt;br /&gt;
| USB 2.0 ports:&lt;br /&gt;
| 1(provided by the BCM2835)&lt;br /&gt;
| 2 (via integrated USB hub)&lt;br /&gt;
|-&lt;br /&gt;
| Video outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Composite video|Composite RCA, HDMI (not at the same time)&lt;br /&gt;
|-&lt;br /&gt;
| Audio outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | TRS connector|3.5 mm jack, HDMI&lt;br /&gt;
|-&lt;br /&gt;
| Audio inputs:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | none, but a USB mic or sound-card could be added&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Storage:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Secure Digital|SD / MMC / SDIO card slot&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Network:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| None&lt;br /&gt;
| 10/100 wired Ethernet RJ45&lt;br /&gt;
|-&lt;br /&gt;
| Low-level peripherals:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S&amp;lt;ref name=&amp;quot;i2s&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;, Universal asynchronous receiver/transmitter (UART)&lt;br /&gt;
|-&lt;br /&gt;
| Real-time clock:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | None&lt;br /&gt;
|-&lt;br /&gt;
| Power ratings (provisional, from alpha board):&lt;br /&gt;
| 500mA, (2.5 Watt) &amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| 700mA, (3.5 Watt)&lt;br /&gt;
|-&lt;br /&gt;
| Power source:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 5V via Micro USB or GPIO header&lt;br /&gt;
|-&lt;br /&gt;
| Size:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 85.60mm x 53.98mm&amp;lt;ref&amp;gt;[http://www.raspberrypi.org/archives/344 Final PCB artwork]&amp;lt;/ref&amp;gt; (3.370 × 2.125 inch)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Components==&lt;br /&gt;
[[File:Raspi-Model-AB-Mono-2-699x1024.png|400px|thumb|right|A diagram denoting the places of the different components on the Rpi, made by Paul&lt;br /&gt;
Beech, edited to show 256MB ram for both boards]]&lt;br /&gt;
(Provisional - some of the expansion interfaces won't be available on production boards)&lt;br /&gt;
(PCB IDs are those of the Model B Beta board) &lt;br /&gt;
&lt;br /&gt;
* SoC: [http://www.broadcom.com/products/BCM2835 Broadcom BCM2835 media processor] ([http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf datasheet], [[BCM2835 datasheet errata]]) system-on-chip featuring:&lt;br /&gt;
** CPU core: [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0301h/DDI0301H_arm1176jzfs_r0p7_trm.pdf ARM1176JZF-S] ARM11 core clocked at 700MHz; ARM VFP.  The ARM11 core implements the ARMv6 Architecture.  For details on ARM instruction sets and naming conventions, see [http://en.wikipedia.org/wiki/ARM_architecture ARM architecture] and [http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores List of ARM microprocessor cores].&lt;br /&gt;
** GPU core: a Broadcom [http://en.wikipedia.org/wiki/Videocore VideoCore] IV GPU providing OpenGL ES 1.1, OpenGL ES 2.0, hardware-accelerated OpenVG 1.1, Open EGL, OpenMAX and 1080p30 H.264 high-profile decode.  There are 24 GFLOPS of general purpose compute and a bunch of texture filtering and DMA infrastructure.  Eben worked on the architecture team for this and the Raspberry Pi team are looking at how they can make some of the proprietary features available to application programmers&lt;br /&gt;
** DSP core: There is a DSP, but there isn't currently a public API (Liz thinks the BC team are keen to make one available at some point)&lt;br /&gt;
** 256MiB of SDRAM.  The RAM is physically stacked on top of the Broadcom media processor (package-on-package technology)&lt;br /&gt;
* LAN9512 ([http://www.smsc.com/media/Downloads_Public/Data_Briefs/9512db.pdf Data Brief] | [http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf Data Sheet])'''(Model B)''' providing:&lt;br /&gt;
** 10/100Mb Ethernet (Auto-MDIX)&amp;lt;ref name=autoMDIX&amp;gt;[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]&amp;lt;/ref&amp;gt;&lt;br /&gt;
** 2x USB 2.0 &lt;br /&gt;
* S1: Micro USB power jack (5v - Power Only)&lt;br /&gt;
* S2: DSI interface.  15-pin surface mounted flat flex connector, providing two data lanes, one clock lane, 3.3V and GND.&lt;br /&gt;
* S3: HDMI connector providing type A HDMI 1.3a out&lt;br /&gt;
* S4: Composite Video connector: RCA&lt;br /&gt;
* S5: MIPI CSI-2 interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S6: Audio connector: 3.5mm stereo jack (output only)&lt;br /&gt;
* S8: SD/MMC/SDIO memory card slot (underside)&lt;br /&gt;
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''&lt;br /&gt;
* P1: 26-pin 2.54mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]&lt;br /&gt;
** 8 GPIOs at 3v3&lt;br /&gt;
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3&lt;br /&gt;
** I2C interface (3v3); or 2 GPIOs at 3v3&lt;br /&gt;
** SPI interface (3v3); or 5 GPIOs at 3v3&lt;br /&gt;
** 3v3, 5v and GND supply pins&lt;br /&gt;
** ARM JTAG (if pins are reconfigured in software)&lt;br /&gt;
** Second I2C interface (3v3) (if pins are reconfigured in software)&lt;br /&gt;
** I2S interface (if pins are reconfigured in software, hardware hack may be required&amp;lt;ref name=&amp;quot;i2s&amp;quot;/&amp;gt;)&lt;br /&gt;
** 6 pins reserved for future use&lt;br /&gt;
* P2 8-pin 2.54mm header expansion providing GPU JTAG (ARM11 pinout, pin 7 is nofit for locating)&lt;br /&gt;
* P3: 7-pin 2.54mm header expansion (header not fitted), providing LAN9512 JTAG (pin 6 is nofit for locating)&lt;br /&gt;
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''&lt;br /&gt;
* TP1 and TP2: Test Points giving access to +5V and GND respectively&lt;br /&gt;
* 5 Status LEDs&amp;lt;ref name=&amp;quot;PCBs&amp;quot;&amp;gt;[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDs&amp;quot;&amp;gt;[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDsGPIO&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/what-do-the-status-indicator-leds-indicate-the-status-of Forum:What do the status indicator LEDs indicate the status of?]&amp;lt;/ref&amp;gt;:&lt;br /&gt;
** D5(Yellow) - OK  - SDCard Access (via GPIO16)&lt;br /&gt;
** D6(Red) - PWR - 3.3V Power&lt;br /&gt;
** D7(Green) - FDX - Full Duplex (LAN) '''(Model B)'''&lt;br /&gt;
** D8(Green) - LNK - Link/Activity (LAN) '''(Model B)'''&lt;br /&gt;
** D9(Yellow) - 10M - 10/100Mbit (LAN) '''(Model B)'''&lt;br /&gt;
&lt;br /&gt;
* Board size: 85.60mm x 53.98mm.  Overall height expected to be less than 25mm. &amp;lt;ref name=&amp;quot;artwork&amp;quot;&amp;gt;http://www.raspberrypi.org/archives/344&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Weight: &amp;lt;40g? (Alpha board weighs ~55g &amp;lt;ref&amp;gt;http://www.raspberrypi.org/?page_id=43&amp;amp;mingleforumaction=viewtopic&amp;amp;t=285.0&amp;lt;/ref&amp;gt;)&lt;br /&gt;
* 6 layer PCB &amp;lt;ref name=&amp;quot;artwork&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Schematic / Layout==&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot]&lt;br /&gt;
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot, labelled version]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1-300x225.jpg Low-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back-300x225.jpg Low-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1.jpg High-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back.jpg High-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official schematics PDF] | [[RPi_schematic_errata|errata]]&lt;br /&gt;
&lt;br /&gt;
==Power==&lt;br /&gt;
&lt;br /&gt;
The board takes fixed 5V input, (with the 1V2 core voltage generated directly from the input using the internal switch-mode supply on the BCM2835 die). &lt;br /&gt;
This permits adoption of the micro USB form factor, which, in turn, prevents the user from inadvertently plugging in out-of-range power inputs; that would be dangerous, since the 5V would go straight to HDMI and output USB ports, even though the problem should be mitigated by some protections applied to the input power: The board provides a polarity protection diode, a voltage clamp, and a self-resetting semiconductor fuse.&lt;br /&gt;
&lt;br /&gt;
Power consumption of the Raspberry Pi device is&lt;br /&gt;
&lt;br /&gt;
* Board A: 5V, 500 mA (2.5W) '''minimum, without any devices connected''' (e.g. USB, Ethernet, HDMI)&lt;br /&gt;
* Board B: 5V, 700 mA (3.5W) '''minimum, without any devices connected''' (e.g. USB, Ethernet, HDMI)&lt;br /&gt;
&lt;br /&gt;
You will need to provide a power supply that can provide enough current to power the device plus any connected peripherals, and taking into account inefficiencies of the supply itself and the cable between the power supply and Raspberry Pi.  The Foundation and its distributors haven't made any formal recommendations of power supply yet, but opting for one that can supply at least 1A is advisable by the community.&lt;br /&gt;
&lt;br /&gt;
*As the 5V rail is brought out in the [[Rpi_Low-level_peripherals | GPIO pins]], you can power the Rpi from there too. You should mind however, that those are ''behind'' the power protection circuitry , so you should provide your own.&lt;br /&gt;
* It is possible to power the Rpi from a powered USB hub the Rpi controls, but only on 'dumb' devices, that allow the port to supply the full current without waiting for the usb device to ask for it[http://www.raspberrypi.org/forum/general-discussion/power-pi-from-usb-hub-connected-to-pi]. As the power input of the Rpi doesn't have its data leads connected, there is no chance for a communication loop of some sorts.&lt;br /&gt;
* POE ([http://nl.wikipedia.org/wiki/Power_over_Ethernet power over ethernet]) is currently not available for the Rpi (but nobody stops you from taking your soldering iron and doing it yourself)&lt;br /&gt;
&lt;br /&gt;
===Power Supply Problems===&lt;br /&gt;
&lt;br /&gt;
There have been a number of problems reported that seem to be caused by inadequate power, this is an attempt to explain what is needed and the consequences of not having enough power.&lt;br /&gt;
&lt;br /&gt;
The power required by the Pi will vary depending on how busy it is and what peripherals are connected.&lt;br /&gt;
* Running a GUI will take more power.&lt;br /&gt;
* The USB devices and Ethernet connection will take power.&lt;br /&gt;
* Running software will take power.&lt;br /&gt;
&lt;br /&gt;
This means that it's difficult to say exactly how much power is needed.  People have reported current requirements of between 300mA and 550mA. But it could in reality take more, especially for short periods. A simple multimeter will not show short surges on the power requirement. A surge in the power requirement for a few milliseconds will not be detectable by a meter but will be enough to cause problems.&lt;br /&gt;
If the board does not get enough power the voltage will drop. If it drops enough parts of the system will run unreliably because data can get corrupted.  The USB IC runs on 5V and handles the USB and Ethernet ports so it's likely that this will be the first thing to fail. Problems seen are unreliable Ethernet connection and unreliable operation of the Keyboard and/or mouse.&lt;br /&gt;
&lt;br /&gt;
There are several reasons why the power to the board may be inadequate:&lt;br /&gt;
* The PSU may not deliver enough power.  Although the maximum power requirement is said to be 700mA, that is with no peripherals connected (USB, Ethernet etc), so a 1000mA PSU should be regarded as a minimum.  This allows some leeway in case the power supply cannot deliver it's full power without the voltage dropping.&lt;br /&gt;
* The PSU is not regulated.&lt;br /&gt;
* The cable connecting the PSU to the Pi may not be good. People have reported cables with 4 ohms resistance on the power connections. At 500mA drain this would reduce a 5V supply to 3V.&lt;br /&gt;
&lt;br /&gt;
====How Can I tell if the power supply is inadequate?====&lt;br /&gt;
&lt;br /&gt;
Common symptoms of an inadequate power supply are&lt;br /&gt;
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.&lt;br /&gt;
* SD card errors at start up seems to be another symptom of poor power.&lt;br /&gt;
&lt;br /&gt;
If you think you have a problem with your power supply, it is a good idea to check the actual voltage&lt;br /&gt;
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board&lt;br /&gt;
to facilitate voltage measurements.&lt;br /&gt;
&lt;br /&gt;
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.  Anything inside, but close to the limits, of this range ''may'' indicate a problem.&lt;br /&gt;
&lt;br /&gt;
[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]&lt;br /&gt;
&lt;br /&gt;
====Things that can cause problems====&lt;br /&gt;
* A USB connection on a TV or PC. The USB power supply specification is for up to 500mA and if the TV implements this then it can cause problems.  The system may work initially but be unreliable because as it becomes more active the power requirement increases.&lt;br /&gt;
* A single supply from a powered hub.  Most hubs seem to deliver more than the specified current but there's no guarantee.  Check the power supply rating, it must be enough to supply everything that's connected to the hub.&lt;br /&gt;
* A power supply that is rated for less than 700mA may work some of the time.&lt;br /&gt;
* Adding a USB hard disk drive. A HDD will take quite a lot of power as it starts, maybe an amp or more. It the power supply for this also supplies the Pi then this could overload things and cause trouble.&lt;br /&gt;
* Some complex keyboards have been reported to take a considerable amount of power, maybe up to 500mA.  The Pi cannot deliver this amount of power.  Simpler budget keyboards may be better. If the system works with no keyboard attached but not with a keyboard then it's worth trying a different, simpler, keyboard.&lt;br /&gt;
&lt;br /&gt;
====Summary====&lt;br /&gt;
&lt;br /&gt;
* If you are having unreliable operation the first thing to do is check your power supply.&lt;br /&gt;
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).&lt;br /&gt;
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.&lt;br /&gt;
* Not all power supplies will deliver what they claim.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hardware</id>
		<title>RPi Hardware</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hardware"/>
				<updated>2012-04-22T13:03:06Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Power */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]&lt;br /&gt;
The first product is the size of a credit card, and is designed to plug into a TV or HDMI monitor. It comes in two variants, model A and B, with B having more features. The expected price is $25 for model A and $35 for model B. The [[Rpi Low-level peripherals| GPIO pins]] on each board allow the use of optional [[Rpi expansion boards|expansion boards]].&lt;br /&gt;
&lt;br /&gt;
Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].&lt;br /&gt;
&lt;br /&gt;
==Specifications==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!&lt;br /&gt;
! Model A&lt;br /&gt;
! Model B&lt;br /&gt;
|-&lt;br /&gt;
| Target price:&amp;lt;ref name=&amp;quot;faq&amp;quot; &amp;gt;http://www.raspberrypi.org/faqs&amp;lt;/ref&amp;gt;&lt;br /&gt;
| US$25 (GBP £16)&lt;br /&gt;
| US$35 (GBP £22)&lt;br /&gt;
|-&lt;br /&gt;
| System-on-a-chip (SoC):&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom BCM2835 (CPU + GPU + SDRAM)&lt;br /&gt;
|-&lt;br /&gt;
| CPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 700&amp;amp;nbsp;MHz ARM11 ARM1176JZF-S core&lt;br /&gt;
|-&lt;br /&gt;
| GPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode &lt;br /&gt;
|-&lt;br /&gt;
| Memory (SDRAM)iB&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 256 MiB (previously listed as 128MiB for model A, but an upgrade to 256MiB was announced on 29 Feb 2012)&lt;br /&gt;
|-&lt;br /&gt;
| USB 2.0 ports:&lt;br /&gt;
| 1(provided by the BCM2835)&lt;br /&gt;
| 2 (via integrated USB hub)&lt;br /&gt;
|-&lt;br /&gt;
| Video outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Composite video|Composite RCA, HDMI (not at the same time)&lt;br /&gt;
|-&lt;br /&gt;
| Audio outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | TRS connector|3.5 mm jack, HDMI&lt;br /&gt;
|-&lt;br /&gt;
| Audio inputs:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | none, but a USB mic or sound-card could be added&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Storage:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Secure Digital|SD / MMC / SDIO card slot&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Network:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| None&lt;br /&gt;
| 10/100 wired Ethernet RJ45&lt;br /&gt;
|-&lt;br /&gt;
| Low-level peripherals:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S&amp;lt;ref name=&amp;quot;i2s&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;, Universal asynchronous receiver/transmitter (UART)&lt;br /&gt;
|-&lt;br /&gt;
| Real-time clock:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | None&lt;br /&gt;
|-&lt;br /&gt;
| Power ratings (provisional, from alpha board):&lt;br /&gt;
| 500mA, (2.5 Watt) &amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| 700mA, (3.5 Watt)&lt;br /&gt;
|-&lt;br /&gt;
| Power source:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 5V via Micro USB or GPIO header&lt;br /&gt;
|-&lt;br /&gt;
| Size:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 85.60mm x 53.98mm&amp;lt;ref&amp;gt;[http://www.raspberrypi.org/archives/344 Final PCB artwork]&amp;lt;/ref&amp;gt; (3.370 × 2.125 inch)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Components==&lt;br /&gt;
[[File:Raspi-Model-AB-Mono-2-699x1024.png|400px|thumb|right|A diagram denoting the places of the different components on the Rpi, made by Paul&lt;br /&gt;
Beech, edited to show 256MB ram for both boards]]&lt;br /&gt;
(Provisional - some of the expansion interfaces won't be available on production boards)&lt;br /&gt;
(PCB IDs are those of the Model B Beta board) &lt;br /&gt;
&lt;br /&gt;
* SoC: [http://www.broadcom.com/products/BCM2835 Broadcom BCM2835 media processor] ([http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf datasheet], [[BCM2835 datasheet errata]]) system-on-chip featuring:&lt;br /&gt;
** CPU core: [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0301h/DDI0301H_arm1176jzfs_r0p7_trm.pdf ARM1176JZF-S] ARM11 core clocked at 700MHz; ARM VFP.  The ARM11 core implements the ARMv6 Architecture.  For details on ARM instruction sets and naming conventions, see [http://en.wikipedia.org/wiki/ARM_architecture ARM architecture] and [http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores List of ARM microprocessor cores].&lt;br /&gt;
** GPU core: a Broadcom [http://en.wikipedia.org/wiki/Videocore VideoCore] IV GPU providing OpenGL ES 1.1, OpenGL ES 2.0, hardware-accelerated OpenVG 1.1, Open EGL, OpenMAX and 1080p30 H.264 high-profile decode.  There are 24 GFLOPS of general purpose compute and a bunch of texture filtering and DMA infrastructure.  Eben worked on the architecture team for this and the Raspberry Pi team are looking at how they can make some of the proprietary features available to application programmers&lt;br /&gt;
** DSP core: There is a DSP, but there isn't currently a public API (Liz thinks the BC team are keen to make one available at some point)&lt;br /&gt;
** 256MiB of SDRAM.  The RAM is physically stacked on top of the Broadcom media processor (package-on-package technology)&lt;br /&gt;
* LAN9512 ([http://www.smsc.com/media/Downloads_Public/Data_Briefs/9512db.pdf Data Brief] | [http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf Data Sheet])'''(Model B)''' providing:&lt;br /&gt;
** 10/100Mb Ethernet (Auto-MDIX)&amp;lt;ref name=autoMDIX&amp;gt;[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]&amp;lt;/ref&amp;gt;&lt;br /&gt;
** 2x USB 2.0 &lt;br /&gt;
* S1: Micro USB power jack (5v - Power Only)&lt;br /&gt;
* S2: DSI interface.  15-pin surface mounted flat flex connector, providing two data lanes, one clock lane, 3.3V and GND.&lt;br /&gt;
* S3: HDMI connector providing type A HDMI 1.3a out&lt;br /&gt;
* S4: Composite Video connector: RCA&lt;br /&gt;
* S5: MIPI CSI-2 interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S6: Audio connector: 3.5mm stereo jack (output only)&lt;br /&gt;
* S8: SD/MMC/SDIO memory card slot (underside)&lt;br /&gt;
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''&lt;br /&gt;
* P1: 26-pin 2.54mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]&lt;br /&gt;
** 8 GPIOs at 3v3&lt;br /&gt;
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3&lt;br /&gt;
** I2C interface (3v3); or 2 GPIOs at 3v3&lt;br /&gt;
** SPI interface (3v3); or 5 GPIOs at 3v3&lt;br /&gt;
** 3v3, 5v and GND supply pins&lt;br /&gt;
** ARM JTAG (if pins are reconfigured in software)&lt;br /&gt;
** Second I2C interface (3v3) (if pins are reconfigured in software)&lt;br /&gt;
** I2S interface (if pins are reconfigured in software, hardware hack may be required&amp;lt;ref name=&amp;quot;i2s&amp;quot;/&amp;gt;)&lt;br /&gt;
** 6 pins reserved for future use&lt;br /&gt;
* P2 8-pin 2.54mm header expansion providing GPU JTAG (ARM11 pinout, pin 7 is nofit for locating)&lt;br /&gt;
* P3: 7-pin 2.54mm header expansion (header not fitted), providing LAN9512 JTAG (pin 6 is nofit for locating)&lt;br /&gt;
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''&lt;br /&gt;
* TP1 and TP2: Test Points giving access to +5V and GND respectively&lt;br /&gt;
* 5 Status LEDs&amp;lt;ref name=&amp;quot;PCBs&amp;quot;&amp;gt;[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDs&amp;quot;&amp;gt;[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDsGPIO&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/what-do-the-status-indicator-leds-indicate-the-status-of Forum:What do the status indicator LEDs indicate the status of?]&amp;lt;/ref&amp;gt;:&lt;br /&gt;
** D5(Yellow) - OK  - SDCard Access (via GPIO16)&lt;br /&gt;
** D6(Red) - PWR - 3.3V Power&lt;br /&gt;
** D7(Green) - FDX - Full Duplex (LAN) '''(Model B)'''&lt;br /&gt;
** D8(Green) - LNK - Link/Activity (LAN) '''(Model B)'''&lt;br /&gt;
** D9(Yellow) - 10M - 10/100Mbit (LAN) '''(Model B)'''&lt;br /&gt;
&lt;br /&gt;
* Board size: 85.60mm x 53.98mm.  Overall height expected to be less than 25mm. &amp;lt;ref name=&amp;quot;artwork&amp;quot;&amp;gt;http://www.raspberrypi.org/archives/344&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Weight: &amp;lt;40g? (Alpha board weighs ~55g &amp;lt;ref&amp;gt;http://www.raspberrypi.org/?page_id=43&amp;amp;mingleforumaction=viewtopic&amp;amp;t=285.0&amp;lt;/ref&amp;gt;)&lt;br /&gt;
* 6 layer PCB &amp;lt;ref name=&amp;quot;artwork&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Schematic / Layout==&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot]&lt;br /&gt;
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot, labelled version]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1-300x225.jpg Low-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back-300x225.jpg Low-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1.jpg High-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back.jpg High-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official schematics PDF] | [[RPi_schematic_errata|errata]]&lt;br /&gt;
&lt;br /&gt;
==Power==&lt;br /&gt;
&lt;br /&gt;
The board takes fixed 5V input, (with the 1V2 core voltage generated directly from the input using the internal switch-mode supply on the BCM2835 die). &lt;br /&gt;
This permits adoption of the micro USB form factor, which, in turn, prevents the user from inadvertently plugging in out-of-range power inputs; that would be dangerous, since the 5V would go straight to HDMI and output USB ports, even though the problem should be mitigated by some protections applied to the input power: The board provides a polarity protection diode, a voltage clamp, and a self-resetting semiconductor fuse.&lt;br /&gt;
&lt;br /&gt;
Power consumption of the Raspberry Pi device is&lt;br /&gt;
&lt;br /&gt;
* Board A: 5V, 500 mA (2.5W) '''minimum, without any devices connected''' (e.g. USB, Ethernet, HDMI)&lt;br /&gt;
* Board B: 5V, 700 mA (3.5W) '''minimum, without any devices connected''' (e.g. USB, Ethernet, HDMI)&lt;br /&gt;
&lt;br /&gt;
You will need to provide a power supply that can provide enough current to power the device plus any connected peripherals, and taking into account inefficiencies of the supply itself and the cable between the power supply and Raspberry Pi.  The Foundation and its distributors haven't made any formal recommendations of power supply yet, but opting for one that can supply at least 1A is advisable by the community.&lt;br /&gt;
&lt;br /&gt;
*As the 5V rail is brought out in the [[Rpi_Low-level_peripherals | GPIO pins]], you can power the Rpi from there too. You should mind however, that those are ''behind'' the power protection circuitry , so you should provide your own.&lt;br /&gt;
* It is possible to power the Rpi from a powered USB hub the Rpi controls, but only on 'dumb' devices, that allow the port to supply the full current without waiting for the usb device to ask for it[http://www.raspberrypi.org/forum/general-discussion/power-pi-from-usb-hub-connected-to-pi]. As the power input of the Rpi doesn't have its data leads connected, there is no chance for a communication loop of some sorts.&lt;br /&gt;
* POE ([http://nl.wikipedia.org/wiki/Power_over_Ethernet power over ethernet]) is currently not available for the Rpi (but nobody stops you from taking your soldering iron and doing it yourself)&lt;br /&gt;
&lt;br /&gt;
===Power Supply Problems===&lt;br /&gt;
&lt;br /&gt;
There have been a number of problems reported that seem to be caused by inadequate power, this is an attempt to explain what is needed and the consequences of not having enough power.&lt;br /&gt;
&lt;br /&gt;
The power required by the Pi will vary depending on how busy it is and what peripherals are connected.&lt;br /&gt;
* Running a GUI will take more power.&lt;br /&gt;
* The USB devices and Ethernet connection will take power.&lt;br /&gt;
* Running software will take power.&lt;br /&gt;
&lt;br /&gt;
This means that it's difficult to say exactly how much power is needed.  People have reported current requirements of between 300mA and 550mA. But it could in reality take more, especially for short periods. A simple multimeter will not show short surges on the power requirement. A surge in the power requirement for a few milliseconds will not be detectable by a meter but will be enough to cause problems.&lt;br /&gt;
If the board does not get enough power the voltage will drop. If it drops enough parts of the system will run unreliably because data can get corrupted.  The USB IC runs on 5V and handles the USB and Ethernet ports so it's likely that this will be the first thing to fail. Problems seen are unreliable Ethernet connection and unreliable operation of the Keyboard and/or mouse.&lt;br /&gt;
&lt;br /&gt;
There are several reasons why the power to the board may be inadequate:&lt;br /&gt;
* The PSU may not deliver enough power.  Although the maximum power requirement is said to be 700mA, that is with no peripherals connected (USB, Ethernet etc), so a 1000mA PSU should be regarded as a minimum.  This allows some leeway in case the power supply cannot deliver it's full power without the voltage dropping.&lt;br /&gt;
* The PSU is not regulated.&lt;br /&gt;
* The cable connecting the PSU to the Pi may not be good. People have reported cables with 4 ohms resistance on the power connections. At 500mA drain this would reduce a 5V supply to 3V.&lt;br /&gt;
&lt;br /&gt;
====How Can I tell if the power supply is inadequate?====&lt;br /&gt;
&lt;br /&gt;
Common symptoms of an inadequate power supply are&lt;br /&gt;
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.&lt;br /&gt;
* SD card errors at start up seems to be another symptom of poor power.&lt;br /&gt;
&lt;br /&gt;
If you think you have a problem with your power supply, it is a good idea to check the actual voltage&lt;br /&gt;
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board&lt;br /&gt;
to facilitate voltage measurements.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]&lt;br /&gt;
&lt;br /&gt;
====Things that can cause problems====&lt;br /&gt;
* A USB connection on a TV or PC. The USB power supply specification is for up to 500mA and if the TV implements this then it can cause problems.  The system may work initially but be unreliable because as it becomes more active the power requirement increases.&lt;br /&gt;
* A single supply from a powered hub.  Most hubs seem to deliver more than the specified current but there's no guarantee.  Check the power supply rating, it must be enough to supply everything that's connected to the hub.&lt;br /&gt;
* A power supply that is rated for less than 700mA may work some of the time.&lt;br /&gt;
* Adding a USB hard disk drive. A HDD will take quite a lot of power as it starts, maybe an amp or more. It the power supply for this also supplies the Pi then this could overload things and cause trouble.&lt;br /&gt;
* Some complex keyboards have been reported to take a considerable amount of power, maybe up to 500mA.  The Pi cannot deliver this amount of power.  Simpler budget keyboards may be better. If the system works with no keyboard attached but not with a keyboard then it's worth trying a different, simpler, keyboard.&lt;br /&gt;
&lt;br /&gt;
====Summary====&lt;br /&gt;
&lt;br /&gt;
* If you are having unreliable operation the first thing to do is check your power supply.&lt;br /&gt;
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).&lt;br /&gt;
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.&lt;br /&gt;
* Not all power supplies will deliver what they claim.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hub</id>
		<title>RPi Hub</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hub"/>
				<updated>2012-04-22T11:59:05Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Now shipping to customers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC right}}{{Template:Hub_Flags}} &amp;lt;!-- please edit template to alter banner and flag display on all hubs --&amp;gt;&lt;br /&gt;
{{Clear}}&lt;br /&gt;
'''The Raspberry Pi wiki pages on this site are a community work - the Raspberry Pi Foundation is not responsible for content on these pages.'''&lt;br /&gt;
&lt;br /&gt;
==Now shipping to customers==&lt;br /&gt;
Premier Farnell and RS Components have started shipping to customers. Congratulations to those at the front of the queue.&lt;br /&gt;
&lt;br /&gt;
Work is ongoing to clear the backlog of orders.&lt;br /&gt;
&lt;br /&gt;
See the [[RPi Buying Guide | Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]&lt;br /&gt;
&lt;br /&gt;
==About==&lt;br /&gt;
[[File:RpiFront.jpg|300px|thumb|right|The Rpi beta board (model B)]]&lt;br /&gt;
&lt;br /&gt;
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. We expect this computer to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
* 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.&lt;br /&gt;
* Products are RoHS, CE, FCC, CTick and CSA compliant.  Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.&lt;br /&gt;
* Expected cost: ~16GBP or 25USD Model A, ~23GBP or 35USD for Model B. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===History===&lt;br /&gt;
* Confused about seeing different versions of the board? Visit the [[Rpi HardwareHistory | History of the Raspberry Pi Hardware]] for information about the past versions.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
&lt;br /&gt;
* 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)&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
===[[Buying RPi |Buying Guide]]===&lt;br /&gt;
----&lt;br /&gt;
Where can I get one and for how much?&lt;br /&gt;
* Raspberry Pi can only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.&lt;br /&gt;
&lt;br /&gt;
* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop].&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Hardware Basic Setup | Basic Setup]]===&lt;br /&gt;
----&lt;br /&gt;
First little Raspberry Pi Steps...&lt;br /&gt;
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.&lt;br /&gt;
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.&lt;br /&gt;
* Prepare your SD card with the [http://www.raspberrypi.org/archives/805 Pi Fedora Remix Operating System] - more details see [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix Fedora's Raspberry Pi wiki].&lt;br /&gt;
&lt;br /&gt;
* '''Having problems? Try the [http://elinux.org/R-Pi_Troubleshooting Troubleshooting] page.'''&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Beginners | Beginners Guide]]===&lt;br /&gt;
----&lt;br /&gt;
You've just got your new Raspberry Pi device - what now?&lt;br /&gt;
* [[RPi Beginners | Beginners Guide]]&lt;br /&gt;
&lt;br /&gt;
* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.&lt;br /&gt;
&lt;br /&gt;
* Get started with some basic projects and tutorials:&lt;br /&gt;
[[RPi Tutorial Easy GPIO Hardware &amp;amp; Software | Easy GPIO Hardware &amp;amp; Software]] - in-progress at the moment&lt;br /&gt;
 Example projects/tuts which can be linked from here&lt;br /&gt;
 (or from within a beginners guide page perhaps):&lt;br /&gt;
  Setup XBMC media centre&lt;br /&gt;
  Programming tutorials (Liams YouTube etc)&lt;br /&gt;
  Easy GPIO (when complete or similar thing).&lt;br /&gt;
  Also links to some basic linux user guides.&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Hardware|Hardware]] &amp;amp; [[RPi VerifiedPeripherals|Peripherals]]===&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
*The Model B is more advanced than the Model A - see [[RPi Hardware]].&lt;br /&gt;
*The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].&lt;br /&gt;
*The unit will support a range of [[RPi VerifiedPeripherals |USB devices, peripherals and accessories]].&lt;br /&gt;
*The [[Rpi Low-level peripherals| Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.&lt;br /&gt;
*For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].&lt;br /&gt;
*[[RPi Peripherals|Setting up peripherals - examples/HowTos]]&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[Rpi_Software|Software]] &amp;amp; [[RPi_Distributions|OS Distributions]]===&lt;br /&gt;
----&lt;br /&gt;
The Raspberry Pi will run a range of OS Distributions and run a variety of software.&lt;br /&gt;
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.&lt;br /&gt;
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/PuppySchoolRaspberryPi Raspberry PupPy] from Puppy Linux.&lt;br /&gt;
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]] or [[RPi_Performance|test the Pi's performance]].&lt;br /&gt;
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Documentation|Documentation]]===&lt;br /&gt;
----&lt;br /&gt;
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].&lt;br /&gt;
&lt;br /&gt;
[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]&lt;br /&gt;
&lt;br /&gt;
 Example documents which can be linked from here (or sub page):&lt;br /&gt;
  Official Datasheets&lt;br /&gt;
  White Papers&lt;br /&gt;
  User Manuals&lt;br /&gt;
  Recommended books (perhaps)&lt;br /&gt;
&lt;br /&gt;
===[[R-Pi Troubleshooting|How to fix common problems]]===&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Community==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Projects |Projects]], [[RPi Guides |Guides]] &amp;amp; [[RPi Tutorials |Tutorials]]===&lt;br /&gt;
----&lt;br /&gt;
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].&lt;br /&gt;
*Knowledgeable users may want to review and help out with the [[RPi Tasks |Tasks page]].&lt;br /&gt;
*Get started by following some of the many [[RPi Tutorials | Tutorials]].&lt;br /&gt;
*Common tasks and useful tip are available through the [[RPi Guides | Guides page]]. &lt;br /&gt;
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[Rpi Education|Schools, Universities, Clubs &amp;amp; Groups]]===&lt;br /&gt;
----&lt;br /&gt;
*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.&lt;br /&gt;
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
===[[RPi Community |Supporting Communities]]===&lt;br /&gt;
----&lt;br /&gt;
The [[RPi Community |Raspberry Pi Community]] is steadily growing: &lt;br /&gt;
*[http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]&lt;br /&gt;
&lt;br /&gt;
*[http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]&lt;br /&gt;
&lt;br /&gt;
*[http://www.raspberrymod.com/ Raspberrymod] and [http://www.raspberrypiforums.com/forum RPiforums] Un-Official Raspberry Pi Discussion Boards&lt;br /&gt;
&lt;br /&gt;
*[http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]&lt;br /&gt;
&lt;br /&gt;
*[http://www.worldofpi/com/ World Of Pi] A forum based on all things Raspberry Pi.&lt;br /&gt;
&lt;br /&gt;
*[[RPi Community Magazine]] - User contributed eMagazine, get involved!&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==About the RPi Wiki==&lt;br /&gt;
&lt;br /&gt;
'''Do not be afraid to add your bit, content is vital for the wiki to function.'''&lt;br /&gt;
&lt;br /&gt;
[[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]]]&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Translations ===&lt;br /&gt;
&lt;br /&gt;
The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:&lt;br /&gt;
&lt;br /&gt;
* English: [[R-Pi Hub]]&lt;br /&gt;
* French: [[FR:R-Pi Hub]]&lt;br /&gt;
* German: [[DE:R-Pi Hub]]&lt;br /&gt;
* Greek: [[EL:R-Pi Hub]]&lt;br /&gt;
* Hungarian: [[HU:R-Pi Hub]]&lt;br /&gt;
* Japanese: [[JP:R-Pi_Hub]]&lt;br /&gt;
* Polish: [[PL:R-Pi_Hub]]&lt;br /&gt;
* Portugese: [[pt-BR:Raspberry Pi Board]]&lt;br /&gt;
* Romanian: [[RO:R-Pi_Hub]]&lt;br /&gt;
* Russian: [[RU:RaspberryPiBoard]]&lt;br /&gt;
* Spanish: [[ES:R-Pi Hub]]&lt;br /&gt;
* Italiano: [[IT:R-Pi Hub]]&lt;br /&gt;
* Chinese:[[CH:R-Pi Hub]]&lt;br /&gt;
&lt;br /&gt;
Any help translating would be greatly appreciated. Thank you to those who have already contributed!&lt;br /&gt;
&lt;br /&gt;
===Admins/Contributors===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Talk:R-Pi_Hub]] page for outstanding issues and discussions regarding the RPi Hub and related pages.&lt;br /&gt;
Also , have look at [[RPi Wiki Best Practice]]. Discuss it [[Talk:RPi Wiki Best Practice | here ]]&lt;br /&gt;
&lt;br /&gt;
To share your thoughts, comments, thanks and interesting articles, see our [[RPi Visitor Book |Visitor Book]].&lt;br /&gt;
&lt;br /&gt;
''Big thanks to elinux.org and their groups for the wiki space and content from which these pages have been grown.''&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;br /&gt;
[[Category:RaspberryPi]]&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hub</id>
		<title>RPi Hub</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hub"/>
				<updated>2012-04-22T11:58:37Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* About */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC right}}{{Template:Hub_Flags}} &amp;lt;!-- please edit template to alter banner and flag display on all hubs --&amp;gt;&lt;br /&gt;
{{Clear}}&lt;br /&gt;
==Now shipping to customers==&lt;br /&gt;
Premier Farnell and RS Components have started shipping to customers. Congratulations to those at the front of the queue.&lt;br /&gt;
&lt;br /&gt;
Work is ongoing to clear the backlog of orders.&lt;br /&gt;
&lt;br /&gt;
See the [[RPi Buying Guide | Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]&lt;br /&gt;
&lt;br /&gt;
'''The Raspberry Pi wiki pages on this site are a community work - the Raspberry Pi Foundation is not responsible for content on these pages.'''&lt;br /&gt;
&lt;br /&gt;
==About==&lt;br /&gt;
[[File:RpiFront.jpg|300px|thumb|right|The Rpi beta board (model B)]]&lt;br /&gt;
&lt;br /&gt;
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. We expect this computer to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
* 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.&lt;br /&gt;
* Products are RoHS, CE, FCC, CTick and CSA compliant.  Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.&lt;br /&gt;
* Expected cost: ~16GBP or 25USD Model A, ~23GBP or 35USD for Model B. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===History===&lt;br /&gt;
* Confused about seeing different versions of the board? Visit the [[Rpi HardwareHistory | History of the Raspberry Pi Hardware]] for information about the past versions.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
&lt;br /&gt;
* 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)&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
===[[Buying RPi |Buying Guide]]===&lt;br /&gt;
----&lt;br /&gt;
Where can I get one and for how much?&lt;br /&gt;
* Raspberry Pi can only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.&lt;br /&gt;
&lt;br /&gt;
* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop].&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Hardware Basic Setup | Basic Setup]]===&lt;br /&gt;
----&lt;br /&gt;
First little Raspberry Pi Steps...&lt;br /&gt;
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.&lt;br /&gt;
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.&lt;br /&gt;
* Prepare your SD card with the [http://www.raspberrypi.org/archives/805 Pi Fedora Remix Operating System] - more details see [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix Fedora's Raspberry Pi wiki].&lt;br /&gt;
&lt;br /&gt;
* '''Having problems? Try the [http://elinux.org/R-Pi_Troubleshooting Troubleshooting] page.'''&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Beginners | Beginners Guide]]===&lt;br /&gt;
----&lt;br /&gt;
You've just got your new Raspberry Pi device - what now?&lt;br /&gt;
* [[RPi Beginners | Beginners Guide]]&lt;br /&gt;
&lt;br /&gt;
* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.&lt;br /&gt;
&lt;br /&gt;
* Get started with some basic projects and tutorials:&lt;br /&gt;
[[RPi Tutorial Easy GPIO Hardware &amp;amp; Software | Easy GPIO Hardware &amp;amp; Software]] - in-progress at the moment&lt;br /&gt;
 Example projects/tuts which can be linked from here&lt;br /&gt;
 (or from within a beginners guide page perhaps):&lt;br /&gt;
  Setup XBMC media centre&lt;br /&gt;
  Programming tutorials (Liams YouTube etc)&lt;br /&gt;
  Easy GPIO (when complete or similar thing).&lt;br /&gt;
  Also links to some basic linux user guides.&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Hardware|Hardware]] &amp;amp; [[RPi VerifiedPeripherals|Peripherals]]===&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
*The Model B is more advanced than the Model A - see [[RPi Hardware]].&lt;br /&gt;
*The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].&lt;br /&gt;
*The unit will support a range of [[RPi VerifiedPeripherals |USB devices, peripherals and accessories]].&lt;br /&gt;
*The [[Rpi Low-level peripherals| Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.&lt;br /&gt;
*For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].&lt;br /&gt;
*[[RPi Peripherals|Setting up peripherals - examples/HowTos]]&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[Rpi_Software|Software]] &amp;amp; [[RPi_Distributions|OS Distributions]]===&lt;br /&gt;
----&lt;br /&gt;
The Raspberry Pi will run a range of OS Distributions and run a variety of software.&lt;br /&gt;
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.&lt;br /&gt;
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/PuppySchoolRaspberryPi Raspberry PupPy] from Puppy Linux.&lt;br /&gt;
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]] or [[RPi_Performance|test the Pi's performance]].&lt;br /&gt;
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Documentation|Documentation]]===&lt;br /&gt;
----&lt;br /&gt;
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].&lt;br /&gt;
&lt;br /&gt;
[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]&lt;br /&gt;
&lt;br /&gt;
 Example documents which can be linked from here (or sub page):&lt;br /&gt;
  Official Datasheets&lt;br /&gt;
  White Papers&lt;br /&gt;
  User Manuals&lt;br /&gt;
  Recommended books (perhaps)&lt;br /&gt;
&lt;br /&gt;
===[[R-Pi Troubleshooting|How to fix common problems]]===&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Community==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Projects |Projects]], [[RPi Guides |Guides]] &amp;amp; [[RPi Tutorials |Tutorials]]===&lt;br /&gt;
----&lt;br /&gt;
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].&lt;br /&gt;
*Knowledgeable users may want to review and help out with the [[RPi Tasks |Tasks page]].&lt;br /&gt;
*Get started by following some of the many [[RPi Tutorials | Tutorials]].&lt;br /&gt;
*Common tasks and useful tip are available through the [[RPi Guides | Guides page]]. &lt;br /&gt;
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[Rpi Education|Schools, Universities, Clubs &amp;amp; Groups]]===&lt;br /&gt;
----&lt;br /&gt;
*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.&lt;br /&gt;
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
===[[RPi Community |Supporting Communities]]===&lt;br /&gt;
----&lt;br /&gt;
The [[RPi Community |Raspberry Pi Community]] is steadily growing: &lt;br /&gt;
*[http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]&lt;br /&gt;
&lt;br /&gt;
*[http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]&lt;br /&gt;
&lt;br /&gt;
*[http://www.raspberrymod.com/ Raspberrymod] and [http://www.raspberrypiforums.com/forum RPiforums] Un-Official Raspberry Pi Discussion Boards&lt;br /&gt;
&lt;br /&gt;
*[http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]&lt;br /&gt;
&lt;br /&gt;
*[http://www.worldofpi/com/ World Of Pi] A forum based on all things Raspberry Pi.&lt;br /&gt;
&lt;br /&gt;
*[[RPi Community Magazine]] - User contributed eMagazine, get involved!&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==About the RPi Wiki==&lt;br /&gt;
&lt;br /&gt;
'''Do not be afraid to add your bit, content is vital for the wiki to function.'''&lt;br /&gt;
&lt;br /&gt;
[[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]]]&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Translations ===&lt;br /&gt;
&lt;br /&gt;
The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:&lt;br /&gt;
&lt;br /&gt;
* English: [[R-Pi Hub]]&lt;br /&gt;
* French: [[FR:R-Pi Hub]]&lt;br /&gt;
* German: [[DE:R-Pi Hub]]&lt;br /&gt;
* Greek: [[EL:R-Pi Hub]]&lt;br /&gt;
* Hungarian: [[HU:R-Pi Hub]]&lt;br /&gt;
* Japanese: [[JP:R-Pi_Hub]]&lt;br /&gt;
* Polish: [[PL:R-Pi_Hub]]&lt;br /&gt;
* Portugese: [[pt-BR:Raspberry Pi Board]]&lt;br /&gt;
* Romanian: [[RO:R-Pi_Hub]]&lt;br /&gt;
* Russian: [[RU:RaspberryPiBoard]]&lt;br /&gt;
* Spanish: [[ES:R-Pi Hub]]&lt;br /&gt;
* Italiano: [[IT:R-Pi Hub]]&lt;br /&gt;
* Chinese:[[CH:R-Pi Hub]]&lt;br /&gt;
&lt;br /&gt;
Any help translating would be greatly appreciated. Thank you to those who have already contributed!&lt;br /&gt;
&lt;br /&gt;
===Admins/Contributors===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Talk:R-Pi_Hub]] page for outstanding issues and discussions regarding the RPi Hub and related pages.&lt;br /&gt;
Also , have look at [[RPi Wiki Best Practice]]. Discuss it [[Talk:RPi Wiki Best Practice | here ]]&lt;br /&gt;
&lt;br /&gt;
To share your thoughts, comments, thanks and interesting articles, see our [[RPi Visitor Book |Visitor Book]].&lt;br /&gt;
&lt;br /&gt;
''Big thanks to elinux.org and their groups for the wiki space and content from which these pages have been grown.''&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;br /&gt;
[[Category:RaspberryPi]]&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Philosophy</id>
		<title>RPi Philosophy</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Philosophy"/>
				<updated>2012-04-22T11:45:45Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: Created page with &amp;quot;Category: RaspberryPi  =Overview=  The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, which exists to promote the study...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
=Overview=&lt;br /&gt;
&lt;br /&gt;
The Raspberry Pi Foundation is a UK registered charity (Registration Number 1129409), based in Cambridge, 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.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI is a charitable foundation with the aim of bringing real programming and related electronics experimentation back into the classroom.&lt;br /&gt;
&lt;br /&gt;
Raspberry PI itself is a single board computer designed to bring the &amp;quot;Homebrew&amp;quot; back into electronics - getting away from the pre-packaged products, which lack the spirit of technical adventure.&lt;br /&gt;
&lt;br /&gt;
Children are naturally curious - but prising the back of your XBox or IPad does not go down well! A Raspberry PI is cheap enough to break, and powerful enough (we hope) to catch their imagination. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Landmarks and minor drivers=&lt;br /&gt;
&lt;br /&gt;
* Use of educational computers should not be fenced into 1 or 2 hours a week of 'formal curriculum time'&lt;br /&gt;
* Devices (should) belong to the student, not the school&lt;br /&gt;
* If it costs money, it doesn't get added to the hardware design&lt;br /&gt;
* A thing that you can plug into things you already own; A peripheral for your TV&lt;br /&gt;
* Follow the tail of the [http://en.wikipedia.org/wiki/Moore%27s_law#The_tip_and_tail_of_the_curve Moore's Law] curve down (ie basic computing getting cheaper over time) rather than following the tip of the curve up (over time computers becoming more powerful, with more features, while maintaining their price point relative to inflation).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Success=&lt;br /&gt;
What does success look like?&lt;br /&gt;
&lt;br /&gt;
Eben's personal view: Another 1000 Engineers a year entering the UK ICT Industry&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_VerifiedPeripherals</id>
		<title>RPi VerifiedPeripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_VerifiedPeripherals"/>
				<updated>2012-04-21T15:30:34Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Working SD Cards */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Linux]]&lt;br /&gt;
[[Category:ARM Development Boards]]&lt;br /&gt;
[[Category: Broadcom]]&lt;br /&gt;
[[Category: Development Boards]]&lt;br /&gt;
[[Category: RaspberryPi]]&lt;br /&gt;
[[Category: Education]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
&lt;br /&gt;
19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the default Debian distribution unless stated otherwise. A suggested suffix markup scheme is as follows:&lt;br /&gt;
&lt;br /&gt;
* (A) - Relates to model A production board&lt;br /&gt;
* (B) - Relates to model B production board&lt;br /&gt;
* (!) - Information from alpha board days&lt;br /&gt;
* No markup - relates to all production boards&lt;br /&gt;
&lt;br /&gt;
''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247]''&lt;br /&gt;
&lt;br /&gt;
If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Power Supplies ==&lt;br /&gt;
It is very important that a suitable power supply is used. Many of the most common issues are power related. A 5V power supply that is capable of delivering at least 700 mA (B) should be used.&lt;br /&gt;
&lt;br /&gt;
{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}&lt;br /&gt;
&lt;br /&gt;
=== Working Power Supplies ===&lt;br /&gt;
=== Problem Power Supplies ===&lt;br /&gt;
&lt;br /&gt;
== Powered USB Hubs ==&lt;br /&gt;
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.&lt;br /&gt;
&lt;br /&gt;
===Working USB Hubs===&lt;br /&gt;
None currently reported.&lt;br /&gt;
&lt;br /&gt;
===Problem USB Hubs===&lt;br /&gt;
*Unbranded / Multiple Brands&lt;br /&gt;
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra'&lt;br /&gt;
&lt;br /&gt;
== USB Keyboards ==&lt;br /&gt;
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work.  &lt;br /&gt;
=== Working USB Keyboards ===&lt;br /&gt;
The following is a list of specific keyboards known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* Acer&lt;br /&gt;
** Compact Keyboard KU-0906 (B)&lt;br /&gt;
&lt;br /&gt;
* Cerulian &lt;br /&gt;
** Mini wireless keyboard and mouse deskset (B)&lt;br /&gt;
&lt;br /&gt;
* Dell&lt;br /&gt;
** SK-8135 (B)&lt;br /&gt;
&lt;br /&gt;
* Fujitsu Siemens &lt;br /&gt;
**KB SC USB UK (!)&lt;br /&gt;
&lt;br /&gt;
* Genius&lt;br /&gt;
** KB-06XE (K639) (B)&lt;br /&gt;
&lt;br /&gt;
* Lenovo&lt;br /&gt;
** SK-8825 UK (B)&lt;br /&gt;
&lt;br /&gt;
* Logitech &lt;br /&gt;
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)&lt;br /&gt;
** Wii wireless keyboard KG-0802 (!)&lt;br /&gt;
** C-BG17-Dual Wireless keyboard and mouse with wired USB received (B)&lt;br /&gt;
&lt;br /&gt;
* Microsoft &lt;br /&gt;
**Comfort Curve Keyboard 2000 v1.0 (Debian 13-Apr-2012 on Production Model B)&lt;br /&gt;
&lt;br /&gt;
* Xenta&lt;br /&gt;
** 2.5Ghz Wireless Multimedia Entertainment Keyboard with Touchpad (B)&lt;br /&gt;
&lt;br /&gt;
===Problem USB Keyboards===&lt;br /&gt;
&lt;br /&gt;
* Microsoft Wireless Desktop 800 - Keyboard has 'sticky' keys. (!)&lt;br /&gt;
* Novatech (B)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Unbranded, model no. HK-6106 (B) &amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== USB Mouse devices ==&lt;br /&gt;
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.  &lt;br /&gt;
&lt;br /&gt;
===Working USB Mouse Devices===&lt;br /&gt;
The following is a list of specific mouse devices known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* Dell&lt;br /&gt;
** M-UVDEL1 (B)&lt;br /&gt;
** M056U0A (B)&lt;br /&gt;
&lt;br /&gt;
* Genius&lt;br /&gt;
** GM-04003A (B)&lt;br /&gt;
&lt;br /&gt;
* Microsoft &lt;br /&gt;
** Compact optical mouse 500 V2.0 (B)&lt;br /&gt;
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)&lt;br /&gt;
&lt;br /&gt;
* Logitech&lt;br /&gt;
** M505 USB wireless laser, model no: 910-001324 (B)&lt;br /&gt;
&lt;br /&gt;
== USB WiFi Adapters ==&lt;br /&gt;
&lt;br /&gt;
See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing&lt;br /&gt;
&lt;br /&gt;
There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.&lt;br /&gt;
&lt;br /&gt;
===Working USB Wifi Adapters===&lt;br /&gt;
&lt;br /&gt;
These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.&lt;br /&gt;
&lt;br /&gt;
* 3COM&lt;br /&gt;
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)&lt;br /&gt;
* Asus&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 USB-N10 ] USB ID 0b05:1786, r8712u driver on Fedora Remix, must compile if on Debian 2012-04-13, requires firmware-realtek (B)&lt;br /&gt;
* IOGear&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u driver on Fedora Remix, must compile if on Debian 2012-04-13, requires firmware-realtek (B)&lt;br /&gt;
* Netgear &lt;br /&gt;
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the &amp;lt;code&amp;gt;firmware-atheros&amp;lt;/code&amp;gt; package from the &amp;lt;code&amp;gt;squeeze-backports&amp;lt;/code&amp;gt; non-free repository  (!)&lt;br /&gt;
** WG111v2: Realtek rtl8187 chipset (!)&lt;br /&gt;
* Tenda &lt;br /&gt;
** USB 11n adapter on a G network: Ralink  2870/3070 driver (!)&lt;br /&gt;
* TP-Link&lt;br /&gt;
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw) (B)&lt;br /&gt;
* Generic&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter] USB ID 148f:2573, tested on debian 2012-04-13 img; must install firmware-ralink package (B)&lt;br /&gt;
&lt;br /&gt;
== USB Bluetooth adapters ==&lt;br /&gt;
&lt;br /&gt;
== USB Ethernet adapters ==&lt;br /&gt;
&lt;br /&gt;
== USB IR Receivers==&lt;br /&gt;
&lt;br /&gt;
== USB TV Tuners==&lt;br /&gt;
&lt;br /&gt;
== USB UART adapters ==&lt;br /&gt;
The USB UART adapter is used to access the serial console of the Raspberry Pi from a development host such as a laptop or desktop PC.  The USB end connects to the PC and the UART header end connects to the USB.  While it is possible to connect the USB end to another Raspberry Pi, this configuration has not been tested unless explicitly mentioned against an individual entry below.&lt;br /&gt;
&lt;br /&gt;
== Power adapters ==&lt;br /&gt;
The Raspberry Pi uses a standard MicroUSB power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.&lt;br /&gt;
* All HTC mobile phone adaptors&lt;br /&gt;
** TCP-300 Single port USB mains phone charger 5v 1A (B)&lt;br /&gt;
* Stontronics&lt;br /&gt;
** S2097ST switching PSU, 7.5V 1.6A (!) '''Note that the power connector and voltage requirements for production boards are completely different'''&lt;br /&gt;
&lt;br /&gt;
== SD cards ==&lt;br /&gt;
&lt;br /&gt;
Note that manufacturers change their designs over time, even as the specs stay the same. (E.g. an ACME 8 GB class 4 card manufactured in 2011 might work, while one manufactured in 2012 might not.)&lt;br /&gt;
For this reason, please specify product numbers in the lists below, when possible.&lt;br /&gt;
&lt;br /&gt;
===Working SD Cards===&lt;br /&gt;
* Adata Class 10 8GB (AUSDH8GCL10-R)&lt;br /&gt;
* Dane-Elec 16Gb class 4&lt;br /&gt;
* Integral Ultima Pro 16GB Class 10 (20MB/s)&lt;br /&gt;
* Kingston SD 2GB (no class mentioned)&lt;br /&gt;
* Kingston SDHC 8GB class 4&lt;br /&gt;
* Lexar 8GB SDHC Class4&lt;br /&gt;
* Peak 4GB microSDHC class4 (MMBTR04GUBCA-ME) tested with Arch&lt;br /&gt;
* PNY 4GB SDHC Class 4&lt;br /&gt;
* Samsung SDHC 8GB&lt;br /&gt;
* SanDisk Ultra 2GB Class 4 (15MB/s)&lt;br /&gt;
* SanDisk Ultra II SD 2GB class 4&lt;br /&gt;
* SanDisk 2GB (non sdhc but with a circle 2), writes at 3.5 Mb/s&lt;br /&gt;
* SanDisk 2GB, white &amp;quot;SanDisk for Wii&amp;quot; branded, no class mentioned&lt;br /&gt;
* SanDisk Ultra SDHC 4GB class 6 (SDSDH-004G-U46 - BH1136121837G)&lt;br /&gt;
* SanDisk 8GB SDHC (class 4); writes at ~1.5MB/s&lt;br /&gt;
* SanDisk 8GB Micro SDHC (with Sandisk MicroSD =&amp;gt; SD adaptor) Class 4&lt;br /&gt;
* SanDisk 16GB SDHC (class 4)&lt;br /&gt;
* Transcend SDHC 16GB class 10&lt;br /&gt;
* Transcend SDHC 8GB class 6 (5.8 MB/s following [[RPi_Performance#SD_card]])&lt;br /&gt;
* Transcend SDHD 4GB class 4 - we've found these to work without any errors and offer reasonable performance&lt;br /&gt;
* Transcend SDHC 4GB class 4 (TS4GSDHC4 - BH1130821915G)&lt;br /&gt;
* Transcend SDHC 8GB class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;
Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).&lt;br /&gt;
&lt;br /&gt;
===Problem SD Cards===&lt;br /&gt;
&lt;br /&gt;
There are issues with most Class 10 SDHC cards, apparently due to a bug in the Broadcom bootloader.[http://www.raspberrypi.org/forum/general-discussion/class-10-sd-cards-on-the-production-boards/page-3/#p39181]&lt;br /&gt;
&lt;br /&gt;
This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.&lt;br /&gt;
&lt;br /&gt;
* Patriot Class 10 8GB (PSF8GSDHC10)&lt;br /&gt;
* SanDisk Ultra Class 6 8GB (B11201421964G)&lt;br /&gt;
* Kingston SDHC 4GB class 4 (works but gets mmc errors: mmc0: final write to SD card still running) Russel King might have a kernel patch for this problem.&lt;br /&gt;
&lt;br /&gt;
The usual warnings against less reputable sellers (such as Ebay merchants) apply.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):&lt;br /&gt;
&lt;br /&gt;
 mmc0: timeout waiting for hardware interrupt&lt;br /&gt;
&lt;br /&gt;
=== Benchmarks ===&lt;br /&gt;
&lt;br /&gt;
* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html&lt;br /&gt;
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11&lt;br /&gt;
&lt;br /&gt;
== Foreign Language Translations ==&lt;br /&gt;
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_VerifiedPeripherals</id>
		<title>RPi VerifiedPeripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_VerifiedPeripherals"/>
				<updated>2012-04-21T09:19:04Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Problem USB Keyboards */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: Linux]]&lt;br /&gt;
[[Category:ARM Development Boards]]&lt;br /&gt;
[[Category: Broadcom]]&lt;br /&gt;
[[Category: Development Boards]]&lt;br /&gt;
[[Category: RaspberryPi]]&lt;br /&gt;
[[Category: Education]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Notes==&lt;br /&gt;
&lt;br /&gt;
19-Apr-2012: Now that the Model B board is shipping, details added should relate to this board and the default Debian distribution unless stated otherwise. A suggested suffix markup scheme is as follows:&lt;br /&gt;
&lt;br /&gt;
* (A) - Relates to model A production board&lt;br /&gt;
* (B) - Relates to model B production board&lt;br /&gt;
* (!) - Information from alpha board days&lt;br /&gt;
* No markup - relates to all production boards&lt;br /&gt;
&lt;br /&gt;
''Discuss: [http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247 http://www.raspberrypi.org/forum/?mingleforumaction=viewtopic&amp;amp;t=247]''&lt;br /&gt;
&lt;br /&gt;
If you are adding to a product list it would help clarity if entries are kept/added in alphabetical order.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Power Supplies ==&lt;br /&gt;
It is very important that a suitable power supply is used. Many of the most common issues are power related. A 5V power supply that is capable of delivering at least 700 mA (B) should be used.&lt;br /&gt;
&lt;br /&gt;
{{Warning|Adding peripherals may increase the loading on the power supply to your board and this, in turn, may affect the voltage presented to the RPi. If the RPi's supply voltage falls below a certain value (anecdotally stated as around 4.75V), or it begins to fluctuate, your setup may become unstable. There is a [http://elinux.org/RPi_Hardware#Power Wiki section about this issue] which is worth a read.}}&lt;br /&gt;
&lt;br /&gt;
=== Working Power Supplies ===&lt;br /&gt;
=== Problem Power Supplies ===&lt;br /&gt;
&lt;br /&gt;
== Powered USB Hubs ==&lt;br /&gt;
A number of low-cost powered USB hubs are known to have caused problems. Members of the Raspberry Pi forums have reported low power or no power at all in some cases. The following is a list of specific Powered USB Hubs which appear to be fault-free. Please note that these do not take into account powering the Raspberry Pi from the hub, in addition to its peripherals.&lt;br /&gt;
&lt;br /&gt;
===Working USB Hubs===&lt;br /&gt;
None currently reported.&lt;br /&gt;
&lt;br /&gt;
===Problem USB Hubs===&lt;br /&gt;
*Unbranded / Multiple Brands&lt;br /&gt;
** 7-port silver/black hub. Also sold elsewhere under brands such as 'EX-Pro', 'Trixes' and 'Xentra'&lt;br /&gt;
&lt;br /&gt;
== USB Keyboards ==&lt;br /&gt;
USB keyboards that present themselves as a standard HID (Human Interface Device) device should work.  &lt;br /&gt;
=== Working USB Keyboards ===&lt;br /&gt;
The following is a list of specific keyboards known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* Acer&lt;br /&gt;
** Compact Keyboard KU-0906 (B)&lt;br /&gt;
&lt;br /&gt;
* Cerulian &lt;br /&gt;
** Mini wireless keyboard and mouse deskset (B)&lt;br /&gt;
&lt;br /&gt;
* Dell&lt;br /&gt;
** SK-8135 (B)&lt;br /&gt;
&lt;br /&gt;
* Fujitsu Siemens &lt;br /&gt;
**KB SC USB UK (!)&lt;br /&gt;
&lt;br /&gt;
* Genius&lt;br /&gt;
** KB-06XE (K639) (B)&lt;br /&gt;
&lt;br /&gt;
* Lenovo&lt;br /&gt;
** SK-8825 UK (B)&lt;br /&gt;
&lt;br /&gt;
* Logitech &lt;br /&gt;
** diNovo Mini wireless keyboard with media controls and clickpad 920-000586 (B)&lt;br /&gt;
** Wii wireless keyboard KG-0802 (!)&lt;br /&gt;
** C-BG17-Dual Wireless keyboard and mouse with wired USB received (B)&lt;br /&gt;
&lt;br /&gt;
* Microsoft &lt;br /&gt;
**Comfort Curve Keyboard 2000 v1.0 (Debian 13-Apr-2012 on Production Model B)&lt;br /&gt;
&lt;br /&gt;
* Xenta&lt;br /&gt;
** 2.5Ghz Wireless Multimedia Entertainment Keyboard with Touchpad (B)&lt;br /&gt;
&lt;br /&gt;
===Problem USB Keyboards===&lt;br /&gt;
&lt;br /&gt;
* Microsoft Wireless Desktop 800 - Keyboard has 'sticky' keys. (!)&lt;br /&gt;
* Novatech (B)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Unbranded, model no. HK-6106 (B) &amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/troubleshooting/keyboard-creates-kernal-panic/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== USB Mouse devices ==&lt;br /&gt;
USB mouse devices that present themselves as a standard HID (Human Interface Device) device should work, however some hardware requires special drivers or additional software, usually only compatible with Windows operating systems.  &lt;br /&gt;
&lt;br /&gt;
===Working USB Mouse Devices===&lt;br /&gt;
The following is a list of specific mouse devices known to work and which appear to be fault-free.&lt;br /&gt;
&lt;br /&gt;
* Dell&lt;br /&gt;
** M-UVDEL1 (B)&lt;br /&gt;
** M056U0A (B)&lt;br /&gt;
&lt;br /&gt;
* Genius&lt;br /&gt;
** GM-04003A (B)&lt;br /&gt;
&lt;br /&gt;
* Microsoft &lt;br /&gt;
** Compact optical mouse 500 V2.0 (B)&lt;br /&gt;
** Wheel Optical Mouse (wheel and additional buttons not tested) (B)&lt;br /&gt;
&lt;br /&gt;
* Logitech&lt;br /&gt;
** M505 USB wireless laser, model no: 910-001324 (B)&lt;br /&gt;
&lt;br /&gt;
== USB WiFi Adapters ==&lt;br /&gt;
&lt;br /&gt;
See also: http://www.element14.com/community/docs/DOC-44703/l/raspberry-pi-wifi-adapter-testing&lt;br /&gt;
&lt;br /&gt;
There is a howto on installing the TL-WN722N adapter [http://elinux.org/RPi_Peripherals#Wireless:_TP-Link_TL-WN722N_USB_wireless_adapter_.28Debian_6.29 here], which also acts as a guide for installing others too.&lt;br /&gt;
&lt;br /&gt;
===Working USB Wifi Adapters===&lt;br /&gt;
&lt;br /&gt;
These adapters are known to work on the Raspberry Pi. This list is not exhaustive, other adapters may well work, but have not yet been tried.&lt;br /&gt;
&lt;br /&gt;
* 3COM&lt;br /&gt;
** 3CRUSB10075: ZyDAS zd1211rw chipset (!)&lt;br /&gt;
* Asus&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 USB-N10 ] USB ID 0b05:1786, r8712u driver on Fedora Remix, must compile if on Debian 2012-04-13, requires firmware-realtek (B)&lt;br /&gt;
* IOGear&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 GWU625] USB ID 0bda:8172, r8712u driver on Fedora Remix, must compile if on Debian 2012-04-13, requires firmware-realtek (B)&lt;br /&gt;
* Netgear &lt;br /&gt;
** N150: Reported as WNA1100 device, uses the Atheros ar9271 chipset. On Debian, requires the &amp;lt;code&amp;gt;firmware-atheros&amp;lt;/code&amp;gt; package from the &amp;lt;code&amp;gt;squeeze-backports&amp;lt;/code&amp;gt; non-free repository  (!)&lt;br /&gt;
** WG111v2: Realtek rtl8187 chipset (!)&lt;br /&gt;
* Tenda &lt;br /&gt;
** USB 11n adapter on a G network: Ralink  2870/3070 driver (!)&lt;br /&gt;
* TP-Link&lt;br /&gt;
** TL-WN722N (ath9k_htc device with htc_9271.fw file from http://linuxwireless.org/download/htc_fw/1.3/htc_9271.fw) (B)&lt;br /&gt;
* Generic&lt;br /&gt;
** [http://www.element14.com/community/docs/DOC-44703 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter] USB ID 148f:2573, tested on debian 2012-04-13 img; must install firmware-ralink package (B)&lt;br /&gt;
&lt;br /&gt;
== USB Bluetooth adapters ==&lt;br /&gt;
&lt;br /&gt;
== USB Ethernet adapters ==&lt;br /&gt;
&lt;br /&gt;
== USB IR Receivers==&lt;br /&gt;
&lt;br /&gt;
== USB TV Tuners==&lt;br /&gt;
&lt;br /&gt;
== USB UART adapters ==&lt;br /&gt;
The USB UART adapter is used to access the serial console of the Raspberry Pi from a development host such as a laptop or desktop PC.  The USB end connects to the PC and the UART header end connects to the USB.  While it is possible to connect the USB end to another Raspberry Pi, this configuration has not been tested unless explicitly mentioned against an individual entry below.&lt;br /&gt;
&lt;br /&gt;
== Power adapters ==&lt;br /&gt;
The Raspberry Pi uses a standard MicroUSB power connector, which runs at 5v. Generally you can use a MicroUSB to USB cable and then either power the Raspberry Pi directly from your main computers USB ports (if they provide enough power), or by using a USB to Mains adaptor. A number of mobile phones use MicroUSB power cables, and these are compatible with the Raspberry Pi in most cases. Below is a list of power adaptors known to work.&lt;br /&gt;
* All HTC mobile phone adaptors&lt;br /&gt;
** TCP-300 Single port USB mains phone charger 5v 1A (B)&lt;br /&gt;
* Stontronics&lt;br /&gt;
** S2097ST switching PSU, 7.5V 1.6A (!) '''Note that the power connector and voltage requirements for production boards are completely different'''&lt;br /&gt;
&lt;br /&gt;
== SD cards ==&lt;br /&gt;
&lt;br /&gt;
Note that manufacturers change their designs over time, even as the specs stay the same. (E.g. an ACME 8 GB class 4 card manufactured in 2011 might work, while one manufactured in 2012 might not.)&lt;br /&gt;
For this reason, please specify product numbers in the lists below, when possible.&lt;br /&gt;
&lt;br /&gt;
===Working SD Cards===&lt;br /&gt;
* Adata Class 10 8GB (AUSDH8GCL10-R)&lt;br /&gt;
* Dane-Elec 16Gb class 4&lt;br /&gt;
* Integral Ultima Pro 16GB Class 10 (20MB/s)&lt;br /&gt;
* Kingston SD 2GB (no class mentioned)&lt;br /&gt;
* Kingston SDHC 8GB class 4&lt;br /&gt;
* Samsung SDHC 8GB&lt;br /&gt;
* SanDisk Ultra 2GB Class 4 (15MB/s)&lt;br /&gt;
* SanDisk Ultra II SD 2GB class 4&lt;br /&gt;
* SanDisk 2GB (non sdhc but with a circle 2), writes at 3.5 Mb/s&lt;br /&gt;
* SanDisk 2GB, white &amp;quot;SanDisk for Wii&amp;quot; branded, no class mentioned&lt;br /&gt;
* SanDisk 8GB SDHC (class 4); writes at ~1.5MB/s&lt;br /&gt;
* SanDisk 16GB SDHC (class 4)&lt;br /&gt;
* Transcend SDHC 16GB class 10&lt;br /&gt;
* Transcend SDHC 8GB class 6 (5.8 MB/s following [[RPi_Performance#SD_card]])&lt;br /&gt;
* Transcend SDHD 4GB class 4 - we've found these to work without any errors and offer reasonable performance&lt;br /&gt;
* Transcend SDHC 4GB class 4 (TS4GSDHC4 - BH1130821915G)&lt;br /&gt;
* Transcend SDHC 8GB class 6 (TS8GSDHC6-P2 - MMBFG08GWACA-M6)&lt;br /&gt;
* SanDisk Ultra SDHC 4GB class 6 (SDSDH-004G-U46 - BH1136121837G)&lt;br /&gt;
* Peak 4GB microSDHC class4 (MMBTR04GUBCA-ME) tested with Arch&lt;br /&gt;
 &lt;br /&gt;
Known good (and pre-loaded) cards will be available for sale from RS and element14 at a ''later'' date (TBA).&lt;br /&gt;
&lt;br /&gt;
===Problem SD Cards===&lt;br /&gt;
&lt;br /&gt;
There are issues with most Class 10 SDHC cards, apparently due to a bug in the Broadcom bootloader.[http://www.raspberrypi.org/forum/general-discussion/class-10-sd-cards-on-the-production-boards/page-3/#p39181]&lt;br /&gt;
&lt;br /&gt;
This seems to have been fixed in sdhci.c: [https://github.com/raspberrypi/linux/commit/7e8ae226fe6e95954df6b0dcdde40a53dbbc1a0b] Further feedback will be useful.&lt;br /&gt;
&lt;br /&gt;
* Patriot Class 10 8GB (PSF8GSDHC10)&lt;br /&gt;
* SanDisk Ultra Class 6 8GB (B11201421964G)&lt;br /&gt;
* Kingston SDHC 4GB class 4 (works but gets mmc errors: mmc0: final write to SD card still running) Russel King might have a kernel patch for this problem.&lt;br /&gt;
&lt;br /&gt;
The usual warnings against less reputable sellers (such as Ebay merchants) apply.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Note that the following error is sometimes accompanied with a non-working SD card after booting (on Debian):&lt;br /&gt;
&lt;br /&gt;
 mmc0: timeout waiting for hardware interrupt&lt;br /&gt;
&lt;br /&gt;
=== Benchmarks ===&lt;br /&gt;
&lt;br /&gt;
* http://www.sakoman.com/OMAP/microsd-card-perfomance-test-results.html&lt;br /&gt;
* http://usbspeed.nirsoft.net/usb_drive_speed_summary.html?o=11&lt;br /&gt;
&lt;br /&gt;
== Foreign Language Translations ==&lt;br /&gt;
* [[Ru:RaspberryPiBoardVerifiedPeripherals]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T23:02:53Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* General Purpose Input/Output (GPIO) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For further general information about GPIOs, see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
The production Raspberry Pi board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is the pin in the first column and on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
GPIO voltage levels are 3v3 and are not 5v tolerant.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions and full details of how to access are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used.&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC&lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0) || GPIO14-ALT5 is UART1_TXD, GPIO14&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0) || GPIO15-ALT5 is UART1_RXD, GPIO15&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC&lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC&lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0) || GPIO08&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0) || GPIO08&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0) || GPIO00&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0) || GPIO01&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | GPCLK0 || || (BCM2835 GPIO4-ALT0) || GPIO04-ALT5 is ARM_TDI, GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC&lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || ||| GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC&lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0) || GPIO10&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0) || GPIO09&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0) || GPIO11&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure GPIO connector pins P1-7, 15, 16, 18, 22 (chipset GPIOs 4 and 22 to 25) to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available on the GPIO connector (chipset pin 12 or 27 is needed).  Chipset pin 27 is available on S5, the CSI camera interface however.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure GPIO connector pins P1-12 and 13 (chipset GPIO 18 and 21) to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 and 20) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
A second I2C interface (GPIO02_ALT0 is SDA1 and GPIO03_ALT0 is SCL1) and two further GPIOs (GPIO05_ALT0 is GPCLK1, and GPIO27) are available on S5, the CSI camera interface.&lt;br /&gt;
&lt;br /&gt;
===A note about GPIO vs the schematic===&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as DNC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those DNC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
===Referring to pins on the Expansion header===&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===Power pins===&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
=== GPIO hardware hacking ===&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available on the GPIO connector is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As noted above, GPIO00 and 01 (SDA0 and SCL0) have 1K8 pull-up resistors to 3v3.&lt;br /&gt;
&lt;br /&gt;
If 17 GPIOs aren't sufficient for your project, there are a few other signals potentially available, with varying levels of software and hardware (soldering iron) hackery skills:&lt;br /&gt;
&lt;br /&gt;
GPIO02, 03, 05 and 27 are available on S5 (the CSI interface) when a camera peripheral is not connected to that socket, and are configured by default to provide the functions SDA1, SCL1, CAM_CLK and CAM_GPIO respectively.  SDA1 and SCL1 have 1K6 pull-up resistors to 3v3.&lt;br /&gt;
&lt;br /&gt;
GPIO06 is LAN_RUN and is available on pad 12 of the footprint for IC3 on the Model A.  On Model B, it is in use for the Ethernet function.&lt;br /&gt;
&lt;br /&gt;
There are a few other chipset GPIO pins accessible on the PCB but are in use:&lt;br /&gt;
&lt;br /&gt;
GPIO16 drives status LED D5 (usually SD card access indicator)&lt;br /&gt;
GPIO28-31 are used by the board ID and are connected to resistors R3 to R10.&lt;br /&gt;
GPIO40 and 45 are used by analogue audio and support PWM.  They connect to the analogue audio circuitry via R21 and R27 respectively.&lt;br /&gt;
GPIO46 is HDMI hotplug detect (goes to pin 6 of IC1).&lt;br /&gt;
GPIO47 to 53 are used by the SD card interface.  In particular, GPIO47 is SD card detect (this would seem to be a good candidate for re-use).  GPIO47 is connected to the SD card interface card detect switch; GPIO48 to 53 are connected to the SD card interface via resistors R45 to R50.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T22:08:29Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* General Purpose Input/Output (GPIO) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For further general information about GPIOs, see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
The production Raspberry Pi board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is the pin in the first column and on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions and full details of how to access are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used.&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC || pulled high (5v) in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0) || GPIO14-ALT5 is UART1_TXD, GPIO14&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0) || GPIO15-ALT5 is UART1_RXD, GPIO15&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0) || GPIO08&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0) || GPIO08&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0) || GPIO00&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0) || GPIO01&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | GPCLK0 || || (BCM2835 GPIO4-ALT0) || GPIO04-ALT5 is ARM_TDI, GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || ||| GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC || pulled high (3v3) in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0) || GPIO10&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0) || GPIO09&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0) || GPIO11&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC || pulled low in v1&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
===A note about GPIO vs the schematic===&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
===Referring to pins on the Expansion header===&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===Power pins===&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
=== GPIO hardware hacking ===&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available on the GPIO connector is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
As noted above, GPIO00 and 01 (SDA0 and SCL0) have 1K8 pull-up resistors to 3v3.&lt;br /&gt;
&lt;br /&gt;
If 17 GPIOs aren't sufficient for your project, there are a few other signals potentially available, with varying levels of software and hardware (soldering iron) hackery skills:&lt;br /&gt;
&lt;br /&gt;
GPIO02, 03, 05 and 27 are available on S5 (the CSI interface) when a camera peripheral is not connected to that socket, and are configured by default to provide the functions SDA1, SCL1, CAM_CLK and CAM_GPIO respectively.  SDA1 and SCL1 have 1K6 pull-up resistors to 3v3.&lt;br /&gt;
&lt;br /&gt;
GPIO06 is LAN_RUN and is available on pad 12 of the footprint for IC3 on the Model A.  On Model B, it is in use for the Ethernet function.&lt;br /&gt;
&lt;br /&gt;
There are a few other chipset GPIO pins accessible on the PCB but are in use:&lt;br /&gt;
&lt;br /&gt;
GPIO16 drives status LED D5 (usually SD card access indicator)&lt;br /&gt;
GPIO28-31 are used by the board ID and are connected to resistors R3 to R10.&lt;br /&gt;
GPIO40 and 45 are used by analogue audio and support PWM.  They connect to the analogue audio circuitry via R21 and R27 respectively.&lt;br /&gt;
GPIO46 is HDMI hotplug detect (goes to pin 6 of IC1).&lt;br /&gt;
GPIO47 to 53 are used by the SD card interface.  In particular, GPIO47 is SD card detect (this would seem to be a good candidate for re-use).  GPIO47 is connected to the SD card interface card detect switch; GPIO48 to 53 are connected to the SD card interface via resistors R45 to R50.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T21:01:56Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* General Purpose Input/Output (GPIO) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For further general information about GPIOs, see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
The production Raspberry Pi board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is the pin in the first column and on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions and full details of how to access are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used.&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC || pulled high (5v) in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0) || GPIO14-ALT5 is UART1_TXD, GPIO14&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0) || GPIO15-ALT5 is UART1_RXD, GPIO15&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0) || GPIO08&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0) || GPIO08&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0) || GPIO00&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0) || GPIO01&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | GPCLK0 || || (BCM2835 GPIO4-ALT0) || GPIO04-ALT5 is ARM_TDI, GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || ||| GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC || pulled high (3v3) in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0) || GPIO10&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0) || GPIO09&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0) || GPIO11&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC || pulled low in v1&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
===A note about GPIO vs the schematic===&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
===Referring to pins on the Expansion header===&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===Power pins===&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T20:53:31Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* General Purpose Input/Output (GPIO) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For further general information about GPIOs, see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
The production Raspberry Pi board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is the pin in the first column and on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions and full details of how to access are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used.&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC || pulled high (5v) in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0) || GPIO14-ALT5 is UART1_TXD, GPIO14&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0) || GPIO15-ALT5 is UART1_RXD, GPIO15&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0) || GPIO08&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0) || GPIO08&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0) || GPIO00&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0) || GPIO01&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC || pulled low in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || ||| GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC || pulled high (3v3) in v1&lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0) || GPIO10&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0) || GPIO09&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0) || GPIO11&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC || pulled low in v1&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
===A note about GPIO vs the schematic===&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
===Referring to pins on the Expansion header===&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===Power pins===&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hardware</id>
		<title>RPi Hardware</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hardware"/>
				<updated>2012-04-20T20:39:31Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Components */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]&lt;br /&gt;
The first product is the size of a credit card, and is designed to plug into a TV or HDMI monitor. It comes in two variants, model A and B, with B having more features. The expected price is $25 for model A and $35 for model B. The [[Rpi Low-level peripherals| GPIO pins]] on each board allow the use of optional [[Rpi expansion boards|expansion boards]].&lt;br /&gt;
&lt;br /&gt;
Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].&lt;br /&gt;
&lt;br /&gt;
==Specifications==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!&lt;br /&gt;
! Model A&lt;br /&gt;
! Model B&lt;br /&gt;
|-&lt;br /&gt;
| Target price:&amp;lt;ref name=&amp;quot;faq&amp;quot; &amp;gt;http://www.raspberrypi.org/faqs&amp;lt;/ref&amp;gt;&lt;br /&gt;
| US$25 (GBP £16)&lt;br /&gt;
| US$35 (GBP £22)&lt;br /&gt;
|-&lt;br /&gt;
| System-on-a-chip (SoC):&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom BCM2835 (CPU + GPU + SDRAM)&lt;br /&gt;
|-&lt;br /&gt;
| CPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 700&amp;amp;nbsp;MHz ARM11 ARM1176JZF-S core&lt;br /&gt;
|-&lt;br /&gt;
| GPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode &lt;br /&gt;
|-&lt;br /&gt;
| Memory (SDRAM)iB&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 256 MiB (previously listed as 128MiB for model A, but an upgrade to 256MiB was announced on 29 Feb 2012)&lt;br /&gt;
|-&lt;br /&gt;
| USB 2.0 ports:&lt;br /&gt;
| 1(provided by the BCM2835)&lt;br /&gt;
| 2 (via integrated USB hub)&lt;br /&gt;
|-&lt;br /&gt;
| Video outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Composite video|Composite RCA, HDMI (not at the same time)&lt;br /&gt;
|-&lt;br /&gt;
| Audio outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | TRS connector|3.5 mm jack, HDMI&lt;br /&gt;
|-&lt;br /&gt;
| Audio inputs:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | none, but a USB mic or sound-card could be added&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Storage:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Secure Digital|SD / MMC / SDIO card slot&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Network:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| None&lt;br /&gt;
| 10/100 wired Ethernet RJ45&lt;br /&gt;
|-&lt;br /&gt;
| Low-level peripherals:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S&amp;lt;ref name=&amp;quot;i2s&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;, Universal asynchronous receiver/transmitter (UART)&lt;br /&gt;
|-&lt;br /&gt;
| Real-time clock:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | None&lt;br /&gt;
|-&lt;br /&gt;
| Power ratings (provisional, from alpha board):&lt;br /&gt;
| 500mA, (2.5 Watt) &amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| 700mA, (3.5 Watt)&lt;br /&gt;
|-&lt;br /&gt;
| Power source:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 5V via Micro USB or GPIO header&lt;br /&gt;
|-&lt;br /&gt;
| Size:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 85.60mm x 53.98mm&amp;lt;ref&amp;gt;[http://www.raspberrypi.org/archives/344 Final PCB artwork]&amp;lt;/ref&amp;gt; (3.370 × 2.125 inch)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Components==&lt;br /&gt;
[[File:Raspi-Model-AB-Mono-2-699x1024.png|400px|thumb|right|A diagram denoting the places of the different components on the Rpi, made by Paul&lt;br /&gt;
Beech, edited to show 256MB ram for both boards]]&lt;br /&gt;
(Provisional - some of the expansion interfaces won't be available on production boards)&lt;br /&gt;
(PCB IDs are those of the Model B Beta board) &lt;br /&gt;
&lt;br /&gt;
* SoC: [http://www.broadcom.com/products/BCM2835 Broadcom BCM2835 media processor] ([http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf datasheet], [[BCM2835 datasheet errata]]) system-on-chip featuring:&lt;br /&gt;
** CPU core: [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0301h/DDI0301H_arm1176jzfs_r0p7_trm.pdf ARM1176JZF-S] ARM11 core clocked at 700MHz; ARM VFP.  The ARM11 core implements the ARMv6 Architecture.  For details on ARM instruction sets and naming conventions, see [http://en.wikipedia.org/wiki/ARM_architecture ARM architecture] and [http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores List of ARM microprocessor cores].&lt;br /&gt;
** GPU core: a Broadcom [http://en.wikipedia.org/wiki/Videocore VideoCore] IV GPU providing OpenGL ES 1.1, OpenGL ES 2.0, hardware-accelerated OpenVG 1.1, Open EGL, OpenMAX and 1080p30 H.264 high-profile decode.  There are 24 GFLOPS of general purpose compute and a bunch of texture filtering and DMA infrastructure.  Eben worked on the architecture team for this and the Raspberry Pi team are looking at how they can make some of the proprietary features available to application programmers&lt;br /&gt;
** DSP core: There is a DSP, but there isn't currently a public API (Liz thinks the BC team are keen to make one available at some point)&lt;br /&gt;
** 256MiB of SDRAM.  The RAM is physically stacked on top of the Broadcom media processor (package-on-package technology)&lt;br /&gt;
* LAN9512 ([http://www.smsc.com/media/Downloads_Public/Data_Briefs/9512db.pdf Data Brief] | [http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf Data Sheet])'''(Model B)''' providing:&lt;br /&gt;
** 10/100Mb Ethernet (Auto-MDIX)&amp;lt;ref name=autoMDIX&amp;gt;[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]&amp;lt;/ref&amp;gt;&lt;br /&gt;
** 2x USB 2.0 &lt;br /&gt;
* S1: Micro USB power jack (5v - Power Only)&lt;br /&gt;
* S2: DSI interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S3: HDMI connector providing type A HDMI 1.3a out&lt;br /&gt;
* S4: Composite Video connector: RCA&lt;br /&gt;
* S5: MIPI CSI-2 interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S6: Audio connector: 3.5mm stereo jack (output only)&lt;br /&gt;
* S8: SD/MMC/SDIO memory card slot (underside)&lt;br /&gt;
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''&lt;br /&gt;
* P1: 26-pin 2.54mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]&lt;br /&gt;
** 8 GPIOs at 3v3&lt;br /&gt;
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3&lt;br /&gt;
** I2C interface (3v3); or 2 GPIOs at 3v3&lt;br /&gt;
** SPI interface (3v3); or 5 GPIOs at 3v3&lt;br /&gt;
** 3v3, 5v and GND supply pins&lt;br /&gt;
** ARM JTAG (if pins are reconfigured in software)&lt;br /&gt;
** Second I2C interface (3v3) (if pins are reconfigured in software)&lt;br /&gt;
** I2S interface (if pins are reconfigured in software, hardware hack may be required&amp;lt;ref name=&amp;quot;i2s&amp;quot;/&amp;gt;)&lt;br /&gt;
** 6 pins reserved for future use&lt;br /&gt;
* P2 8-pin 2.54mm header expansion providing GPU JTAG (ARM11 pinout, pin 7 is nofit for locating)&lt;br /&gt;
* P3: 7-pin 2.54mm header expansion (header not fitted), providing LAN9512 JTAG (pin 6 is nofit for locating)&lt;br /&gt;
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''&lt;br /&gt;
* TP1 and TP2: Test Points giving access to +5V and GND respectively&lt;br /&gt;
* 5 Status LEDs&amp;lt;ref name=&amp;quot;PCBs&amp;quot;&amp;gt;[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDs&amp;quot;&amp;gt;[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDsGPIO&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/what-do-the-status-indicator-leds-indicate-the-status-of Forum:What do the status indicator LEDs indicate the status of?]&amp;lt;/ref&amp;gt;:&lt;br /&gt;
** D5(Yellow) - OK  - SDCard Access (via GPIO16)&lt;br /&gt;
** D6(Red) - PWR - 3.3V Power&lt;br /&gt;
** D7(Green) - FDX - Full Duplex (LAN) '''(Model B)'''&lt;br /&gt;
** D8(Green) - LNK - Link/Activity (LAN) '''(Model B)'''&lt;br /&gt;
** D9(Yellow) - 10M - 10/100Mbit (LAN) '''(Model B)'''&lt;br /&gt;
&lt;br /&gt;
* Board size: 85.60mm x 53.98mm.  Overall height expected to be less than 25mm. &amp;lt;ref name=&amp;quot;artwork&amp;quot;&amp;gt;http://www.raspberrypi.org/archives/344&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Weight: &amp;lt;40g? (Alpha board weighs ~55g &amp;lt;ref&amp;gt;http://www.raspberrypi.org/?page_id=43&amp;amp;mingleforumaction=viewtopic&amp;amp;t=285.0&amp;lt;/ref&amp;gt;)&lt;br /&gt;
* 6 layer PCB &amp;lt;ref name=&amp;quot;artwork&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Schematic / Layout==&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot]&lt;br /&gt;
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot, labelled version]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1-300x225.jpg Low-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back-300x225.jpg Low-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1.jpg High-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back.jpg High-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official schematics PDF] | [[RPi_schematic_errata|errata]]&lt;br /&gt;
&lt;br /&gt;
==Power==&lt;br /&gt;
&lt;br /&gt;
The board takes fixed 5V input, (with the 1V2 core voltage generated directly from the input using the internal switch-mode supply on the BCM2835 die). &lt;br /&gt;
This permits adoption of the micro USB form factor, which, in turn, prevents the user from inadvertently plugging in out-of-range power inputs; that would be dangerous, since the 5V would go straight to HDMI and output USB ports, even though the problem should be mitigated by some protections applied to the input power: The board provides a polarity protection diode, a voltage clamp, and a self-resetting semiconductor fuse.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Board A: 5V, 500 mA (2.5W) without any devices connected&lt;br /&gt;
* Board B: 5V, 700 mA (3.5W) without any devices connected&lt;br /&gt;
&lt;br /&gt;
*As the 5V rail is brought out in the [[Rpi_Low-level_peripherals | GPIO pins]], you can power the Rpi from there too. You should mind however, that those are ''behind'' the power protection circuitry , so you should provide your own.&lt;br /&gt;
* It is possible to power the Rpi from a powered USB hub the Rpi controls, but only on 'dumb' devices, that allow the port to supply the full current without waiting for the usb device to ask for it[http://www.raspberrypi.org/forum/general-discussion/power-pi-from-usb-hub-connected-to-pi]. As the power input of the Rpi doesn't have its data leads connected, there is no chance for a communication loop of some sorts.&lt;br /&gt;
* POE ([http://nl.wikipedia.org/wiki/Power_over_Ethernet power over ethernet]) is currently not available for the Rpi (but nobody stops you from taking your soldering iron and doing it yourself)&lt;br /&gt;
&lt;br /&gt;
===Power Supply Problems===&lt;br /&gt;
&lt;br /&gt;
There have been a number of problems reported that seem to be caused by inadequate power, this is an attempt to explain what is needed and the consequences of not having enough power.&lt;br /&gt;
&lt;br /&gt;
The power required by the Pi will vary depending on how busy it is and what peripherals are connected.&lt;br /&gt;
* Running a GUI will take more power.&lt;br /&gt;
* The USB devices and Ethernet connection will take power.&lt;br /&gt;
* Running software will take power.&lt;br /&gt;
&lt;br /&gt;
This means that it's difficult to say exactly how much power is needed.  People have reported current requirements of between 300mA and 550mA. But it could in reality take more, especially for short periods. A simple multimeter will not show short surges on the power requirement. A surge in the power requirement for a few milliseconds will not be detectable by a meter but will be enough to cause problems.&lt;br /&gt;
If the board does not get enough power the voltage will drop. If it drops enough parts of the system will run unreliably because data can get corrupted.  The USB IC runs on 5V and handles the USB and Ethernet ports so it's likely that this will be the first thing to fail. Problems seen are unreliable Ethernet connection and unreliable operation of the Keyboard and/or mouse.&lt;br /&gt;
&lt;br /&gt;
There are several reasons why the power to the board may be inadequate:&lt;br /&gt;
* The PSU may not deliver enough power.  Although the maximum power requirement is said to be 700mA a 1000mA PSU should be the minimum.  This allows some leeway in case the power supply cannot deliver it's full power without the voltage dropping.&lt;br /&gt;
* The PSU is not regulated.&lt;br /&gt;
* The cable connecting the PSU to the Pi may not be good. People have reported cables with 4 ohms resistance on the power connections. At 500mA drain this would reduce a 5V supply to 3V.&lt;br /&gt;
&lt;br /&gt;
====How Can I tell if the power supply is inadequate?====&lt;br /&gt;
&lt;br /&gt;
Common symptoms of an inadequate power supply are&lt;br /&gt;
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.&lt;br /&gt;
* SD card errors at start up seems to be another symptom of poor power.&lt;br /&gt;
&lt;br /&gt;
If you think you have a problem with your power supply, it is a good idea to check the actual voltage&lt;br /&gt;
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board&lt;br /&gt;
to facilitate voltage measurements.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]&lt;br /&gt;
&lt;br /&gt;
====Things that can cause problems====&lt;br /&gt;
* A USB connection on a TV or PC. The USB power supply specification is for up to 500mA and if the TV implements this then it can cause problems.  The system may work initially but be unreliable because as it becomes more active the power requirement increases.&lt;br /&gt;
* A single supply from a powered hub.  Most hubs seem to deliver more than the specified current but there's no guarantee.  Check the power supply rating, it must be enough to supply everything that's connected to the hub.&lt;br /&gt;
* A power supply that is rated for less than 700mA may work some of the time.&lt;br /&gt;
* Adding a USB hard disk drive. A HDD will take quite a lot of power as it starts, maybe an amp or more. It the power supply for this also supplies the Pi then this could overload things and cause trouble.&lt;br /&gt;
* Some complex keyboards have been reported to take a considerable amount of power, maybe up to 500mA.  The Pi cannot deliver this amount of power.  Simpler budget keyboards may be better. If the system works with no keyboard attached but not with a keyboard then it's worth trying a different, simpler, keyboard.&lt;br /&gt;
&lt;br /&gt;
====Summary====&lt;br /&gt;
&lt;br /&gt;
* If you are having unreliable operation the first thing to do is check your power supply.&lt;br /&gt;
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).&lt;br /&gt;
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.&lt;br /&gt;
* Not all power supplies will deliver what they claim.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hardware</id>
		<title>RPi Hardware</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hardware"/>
				<updated>2012-04-20T20:26:14Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Components */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]&lt;br /&gt;
The first product is the size of a credit card, and is designed to plug into a TV or HDMI monitor. It comes in two variants, model A and B, with B having more features. The expected price is $25 for model A and $35 for model B. The [[Rpi Low-level peripherals| GPIO pins]] on each board allow the use of optional [[Rpi expansion boards|expansion boards]].&lt;br /&gt;
&lt;br /&gt;
Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].&lt;br /&gt;
&lt;br /&gt;
==Specifications==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!&lt;br /&gt;
! Model A&lt;br /&gt;
! Model B&lt;br /&gt;
|-&lt;br /&gt;
| Target price:&amp;lt;ref name=&amp;quot;faq&amp;quot; &amp;gt;http://www.raspberrypi.org/faqs&amp;lt;/ref&amp;gt;&lt;br /&gt;
| US$25 (GBP £16)&lt;br /&gt;
| US$35 (GBP £22)&lt;br /&gt;
|-&lt;br /&gt;
| System-on-a-chip (SoC):&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom BCM2835 (CPU + GPU + SDRAM)&lt;br /&gt;
|-&lt;br /&gt;
| CPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 700&amp;amp;nbsp;MHz ARM11 ARM1176JZF-S core&lt;br /&gt;
|-&lt;br /&gt;
| GPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode &lt;br /&gt;
|-&lt;br /&gt;
| Memory (SDRAM)iB&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 256 MiB (previously listed as 128MiB for model A, but an upgrade to 256MiB was announced on 29 Feb 2012)&lt;br /&gt;
|-&lt;br /&gt;
| USB 2.0 ports:&lt;br /&gt;
| 1(provided by the BCM2835)&lt;br /&gt;
| 2 (via integrated USB hub)&lt;br /&gt;
|-&lt;br /&gt;
| Video outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Composite video|Composite RCA, HDMI (not at the same time)&lt;br /&gt;
|-&lt;br /&gt;
| Audio outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | TRS connector|3.5 mm jack, HDMI&lt;br /&gt;
|-&lt;br /&gt;
| Audio inputs:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | none, but a USB mic or sound-card could be added&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Storage:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Secure Digital|SD / MMC / SDIO card slot&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Network:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| None&lt;br /&gt;
| 10/100 wired Ethernet RJ45&lt;br /&gt;
|-&lt;br /&gt;
| Low-level peripherals:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S&amp;lt;ref name=&amp;quot;i2s&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;, Universal asynchronous receiver/transmitter (UART)&lt;br /&gt;
|-&lt;br /&gt;
| Real-time clock:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | None&lt;br /&gt;
|-&lt;br /&gt;
| Power ratings (provisional, from alpha board):&lt;br /&gt;
| 500mA, (2.5 Watt) &amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| 700mA, (3.5 Watt)&lt;br /&gt;
|-&lt;br /&gt;
| Power source:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 5V via Micro USB or GPIO header&lt;br /&gt;
|-&lt;br /&gt;
| Size:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 85.60mm x 53.98mm&amp;lt;ref&amp;gt;[http://www.raspberrypi.org/archives/344 Final PCB artwork]&amp;lt;/ref&amp;gt; (3.370 × 2.125 inch)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Components==&lt;br /&gt;
[[File:Raspi-Model-AB-Mono-2-699x1024.png|400px|thumb|right|A diagram denoting the places of the different components on the Rpi, made by Paul&lt;br /&gt;
Beech, edited to show 256MB ram for both boards]]&lt;br /&gt;
(Provisional - some of the expansion interfaces won't be available on production boards)&lt;br /&gt;
(PCB IDs are those of the Model B Beta board) &lt;br /&gt;
&lt;br /&gt;
* SoC: [http://www.broadcom.com/products/BCM2835 Broadcom BCM2835 media processor] ([http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf datasheet], [[BCM2835 datasheet errata]]) system-on-chip featuring:&lt;br /&gt;
** CPU core: [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0301h/DDI0301H_arm1176jzfs_r0p7_trm.pdf ARM1176JZF-S] ARM11 core clocked at 700MHz; ARM VFP.  The ARM11 core implements the ARMv6 Architecture.  For details on ARM instruction sets and naming conventions, see [http://en.wikipedia.org/wiki/ARM_architecture ARM architecture] and [http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores List of ARM microprocessor cores].&lt;br /&gt;
** GPU core: a Broadcom [http://en.wikipedia.org/wiki/Videocore VideoCore] IV GPU providing OpenGL ES 1.1, OpenGL ES 2.0, hardware-accelerated OpenVG 1.1, Open EGL, OpenMAX and 1080p30 H.264 high-profile decode.  There are 24 GFLOPS of general purpose compute and a bunch of texture filtering and DMA infrastructure.  Eben worked on the architecture team for this and the Raspberry Pi team are looking at how they can make some of the proprietary features available to application programmers&lt;br /&gt;
** DSP core: There is a DSP, but there isn't currently a public API (Liz thinks the BC team are keen to make one available at some point)&lt;br /&gt;
** 256MiB of SDRAM.  The RAM is physically stacked on top of the Broadcom media processor (package-on-package technology)&lt;br /&gt;
* LAN9512 ([http://www.smsc.com/media/Downloads_Public/Data_Briefs/9512db.pdf Data Brief] | [http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf Data Sheet])'''(Model B)''' providing:&lt;br /&gt;
** 10/100Mb Ethernet (Auto-MDIX)&amp;lt;ref name=autoMDIX&amp;gt;[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]&amp;lt;/ref&amp;gt;&lt;br /&gt;
** 2x USB 2.0 &lt;br /&gt;
* S1: Micro USB power jack (5v - Power Only)&lt;br /&gt;
* S2: DSI interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S3: HDMI connector providing type A HDMI 1.3a out&lt;br /&gt;
* S4: Composite Video connector: RCA&lt;br /&gt;
* S5: MIPI CSI-2 interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S6: Audio connector: 3.5mm stereo jack (output only)&lt;br /&gt;
* S8: SD/MMC/SDIO memory card slot (underside)&lt;br /&gt;
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''&lt;br /&gt;
* P1: 26-pin 2.54mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]&lt;br /&gt;
** 8 GPIOs at 3v3&lt;br /&gt;
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3&lt;br /&gt;
** I2C interface (3v3); or 2 GPIOs at 3v3&lt;br /&gt;
** SPI interface (3v3); or 5 GPIOs at 3v3&lt;br /&gt;
** 3v3, 5v and GND supply pins&lt;br /&gt;
** ARM JTAG (if pins are reconfigured in software)&lt;br /&gt;
** Second I2C interface (3v3) (if pins are reconfigured in software)&lt;br /&gt;
** I2S interface (if pins are reconfigured in software, hardware hack may be required&amp;lt;ref name=&amp;quot;i2s&amp;quot;/&amp;gt;)&lt;br /&gt;
** 6 pins reserved for future use&lt;br /&gt;
* P2 and P3: 8-pin and 7-pin 2.54mm header expansion (P3 header not fitted), providing:&lt;br /&gt;
** 6-pin GPU JTAG (ARM11 pinout)&lt;br /&gt;
** 6-pin LAN9512 JTAG&lt;br /&gt;
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''&lt;br /&gt;
* TP1 and TP2: Test Points giving access to +5V and GND respectively&lt;br /&gt;
* 5 Status LEDs&amp;lt;ref name=&amp;quot;PCBs&amp;quot;&amp;gt;[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDs&amp;quot;&amp;gt;[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDsGPIO&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/what-do-the-status-indicator-leds-indicate-the-status-of Forum:What do the status indicator LEDs indicate the status of?]&amp;lt;/ref&amp;gt;:&lt;br /&gt;
** D5(Yellow) - OK  - SDCard Access (via GPIO16)&lt;br /&gt;
** D6(Red) - PWR - 3.3V Power&lt;br /&gt;
** D7(Green) - FDX - Full Duplex (LAN) '''(Model B)'''&lt;br /&gt;
** D8(Green) - LNK - Link/Activity (LAN) '''(Model B)'''&lt;br /&gt;
** D9(Yellow) - 10M - 10/100Mbit (LAN) '''(Model B)'''&lt;br /&gt;
&lt;br /&gt;
* Board size: 85.60mm x 53.98mm.  Overall height expected to be less than 25mm. &amp;lt;ref name=&amp;quot;artwork&amp;quot;&amp;gt;http://www.raspberrypi.org/archives/344&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Weight: &amp;lt;40g? (Alpha board weighs ~55g &amp;lt;ref&amp;gt;http://www.raspberrypi.org/?page_id=43&amp;amp;mingleforumaction=viewtopic&amp;amp;t=285.0&amp;lt;/ref&amp;gt;)&lt;br /&gt;
* 6 layer PCB &amp;lt;ref name=&amp;quot;artwork&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Schematic / Layout==&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot]&lt;br /&gt;
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot, labelled version]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1-300x225.jpg Low-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back-300x225.jpg Low-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1.jpg High-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back.jpg High-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official schematics PDF] | [[RPi_schematic_errata|errata]]&lt;br /&gt;
&lt;br /&gt;
==Power==&lt;br /&gt;
&lt;br /&gt;
The board takes fixed 5V input, (with the 1V2 core voltage generated directly from the input using the internal switch-mode supply on the BCM2835 die). &lt;br /&gt;
This permits adoption of the micro USB form factor, which, in turn, prevents the user from inadvertently plugging in out-of-range power inputs; that would be dangerous, since the 5V would go straight to HDMI and output USB ports, even though the problem should be mitigated by some protections applied to the input power: The board provides a polarity protection diode, a voltage clamp, and a self-resetting semiconductor fuse.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Board A: 5V, 500 mA (2.5W) without any devices connected&lt;br /&gt;
* Board B: 5V, 700 mA (3.5W) without any devices connected&lt;br /&gt;
&lt;br /&gt;
*As the 5V rail is brought out in the [[Rpi_Low-level_peripherals | GPIO pins]], you can power the Rpi from there too. You should mind however, that those are ''behind'' the power protection circuitry , so you should provide your own.&lt;br /&gt;
* It is possible to power the Rpi from a powered USB hub the Rpi controls, but only on 'dumb' devices, that allow the port to supply the full current without waiting for the usb device to ask for it[http://www.raspberrypi.org/forum/general-discussion/power-pi-from-usb-hub-connected-to-pi]. As the power input of the Rpi doesn't have its data leads connected, there is no chance for a communication loop of some sorts.&lt;br /&gt;
* POE ([http://nl.wikipedia.org/wiki/Power_over_Ethernet power over ethernet]) is currently not available for the Rpi (but nobody stops you from taking your soldering iron and doing it yourself)&lt;br /&gt;
&lt;br /&gt;
===Power Supply Problems===&lt;br /&gt;
&lt;br /&gt;
There have been a number of problems reported that seem to be caused by inadequate power, this is an attempt to explain what is needed and the consequences of not having enough power.&lt;br /&gt;
&lt;br /&gt;
The power required by the Pi will vary depending on how busy it is and what peripherals are connected.&lt;br /&gt;
* Running a GUI will take more power.&lt;br /&gt;
* The USB devices and Ethernet connection will take power.&lt;br /&gt;
* Running software will take power.&lt;br /&gt;
&lt;br /&gt;
This means that it's difficult to say exactly how much power is needed.  People have reported current requirements of between 300mA and 550mA. But it could in reality take more, especially for short periods. A simple multimeter will not show short surges on the power requirement. A surge in the power requirement for a few milliseconds will not be detectable by a meter but will be enough to cause problems.&lt;br /&gt;
If the board does not get enough power the voltage will drop. If it drops enough parts of the system will run unreliably because data can get corrupted.  The USB IC runs on 5V and handles the USB and Ethernet ports so it's likely that this will be the first thing to fail. Problems seen are unreliable Ethernet connection and unreliable operation of the Keyboard and/or mouse.&lt;br /&gt;
&lt;br /&gt;
There are several reasons why the power to the board may be inadequate:&lt;br /&gt;
* The PSU may not deliver enough power.  Although the maximum power requirement is said to be 700mA a 1000mA PSU should be the minimum.  This allows some leeway in case the power supply cannot deliver it's full power without the voltage dropping.&lt;br /&gt;
* The PSU is not regulated.&lt;br /&gt;
* The cable connecting the PSU to the Pi may not be good. People have reported cables with 4 ohms resistance on the power connections. At 500mA drain this would reduce a 5V supply to 3V.&lt;br /&gt;
&lt;br /&gt;
====How Can I tell if the power supply is inadequate?====&lt;br /&gt;
&lt;br /&gt;
Common symptoms of an inadequate power supply are&lt;br /&gt;
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.&lt;br /&gt;
* SD card errors at start up seems to be another symptom of poor power.&lt;br /&gt;
&lt;br /&gt;
If you think you have a problem with your power supply, it is a good idea to check the actual voltage&lt;br /&gt;
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board&lt;br /&gt;
to facilitate voltage measurements.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]&lt;br /&gt;
&lt;br /&gt;
====Things that can cause problems====&lt;br /&gt;
* A USB connection on a TV or PC. The USB power supply specification is for up to 500mA and if the TV implements this then it can cause problems.  The system may work initially but be unreliable because as it becomes more active the power requirement increases.&lt;br /&gt;
* A single supply from a powered hub.  Most hubs seem to deliver more than the specified current but there's no guarantee.  Check the power supply rating, it must be enough to supply everything that's connected to the hub.&lt;br /&gt;
* A power supply that is rated for less than 700mA may work some of the time.&lt;br /&gt;
* Adding a USB hard disk drive. A HDD will take quite a lot of power as it starts, maybe an amp or more. It the power supply for this also supplies the Pi then this could overload things and cause trouble.&lt;br /&gt;
* Some complex keyboards have been reported to take a considerable amount of power, maybe up to 500mA.  The Pi cannot deliver this amount of power.  Simpler budget keyboards may be better. If the system works with no keyboard attached but not with a keyboard then it's worth trying a different, simpler, keyboard.&lt;br /&gt;
&lt;br /&gt;
====Summary====&lt;br /&gt;
&lt;br /&gt;
* If you are having unreliable operation the first thing to do is check your power supply.&lt;br /&gt;
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).&lt;br /&gt;
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.&lt;br /&gt;
* Not all power supplies will deliver what they claim.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T20:21:17Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* General Purpose Input/Output (GPIO) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For further general information about GPIOs, see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
The production Raspberry Pi board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is the pin in the first column and on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions and full details of how to access are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used.&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0) || GPIO14-ALT5 is UART1_TXD, GPIO14&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0) || GPIO15-ALT5 is UART1_RXD, GPIO15&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0) || GPIO08&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0) || GPIO08&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes''' || '''Alternative Functions'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0) || GPIO00&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0) || GPIO01&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || ||| GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0) || GPIO10&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0) || GPIO09&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0) || GPIO11&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
===A note about GPIO vs the schematic===&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
===Referring to pins on the Expansion header===&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===Power pins===&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T20:09:12Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For further general information about GPIOs, see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
The production Raspberry Pi board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is the pin in the first column and on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions and full details of how to access are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used.&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0), GPIO14-ALT5 is UART1_TXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0), GPIO15-ALT5 is UART1_RXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
===A note about GPIO vs the schematic===&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
===Referring to pins on the Expansion header===&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
===Power pins===&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T20:02:35Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* General Purpose Input/Output (GPIO) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For more information see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
The production board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is the pin in the first column and on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions and full details of how to access are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;.&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used.&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0), GPIO14-ALT5 is UART1_TXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0), GPIO15-ALT5 is UART1_RXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
==A note about GPIO vs the schematic==&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
==Referring to pins on the Expansion header==&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==Power pins==&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T19:58:40Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* General Purpose Input/Output (GPIO) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For more information see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
The production board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is the pin in the first column and on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux or detailed above. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used. All exposed pins can be used for GPIO.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
The chipset datasheet provides full information on accessing low level functions are available here: [http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf BCM2835-ARM-Peripherals.pdf ]&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0), GPIO14-ALT5 is UART1_TXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0), GPIO15-ALT5 is UART1_RXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
==A note about GPIO vs the schematic==&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
==Referring to pins on the Expansion header==&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==Power pins==&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T19:54:44Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: deleted duplicate table, reordered paragraphs to improve flow&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[TODO]&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software.&lt;br /&gt;
&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs.&lt;br /&gt;
&lt;br /&gt;
For more information see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
&lt;br /&gt;
The production board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is column 0 on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux or detailed above. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used. All exposed pins can be used for GPIO.&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
The chipset datasheet provides full information on accessing low level functions are available here: [http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf BCM2835-ARM-Peripherals.pdf ]&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0), GPIO14-ALT5 is UART1_TXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0), GPIO15-ALT5 is UART1_RXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
==A note about GPIO vs the schematic==&lt;br /&gt;
&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
==Referring to pins on the Expansion header==&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==Power pins==&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Low-level_peripherals</id>
		<title>RPi Low-level peripherals</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Low-level_peripherals"/>
				<updated>2012-04-20T19:44:43Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[[File:GPIOs.png|thumb|254px|right|the layout of the Rpi GPIO's, colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]&lt;br /&gt;
The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs. The production board has a 26-pin 2.54mm (100mil)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907&amp;lt;/ref&amp;gt; expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is column 0 on the bottom row. &amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide a second I2C interface. [no-ref]&lt;br /&gt;
&lt;br /&gt;
Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200bps.&lt;br /&gt;
&lt;br /&gt;
The chipset datasheet provides full information on accessing low level functions are available here: [http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf BCM2835-ARM-Peripherals.pdf ]&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, top row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-02 || bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;5V0&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-04 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-06 || bgcolor=&amp;quot;black&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;GND&amp;lt;/span&amp;gt; &lt;br /&gt;
|-&lt;br /&gt;
| P1-08 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_TXD || || (BCM2835 GPIO14-ALT0), GPIO14-ALT5 is UART1_TXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-10 || bgcolor=&amp;quot;yellow&amp;quot; | UART0_RXD || || (BCM2835 GPIO15-ALT0), GPIO15-ALT5 is UART1_RXD&lt;br /&gt;
|-&lt;br /&gt;
| P1-12 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO18 || || GPIO18-ALT5 is PWM0&lt;br /&gt;
|-&lt;br /&gt;
| P1-14 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-16 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO23&lt;br /&gt;
|-&lt;br /&gt;
| P1-18 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO24&lt;br /&gt;
|-&lt;br /&gt;
| P1-20 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-22 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO25&lt;br /&gt;
|-&lt;br /&gt;
| P1-24 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE0_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO8-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-26 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_CE1_N&amp;lt;/span&amp;gt; || || (BCM2835 GPIO7-ALT0)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''Header Pinout, bottom row:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| '''Pin Name''' || '''Pin Function''' || '''Hardware Notes''' || '''General Notes'''&lt;br /&gt;
|-&lt;br /&gt;
| P1-01 || bgcolor=&amp;quot;orange&amp;quot; | 3V3 &lt;br /&gt;
|-&lt;br /&gt;
| P1-03 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SDA || 1K8 pull up resistor || (BCM2835 GPIO0-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-05 || bgcolor=&amp;quot;cyan&amp;quot; | I2C0_SCL || 1K8 pull up resistor || (BCM2835 GPIO1-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-07 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO4&lt;br /&gt;
|-&lt;br /&gt;
| P1-09 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-11 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO17 || || GPIO17_ALT3 is UART0_RTS&lt;br /&gt;
|-&lt;br /&gt;
| P1-13 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO21 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-15 || bgcolor=&amp;quot;lime&amp;quot; | BCM2835 GPIO22 || ||&lt;br /&gt;
|-&lt;br /&gt;
| P1-17 || DNC &lt;br /&gt;
|-&lt;br /&gt;
| P1-19 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MOSI&amp;lt;/span&amp;gt; || || (BCM2835 GPIO10-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-21 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_MISO&amp;lt;/span&amp;gt; || || (BCM2835 GPIO09-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-23 || bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI_SCLK&amp;lt;/span&amp;gt; || || (BCM2835 GPIO11-ALT0)&lt;br /&gt;
|-&lt;br /&gt;
| P1-25 || DNC&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{| border=&amp;quot;1&amp;quot;&lt;br /&gt;
! Colour legend&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;red&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;+5V&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;orange&amp;quot; | +3.3V&lt;br /&gt;
|-&lt;br /&gt;
| Do not connect&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;yellow&amp;quot; | UART&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;lime&amp;quot; | GPIO&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;purple&amp;quot; | &amp;lt;span style=&amp;quot;color:white&amp;quot;&amp;gt;SPI&amp;lt;/span&amp;gt;&lt;br /&gt;
|-&lt;br /&gt;
| bgcolor=&amp;quot;cyan&amp;quot; | I2C&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
KiCad symbol: [[File:Conn-raspberry.lib]]&lt;br /&gt;
There is also some information here [http://elinux.org/RPi_Tutorial_Easy_GPIO_Hardware_%26_Software]&lt;br /&gt;
&lt;br /&gt;
==A note about GPIO vs the schematic==&lt;br /&gt;
You may notice that the GPIO connector as documented in the schematic does NOT match with what is on this wiki page. Do NOT update this wiki page. The pins which are marked as NC should not be used in order to be compatible with possible future designs. The plan is that if a new design comes along and if the layout permits it we will connect additional GPIO pins to those NC pins. (Gert's first vote is for GPIO 19 and 20, That gives us the second PWM, second SPI and I2S)&lt;br /&gt;
&lt;br /&gt;
==Referring to pins on the Expansion header==&lt;br /&gt;
&lt;br /&gt;
The header is referred to as &amp;quot;The GPIO Connector (P1)&amp;quot;.  To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended:&lt;br /&gt;
&lt;br /&gt;
* The expansion header is referred to as &amp;quot;Expansion Header&amp;quot; or &amp;quot;GPIO Connector (P1)&amp;quot;&lt;br /&gt;
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.&lt;br /&gt;
* Names GPIO0, GPIO1, GPIOx-ALTy, etc refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where &amp;quot;x&amp;quot; matches BCM2835 number (without leading zero) and &amp;quot;y&amp;quot; is the alternate number column 0 to 5 on page 102-103 of the Broadcom document.  For example, depending on what you are describing, use either &amp;quot;GPIO7&amp;quot; to refer to a row of the table, and &amp;quot;GPIO7-ALT0&amp;quot; would refer to a specific cell of the table.&lt;br /&gt;
* When refering to signal names, you should modify the Broadcom name slightly to minimize confusion.  The Broadcom SPI bus pin names are fine, such as &amp;quot;SPI0_*&amp;quot; and &amp;quot;SPI1_*&amp;quot;, but they didn't do the same on the I2C and UART pins.  Instead of using &amp;quot;SDA0&amp;quot; and &amp;quot;SCL0&amp;quot;, you should use &amp;quot;I2C0_SDA&amp;quot; and &amp;quot;I2C0_SCL&amp;quot;; and instead of &amp;quot;TX&amp;quot; or &amp;quot;TXD&amp;quot; and &amp;quot;RX&amp;quot; or &amp;quot;RXD&amp;quot;, you should use &amp;quot;UART0_TXD&amp;quot; and &amp;quot;UART0_RXD&amp;quot;.&lt;br /&gt;
&lt;br /&gt;
==Power pins==&lt;br /&gt;
Maximum permitted current draw from the 3v3 pin is 50mA.&lt;br /&gt;
&lt;br /&gt;
Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1536#postid-21841&amp;lt;/ref&amp;gt;&lt;br /&gt;
*Model A: 1000mA - 500mA -&amp;gt; max power draw: 500mA&lt;br /&gt;
*Model B: 1000mA - 700mA -&amp;gt; max power draw: 300mA&lt;br /&gt;
&lt;br /&gt;
==General Purpose Input/Output (GPIO)==&lt;br /&gt;
&lt;br /&gt;
General Purpose Input/Output (a.k.a. GPIO) is a generic pin on a chip whose behavior (including whether it is an input or output pin) can be controlled (programmed) through software. For more information see:[http://en.wikipedia.org/wiki/GPIO the wikipedia article].&lt;br /&gt;
&lt;br /&gt;
On the production board, all the UART, SPI and I2C pins can be reconfigured as GPIO pins, to provide a total of 17 GPIO pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384&amp;lt;/ref&amp;gt;. Each of their functions are detailed in the chipset datasheet &amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The availabile alternative functions and their corresponding pins are detailed below. These numbers are in reference to the chipset documentation and may not match the numbers exposed in linux or detailed above. Only fully usable functions are detailed, for some alternative functions not all the necessary pins are available for the funtionality to be actually used. All exposed pins can be used for GPIO&lt;br /&gt;
&lt;br /&gt;
'''Top Row Pinout:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
|- &lt;br /&gt;
| Header   || 2  || 4   ||  6  ||  8  || 10  || 12    || 14  || 16   || 18   || 20  || 22    || 24 || 26 &lt;br /&gt;
|- &lt;br /&gt;
| Chipset  ||    ||     ||     ||  14 || 15  || 18    ||     || 23   || 24   ||     || 25    || 8 || 7 &lt;br /&gt;
|- &lt;br /&gt;
| Function ||5V0 || DNC || GND || TXD || RXD || PWM/GPIO1   || DNC || GPIO4 || GPIO5 || DNC || GPIO6  || SPI_CE0_N || SPI_CE1_N&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
'''Bottom Row Pinout:'''&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;text-align:center;&amp;quot;&lt;br /&gt;
| Header   || 1  || 3    ||  5   || 7    || 9   || 11   || 13   || 15   || 17  || 19       || 21       || 23       || 25&lt;br /&gt;
|-    &lt;br /&gt;
| Chipset  ||    ||  0   ||  1   ||  4   ||     || 17   || 21   || 22   ||     || 10       || 9        || 11       || &lt;br /&gt;
|-   &lt;br /&gt;
| Function ||3V3 || SDA0 || SCL0 || GPIO7 || DNC || GPIO0 || GPIO2 || GPIO3 || DNC || SPI_MOSI || SPI_MISO || SPI_SCLK || DNC&lt;br /&gt;
|}&lt;br /&gt;
&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
The complete list of chipset GPIO pins which are available is: &amp;lt;pre&amp;gt;0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as I2C interface. So there are 1K8 pulls up resistors on the board for these pins.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Pin 12 supports PWM.&lt;br /&gt;
&lt;br /&gt;
GPIO voltage level is 3V3 and are not 5V tolerant.&lt;br /&gt;
&lt;br /&gt;
Each GPIO can interrupt, high/low/rise/fall/change.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/384#comment-5217&amp;lt;/ref&amp;gt;&amp;lt;ref&amp;gt;http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an ARM JTAG interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.1&amp;lt;/ref&amp;gt; However ARM_TMS isn't available for this (chipset pin 12 or 27 is needed).&lt;br /&gt;
&lt;br /&gt;
It is also possible to reconfigure some of the pins to provide an I2S (hardware mod may be required&amp;lt;ref name=&amp;quot;I2S&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;) or PCM interface.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1288.2&amp;lt;/ref&amp;gt; However, PCM_FS and PCM_DIN (chipset pins 19 or 29 and 20 or 30) are needed for I2S or PCM.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===Driver support===&lt;br /&gt;
&lt;br /&gt;
The Foundation will not include a GPIO driver in the initial release, standard linux GPIO drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an SPI driver in the initial release, we hope the community might write one.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1278.0&amp;lt;/ref&amp;gt;&lt;br /&gt;
The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&amp;amp;t=1202&amp;lt;/ref&amp;gt;&lt;br /&gt;
&lt;br /&gt;
===Code examples===&lt;br /&gt;
====GPIO Driving Example (C)====&lt;br /&gt;
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo &amp;amp; Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.&lt;br /&gt;
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)&lt;br /&gt;
Example GPIO code:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
//&lt;br /&gt;
//  How to access GPIO registers from C-code on the Raspberry-Pi&lt;br /&gt;
//  Example program&lt;br /&gt;
//  15-January-2012&lt;br /&gt;
//  Dom and Gert&lt;br /&gt;
//&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// Access from ARM Running Linux&lt;br /&gt;
&lt;br /&gt;
#define BCM2708_PERI_BASE        0x20000000&lt;br /&gt;
#define GPIO_BASE                (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;stdio.h&amp;gt;&lt;br /&gt;
#include &amp;lt;string.h&amp;gt;&lt;br /&gt;
#include &amp;lt;stdlib.h&amp;gt;&lt;br /&gt;
#include &amp;lt;dirent.h&amp;gt;&lt;br /&gt;
#include &amp;lt;fcntl.h&amp;gt;&lt;br /&gt;
#include &amp;lt;assert.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/mman.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/types.h&amp;gt;&lt;br /&gt;
#include &amp;lt;sys/stat.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#include &amp;lt;unistd.h&amp;gt;&lt;br /&gt;
&lt;br /&gt;
#define PAGE_SIZE (4*1024)&lt;br /&gt;
#define BLOCK_SIZE (4*1024)&lt;br /&gt;
&lt;br /&gt;
int  mem_fd;&lt;br /&gt;
char *gpio_mem, *gpio_map;&lt;br /&gt;
char *spi0_mem, *spi0_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// I/O access&lt;br /&gt;
volatile unsigned *gpio;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)&lt;br /&gt;
#define INP_GPIO(g) *(gpio+((g)/10)) &amp;amp;= ~(7&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define OUT_GPIO(g) *(gpio+((g)/10)) |=  (1&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)&amp;lt;=3?(a)+4:(a)==4?3:2)&amp;lt;&amp;lt;(((g)%10)*3))&lt;br /&gt;
&lt;br /&gt;
#define GPIO_SET *(gpio+7)  // sets   bits which are 1 ignores bits which are 0&lt;br /&gt;
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0&lt;br /&gt;
&lt;br /&gt;
void setup_io();&lt;br /&gt;
&lt;br /&gt;
int main(int argc, char **argv)&lt;br /&gt;
{ int g,rep;&lt;br /&gt;
&lt;br /&gt;
  // Set up gpi pointer for direct register access&lt;br /&gt;
  setup_io();&lt;br /&gt;
&lt;br /&gt;
  // Switch GPIO 7..11 to output mode&lt;br /&gt;
&lt;br /&gt;
 /************************************************************************\&lt;br /&gt;
  * You are about to change the GPIO settings of your computer.          *&lt;br /&gt;
  * Mess this up and it will stop working!                               *&lt;br /&gt;
  * It might be a good idea to 'sync' before running this program        *&lt;br /&gt;
  * so at least you still have your code changes written to the SD-card! *&lt;br /&gt;
 \************************************************************************/&lt;br /&gt;
&lt;br /&gt;
  // Set GPIO pins 7-11 to output&lt;br /&gt;
  for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
  {&lt;br /&gt;
    INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO&lt;br /&gt;
    OUT_GPIO(g);&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  for (rep=0; rep&amp;lt;10; rep++)&lt;br /&gt;
  {&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_SET = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
     for (g=7; g&amp;lt;=11; g++)&lt;br /&gt;
     {&lt;br /&gt;
       GPIO_CLR = 1&amp;lt;&amp;lt;g;&lt;br /&gt;
       sleep(1);&lt;br /&gt;
     }&lt;br /&gt;
  }&lt;br /&gt;
&lt;br /&gt;
  return 0;&lt;br /&gt;
&lt;br /&gt;
} // main&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
//&lt;br /&gt;
// Set up a memory regions to access GPIO&lt;br /&gt;
//&lt;br /&gt;
void setup_io()&lt;br /&gt;
{&lt;br /&gt;
&lt;br /&gt;
   /* open /dev/mem */&lt;br /&gt;
   if ((mem_fd = open(&amp;quot;/dev/mem&amp;quot;, O_RDWR|O_SYNC) ) &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;can't open /dev/mem \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   /* mmap GPIO */&lt;br /&gt;
&lt;br /&gt;
   // Allocate MAP block&lt;br /&gt;
   if ((gpio_mem = malloc(BLOCK_SIZE + (PAGE_SIZE-1))) == NULL) {&lt;br /&gt;
      printf(&amp;quot;allocation error \n&amp;quot;);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Make sure pointer is on 4K boundary&lt;br /&gt;
   if ((unsigned long)gpio_mem % PAGE_SIZE)&lt;br /&gt;
     gpio_mem += PAGE_SIZE - ((unsigned long)gpio_mem % PAGE_SIZE);&lt;br /&gt;
&lt;br /&gt;
   // Now map it&lt;br /&gt;
   gpio_map = (unsigned char *)mmap(&lt;br /&gt;
      (caddr_t)gpio_mem,&lt;br /&gt;
      BLOCK_SIZE,&lt;br /&gt;
      PROT_READ|PROT_WRITE,&lt;br /&gt;
      MAP_SHARED|MAP_FIXED,&lt;br /&gt;
      mem_fd,&lt;br /&gt;
      GPIO_BASE&lt;br /&gt;
   );&lt;br /&gt;
&lt;br /&gt;
   if ((long)gpio_map &amp;lt; 0) {&lt;br /&gt;
      printf(&amp;quot;mmap error %d\n&amp;quot;, (int)gpio_map);&lt;br /&gt;
      exit (-1);&lt;br /&gt;
   }&lt;br /&gt;
&lt;br /&gt;
   // Always use volatile pointer!&lt;br /&gt;
   gpio = (volatile unsigned *)gpio_map;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
} // setup_io&lt;br /&gt;
&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Pull Up/Pull Down Register Example====&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
   // enable pull-up on GPIO24&amp;amp;25&lt;br /&gt;
   GPIO_PULL = 2;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   // clock on GPIO 24 &amp;amp; 25 (bit 24 &amp;amp; 25 set)&lt;br /&gt;
   GPIO_PULLCLK0 = 0x03000000;&lt;br /&gt;
   short_wait();&lt;br /&gt;
   GPIO_PULL = 0;&lt;br /&gt;
   GPIO_PULLCLK0 = 0;&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Python)====&lt;br /&gt;
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
import RPi.GPIO as GPIO&lt;br /&gt;
&lt;br /&gt;
# set up the GPIO channels - channel 0 (input) and channel 1 (output)&lt;br /&gt;
GPIO.setup(0, GPIO.IN)&lt;br /&gt;
GPIO.setup(1, GPIO.OUT)&lt;br /&gt;
&lt;br /&gt;
# input from channel 0 - note that input_value will be a boolean&lt;br /&gt;
input_value = GPIO.input(0)&lt;br /&gt;
&lt;br /&gt;
# output True to channel 1.  NB you can use '1', 1 or anything that evaluates to True/False&lt;br /&gt;
GPIO.output(1, True)&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
====GPIO Driving Example (Shell script)====&lt;br /&gt;
* Disclaimer: Untested !&lt;br /&gt;
&amp;lt;pre&amp;gt;&lt;br /&gt;
#!/bin/sh&lt;br /&gt;
&lt;br /&gt;
# GPIO numbers should be from this list&lt;br /&gt;
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 4 and set to output&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;out&amp;quot; &amp;gt; /sys/class/gpio/gpio4/direction&lt;br /&gt;
&lt;br /&gt;
# set up GPIO 7 and set to input&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/export&lt;br /&gt;
echo &amp;quot;in&amp;quot; &amp;gt; /sys/class/gpio/gpio7/direction&lt;br /&gt;
&lt;br /&gt;
# write output&lt;br /&gt;
echo &amp;quot;1&amp;quot; &amp;gt; /sys/class/gpio/gpio4/value&lt;br /&gt;
&lt;br /&gt;
# read from input&lt;br /&gt;
cat /sys/class/gpio/gpio7/value &lt;br /&gt;
&lt;br /&gt;
# clean up&lt;br /&gt;
echo &amp;quot;4&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
echo &amp;quot;7&amp;quot; &amp;gt; /sys/class/gpio/unexport&lt;br /&gt;
&amp;lt;/pre&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==MIPI CSI-2==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the MIPI CSI-2 interface to a 15-way flat flex connector&lt;br /&gt;
&lt;br /&gt;
is Sony sub-LVDS same as MIPI CSI-2? Sony IMX020 5Mbip module is available for $5-7 (SE K850i replacement camera).&lt;br /&gt;
&lt;br /&gt;
Looks like Nokia N95 uses CSI-2 5Mpix camera module with autofocus. ~$15 replacement part.&lt;br /&gt;
&lt;br /&gt;
==DSI==&lt;br /&gt;
&lt;br /&gt;
On the production board, we bring out the DSI interface to a 15-way flat flex connector.&lt;br /&gt;
&lt;br /&gt;
==CEC==&lt;br /&gt;
&lt;br /&gt;
[[CEC (Consumer Electronics Control) over HDMI|HDMI-CEC (Consumer Electronics Control for HDMI)]] is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.&lt;br /&gt;
Eben notes that he has seen CEC demos on the Broadcom SoC they are using. &lt;br /&gt;
&lt;br /&gt;
For more information about HDMI-CEC and what you could do with it on the Raspberry Pi please see the [[CEC (Consumer Electronics Control) over HDMI]] article.&lt;br /&gt;
&lt;br /&gt;
== References ==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Buying_Guide</id>
		<title>RPi Buying Guide</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Buying_Guide"/>
				<updated>2012-04-20T10:15:52Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Sales order numbers */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Startup}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=Ordering=&lt;br /&gt;
Raspberry Pi has appointed [http://www.element14.com/raspberrypi Premier Farnell] and [http://rswww.com RS Components] as its authorised manufacturing distributors.&lt;br /&gt;
&lt;br /&gt;
If you see the units for sale from other sources (in particular eBay), it is likely that they are at BEST hopeful resellers, or SCAM sites, either way units will not be available any sooner than through the above distributors, or you will pay far more than it is worth (if you get it at all).&lt;br /&gt;
&lt;br /&gt;
Raspberry Pi's distributors will ship worldwide to the best of their ability (ie subject to origin export and local import laws).&lt;br /&gt;
&lt;br /&gt;
Countries that are currently subject to UK (including EU and UN) export restrictions include North Korea, Iran, Ivory Coast, Liberia and Zimbabwe. A full list and further details are provided at [http://www.businesslink.gov.uk/bdotg/action/layer?topicId=1084100244]&lt;br /&gt;
&lt;br /&gt;
For shipping costs, please refer to the websites of the authorised resellers.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Distributor Links==&lt;br /&gt;
[[RPi Buying Links By Country | Buying Links By Country]] to order from your part of the world (includes direct links to the product and additional details about each local distributor etc, or see the worldwide links below.&lt;br /&gt;
&lt;br /&gt;
===Farnell Worldwide===&lt;br /&gt;
'''Premier Farnell''' also trades worldwide under the names '''Farnell''', '''Element14''', '''Newark Electronics''', '''CPC''' and '''MCM Electronics'''.&lt;br /&gt;
&lt;br /&gt;
[http://www.farnell.com/ Farnell Worldwide Links]&lt;br /&gt;
&lt;br /&gt;
Farnell Partner Sites:&lt;br /&gt;
&lt;br /&gt;
[http://cpc.farnell.com/ CPC]&lt;br /&gt;
&lt;br /&gt;
[http://www.newark.com/ Newark Electronics]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===RS Components Worldwide===&lt;br /&gt;
'''RS Components''' also trades worldwide under the names '''Electrocomponents''', '''Allied Electronics''' and '''DesignSpark'''.&lt;br /&gt;
&lt;br /&gt;
[http://www.rs-components.com/index.html RS-Components Worldwide Links]&lt;br /&gt;
&lt;br /&gt;
== Sales order numbers ==&lt;br /&gt;
* Allied Electronics: 70229569&lt;br /&gt;
* CPC Farnell: SC12590&lt;br /&gt;
* Farnell, Element 14: 2081185 or 83T1943&lt;br /&gt;
* FarnellNewark.br: currently unknown&lt;br /&gt;
* Newark: 83T1943&lt;br /&gt;
* RS, Electrocomponents: currently unknown.  To order from RS or Electrocomponents, please fill in their expression of interest page to be added to the queue.  When they are ready to fulfil, they'll invite you to complete a secure payment form.&lt;br /&gt;
&lt;br /&gt;
=1st Production Run &amp;amp; Release=&lt;br /&gt;
 The initial 10,000 RaspberryPi Boards have sold out. Preorders for coming batches are possible.&lt;br /&gt;
&lt;br /&gt;
# The foundation have built an initial run of 10,000 Model-B units.&lt;br /&gt;
# Due to extreme demand, the units will be NOT sold directly from the [http://www.raspberrypi.com shop] (see [[#Licensed Manufacture]] below).&lt;br /&gt;
# You may buy a Raspberry Pi from [http://www.element14.com/raspberrypi Farnell] or from [http://rswww.com RS Components]&lt;br /&gt;
# A limit of one unit per person - unfortunately this also means no combined shipping for this batch (demand depends how long this will be enforced)*&lt;br /&gt;
# Normal unlimited sales should take place quickly after.&lt;br /&gt;
&lt;br /&gt;
 * There were reports that several people ordered multiple units at launch,&lt;br /&gt;
   however it appears that Farnell removed any excess items when they reviewed&lt;br /&gt;
   and confirmed the order for shipping dates.&lt;br /&gt;
   This has also appears to apply for the pre-orders they have taken.&lt;br /&gt;
&lt;br /&gt;
==1st Batch Order FAQ==&lt;br /&gt;
 NOTE: While every attempt has been made to provide accurate information,&lt;br /&gt;
       this FAQ is not official and is based on what information is available at the time of writing.&lt;br /&gt;
===Press Releases===&lt;br /&gt;
'''Farnell:'''&lt;br /&gt;
&lt;br /&gt;
[http://www.element14.com/community/docs/DOC-43262/l/frequently-asked-questions-about-raspberry-pi/?CMP=SOM-TW-e14RasPiFAQ Post-Launch FAQ by Farnell], see their attached docx file for details.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''RS Components:'''&lt;br /&gt;
&lt;br /&gt;
[http://www.electrocomponents.com/media/press-releases/2012/02/29th/ Post-Launch statement by RS Components]&lt;br /&gt;
&lt;br /&gt;
[http://uk.rs-online.com/web/generalDisplay.html?id=raspberrypi&amp;amp;file=questions&amp;amp;cm_sp=raspberrypi-_--_-questions Raspberry Pi, Your Questions Answered by RS Components]&lt;br /&gt;
&lt;br /&gt;
====Q: Couldn't this have been handled better, I couldn't get on the site to order and they sold too quickly?====&lt;br /&gt;
Both distributors were indeed unprepared for the volume of traffic the launch generated (they were warned by the foundation before hand).&lt;br /&gt;
&lt;br /&gt;
Chances are if the foundation had gone with their original plan of selling through their own shop, the situation would have been far worse, with no option of pre-order either.&lt;br /&gt;
&lt;br /&gt;
The distributors only have 5,000 units each to sell, reports have estimated the registered interest/pre-orders totalling over 2 million (no official figures available yet).&lt;br /&gt;
Even if it is half of that, it means the number of available units was less than 1% of the demand.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Q: If interest was obviously so high...why only build 10,000 units?====&lt;br /&gt;
There is a big risk involved with building a large batch of units and selling them, and 10,000 units would take well over $250,000 in capital investment.  For a very small charity, that is a massive ask in itself. Much of that funding came from the Foundation Trustees' own personal investment.&lt;br /&gt;
&lt;br /&gt;
Thankfully, the massive bonus of licensing out manufacture, is that the build rate is no longer limited by the foundation's own funding, which means there will be many more units available much sooner.&lt;br /&gt;
&lt;br /&gt;
====Q: I've been unable to register an account with the distributor, as I am not a company?====&lt;br /&gt;
There have been several reported problems with individuals placing orders (i.e. not having company accounts or details).&lt;br /&gt;
&lt;br /&gt;
Both distributors &amp;quot;should&amp;quot; take orders from individuals, however it appears each of the different localised sites may have different requirements so this will be investigated to ensure that this is corrected if needed.&lt;br /&gt;
&lt;br /&gt;
Often, many of the company related fields on application are optional, if in doubt contact their sales team for help.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Q: Worldwide launch? It was not available here! ====&lt;br /&gt;
The distributors decided to make the units only available from selected locations, it appears the foundation were not made aware of this beforehand.&lt;br /&gt;
&lt;br /&gt;
Considering the small number of available units, it would have been unlikely to have improved the situation.&lt;br /&gt;
&lt;br /&gt;
Worldwide availability will be monitored, it is expected that they will be made available as soon as possible.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Q: The price for the RPi from Farnell verses the price from RS Components is different, why?====&lt;br /&gt;
Please see the following page for details about [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (13 March 2012).&lt;br /&gt;
&lt;br /&gt;
====Q: I've only been able to register my interest, what now?====&lt;br /&gt;
Be patient, both distributors have said they will contact people when they have more details (alternatively keep an eye on their sites for news).&lt;br /&gt;
&lt;br /&gt;
RS Components, in particular have only taken people's details, and according to the above [[#Press Releases | press-release]] will wait until they receive their allocated 5,000 units.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
====Q: I registered on the Raspberry Pi Site's Mailing List but I didn't get an email====&lt;br /&gt;
Unfortunately, the mail server had problems with sending out the 100K+ emails in time, it is believed the email was often marked as spam by a lot of email systems so was rejected or returned on-mass, or sent to Junk folders.  Yes, this system should have been tested, but the foundation were keen not to send unnecessary emails to people prior to launch.&lt;br /&gt;
&lt;br /&gt;
The email contained the same information about the announcement as was publicly posted on the website (28th Feb 2012) before launch day, no additional or extra information was given through the email.&lt;br /&gt;
&lt;br /&gt;
=Licensed Manufacture=&lt;br /&gt;
The foundation has chosen to license manufacture of the RPi, which should provide several advantages including:&lt;br /&gt;
&lt;br /&gt;
# The involvement of RS Components and Premier Farnell means that build volume can be increased much, much faster than would have been possible otherwise.  Due to costs and working capital, the foundation would have been limited to batches of only 10k Raspberry Pis; the Raspberry Pi will now be being built to match demand.&lt;br /&gt;
# Both Premier Farnell and RS Components have worldwide distribution networks, so wherever you are in the world, you will be able to buy from a local distributor.  It’s a much better way for you to buy than getting them all shipped from the Foundation in the UK.&lt;br /&gt;
# Both RS Components and Premier Farnell will be taking preorders, something which the foundation would otherwise be unable to do.&lt;br /&gt;
# The foundation will still receive a percentage from the sale of every RPi sold, which will be put straight back into the charity.&lt;br /&gt;
# Primarily, by removing the focus on dealing with manufacture, distribution and sales, this frees up the limited resources of the foundation to focus on the original aims and goals of the project.&lt;br /&gt;
&lt;br /&gt;
Additional detail is available in the [http://hardware.slashdot.org/story/12/02/28/2347222/raspberry-pi-now-has-distributors----and-will-soon-have-boards-for-all-video video interview between Eben Upton and SlashDot here (28/02/12)].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=What You Get In The Box=&lt;br /&gt;
This is unconfirmed until units start to ship:&lt;br /&gt;
&lt;br /&gt;
1. Pre-Assembled Raspberry Pi board&lt;br /&gt;
&lt;br /&gt;
2. Quick Start Guide (likely to be paper copy of [http://elinux.org/File:Raspi-Model-AB-Mono-1-699x1024.png RPi Model-AB Guide])&lt;br /&gt;
&lt;br /&gt;
''Note:''&lt;br /&gt;
&lt;br /&gt;
''1. The board will be supplied assembled (since most of the components are not suitable for home builds, including the BGA&amp;lt;ref name=&amp;quot;BGA&amp;quot;&amp;gt;http://en.wikipedia.org/wiki/Ball_grid_array&amp;lt;/ref&amp;gt;package mounted SoC&amp;lt;ref name=&amp;quot;SoC&amp;quot;&amp;gt;http://en.wikipedia.org/wiki/System_on_a_chip&amp;lt;/ref&amp;gt; and PoP&amp;lt;ref name=&amp;quot;PoP&amp;quot;&amp;gt;http://en.wikipedia.org/wiki/Package_on_package&amp;lt;/ref&amp;gt; memory).''&lt;br /&gt;
&lt;br /&gt;
''2. The board will NOT have GPIO or JTAG header pins (are not supplied, although may be available from the shop later on).''&lt;br /&gt;
&lt;br /&gt;
''3. The board will NOT have CSI and DSI connectors fitted (needs confirmation).''&lt;br /&gt;
&lt;br /&gt;
''4. All other connectors will be assembled in place.''&lt;br /&gt;
&lt;br /&gt;
=Accessories=&lt;br /&gt;
Some accessories will be made available from the shop (farnell have several bundles planned):&lt;br /&gt;
* USB Power Supply (UK/EU/US Compatible)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/forum/general-discussion/is-the-raspberrypi-going-to-be-sold-as-a-kit/#p32289&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Pre-Prepared System SD-Card (software will be provided to prepare your own) -size is unconfirmed&lt;br /&gt;
* Cases (will be available in a few months - i.e. Q2 2012)&lt;br /&gt;
* [[Rpi expansion boards | AddOn/Expansion Boards]] (will be available later on - i.e. [[Rpi Gertboard | GertBoard]] due soon)&lt;br /&gt;
''See [[RPi Hardware Basic Setup#Typical Hardware You Will Need | Typical Hardware You Will Need]] for details about other items you may require.''&lt;br /&gt;
&lt;br /&gt;
=Price=&lt;br /&gt;
Although the foundation is UK based, the guide price of the units are in USD since the RPi components are sourced in USD$.&lt;br /&gt;
&lt;br /&gt;
The price is $25USD (~£16GBP) for model A, and $35USD (~£23GBP) for model B.&lt;br /&gt;
&lt;br /&gt;
Items will be subject to local Tax (i.e. UK will have 20% VAT added) and shipping cost is not included.&lt;br /&gt;
&lt;br /&gt;
See the following update on [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (13th March 2012).&lt;br /&gt;
&lt;br /&gt;
=Clones &amp;amp; Copies=&lt;br /&gt;
The foundation plans to release all the required schematics and plans to reproduce the RPi hardware, so clones and copies will be welcome.&lt;br /&gt;
&lt;br /&gt;
However, since the unit is built around the Broadcom SoC, the interested party will require suitable sized orders to obtain them.  The foundation were fortunate enough to be supported in this aspect by Broadcom to enable the project to be feasible.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=References=&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_schematic_errata</id>
		<title>RPi schematic errata</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_schematic_errata"/>
				<updated>2012-04-20T10:05:29Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Unverified typos */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
Back to [[RPi_Hardware#Components]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Raspberry Pi schematic errata =&lt;br /&gt;
&lt;br /&gt;
The (partial) datasheet was published here: [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf | at raspberrypi.org] and [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf | a mirror]&lt;br /&gt;
&lt;br /&gt;
It has a couple of typos. Some more serious than others. &lt;br /&gt;
&lt;br /&gt;
Let's gather those schematic typos and errors here. &lt;br /&gt;
&lt;br /&gt;
The quality of the schematic is high. It looks like it contains the information that designers need. &lt;br /&gt;
&lt;br /&gt;
==Schematic v1.0 (Model B)==&lt;br /&gt;
&lt;br /&gt;
===Unverified typos===&lt;br /&gt;
&lt;br /&gt;
* On sheet 3, area C9, should that not be a (B) instead of (A) under the “IC3?”&lt;br /&gt;
* Also D10 close by&lt;br /&gt;
* R22,23,24,25 &amp;amp; C28 all missing (B) designation&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hardware</id>
		<title>RPi Hardware</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hardware"/>
				<updated>2012-04-20T07:59:34Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* Schematic / Layout */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
{{Template:RPi_Hardware}}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
==Introduction==&lt;br /&gt;
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]&lt;br /&gt;
The first product is the size of a credit card, and is designed to plug into a TV or HDMI monitor. It comes in two variants, model A and B, with B having more features. The expected price is $25 for model A and $35 for model B. The [[Rpi Low-level peripherals| GPIO pins]] on each board allow the use of optional [[Rpi expansion boards|expansion boards]].&lt;br /&gt;
&lt;br /&gt;
Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].&lt;br /&gt;
&lt;br /&gt;
==Specifications==&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
!&lt;br /&gt;
! Model A&lt;br /&gt;
! Model B&lt;br /&gt;
|-&lt;br /&gt;
| Target price:&amp;lt;ref name=&amp;quot;faq&amp;quot; &amp;gt;http://www.raspberrypi.org/faqs&amp;lt;/ref&amp;gt;&lt;br /&gt;
| US$25 (GBP £16)&lt;br /&gt;
| US$35 (GBP £22)&lt;br /&gt;
|-&lt;br /&gt;
| System-on-a-chip (SoC):&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom BCM2835 (CPU + GPU + SDRAM)&lt;br /&gt;
|-&lt;br /&gt;
| CPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 700&amp;amp;nbsp;MHz ARM11 ARM1176JZF-S core&lt;br /&gt;
|-&lt;br /&gt;
| GPU:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode &lt;br /&gt;
|-&lt;br /&gt;
| Memory (SDRAM)iB&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 256 MiB (previously listed as 128MiB for model A, but an upgrade to 256MiB was announced on 29 Feb 2012)&lt;br /&gt;
|-&lt;br /&gt;
| USB 2.0 ports:&lt;br /&gt;
| 1(provided by the BCM2835)&lt;br /&gt;
| 2 (via integrated USB hub)&lt;br /&gt;
|-&lt;br /&gt;
| Video outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Composite video|Composite RCA, HDMI (not at the same time)&lt;br /&gt;
|-&lt;br /&gt;
| Audio outputs:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | TRS connector|3.5 mm jack, HDMI&lt;br /&gt;
|-&lt;br /&gt;
| Audio inputs:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | none, but a USB mic or sound-card could be added&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Storage:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | Secure Digital|SD / MMC / SDIO card slot&lt;br /&gt;
|-&lt;br /&gt;
| Onboard Network:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| None&lt;br /&gt;
| 10/100 wired Ethernet RJ45&lt;br /&gt;
|-&lt;br /&gt;
| Low-level peripherals:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S&amp;lt;ref name=&amp;quot;i2s&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/sad-about-removal-of-i2s-why-was-this-change-made Forum:Sad about removal of I2S. Why was this change made?]&amp;lt;/ref&amp;gt;, Universal asynchronous receiver/transmitter (UART)&lt;br /&gt;
|-&lt;br /&gt;
| Real-time clock:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | None&lt;br /&gt;
|-&lt;br /&gt;
| Power ratings (provisional, from alpha board):&lt;br /&gt;
| 500mA, (2.5 Watt) &amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| 700mA, (3.5 Watt)&lt;br /&gt;
|-&lt;br /&gt;
| Power source:&amp;lt;ref name=&amp;quot;faq&amp;quot; /&amp;gt;&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 5V via Micro USB or GPIO header&lt;br /&gt;
|-&lt;br /&gt;
| Size:&lt;br /&gt;
| colspan=&amp;quot;2&amp;quot; | 85.60mm x 53.98mm&amp;lt;ref&amp;gt;[http://www.raspberrypi.org/archives/344 Final PCB artwork]&amp;lt;/ref&amp;gt; (3.370 × 2.125 inch)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Components==&lt;br /&gt;
[[File:Raspi-Model-AB-Mono-2-699x1024.png|400px|thumb|right|A diagram denoting the places of the different components on the Rpi, made by Paul&lt;br /&gt;
Beech, edited to show 256MB ram for both boards]]&lt;br /&gt;
(Provisional - some of the expansion interfaces won't be available on production boards)&lt;br /&gt;
(PCB IDs are those of the Model B Beta board) &lt;br /&gt;
&lt;br /&gt;
* SoC: [http://www.broadcom.com/products/BCM2835 Broadcom BCM2835 media processor] ([http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf datasheet], [[BCM2835 datasheet errata]]) system-on-chip featuring:&lt;br /&gt;
** CPU core: [http://infocenter.arm.com/help/topic/com.arm.doc.ddi0301h/DDI0301H_arm1176jzfs_r0p7_trm.pdf ARM1176JZF-S] ARM11 core clocked at 700MHz; ARM VFP.  The ARM11 core implements the ARMv6 Architecture.  For details on ARM instruction sets and naming conventions, see [http://en.wikipedia.org/wiki/ARM_architecture ARM architecture] and [http://en.wikipedia.org/wiki/List_of_ARM_microprocessor_cores List of ARM microprocessor cores].&lt;br /&gt;
** GPU core: a Broadcom [http://en.wikipedia.org/wiki/Videocore VideoCore] IV GPU providing OpenGL ES 1.1, OpenGL ES 2.0, hardware-accelerated OpenVG 1.1, Open EGL, OpenMAX and 1080p30 H.264 high-profile decode.  There are 24 GFLOPS of general purpose compute and a bunch of texture filtering and DMA infrastructure.  Eben worked on the architecture team for this and the Raspberry Pi team are looking at how they can make some of the proprietary features available to application programmers&lt;br /&gt;
** DSP core: There is a DSP, but there isn't currently a public API (Liz thinks the BC team are keen to make one available at some point)&lt;br /&gt;
** 256MiB of SDRAM.  The RAM is physically stacked on top of the Broadcom media processor (package-on-package technology)&lt;br /&gt;
* LAN9512 ([http://www.smsc.com/media/Downloads_Public/Data_Briefs/9512db.pdf Data Brief] | [http://www.smsc.com/media/Downloads_Public/Data_Sheets/9512.pdf Data Sheet])'''(Model B)''' providing:&lt;br /&gt;
** 10/100Mb Ethernet (Auto-MDIX)&amp;lt;ref name=autoMDIX&amp;gt;[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]&amp;lt;/ref&amp;gt;&lt;br /&gt;
** 2x USB 2.0 &lt;br /&gt;
* S1: Micro USB power jack (5v - Power Only)&lt;br /&gt;
* S2: DSI interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S3: HDMI connector providing type A HDMI 1.3a out&lt;br /&gt;
* S4: Composite Video connector: RCA&lt;br /&gt;
* S5: MIPI CSI-2 interface.  15-pin surface mounted flat flex connector.&lt;br /&gt;
* S6: Audio connector: 3.5mm stereo jack (output only)&lt;br /&gt;
* S8: SD/MMC/SDIO memory card slot (underside)&lt;br /&gt;
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''&lt;br /&gt;
* P1: 26-pin 2.54mm header expansion (header not fitted), providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]&lt;br /&gt;
** 8 GPIOs at 3v3&lt;br /&gt;
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3&lt;br /&gt;
** I2C interface (3v3); or 2 GPIOs at 3v3&lt;br /&gt;
** SPI interface (3v3); or 5 GPIOs at 3v3&lt;br /&gt;
** 3v3, 5v and GND supply pins&lt;br /&gt;
** ARM JTAG (if pins are reconfigured in software)&lt;br /&gt;
** Second I2C interface (3v3) (if pins are reconfigured in software)&lt;br /&gt;
** I2S interface (if pins are reconfigured in software, hardware hack may be required&amp;lt;ref name=&amp;quot;i2s&amp;quot;/&amp;gt;)&lt;br /&gt;
** 6 pins reserved for future use&lt;br /&gt;
* P2 and P3: 8-pin and 7-pin 2.54mm header expansion (header not fitted), providing:&lt;br /&gt;
** 6-pin GPU JTAG (ARM11 pinout)&lt;br /&gt;
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''&lt;br /&gt;
* 5 Status LEDs&amp;lt;ref name=&amp;quot;PCBs&amp;quot;&amp;gt;[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDs&amp;quot;&amp;gt;[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]&amp;lt;/ref&amp;gt;&amp;lt;ref name=&amp;quot;LEDsGPIO&amp;quot;&amp;gt;[http://www.raspberrypi.org/forum/features-and-requests/what-do-the-status-indicator-leds-indicate-the-status-of Forum:What do the status indicator LEDs indicate the status of?]&amp;lt;/ref&amp;gt;:&lt;br /&gt;
** D5(Yellow) - OK  - SDCard Access (via GPIO16)&lt;br /&gt;
** D6(Red) - PWR - 3.3V Power&lt;br /&gt;
** D7(Green) - FDX - Full Duplex (LAN) '''(Model B)'''&lt;br /&gt;
** D8(Green) - LNK - Link/Activity (LAN) '''(Model B)'''&lt;br /&gt;
** D9(Yellow) - 10M - 10/100Mbit (LAN) '''(Model B)'''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Board size: 85.60mm x 53.98mm.  Overall height expected to be less than 25mm. &amp;lt;ref name=&amp;quot;artwork&amp;quot;&amp;gt;http://www.raspberrypi.org/archives/344&amp;lt;/ref&amp;gt;&lt;br /&gt;
* Weight: &amp;lt;40g? (Alpha board weighs ~55g &amp;lt;ref&amp;gt;http://www.raspberrypi.org/?page_id=43&amp;amp;mingleforumaction=viewtopic&amp;amp;t=285.0&amp;lt;/ref&amp;gt;)&lt;br /&gt;
* 6 layer PCB &amp;lt;ref name=&amp;quot;artwork&amp;quot; /&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Schematic / Layout==&lt;br /&gt;
&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot]&lt;br /&gt;
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot, labelled version]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1-300x225.jpg Low-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back-300x225.jpg Low-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/front1.jpg High-resolution PCB front photo, Beta board]&lt;br /&gt;
* [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2011/12/back.jpg High-resolution PCB back photo, Beta board]&lt;br /&gt;
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official schematics PDF] | [[RPi_schematic_errata|errata]]&lt;br /&gt;
&lt;br /&gt;
==Power==&lt;br /&gt;
&lt;br /&gt;
The board takes fixed 5V input, (with the 1V2 core voltage generated directly from the input using the internal switch-mode supply on the BCM2835 die). &lt;br /&gt;
This permits adoption of the micro USB form factor, which, in turn, prevents the user from inadvertently plugging in out-of-range power inputs; that would be dangerous, since the 5V would go straight to HDMI and output USB ports, even though the problem should be mitigated by some protections applied to the input power: The board provides a polarity protection diode, a voltage clamp, and a self-resetting semiconductor fuse.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Board A: 5V, 500 mA (2.5W) without any devices connected&lt;br /&gt;
* Board B: 5V, 700 mA (3.5W) without any devices connected&lt;br /&gt;
&lt;br /&gt;
*As the 5V rail is brought out in the [[Rpi_Low-level_peripherals | GPIO pins]], you can power the Rpi from there too. You should mind however, that those are ''behind'' the power protection circuitry , so you should provide your own.&lt;br /&gt;
* It is possible to power the Rpi from a powered USB hub the Rpi controls, but only on 'dumb' devices, that allow the port to supply the full current without waiting for the usb device to ask for it[http://www.raspberrypi.org/forum/general-discussion/power-pi-from-usb-hub-connected-to-pi]. As the power input of the Rpi doesn't have its data leads connected, there is no chance for a communication loop of some sorts.&lt;br /&gt;
* POE ([http://nl.wikipedia.org/wiki/Power_over_Ethernet power over ethernet]) is currently not available for the Rpi (but nobody stops you from taking your soldering iron and doing it yourself)&lt;br /&gt;
&lt;br /&gt;
===Power Supply Problems===&lt;br /&gt;
&lt;br /&gt;
There have been a number of problems reported that seem to be caused by inadequate power, this is an attempt to explain what is needed and the consequences of not having enough power.&lt;br /&gt;
&lt;br /&gt;
The power required by the Pi will vary depending on how busy it is and what peripherals are connected.&lt;br /&gt;
* Running a GUI will take more power.&lt;br /&gt;
* The USB devices and Ethernet connection will take power.&lt;br /&gt;
* Running software will take power.&lt;br /&gt;
&lt;br /&gt;
This means that it's difficult to say exactly how much power is needed.  People have reported current requirements of between 300mA and 550mA. But it could in reality take more, especially for short periods. A simple multimeter will not show short surges on the power requirement. A surge in the power requirement for a few milliseconds will not be detectable by a meter but will be enough to cause problems.&lt;br /&gt;
If the board does not get enough power the voltage will drop. If it drops enough parts of the system will run unreliably because data can get corrupted.  The USB IC runs on 5V and handles the USB and Ethernet ports so it's likely that this will be the first thing to fail. Problems seen are unreliable Ethernet connection and unreliable operation of the Keyboard and/or mouse.&lt;br /&gt;
&lt;br /&gt;
There are several reasons why the power to the board may be inadequate:&lt;br /&gt;
* The PSU may not deliver enough power.  Although the maximum power requirement is said to be 700mA a 1000mA PSU should be the minimum.  This allows some leeway in case the power supply cannot deliver it's full power without the voltage dropping.&lt;br /&gt;
* The PSU is not regulated.&lt;br /&gt;
* The cable connecting the PSU to the Pi may not be good. People have reported cables with 4 ohms resistance on the power connections. At 500mA drain this would reduce a 5V supply to 3V.&lt;br /&gt;
&lt;br /&gt;
====How Can I tell if the power supply is inadequate?====&lt;br /&gt;
&lt;br /&gt;
* Check the power level on the board. TP2 is 0V and TP1 is 5V so a meter across these points should register between 4.75V and 5.25V. If the voltage is less than this OR changes as the activity of the device changes then there may be problems.&lt;br /&gt;
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.&lt;br /&gt;
* SD card errors at atart up seems to be another symptom of poor power.&lt;br /&gt;
&lt;br /&gt;
====Things that can cause problems====&lt;br /&gt;
* A USB connection on a TV or PC. The USB power supply specification is for up to 500mA and if the TV implements this then it can cause problems.  The system may work initially but be unreliable because as it becomes more active the power requirement increases.&lt;br /&gt;
* A single supply from a powered hub.  Most hubs seem to deliver more than the specified current but there's no guarantee.  Check the power supply rating, it must be enough to supply everything that's connected to the hub.&lt;br /&gt;
* A power supply that is rated for less than 700mA may work some of the time.&lt;br /&gt;
* Adding a USB hard disk drive. A HDD will take quite a lot of power as it starts, maybe an amp or more. It the power supply for this also supplies the Pi then this could overload things and cause trouble.&lt;br /&gt;
* Some complex keyboards have been reported to take a considerable amount of power, maybe up to 500mA.  The Pi cannot deliver this amount of power.  Simpler budget keyboards may be better. If the system works with no keyboard attached but not with a keyboard then it's worth trying a different, simpler, keyboard.&lt;br /&gt;
&lt;br /&gt;
====Summary====&lt;br /&gt;
&lt;br /&gt;
* If you are having unreliable operation the first thing to do is check your power supply.&lt;br /&gt;
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A.&lt;br /&gt;
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.&lt;br /&gt;
* Not all power supplies will deliver what they claim.&lt;br /&gt;
&lt;br /&gt;
==References==&lt;br /&gt;
&amp;lt;references/&amp;gt;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_schematic_errata</id>
		<title>RPi schematic errata</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_schematic_errata"/>
				<updated>2012-04-20T07:58:26Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: Created page with &amp;quot;Category: RaspberryPi  Back to RPi_Hardware#Components   = Raspberry Pi schematic errata =  The (partial) datasheet was published here: [http://www.raspberrypi.org/wp-con...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category: RaspberryPi]]&lt;br /&gt;
&lt;br /&gt;
Back to [[RPi_Hardware#Components]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
= Raspberry Pi schematic errata =&lt;br /&gt;
&lt;br /&gt;
The (partial) datasheet was published here: [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf| at raspberrypi.org] and [http://dmkenr5gtnd8f.cloudfront.net/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf| a mirror]&lt;br /&gt;
&lt;br /&gt;
It has a couple of typos. Some more serious than others. &lt;br /&gt;
&lt;br /&gt;
Let's gather those schematic typos and errors here. &lt;br /&gt;
&lt;br /&gt;
The quality of the schematic is high. It looks like it contains the information that designers need. &lt;br /&gt;
&lt;br /&gt;
==Schematic v1.0 (Model B)==&lt;br /&gt;
&lt;br /&gt;
===Unverified typos===&lt;br /&gt;
&lt;br /&gt;
* On sheet 3, area C9, should that not be a (B) instead of (A) under the “IC3?”&lt;br /&gt;
* Also D10 close by&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	<entry>
		<id>http://elinux.org/RPi_Hub</id>
		<title>RPi Hub</title>
		<link rel="alternate" type="text/html" href="http://elinux.org/RPi_Hub"/>
				<updated>2012-04-09T14:25:00Z</updated>
		
		<summary type="html">&lt;p&gt;Md84419: /* About */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{TOC right}}{{Template:Hub_Flags}} &amp;lt;!-- please edit template to alter banner and flag display on all hubs --&amp;gt;&lt;br /&gt;
{{Clear}}&lt;br /&gt;
==Launched==&lt;br /&gt;
[[File:RPiLaunch.PNG‎|left|Raspberry Pi Launched]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
See the [[RPi Buying Guide | Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]&lt;br /&gt;
&lt;br /&gt;
==About==&lt;br /&gt;
[[File:RpiFront.jpg|300px|thumb|right|The Rpi beta board (model B)]]&lt;br /&gt;
&lt;br /&gt;
'''The Raspberry Pi wiki pages on this site are a community work - the Raspberry Pi Foundation is not responsible for content on these pages.'''&lt;br /&gt;
&lt;br /&gt;
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. We expect this computer to have many other applications both in the developed and the developing world.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
* 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.&lt;br /&gt;
* Products are RoHS, CE, FCC, CTick and CSA compliant (as of 9th April 2012, the Foundation has to complete some paperwork relating to the last four, and the Distributors need to complete som particulate testing for the first)&amp;lt;ref&amp;gt;http://www.raspberrypi.org/archives/978#comment-19099&amp;lt;/ref&amp;gt;.  Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.&lt;br /&gt;
* Expected cost: ~16GBP or 25USD Model A, ~23GBP or 35USD for Model B. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].&lt;br /&gt;
&lt;br /&gt;
===History===&lt;br /&gt;
* Confused about seeing different versions of the board? Visit the [[Rpi HardwareHistory | History of the Raspberry Pi Hardware]] for information about the past versions.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
* 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].&lt;br /&gt;
&lt;br /&gt;
==Getting Started==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
===[[Buying RPi |Buying Guide]]===&lt;br /&gt;
----&lt;br /&gt;
Where can I get one and for how much?&lt;br /&gt;
* Raspberry Pi can only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.&lt;br /&gt;
&lt;br /&gt;
* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop].&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Hardware Basic Setup | Basic Setup]]===&lt;br /&gt;
----&lt;br /&gt;
First little Raspberry Pi Steps...&lt;br /&gt;
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.&lt;br /&gt;
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.&lt;br /&gt;
* Prepare your SD card with the [http://www.raspberrypi.org/archives/805 Pi Fedora Remix Operating System] - more details see [http://zenit.senecac.on.ca/wiki/index.php/Raspberry_Pi_Fedora_Remix Fedora's Raspberry Pi wiki].&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Beginners | Beginners Guide]]===&lt;br /&gt;
----&lt;br /&gt;
You've just got your new Raspberry Pi device - what now?&lt;br /&gt;
* [[RPi Beginners | Beginners Guide]]&lt;br /&gt;
&lt;br /&gt;
* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.&lt;br /&gt;
&lt;br /&gt;
* Get started with some basic projects and tutorials:&lt;br /&gt;
 Example projects/tuts which can be linked from here&lt;br /&gt;
 (or from within a beginners guide page perhaps):&lt;br /&gt;
  Setup XBMC media centre&lt;br /&gt;
  Programming tutorials (Liams YouTube etc)&lt;br /&gt;
  Easy GPIO (when complete or similar thing).&lt;br /&gt;
  Also links to some basic linux user guides.&lt;br /&gt;
&lt;br /&gt;
* 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.&lt;br /&gt;
&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Resources==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Hardware|Hardware]] &amp;amp; [[RPi VerifiedPeripherals|Peripherals]]===&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
*The Model B is more advanced than the Model A - see [[RPi Hardware]].&lt;br /&gt;
*The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].&lt;br /&gt;
*The unit will support a range of [[RPi VerifiedPeripherals |USB devices, peripherals and accessories]].&lt;br /&gt;
*The [[Rpi Low-level peripherals| Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.&lt;br /&gt;
*For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[Rpi_Software|Software]] &amp;amp; [[RPi_Distributions|OS Distributions]]===&lt;br /&gt;
----&lt;br /&gt;
The Raspberry Pi will run a range of OS Distributions and run a variety of software.&lt;br /&gt;
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.&lt;br /&gt;
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/PARM PARM] from Puppy.&lt;br /&gt;
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]] or [[RPi_Performance|test the Pi's performance]].&lt;br /&gt;
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
===[[RPi Documentation|Documentation]]===&lt;br /&gt;
----&lt;br /&gt;
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].&lt;br /&gt;
&lt;br /&gt;
[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]&lt;br /&gt;
&lt;br /&gt;
 Example documents which can be linked from here (or sub page):&lt;br /&gt;
  Official Datasheets&lt;br /&gt;
  White Papers&lt;br /&gt;
  User Manuals&lt;br /&gt;
  Recommended books (perhaps)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==Community==&lt;br /&gt;
{| border=&amp;quot;1&amp;quot; style=&amp;quot;background:transparent;&amp;quot;&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[RPi Projects |Projects]], [[RPi Guides |Guides]] &amp;amp; [[RPi Tutorials |Tutorials]]===&lt;br /&gt;
----&lt;br /&gt;
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].&lt;br /&gt;
*Knowledgeable users may want to review and help out with the [[RPi Tasks |Tasks page]].&lt;br /&gt;
*Get started by following some of the many [[RPi Tutorials | Tutorials]].&lt;br /&gt;
*Common tasks and useful tip are available through the [[RPi Guides | Guides page]]. &lt;br /&gt;
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
&lt;br /&gt;
===[[Rpi Education|Schools, Universities, Clubs &amp;amp; Groups]]===&lt;br /&gt;
----&lt;br /&gt;
*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.&lt;br /&gt;
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;&amp;quot; |&lt;br /&gt;
===[[RPi Community |Supporting Communities]]===&lt;br /&gt;
----&lt;br /&gt;
The [[RPi Community |Raspberry Pi Community]] is steadily growing: &lt;br /&gt;
*[http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]&lt;br /&gt;
&lt;br /&gt;
*[http://www.frambozenbier.org/index.php/raspi-forum 'Frambozenbier' (Raspberry Pi Homebrew)]&lt;br /&gt;
&lt;br /&gt;
*[http://www.raspberrymod.com/ Raspberrymod] and [http://www.raspberrypiforums.com/forum RPiforums] Un-Official Raspberry Pi Discussion Boards&lt;br /&gt;
&lt;br /&gt;
*[http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]&lt;br /&gt;
&lt;br /&gt;
*[http://www.worldofpi/com/ World Of Pi] A forum based on all things Raspberry Pi.&lt;br /&gt;
&lt;br /&gt;
*[[RPi Community Magazine]] - User contributed eMagazine, get involved!&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
==About the RPi Wiki==&lt;br /&gt;
&lt;br /&gt;
'''Do not be afraid to add your bit, content is vital for the wiki to function.'''&lt;br /&gt;
&lt;br /&gt;
[[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]]]&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
=== Translations ===&lt;br /&gt;
&lt;br /&gt;
The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:&lt;br /&gt;
&lt;br /&gt;
* English: [[R-Pi Hub]]&lt;br /&gt;
* French: [[FR:R-Pi Hub]]&lt;br /&gt;
* German: [[DE:R-Pi Hub]]&lt;br /&gt;
* Greek: [[EL:R-Pi Hub]]&lt;br /&gt;
* Hungarian: [[HU:R-Pi Hub]]&lt;br /&gt;
* Japanese: [[JP:R-Pi_Hub]]&lt;br /&gt;
* Polish: [[PL:R-Pi_Hub]]&lt;br /&gt;
* Portugese: [[pt-BR:Raspberry Pi Board]]&lt;br /&gt;
* Romanian: [[RO:R-Pi_Hub]]&lt;br /&gt;
* Russian: [[RU:RaspberryPiBoard]]&lt;br /&gt;
* Spanish: [[ES:R-Pi Hub]]&lt;br /&gt;
* Italiano: [[IT:R-Pi Hub]]&lt;br /&gt;
* Chinese:[[CH:R-Pi Hub]]&lt;br /&gt;
&lt;br /&gt;
Any help translating would be greatly appreciated. Thank you to those who have already contributed!&lt;br /&gt;
&lt;br /&gt;
===Admins/Contributors===&lt;br /&gt;
&lt;br /&gt;
Please see the [[Talk:R-Pi_Hub]] page for outstanding issues and discussions regarding the RPi Hub and related pages.&lt;br /&gt;
Also , have look at [[RPi Wiki Best Practice]]. Discuss it [[Talk:RPi Wiki Best Practice | here ]]&lt;br /&gt;
&lt;br /&gt;
To share your thoughts, comments, thanks and interesting articles, see our [[RPi Visitor Book |Visitor Book]].&lt;br /&gt;
&lt;br /&gt;
''Big thanks to elinux.org and their groups for the wiki space and content from which these pages have been grown.''&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
{{Template:Raspberry Pi}}&lt;br /&gt;
[[Category:RaspberryPi]]&lt;/div&gt;</summary>
		<author><name>Md84419</name></author>	</entry>

	</feed>