eLinux.org - User contributions [en]

RPi Software

2013-03-12T01:53:08Z

AndrewS: /* GPU bootloaders */ link formatting fix

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

==Overview==

If you just want a working system, all that is required is a correctly formatted SD card. For details on how to create or get one, please see the [[RPi_Hardware_Basic_Setup#Prepared_Operating_System_SD_Card|Hardware Basic Setup]] page.

In order to understand the software compoonents in the RPi, you should first understand how it boots up. At power-up, the CPU is offline, and a small RISC core on the GPU is responsible for booting the SoC, therefore most of the boot components are actually run on the GPU code, not the CPU.

The boot order and components are as follows:
* '''First stage bootloader''' - This is used to mount the FAT32 boot partition on the SD card so that the second stage bootloader can be accessed. It is programmed into the SoC itself during manufacture of the RPi and cannot be reprogrammed by a user.
* '''Second stage bootloader''' (bootcode.bin) - This is used to retrieve the GPU firmware from the SD card, program the firmware, then start the GPU.
* '''GPU firmware''' (start.elf) - Once loaded, this allows the GPU to start up the CPU. An additional file, fixup.dat, is used to configure the SDRAM partition between the GPU and the CPU. At this point, the CPU is release from reset and execution is transferred over.
* '''User code''' - This can be one of any number of binaries. By default, it is the Linux kernel (usually named kernel.img), but it can also be another bootloader (e.g. U-Boot), or a bare-bones application.

Prior to 19th October 2012, there was previously also a third stage bootloader (loader.bin) but this is no longer required. <ref>https://github.com/raspberrypi/firmware/commit/c57ea9dd367f12bf4fb41b7b86806a2dc6281176</ref>

Raspbian Linux image (others?) available on the foundation's website ([http://www.raspberrypi.org/downloads]) also contains cut-down versions of the above files (fixup_cd.dat, start_cd.elf). These are used when GPU memory is set to 16 MB, which in result disables some GPU features. More info [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=198420#p198420 here]. In addition, there are also testing versions of the above files (fixup_x.dat, start_x.elf), which enable potentially unstable/not-fully-tested/hacky functionality - currently, using these files instead of the usual fixup.dat/start.elf will cause extra video codecs to become available.

Because of this boot process, use of an SD card to boot the RPi is mandatory. This does however mean that you cannot 'brick' the device.

==GPU bootloaders==

Currently all of the GPU software and firmware is supplied in binary format. For Raspbian the latest stable release is included in the image and can be updated with apt-get (see the [[Add_software|adding software page]]). The latest bleeding edge version can be downloaded from the [https://github.com/raspberrypi/firmware/tree/master/boot RPI firmware section on GitHub]. At this time, the source code is not available.

[https://github.com/Hexxeh/rpi-update rpi-update] is also available as an easier way of updating the firmware and kernel. Please note, as this firmware is bleeding edge, it really should only be used by advanced users and could potentially still have bugs and be incompatible with existing images.

==Distributions==
''Main page: [[RPi_Distributions|Distributions]]''

SD card images of a number of pre-built distributions including Raspbian (the RPi official distribution based on Debian), Arch Linux ARM, and RISC OS are available from the [http://www.raspberrypi.org/downloads Raspberry Pi foundation website]. Pre-loaded SD cards are also available from [http://thepihut.com/collections/sd-cards The Pi Hut].

Raspbian is the recommended distribution.

==Kernel==
''Main page: [[RPi_Kernel_Compilation|RPi Kernel Compilation]]''

The kernel is sources can be obtained from the [https://github.com/raspberrypi/linux RPI linux section on GitHub]

==Compiler==

The Broadcom processor on Raspberry Pi contains an ARM v6 general purpose processor and a Broadcom VideoCore IV GPU. No data is currently available on other cores (if any) available in the BCM2835.

===ARM===

There is broad compiler support for the ARM processor including GCC - please see [[ARMCompilers|ARM Compilers]].
There are also a number of cross-compiler toolchains - please see [[Toolchains|toolchains]].

The gcc compiler flags which will produce the most optimal code for the RPi are:
<pre>-Ofast -mfpu=vfp -mfloat-abi=hard -march=armv6zk -mtune=arm1176jzf-s</pre>
<tt>-Ofast</tt> may produce compile errors for some programs. In this case, <tt>-O3</tt> or <tt>-O2</tt> should be used instead.
Note that <tt>-mcpu=arm1176jzf-s</tt> can be used in place of <tt>-march=armv6zk -mtune=arm1176jzf-s</tt>.

If you want to generate a relatively up-to-date compiler that uses the optimal flags by default, you can roll your own version of Linaro GCC - see [[RPi_Linaro_GCC_Compilation|RPi Linaro GCC Compilation]].

===GPU===
The GPU provides APIs for Open GL ES 2.0, hardware-accelerated OpenVG, and 1080p30 H.264 high-profile decode.

The GPU is capable of 1Gpixel/s, 1.5Gtexel/s or 24 GFLOPs of general purpose compute and features a bunch of texture filtering and DMA infrastructure - the Raspberry Pi team are looking at how they can make this available to application programmers. For the documentation on some Broadcom APIs exposed to control the GPU, see [[RPi VideoCore APIs]].

The GPU blob is an 18MB elf file, including libraries. It does an awful lot. <ref>http://www.raspberrypi.org/?page_id=43&mingleforumaction=viewtopic&t=247</ref>

===DSP===

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).

==Performance==

A large number of benchmark results are available on the [[RaspberryPiPerformance|performance page]].

==Programming==
A number of development environments are available depending on which language you are writing - see the [[RPi_Programming|programming]] page.

==Emulation==
The ARM processor on the RPi can be emulated using QEMU. See [http://cronicasredux.blogspot.co.uk/2011/09/installing-and-running-debian-armel-on.html emercer's tutorial], and also [http://www.raspberrypi.org/forum/projects-and-collaboration-general/emulating-a-raspi-on-windows this discussion].

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Bugs

2013-03-12T00:40:42Z

AndrewS: /* Hardware */ changed link formatting

[[Category: Linux]]
[[Category:ARM Development Boards]]
[[Category: Broadcom]]
[[Category: Development Boards]]
[[Category: RaspberryPi]]
[[Category: Education]]

See [[R-Pi_Troubleshooting]] for problems that are not bugs.

= Hardware =
* The current R-Pi firmware limits users to 2 hubs and 14 ports.
* Some Hardware is unsupported [[RPi_VerifiedPeripherals|link]]
* The sound output port on boards version 1.0 and 2.0 are miss-wired causing distortion and a DC offset which could damage certain types of DC-coupled amplifiers and even loudspeakers. It is recommended that you use the HDMI or I2S functionality. If you need to use this port, make sure that the equipment you use has a DC blocking capacitor. The specific problem is that the surge suppression network, which should come between the SoC and the DC blocking capacitor comes AFTER the capacitor, creating a rectification effect of the signal, causing a DC offset and distortion. The design fix is simple, move the DC blocking capacitor after the surge suppressing diodes and then add a 100k resistor (470k, or even up to 1M is fine too) to ground. A series 100 ohm resistor just before the jack might also help suppress unwanted RF interference. If high quality output is required from existing boards, it is necessary to remove parts D12 and D13 from the back of the board. The three pads should be VCC, signal and GND respectively, identify each pad and carefully install some resistor between 10k and 100k between the signal and GND, making sure not to short out VCC. This is fairly high-end SMD re-work, I would suggest you get some training, tools and practice before attempting. (ed note: the writer of this comment does not have said skills, only knows what would have to be done).

= Software =
(excluding [[RPi_Distributions | non-official distribution]] specific bugs)

== OS ==
* [http://www.debian.org/Bugs/ debian]
* [https://bugs.launchpad.net/raspbian raspbian]

== Kernel ==
* tracked on [https://github.com/raspberrypi/linux/issues github]

== Firmware ==
* tracked on [https://github.com/raspberrypi/firmware/issues github]
* 73 threads on [https://www.google.ca/#hl=en&q=site%3Ahttp%3A%2F%2Fwww.raspberrypi.org%2FphpBB3+%22kevent+2+may+have+been+dropped%22 kevent 2 may have been dropped] (possible [http://www.raspberrypi.org/phpBB3/viewtopic.php?p=99463#p99463 solution])
* 55 threads on [https://www.google.ca/#hl=en&q=site%3Ahttp%3A%2F%2Fwww.raspberrypi.org%2FphpBB3+%22error+-71%22 error -71] (see the [[Rpi_USB_check-list]])

{{Template:Raspberry Pi}}

RPi HardwareHistory

2013-03-11T19:37:59Z

AndrewS: /* Raspberry Pi USB Prototype Board */ Added name to the "USB Prototype Board"

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

==Board Revision History==
Find out your board revision with the following command:
cat /proc/cpuinfo
You will see your device data including:
Hardware : BCM2708
Revision : 0003

If you see a "1000" at the front of the Revision, e.g. 10000002 then it indicates<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=32&t=18133#p181069</ref> that your Raspberry Pi has been [[RPiconfig#Overclocking|over-volted]], and your board revision is simply the last 4 digits (i.e. 0002 in this example).





{| border="1"
! Revision
! Release Date
! Model
! PCB Revision
! Memory
! Notes

|-
| Beta
| Q1 2012
| B (Beta)
| ?
| 256MB
| Beta Board
|-
| 0002
| Q1 2012
| B
| 1.0
| 256MB
|
|-
| 0003
| Q3 2012
| B (ECN0001)
| 1.0
| 256MB
| Fuses mod and D14 removed
|-
| 0004
| Q3 2012
| B
| 2.0
| 256MB
| (Mfg by Sony)
|-
| 0005
| Q4 2012
| B
| 2.0
| 256MB
| (Mfg by Qisda)
|-
| 0006
| Q4 2012
| B
| 2.0
| 256MB
| (Mfg by Egoman)
|-
| 0007
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Egoman)
|-
| 0008
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Sony)
|-
| 0009
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Qisda)
|-
| 000d
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Egoman)
|-
| 000e
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Sony)
|-
| 000f
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Qisda)
|}

===ECN0001===
ECN0001 is the request to not fit D14 and replace F1 and F2 with 0 ohm.

====D14 Removal====
D14 can interfere with some CEC devices if the Pi is left plugged in and unpowered. The benefits of having it are minimal so it was removed.<ref name="D14">[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=16365 New Pi missing D14]</ref>

====F1 & F2 Replacement/Removal====
F1 & F2 can cause problems with some USB devices which draw high current. In particular due to the recovery characteristics of the Poly-fuses, it can take a while to recover their low resistance state afterwards, adding
additional problems for other devices (lower voltage on the USB bus).

===Model B Revision 2.0===
Based on a new PCB layout that includes previous build fixes from ECN0001 such us removal of the poly-fuses in series with the +5V power for USB devices, and other fixes reported by the community such as the erroneous connection of the LAN9512 VDD18CORE pins to the +1V8 power plane, addition of the 8-pin P5 header (non-populated) for extra GPIO pins, addition to the 2-pin P6 header (non-populated) for a RESET button, and other changes and improvements reported in more detail <ref name="REV2.0">[http://www.raspberrypi.org/archives/1929 Upcoming Board Revision]</ref>.

===Colour Variations===
The vast majority of the Raspberry Pis produced have a <b><span style="color:green">Green</span></b> PCB, but Pis produced by [[RPi_Buying_Guide#Egoman_Technology_Corp|Egoman_Technology_Corp]] (only available in the Far East) have a <b><span style="color:red">Red</span></b><ref>http://www.raspberrypi.org/archives/3195</ref> PCB, and RS Components produced a limited edition of anniversary Pis in <b><span style="color:blue">Blue</span></b><ref>http://www.raspberrypi.org/archives/3422</ref>.

==Raspberry Pi Model-A Full Production Board ==
* As of Feb 2013, available from distributors in Europe but not North America
* Board has 256Mb of RAM rather than the originally planned 128Mb<ref name="postSale">[http://www.raspberrypi.org/archives/723 Post-Launch - And breathe…]</ref>
* The Foundation produced a small Beta batch before handing manufacturing over to RS and Farnell
* The ModelA boards actually use the identical Revision2.0 PCB as ModelB boards, just with a different selection of components fitted (full details available from the [[RPi_Hardware#Schematic_.2F_Layout|schematics]]). AFAIK no ModelA boards using the Revision1.0 PCBs were ever publicly available (or indeed ever made?).

==Raspberry Pi Model-B Full Production Board ==
[[File:RaspiFront.JPG|250px|thumb|right|The Rpi full production board (model B Rev 2.0)]]
* Announced: April 2012, first orders sent out June 2012.
* Manufacturing and Orders will be made through RS and Farnell
* This means a much higher volume of units will be produced and made available.
* Additional detail is available about the manufacturing and distribution agreement here [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)].
* Announced: September 2012, Raspberry Pi Model B Rev 2.0 is now manufactured at Sony's manufacturing plant on Pencoed, South Wales. [http://www.raspberrypi.org/archives/1925 Full announcement from the Raspberry Pi Foundation], [http://www.element14.com/community/thread/19738?tstart=0 Element14 announcement on Raspberry Pi discussion board].

==Raspberry Pi 1st Production Board ==
* Announced: 29th Feb 2012 - Start of Sale Only<ref name="postSale"/>
* Credit-card Format
* Initial 10k Batch (All Model-B's) Manufactured in China (Jan/Feb 2012)<ref name="firstProduction" >[http://www.raspberrypi.org/archives/509 We’ve started manufacture!]</ref>
* Should look identical to the Raspberry Pi Beta Board below (except different SDCard holder).
* The board has a yellow RCA connector, rather than the black one used in the Beta's.
* Nokia/Qt Development group has donated vouchers for 400 RPi units for developers<ref name="nokiaDonate">[http://www.raspberrypi.org/archives/369 Nokia has Raspberry Pi vouchers for 400 Qt developers]</ref>
* The batch was delayed several weeks due to the RJ45 network connector being substituted for the wrong part<ref>[http://www.raspberrypi.org/archives/781 Manufacturing Hiccup]</ref> and also so the board could undergo compliance testing<ref>[http://www.raspberrypi.org/archives/852 Compliance testing]</ref>

==Raspberry Pi Beta Production Board ==
* Announced: December 2011<ref name="#Beta">[http://www.raspberrypi.org/archives/422 Populated boards: an update on where we are]</ref>
* Credit-Card Format
* Manufactured in UK
* Produced 100<ref name="betapcb">[http://www.raspberrypi.org/archives/389 We have PCBs! BETA]</ref> PCBs
* Characteristic feature of hand-modded correction to PCB <ref name="betaError">[http://www.raspberrypi.org/archives/470 (hand-mod) More on the beta boards]</ref>
* See the [http://www.raspberrypi.org/archives/482 blog post] which includes a video explaining how the production units will differ from the beta boards.

* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-002-copy2-e1322775411416.jpg Pre-production board (beta board) PCB, topside]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-003-copy2.jpg Pre-production board (beta board) PCB, underside]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-001-copy.jpg Pre-production board vs credit-card]

===eBay Auction===
10 of the completed Model-B boards were auctioned on eBay (Started on 1st Jan 2012) <ref name="betaebay">[http://www.raspberrypi.org/archives/482 We’re auctioning ten beta Raspberry Pis!]</ref>)
{| border="1"
|SerialNo:
|#1
|#2
|#3
|#4
|#5
|#6
|#7<ref name="#7Donated"/>
|#8<ref name="#8PaulMaunders"/>
|#9
|#10
|-
|Date:
|11-Jan-2012
|11-Jan-2012
|10-Jan-2012
|10-Jan-2012
|09-Jan-2012
|09-Jan-2012
|08-Jan-2012
|08-Jan-2012
|07-Jan-2012
|07-Jan-2012
|-
|Sold For:
|£3,500
|£2,150
|£2,257
|£1,550
|£1,040
|£1,000
|£989
|£1,020
|£930
|£1,900
|}
Board #7 was anonymously (and generously) donated to [http://www.computinghistory.org.uk/ Centre for Computing History]<ref name="#7Donated">[http://www.raspberrypi.org/archives/503 Beta board bought by anonymous bidder and donated to museum]</ref> (also spotted [http://twitpic.com/86trra here..])!

Board #8 Owned by Tech Blogger, Paul Maunders, see his [http://www.pyrosoft.co.uk/blog blog] for details<ref name="#8PaulMaunders">[http://www.pyrosoft.co.uk/blog/2012/01/13/raspberry-pi-8-first-photoshoot/ Paul Maunders - Raspberry Pi #8 First Photoshoot]</ref>

==Raspberry Pi Alpha Board ==
[[File:RPi-alpha.jpg|250px|thumb|right|RPi Alpha Board]]

* Announced: August 2011<ref name="#Alpha">[http://www.raspberrypi.org/archives/78 The alpha boards are here!]</ref>
* Large Format for debugging (Model-B)
* Populated with headers for GPIO, JTAG, DSI, CSI, as well as switches and LEDs for I/O testing.

* [http://www.raspberrypi.org/wp-content/uploads/2011/08/DSCF1809.jpg Alpha prototype board, underside]

==Raspberry Pi USB Prototype Board ==
[[File:Rpi-usbproto.jpg|250px|thumb|right|RPi USB Prototype Board]]
* Announced: May 2011
* The "Computer On A USB Stick" Format
* Included built-in camera
* HDMI one end and single USB the other
* Introduced the RPi Foundation to the world (any earlier links appreciated), featured by [http://www.bbc.co.uk/news/technology-13292450 BBC Online Video].
* Known internally at Broadcom as the <b>MicroDB</b> <ref>http://www.raspberrypi.org/archives/3375</ref> <ref>http://www.raspberrypi.org/archives/3376</ref>

‎

==Raspberry Pi Concept 2006 edition==
[[File:RPi-atmel2006Ed.jpg|250px|thumb|right|Raspberry Pi Concept 2006 edition]]
* Vero-board Prototype & PCB Version
* Atmel ATmega644 microcontroller clocked at 22.1MHz<ref name="2006ed">[http://www.raspberrypi.org/archives/264 Raspberry Pi – 2006 edition]</ref>

==See Also==
===Video===
* [http://news.bbc.co.uk/1/hi/programmes/click_online/9504208.stm BBC iClick's Peter Price asks whether a £15 computer can solve the programming gap] (6 minutes, 3 June 2011)
* [http://www.youtube.com/watch?v=pQ7N4rycsy4 Raspberry Pi's David Braben talks to BBC's Rory Cellan-Jones] (2:28 minutes, 5 May 2011)
* [http://www.youtube.com/RaspberryPiTutorials Raspberry Pi community tutorials on YouTube]

===Audio===
* [http://foundationlibraries.blogspot.com/2011/06/cfl-podcast-eben-upton-raspberry-pi.html Podcast of a phone interview with Eben about the project and the motivations behind it] (15 minutes long.) (3 June 2011) Transcription [http://tomhannen.posterous.com/raspberry-pi-podcast-transcript here].

==References==
<references/>

{{Template:Raspberry Pi}}

RPi HardwareHistory

2013-03-11T19:10:59Z

AndrewS: /* Board Revision History */ Added note about the over-volt bit in the Revision field

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

==Board Revision History==
Find out your board revision with the following command:
cat /proc/cpuinfo
You will see your device data including:
Hardware : BCM2708
Revision : 0003

If you see a "1000" at the front of the Revision, e.g. 10000002 then it indicates<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=32&t=18133#p181069</ref> that your Raspberry Pi has been [[RPiconfig#Overclocking|over-volted]], and your board revision is simply the last 4 digits (i.e. 0002 in this example).





{| border="1"
! Revision
! Release Date
! Model
! PCB Revision
! Memory
! Notes

|-
| Beta
| Q1 2012
| B (Beta)
| ?
| 256MB
| Beta Board
|-
| 0002
| Q1 2012
| B
| 1.0
| 256MB
|
|-
| 0003
| Q3 2012
| B (ECN0001)
| 1.0
| 256MB
| Fuses mod and D14 removed
|-
| 0004
| Q3 2012
| B
| 2.0
| 256MB
| (Mfg by Sony)
|-
| 0005
| Q4 2012
| B
| 2.0
| 256MB
| (Mfg by Qisda)
|-
| 0006
| Q4 2012
| B
| 2.0
| 256MB
| (Mfg by Egoman)
|-
| 0007
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Egoman)
|-
| 0008
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Sony)
|-
| 0009
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Qisda)
|-
| 000d
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Egoman)
|-
| 000e
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Sony)
|-
| 000f
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Qisda)
|}

===ECN0001===
ECN0001 is the request to not fit D14 and replace F1 and F2 with 0 ohm.

====D14 Removal====
D14 can interfere with some CEC devices if the Pi is left plugged in and unpowered. The benefits of having it are minimal so it was removed.<ref name="D14">[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=16365 New Pi missing D14]</ref>

====F1 & F2 Replacement/Removal====
F1 & F2 can cause problems with some USB devices which draw high current. In particular due to the recovery characteristics of the Poly-fuses, it can take a while to recover their low resistance state afterwards, adding
additional problems for other devices (lower voltage on the USB bus).

===Model B Revision 2.0===
Based on a new PCB layout that includes previous build fixes from ECN0001 such us removal of the poly-fuses in series with the +5V power for USB devices, and other fixes reported by the community such as the erroneous connection of the LAN9512 VDD18CORE pins to the +1V8 power plane, addition of the 8-pin P5 header (non-populated) for extra GPIO pins, addition to the 2-pin P6 header (non-populated) for a RESET button, and other changes and improvements reported in more detail <ref name="REV2.0">[http://www.raspberrypi.org/archives/1929 Upcoming Board Revision]</ref>.

===Colour Variations===
The vast majority of the Raspberry Pis produced have a <b><span style="color:green">Green</span></b> PCB, but Pis produced by [[RPi_Buying_Guide#Egoman_Technology_Corp|Egoman_Technology_Corp]] (only available in the Far East) have a <b><span style="color:red">Red</span></b><ref>http://www.raspberrypi.org/archives/3195</ref> PCB, and RS Components produced a limited edition of anniversary Pis in <b><span style="color:blue">Blue</span></b><ref>http://www.raspberrypi.org/archives/3422</ref>.

==Raspberry Pi Model-A Full Production Board ==
* As of Feb 2013, available from distributors in Europe but not North America
* Board has 256Mb of RAM rather than the originally planned 128Mb<ref name="postSale">[http://www.raspberrypi.org/archives/723 Post-Launch - And breathe…]</ref>
* The Foundation produced a small Beta batch before handing manufacturing over to RS and Farnell
* The ModelA boards actually use the identical Revision2.0 PCB as ModelB boards, just with a different selection of components fitted (full details available from the [[RPi_Hardware#Schematic_.2F_Layout|schematics]]). AFAIK no ModelA boards using the Revision1.0 PCBs were ever publicly available (or indeed ever made?).

==Raspberry Pi Model-B Full Production Board ==
[[File:RaspiFront.JPG|250px|thumb|right|The Rpi full production board (model B Rev 2.0)]]
* Announced: April 2012, first orders sent out June 2012.
* Manufacturing and Orders will be made through RS and Farnell
* This means a much higher volume of units will be produced and made available.
* Additional detail is available about the manufacturing and distribution agreement here [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)].
* Announced: September 2012, Raspberry Pi Model B Rev 2.0 is now manufactured at Sony's manufacturing plant on Pencoed, South Wales. [http://www.raspberrypi.org/archives/1925 Full announcement from the Raspberry Pi Foundation], [http://www.element14.com/community/thread/19738?tstart=0 Element14 announcement on Raspberry Pi discussion board].

==Raspberry Pi 1st Production Board ==
* Announced: 29th Feb 2012 - Start of Sale Only<ref name="postSale"/>
* Credit-card Format
* Initial 10k Batch (All Model-B's) Manufactured in China (Jan/Feb 2012)<ref name="firstProduction" >[http://www.raspberrypi.org/archives/509 We’ve started manufacture!]</ref>
* Should look identical to the Raspberry Pi Beta Board below (except different SDCard holder).
* The board has a yellow RCA connector, rather than the black one used in the Beta's.
* Nokia/Qt Development group has donated vouchers for 400 RPi units for developers<ref name="nokiaDonate">[http://www.raspberrypi.org/archives/369 Nokia has Raspberry Pi vouchers for 400 Qt developers]</ref>
* The batch was delayed several weeks due to the RJ45 network connector being substituted for the wrong part<ref>[http://www.raspberrypi.org/archives/781 Manufacturing Hiccup]</ref> and also so the board could undergo compliance testing<ref>[http://www.raspberrypi.org/archives/852 Compliance testing]</ref>

==Raspberry Pi Beta Production Board ==
* Announced: December 2011<ref name="#Beta">[http://www.raspberrypi.org/archives/422 Populated boards: an update on where we are]</ref>
* Credit-Card Format
* Manufactured in UK
* Produced 100<ref name="betapcb">[http://www.raspberrypi.org/archives/389 We have PCBs! BETA]</ref> PCBs
* Characteristic feature of hand-modded correction to PCB <ref name="betaError">[http://www.raspberrypi.org/archives/470 (hand-mod) More on the beta boards]</ref>
* See the [http://www.raspberrypi.org/archives/482 blog post] which includes a video explaining how the production units will differ from the beta boards.

* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-002-copy2-e1322775411416.jpg Pre-production board (beta board) PCB, topside]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-003-copy2.jpg Pre-production board (beta board) PCB, underside]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-001-copy.jpg Pre-production board vs credit-card]

===eBay Auction===
10 of the completed Model-B boards were auctioned on eBay (Started on 1st Jan 2012) <ref name="betaebay">[http://www.raspberrypi.org/archives/482 We’re auctioning ten beta Raspberry Pis!]</ref>)
{| border="1"
|SerialNo:
|#1
|#2
|#3
|#4
|#5
|#6
|#7<ref name="#7Donated"/>
|#8<ref name="#8PaulMaunders"/>
|#9
|#10
|-
|Date:
|11-Jan-2012
|11-Jan-2012
|10-Jan-2012
|10-Jan-2012
|09-Jan-2012
|09-Jan-2012
|08-Jan-2012
|08-Jan-2012
|07-Jan-2012
|07-Jan-2012
|-
|Sold For:
|£3,500
|£2,150
|£2,257
|£1,550
|£1,040
|£1,000
|£989
|£1,020
|£930
|£1,900
|}
Board #7 was anonymously (and generously) donated to [http://www.computinghistory.org.uk/ Centre for Computing History]<ref name="#7Donated">[http://www.raspberrypi.org/archives/503 Beta board bought by anonymous bidder and donated to museum]</ref> (also spotted [http://twitpic.com/86trra here..])!

Board #8 Owned by Tech Blogger, Paul Maunders, see his [http://www.pyrosoft.co.uk/blog blog] for details<ref name="#8PaulMaunders">[http://www.pyrosoft.co.uk/blog/2012/01/13/raspberry-pi-8-first-photoshoot/ Paul Maunders - Raspberry Pi #8 First Photoshoot]</ref>

==Raspberry Pi Alpha Board ==
[[File:RPi-alpha.jpg|250px|thumb|right|RPi Alpha Board]]

* Announced: August 2011<ref name="#Alpha">[http://www.raspberrypi.org/archives/78 The alpha boards are here!]</ref>
* Large Format for debugging (Model-B)
* Populated with headers for GPIO, JTAG, DSI, CSI, as well as switches and LEDs for I/O testing.

* [http://www.raspberrypi.org/wp-content/uploads/2011/08/DSCF1809.jpg Alpha prototype board, underside]

==Raspberry Pi USB Prototype Board ==
[[File:Rpi-usbproto.jpg|250px|thumb|right|RPi USB Prototype Board]]
* Announced: May 2011
* The "Computer On A USB Stick" Format
* Included built-in camera
* HDMI one end and single USB the other
* Introduced the RPi Foundation to the world (any earlier links appreciated), featured by [http://www.bbc.co.uk/news/technology-13292450 BBC Online Video].

‎

==Raspberry Pi Concept 2006 edition==
[[File:RPi-atmel2006Ed.jpg|250px|thumb|right|Raspberry Pi Concept 2006 edition]]
* Vero-board Prototype & PCB Version
* Atmel ATmega644 microcontroller clocked at 22.1MHz<ref name="2006ed">[http://www.raspberrypi.org/archives/264 Raspberry Pi – 2006 edition]</ref>

==See Also==
===Video===
* [http://news.bbc.co.uk/1/hi/programmes/click_online/9504208.stm BBC iClick's Peter Price asks whether a £15 computer can solve the programming gap] (6 minutes, 3 June 2011)
* [http://www.youtube.com/watch?v=pQ7N4rycsy4 Raspberry Pi's David Braben talks to BBC's Rory Cellan-Jones] (2:28 minutes, 5 May 2011)
* [http://www.youtube.com/RaspberryPiTutorials Raspberry Pi community tutorials on YouTube]

===Audio===
* [http://foundationlibraries.blogspot.com/2011/06/cfl-podcast-eben-upton-raspberry-pi.html Podcast of a phone interview with Eben about the project and the motivations behind it] (15 minutes long.) (3 June 2011) Transcription [http://tomhannen.posterous.com/raspberry-pi-podcast-transcript here].

==References==
<references/>

{{Template:Raspberry Pi}}

RPi HardwareHistory

2013-03-11T12:20:49Z

AndrewS: Clarified the info regarding the PCB revisions

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

==Board Revision History==
Find out your board revision with the following command:
cat /proc/cpuinfo
You will see your device data including:
Hardware : BCM2708
Revision : 0003





{| border="1"
! Revision
! Release Date
! Model
! PCB Revision
! Memory
! Notes

|-
| Beta
| Q1 2012
| B (Beta)
| ?
| 256MB
| Beta Board
|-
| 0002
| Q1 2012
| B
| 1.0
| 256MB
|
|-
| 0003
| Q3 2012
| B (ECN0001)
| 1.0
| 256MB
| Fuses mod and D14 removed
|-
| 0004
| Q3 2012
| B
| 2.0
| 256MB
| (Mfg by Sony)
|-
| 0005
| Q4 2012
| B
| 2.0
| 256MB
| (Mfg by Qisda)
|-
| 0006
| Q4 2012
| B
| 2.0
| 256MB
| (Mfg by Egoman)
|-
| 0007
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Egoman)
|-
| 0008
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Sony)
|-
| 0009
| Q1 2013
| A
| 2.0
| 256MB
| (Mfg by Qisda)
|-
| 000d
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Egoman)
|-
| 000e
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Sony)
|-
| 000f
| Q4 2012
| B
| 2.0
| 512MB
| (Mfg by Qisda)
|}

===ECN0001===
ECN0001 is the request to not fit D14 and replace F1 and F2 with 0 ohm.

====D14 Removal====
D14 can interfere with some CEC devices if the Pi is left plugged in and unpowered. The benefits of having it are minimal so it was removed.<ref name="D14">[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=16365 New Pi missing D14]</ref>

====F1 & F2 Replacement/Removal====
F1 & F2 can cause problems with some USB devices which draw high current. In particular due to the recovery characteristics of the Poly-fuses, it can take a while to recover their low resistance state afterwards, adding
additional problems for other devices (lower voltage on the USB bus).

===Model B Revision 2.0===
Based on a new PCB layout that includes previous build fixes from ECN0001 such us removal of the poly-fuses in series with the +5V power for USB devices, and other fixes reported by the community such as the erroneous connection of the LAN9512 VDD18CORE pins to the +1V8 power plane, addition of the 8-pin P5 header (non-populated) for extra GPIO pins, addition to the 2-pin P6 header (non-populated) for a RESET button, and other changes and improvements reported in more detail <ref name="REV2.0">[http://www.raspberrypi.org/archives/1929 Upcoming Board Revision]</ref>.

===Colour Variations===
The vast majority of the Raspberry Pis produced have a <b><span style="color:green">Green</span></b> PCB, but all Pis produced by [[RPi_Buying_Guide#Egoman_Technology_Corp|Egoman_Technology_Corp]] (only available in the Far East) have a <b><span style="color:red">Red</span></b><ref>http://www.raspberrypi.org/archives/3195</ref> PCB, and RS Components produced a limited edition of anniversary Pis in <b><span style="color:blue">Blue</span></b><ref>http://www.raspberrypi.org/archives/3422</ref>.

==Raspberry Pi Model-A Full Production Board ==
* As of Feb 2013, available from distributors in Europe but not North America
* Board has 256Mb of RAM rather than the originally planned 128Mb<ref name="postSale">[http://www.raspberrypi.org/archives/723 Post-Launch - And breathe…]</ref>
* The Foundation produced a small Beta batch before handing manufacturing over to RS and Farnell
* The ModelA boards actually use the identical Revision2.0 PCB as ModelB boards, just with a different selection of components fitted (full details available from the [[RPi_Hardware#Schematic_.2F_Layout|schematics]]). AFAIK no ModelA boards using the Revision1.0 PCBs were ever publicly available (or indeed ever made?).

==Raspberry Pi Model-B Full Production Board ==
[[File:RaspiFront.JPG|250px|thumb|right|The Rpi full production board (model B Rev 2.0)]]
* Announced: April 2012, first orders sent out June 2012.
* Manufacturing and Orders will be made through RS and Farnell
* This means a much higher volume of units will be produced and made available.
* Additional detail is available about the manufacturing and distribution agreement here [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)].
* Announced: September 2012, Raspberry Pi Model B Rev 2.0 is now manufactured at Sony's manufacturing plant on Pencoed, South Wales. [http://www.raspberrypi.org/archives/1925 Full announcement from the Raspberry Pi Foundation], [http://www.element14.com/community/thread/19738?tstart=0 Element14 announcement on Raspberry Pi discussion board].

==Raspberry Pi 1st Production Board ==
* Announced: 29th Feb 2012 - Start of Sale Only<ref name="postSale"/>
* Credit-card Format
* Initial 10k Batch (All Model-B's) Manufactured in China (Jan/Feb 2012)<ref name="firstProduction" >[http://www.raspberrypi.org/archives/509 We’ve started manufacture!]</ref>
* Should look identical to the Raspberry Pi Beta Board below (except different SDCard holder).
* The board has a yellow RCA connector, rather than the black one used in the Beta's.
* Nokia/Qt Development group has donated vouchers for 400 RPi units for developers<ref name="nokiaDonate">[http://www.raspberrypi.org/archives/369 Nokia has Raspberry Pi vouchers for 400 Qt developers]</ref>
* The batch was delayed several weeks due to the RJ45 network connector being substituted for the wrong part<ref>[http://www.raspberrypi.org/archives/781 Manufacturing Hiccup]</ref> and also so the board could undergo compliance testing<ref>[http://www.raspberrypi.org/archives/852 Compliance testing]</ref>

==Raspberry Pi Beta Production Board ==
* Announced: December 2011<ref name="#Beta">[http://www.raspberrypi.org/archives/422 Populated boards: an update on where we are]</ref>
* Credit-Card Format
* Manufactured in UK
* Produced 100<ref name="betapcb">[http://www.raspberrypi.org/archives/389 We have PCBs! BETA]</ref> PCBs
* Characteristic feature of hand-modded correction to PCB <ref name="betaError">[http://www.raspberrypi.org/archives/470 (hand-mod) More on the beta boards]</ref>
* See the [http://www.raspberrypi.org/archives/482 blog post] which includes a video explaining how the production units will differ from the beta boards.

* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-002-copy2-e1322775411416.jpg Pre-production board (beta board) PCB, topside]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-003-copy2.jpg Pre-production board (beta board) PCB, underside]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-001-copy.jpg Pre-production board vs credit-card]

===eBay Auction===
10 of the completed Model-B boards were auctioned on eBay (Started on 1st Jan 2012) <ref name="betaebay">[http://www.raspberrypi.org/archives/482 We’re auctioning ten beta Raspberry Pis!]</ref>)
{| border="1"
|SerialNo:
|#1
|#2
|#3
|#4
|#5
|#6
|#7<ref name="#7Donated"/>
|#8<ref name="#8PaulMaunders"/>
|#9
|#10
|-
|Date:
|11-Jan-2012
|11-Jan-2012
|10-Jan-2012
|10-Jan-2012
|09-Jan-2012
|09-Jan-2012
|08-Jan-2012
|08-Jan-2012
|07-Jan-2012
|07-Jan-2012
|-
|Sold For:
|£3,500
|£2,150
|£2,257
|£1,550
|£1,040
|£1,000
|£989
|£1,020
|£930
|£1,900
|}
Board #7 was anonymously (and generously) donated to [http://www.computinghistory.org.uk/ Centre for Computing History]<ref name="#7Donated">[http://www.raspberrypi.org/archives/503 Beta board bought by anonymous bidder and donated to museum]</ref> (also spotted [http://twitpic.com/86trra here..])!

Board #8 Owned by Tech Blogger, Paul Maunders, see his [http://www.pyrosoft.co.uk/blog blog] for details<ref name="#8PaulMaunders">[http://www.pyrosoft.co.uk/blog/2012/01/13/raspberry-pi-8-first-photoshoot/ Paul Maunders - Raspberry Pi #8 First Photoshoot]</ref>

==Raspberry Pi Alpha Board ==
[[File:RPi-alpha.jpg|250px|thumb|right|RPi Alpha Board]]

* Announced: August 2011<ref name="#Alpha">[http://www.raspberrypi.org/archives/78 The alpha boards are here!]</ref>
* Large Format for debugging (Model-B)
* Populated with headers for GPIO, JTAG, DSI, CSI, as well as switches and LEDs for I/O testing.

* [http://www.raspberrypi.org/wp-content/uploads/2011/08/DSCF1809.jpg Alpha prototype board, underside]

==Raspberry Pi USB Prototype Board ==
[[File:Rpi-usbproto.jpg|250px|thumb|right|RPi USB Prototype Board]]
* Announced: May 2011
* The "Computer On A USB Stick" Format
* Included built-in camera
* HDMI one end and single USB the other
* Introduced the RPi Foundation to the world (any earlier links appreciated), featured by [http://www.bbc.co.uk/news/technology-13292450 BBC Online Video].

‎

==Raspberry Pi Concept 2006 edition==
[[File:RPi-atmel2006Ed.jpg|250px|thumb|right|Raspberry Pi Concept 2006 edition]]
* Vero-board Prototype & PCB Version
* Atmel ATmega644 microcontroller clocked at 22.1MHz<ref name="2006ed">[http://www.raspberrypi.org/archives/264 Raspberry Pi – 2006 edition]</ref>

==See Also==
===Video===
* [http://news.bbc.co.uk/1/hi/programmes/click_online/9504208.stm BBC iClick's Peter Price asks whether a £15 computer can solve the programming gap] (6 minutes, 3 June 2011)
* [http://www.youtube.com/watch?v=pQ7N4rycsy4 Raspberry Pi's David Braben talks to BBC's Rory Cellan-Jones] (2:28 minutes, 5 May 2011)
* [http://www.youtube.com/RaspberryPiTutorials Raspberry Pi community tutorials on YouTube]

===Audio===
* [http://foundationlibraries.blogspot.com/2011/06/cfl-podcast-eben-upton-raspberry-pi.html Podcast of a phone interview with Eben about the project and the motivations behind it] (15 minutes long.) (3 June 2011) Transcription [http://tomhannen.posterous.com/raspberry-pi-podcast-transcript here].

==References==
<references/>

{{Template:Raspberry Pi}}

RPi HardwareHistory

2013-03-11T11:48:45Z

AndrewS: /* Board Revision History */ Added details about the Red and Blue Pi boards

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

==Board Revision History==
Find out your board revision with the following command:
cat /proc/cpuinfo
You will see your device data including:
Hardware : BCM2708
Revision : 0003



{| border="1"
! Revision
! Release Date
! Model
! Memory
! Notes

|-
| Beta
| Q1 2012
| B (Beta)
| 256MB
| Beta Board
|-
| 0002
| Q1 2012
| B
| 256MB
|
|-
| 0003
| Q3 2012
| B (ECN0001)
| 256MB
| Fuses mod and D14 removed
|-
| 0004
| Q3 2012
| B 2.0
| 256MB
| (Mfg by Sony)
|-
| 0005
| Q4 2012
| B 2.0
| 256MB
| (Mfg by Qisda)
|-
| 0006
| Q4 2012
| B 2.0
| 256MB
| (Mfg by Egoman)
|-
| 0007
| Q1 2013
| A
| 256MB
| (Mfg by Egoman)
|-
| 0008
| Q1 2013
| A
| 256MB
| (Mfg by Sony)
|-
| 0009
| Q1 2013
| A
| 256MB
| (Mfg by Qisda)
|-
| 000d
| Q4 2012
| B 2.0
| 512MB
| (Mfg by Egoman)
|-
| 000e
| Q4 2012
| B 2.0
| 512MB
| (Mfg by Sony)
|-
| 000f
| Q4 2012
| B 2.0
| 512MB
| (Mfg by Qisda)
|}

===ECN0001===
ECN0001 is the request to not fit D14 and replace F1 and F2 with 0 ohm.

====D14 Removal====
D14 can interfere with some CEC devices if the Pi is left plugged in and unpowered. The benefits of having it are minimal so it was removed.<ref name="D14">[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=63&t=16365 New Pi missing D14]</ref>

====F1 & F2 Replacement/Removal====
F1 & F2 can cause problems with some USB devices which draw high current. In particular due to the recovery characteristics of the Poly-fuses, it can take a while to recover their low resistance state afterwards, adding
additional problems for other devices (lower voltage on the USB bus).

===Model B Revision 2.0===
Based on a new PCB layout that includes previous build fixes from ECN0001 such us removal of the poly-fuses in series with the +5V power for USB devices, and other fixes reported by the community such as the erroneous connection of the LAN9512 VDD18CORE pins to the +1V8 power plane, addition of the 8-pin P5 header (non-populated) for extra GPIO pins, addition to the 2-pin P6 header (non-populated) for a RESET button, and other changes and improvements reported in more detail <ref name="REV2.0">[http://www.raspberrypi.org/archives/1929 Upcoming Board Revision]</ref>.

===Colour Variations===
The vast majority of the Raspberry Pis produced have a <b><span style="color:green">Green</span></b> PCB, but all Pis produced by [[RPi_Buying_Guide#Egoman_Technology_Corp|Egoman_Technology_Corp]] (only available in the Far East) have a <b><span style="color:red">Red</span></b><ref>http://www.raspberrypi.org/archives/3195</ref> PCB, and RS Components produced a limited edition of anniversary boards in <b><span style="color:blue">Blue</span></b><ref>http://www.raspberrypi.org/archives/3422</ref>.

==Raspberry Pi Model-A Full Production Board ==
* As of Feb 2013, available from distributors in Europe but not North America
* Board has 256Mb of RAM rather than the originally planned 128Mb<ref name="postSale">[http://www.raspberrypi.org/archives/723 Post-Launch - And breathe…]</ref>
* The Foundation produced a small Beta batch before handing manufacturing over to RS and Farnell

==Raspberry Pi Model-B Full Production Board ==
[[File:RaspiFront.JPG|250px|thumb|right|The Rpi full production board (model B Rev 2.0)]]
* Announced: April 2012, first orders sent out June 2012.
* Manufacturing and Orders will be made through RS and Farnell
* This means a much higher volume of units will be produced and made available.
* Additional detail is available about the manufacturing and distribution agreement here [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)].
* Announced: September 2012, Raspberry Pi Model B Rev 2.0 is now manufactured at Sony's manufacturing plant on Pencoed, South Wales. [http://www.raspberrypi.org/archives/1925 Full announcement from the Raspberry Pi Foundation], [http://www.element14.com/community/thread/19738?tstart=0 Element14 announcement on Raspberry Pi discussion board].

==Raspberry Pi 1st Production Board ==
* Announced: 29th Feb 2012 - Start of Sale Only<ref name="postSale"/>
* Credit-card Format
* Initial 10k Batch (All Model-B's) Manufactured in China (Jan/Feb 2012)<ref name="firstProduction" >[http://www.raspberrypi.org/archives/509 We’ve started manufacture!]</ref>
* Should look identical to the Raspberry Pi Beta Board below (except different SDCard holder).
* The board has a yellow RCA connector, rather than the black one used in the Beta's.
* Nokia/Qt Development group has donated vouchers for 400 RPi units for developers<ref name="nokiaDonate">[http://www.raspberrypi.org/archives/369 Nokia has Raspberry Pi vouchers for 400 Qt developers]</ref>
* The batch was delayed several weeks due to the RJ45 network connector being substituted for the wrong part<ref>[http://www.raspberrypi.org/archives/781 Manufacturing Hiccup]</ref> and also so the board could undergo compliance testing<ref>[http://www.raspberrypi.org/archives/852 Compliance testing]</ref>

==Raspberry Pi Beta Production Board ==
* Announced: December 2011<ref name="#Beta">[http://www.raspberrypi.org/archives/422 Populated boards: an update on where we are]</ref>
* Credit-Card Format
* Manufactured in UK
* Produced 100<ref name="betapcb">[http://www.raspberrypi.org/archives/389 We have PCBs! BETA]</ref> PCBs
* Characteristic feature of hand-modded correction to PCB <ref name="betaError">[http://www.raspberrypi.org/archives/470 (hand-mod) More on the beta boards]</ref>
* See the [http://www.raspberrypi.org/archives/482 blog post] which includes a video explaining how the production units will differ from the beta boards.

* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-002-copy2-e1322775411416.jpg Pre-production board (beta board) PCB, topside]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-003-copy2.jpg Pre-production board (beta board) PCB, underside]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/Picture-001-copy.jpg Pre-production board vs credit-card]

===eBay Auction===
10 of the completed Model-B boards were auctioned on eBay (Started on 1st Jan 2012) <ref name="betaebay">[http://www.raspberrypi.org/archives/482 We’re auctioning ten beta Raspberry Pis!]</ref>)
{| border="1"
|SerialNo:
|#1
|#2
|#3
|#4
|#5
|#6
|#7<ref name="#7Donated"/>
|#8<ref name="#8PaulMaunders"/>
|#9
|#10
|-
|Date:
|11-Jan-2012
|11-Jan-2012
|10-Jan-2012
|10-Jan-2012
|09-Jan-2012
|09-Jan-2012
|08-Jan-2012
|08-Jan-2012
|07-Jan-2012
|07-Jan-2012
|-
|Sold For:
|£3,500
|£2,150
|£2,257
|£1,550
|£1,040
|£1,000
|£989
|£1,020
|£930
|£1,900
|}
Board #7 was anonymously (and generously) donated to [http://www.computinghistory.org.uk/ Centre for Computing History]<ref name="#7Donated">[http://www.raspberrypi.org/archives/503 Beta board bought by anonymous bidder and donated to museum]</ref> (also spotted [http://twitpic.com/86trra here..])!

Board #8 Owned by Tech Blogger, Paul Maunders, see his [http://www.pyrosoft.co.uk/blog blog] for details<ref name="#8PaulMaunders">[http://www.pyrosoft.co.uk/blog/2012/01/13/raspberry-pi-8-first-photoshoot/ Paul Maunders - Raspberry Pi #8 First Photoshoot]</ref>

==Raspberry Pi Alpha Board ==
[[File:RPi-alpha.jpg|250px|thumb|right|RPi Alpha Board]]

* Announced: August 2011<ref name="#Alpha">[http://www.raspberrypi.org/archives/78 The alpha boards are here!]</ref>
* Large Format for debugging (Model-B)
* Populated with headers for GPIO, JTAG, DSI, CSI, as well as switches and LEDs for I/O testing.

* [http://www.raspberrypi.org/wp-content/uploads/2011/08/DSCF1809.jpg Alpha prototype board, underside]

==Raspberry Pi USB Prototype Board ==
[[File:Rpi-usbproto.jpg|250px|thumb|right|RPi USB Prototype Board]]
* Announced: May 2011
* The "Computer On A USB Stick" Format
* Included built-in camera
* HDMI one end and single USB the other
* Introduced the RPi Foundation to the world (any earlier links appreciated), featured by [http://www.bbc.co.uk/news/technology-13292450 BBC Online Video].

‎

==Raspberry Pi Concept 2006 edition==
[[File:RPi-atmel2006Ed.jpg|250px|thumb|right|Raspberry Pi Concept 2006 edition]]
* Vero-board Prototype & PCB Version
* Atmel ATmega644 microcontroller clocked at 22.1MHz<ref name="2006ed">[http://www.raspberrypi.org/archives/264 Raspberry Pi – 2006 edition]</ref>

==See Also==
===Video===
* [http://news.bbc.co.uk/1/hi/programmes/click_online/9504208.stm BBC iClick's Peter Price asks whether a £15 computer can solve the programming gap] (6 minutes, 3 June 2011)
* [http://www.youtube.com/watch?v=pQ7N4rycsy4 Raspberry Pi's David Braben talks to BBC's Rory Cellan-Jones] (2:28 minutes, 5 May 2011)
* [http://www.youtube.com/RaspberryPiTutorials Raspberry Pi community tutorials on YouTube]

===Audio===
* [http://foundationlibraries.blogspot.com/2011/06/cfl-podcast-eben-upton-raspberry-pi.html Podcast of a phone interview with Eben about the project and the motivations behind it] (15 minutes long.) (3 June 2011) Transcription [http://tomhannen.posterous.com/raspberry-pi-podcast-transcript here].

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Low-level peripherals

2013-03-11T11:28:32Z

AndrewS: /* General Purpose Input/Output (GPIO) */ Split the P5 pinout table into two rows, to match the style of the P1 pinout table

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

==Introduction==
In addition to the familiar USB, Ethernet and HDMI ports, the R-Pi offers lower-level interfaces intended to connect more directly with chips and subsystem modules. These GPIO (general purpose I/O) signals on the 2x13 header pins include SPI, I2C, serial UART, 3V3 and 5V power. These interfaces are not "plug and play" and require care to avoid miswiring. The pins use a 3V3 logic level and are not tolerant of 5V levels, such as you might find on a 5V powered Arduino. Not yet software-enabled are the flex cable connectors with CSI (camera serial interface) and DSI (display serial interface), and a serial link inside the HDMI connector called CEC. (consumer electronics control)

==General Purpose Input/Output (GPIO)==
[[File:GPIOs.png|thumb|254px|right|The layout of the Raspberry Pi Revision 1 P1 pin-header seen from the top, containing pins useable for general purpose I/O. Colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs2.gif Source] ]]

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.

The Raspberry Pi allows peripherals and expansion boards (such as the [[Rpi Gertboard]]) to access the CPU by exposing the inputs and outputs.

For further general information about GPIOs, see: [http://en.wikipedia.org/wiki/GPIO the wikipedia article].<BR>
For further specific information about the Raspberry Pi's BCM2835 GPIOs, see: [[RPi_BCM2835_GPIOs|this wiki article]].

The production Raspberry Pi board has a 26-pin 2.54 mm (100 mil)<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907</ref> expansion header, marked as P1, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I²C, SPI, UART), as well as +3.3 V, +5 V and GND supply lines. Pin one is the pin in the first column and on the bottom row. <ref>http://www.raspberrypi.org/archives/384</ref>

[[File:RPi_P1_header.png]]

'''GPIO voltage levels are 3.3 V and are not 5 V 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.

All the GPIO pins can be reconfigured to provide alternate functions, SPI, [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM], I²C and so. At reset only pins GPIO 14 & 15 are assigned to the alternate function UART, these two can be switched back to GPIO to provide a total of 17 GPIO pins<ref>http://www.raspberrypi.org/archives/384</ref>. Each of their functions and full details of how to access are detailed in the chipset datasheet <ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref>.

Each GPIO can interrupt, high/low/rise/fall/change.<ref>http://www.raspberrypi.org/archives/384#comment-5217</ref><ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref> There is currently no support for GPIO interrupts in the official kernel, howewer a patch exists, requiring compilation of modified source tree.<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=44&t=7509</ref> The 'Raspbian "wheezy"' <ref>http://www.raspberrypi.org/downloads</ref> version that is currently recommended for starters already includes GPIO interrupts.

GPIO input hysteresis (Schmitt trigger) can be on or off, output slew rate can be fast or limited, and source and sink current is configurable from 2 mA up to 16 mA. Note that chipset GPIO pins 0-27 are in the same block and these properties are set per block, not per pin. See [http://www.scribd.com/doc/101830961/GPIO-Pads-Control2 GPIO Datasheet Addendum - GPIO Pads Control]. Particular attention should be applied to the note regarding SSO (Simultaneous Switching Outputs): to avoid interference, driving currents should be kept as low as possible.

The available [[RPi_BCM2835_GPIOs|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.

There is also some information on the [[RPi Tutorial Easy GPIO Hardware & Software|Tutorial on Easy GPIO Hardware & Software]].

Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200 bit/s.

'''R-Pi PCB Revision 2 UPDATE:''' According to Eben at [http://www.raspberrypi.org/archives/1929#comment-31646] the R-Pi Rev.2 board being rolled out starting in September 2012 adds 4 more GPIO on a new connector called P5, and changes some of the existing P1 GPIO pinouts. On Rev2, GPIO_GEN2 [BCM2835/GPIO27] is routed to P1 pin 13, and changes what was SCL0/SDA0 to SCL1/SDA1: SCL1 [BCM2835/GPIO3] is routed to P1 pin 5, SDA1 [BCM2835/GPIO2] is routed to P1 pin 3. Also the power and ground connections previously marked "Do Not Connect" on P1 will remain as connected, specifically: P1-04:+5V0, P1-09:GND, P1-14:GND, P1-17:+3V3, P1-20:GND, P1-25:GND. According to this comment [http://www.raspberrypi.org/archives/2081#comment-33577] (and confirmed in this post [http://www.raspberrypi.org/archives/2233]) the P1 pinout is not expected to change in future beyond the current Rev.2 layout.

'''P1 Header Pinout, top row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-02 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-04 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-06 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
|-
| P1-08 || bgcolor="lime" | GPIO 14 || bgcolor="lime" | GPIO 14 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_TXD || ALT5 = UART1_TXD
|-
| P1-10 || bgcolor="lime" | GPIO 15 || bgcolor="lime" | GPIO 15 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_RXD || ALT5 = UART1_RXD
|-
| P1-12 || bgcolor="lime" | GPIO 18 || bgcolor="lime" | GPIO 18 || || PCM_CLK || ALT4 = SPI1_CE0_N ALT5 = PWM0
|-
| P1-14 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-16 || bgcolor="lime" | GPIO23 || bgcolor="lime" | GPIO23 || || || ALT3 = SD1_CMD ALT4 = ARM_RTCK
|-
| P1-18 || bgcolor="lime" | GPIO24 || bgcolor="lime" | GPIO24 || || || ALT3 = SD1_DAT0 ALT4 = ARM_TDO
|-
| P1-20 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-22 || bgcolor="lime" | GPIO25 || bgcolor="lime" | GPIO25 || || || ALT3 = SD1_DAT1 ALT4 = ARM_TCK
|-
| P1-24 || bgcolor="lime" | GPIO08 || bgcolor="lime" | GPIO08 || || bgcolor="purple" | <span style="color:white">SPI0_CE0_N</span> ||
|-
| P1-26 || bgcolor="lime" | GPIO07 || bgcolor="lime" | GPIO07 || || bgcolor="purple" | <span style="color:white">SPI0_CE1_N</span> ||
|}

'''P1 Header Pinout, bottom row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-01 || bgcolor="orange" | 3.3 V ||bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-03 || bgcolor="lime" | GPIO 0 || bgcolor="lime" | '''GPIO 2'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SDA / '''I2C1_SDA''' ||
|-
| P1-05 || bgcolor="lime" | GPIO 1 || bgcolor="lime" | '''GPIO 3'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SCL / '''I2C1_SCL''' ||
|-
| P1-07 || bgcolor="lime" | GPIO 4 || bgcolor="lime" | GPIO 4 || || GPCLK0 || ALT5 = ARM_TDI
|-
| P1-09 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-11 || bgcolor="lime" | GPIO17 || bgcolor="lime" | GPIO17 || || ||| ALT3 = UART0_RTS ALT4 = SPI1_CE1_N ALT5 = UART1_RTS
|-
| P1-13 || bgcolor="lime" | GPIO21 || bgcolor="lime" | '''GPIO27''' || || PCM_DOUT / '''reserved''' || ALT4 = SPI1_SCLK ALT5 = GPCLK1 / '''ALT3 = SD1_DAT3 ALT4 = ARM_TMS'''
|-
| P1-15 || bgcolor="lime" | GPIO22 || bgcolor="lime" | GPIO22 || || || ALT3 = SD1_CLK ALT4 = ARM_TRST
|-
| P1-17 || bgcolor="orange" | 3.3 V || bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-19 || bgcolor="lime" | GPIO10 || bgcolor="lime" | GPIO10 || || bgcolor="purple" | <span style="color:white">SPI0_MOSI</span> ||
|-
| P1-21 || bgcolor="lime" | GPIO9 || bgcolor="lime" | GPIO9 || || bgcolor="purple" | <span style="color:white">SPI0_MISO</span> ||
|-
| P1-23 || bgcolor="lime" | GPIO11 || bgcolor="lime" | GPIO11 || || bgcolor="purple" | <span style="color:white">SPI0_SCLK</span> ||
|-
| P1-25 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|}

{| border="1"
! Colour legend
|-
| bgcolor="red" | <span style="color:white">+5 V</span>
|-
| bgcolor="orange" | +3.3 V
|-
| bgcolor="black" | <span style="color:white">Ground, 0V</span>
|-
| bgcolor="yellow" | UART
|-
| bgcolor="lime" | GPIO
|-
| bgcolor="purple" | <span style="color:white">SPI</span>
|-
| bgcolor="cyan" | I²C
|}

KiCad symbol: [[File:Conn-raspberry.lib]]

<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2</ref>

Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as an I²C interface. So there are 1.8 kilohm pulls up resistors on the board for these pins.<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480</ref>

Pin 12 supports [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM] .

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.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.1</ref> 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.

It is also possible to reconfigure GPIO connector pins P1-12 and 13 (chipset GPIO 18 and 21) to provide an I2S (a hardware modification may be required<ref name="I2S">[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?]</ref>) or PCM interface.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.2</ref> However, PCM_FS and PCM_DIN (chipset pins 19 and 20) are needed for I2S or PCM.

A second I²C 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.

===Referring to pins on the Expansion header===

The header is referred to as "The GPIO Connector (P1)". To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended.

* The expansion header is referred to as "Expansion Header" or "GPIO Connector (P1)"
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.
* Names GPIO0, GPIO1, GPIOx-ALTy, etc. refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where "x" matches BCM2835 number (without leading zero) and "y" 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 "GPIO7" to refer to a row of the table, and "GPIO7-ALT0" would refer to a specific cell of the table.
* 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 "SPI0_*" and "SPI1_*", but they didn't do the same on the I²C and UART pins. Instead of using "SDA0" and "SCL0", you should use "I2C0_SDA" and "I2C0_SCL"; and instead of "TX" or "TXD" and "RX" or "RXD", you should use "UART0_TXD" and "UART0_RXD".

===Power pins===
The maximum permitted current draw from the 3.3 V pins is 50 mA.

Maximum permitted current draw from the 5 V pin is the USB input current (usually 1 A) minus any current draw from the rest of the board.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1536#postid-21841</ref>
*Model A: 1000 mA - 500 mA -> max current draw: 500 mA
*Model B: 1000 mA - 700 mA -> max current draw: 300 mA
Be very careful with the 5 V pins P1-02 and P1-04, because if you short 5 V to any other P1 pin you may permanently damage your RasPi. Before probing P1, it's a good idea to strip short pieces of insulation off a wire and push them over the 5 V pins so you don't accidentally short them with a probe.

=== GPIO hardware hacking ===

The complete list of [[RPi_BCM2835_GPIOs|chipset GPIO pins]] which are available on the GPIO connector is: <blockquote>[[RPi_BCM2835_GPIOs#GPIO0|0]], [[RPi_BCM2835_GPIOs#GPIO1|1]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO21|21]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]]</blockquote>

(on the Revision2.0 RaspberryPis, this list changes to: [[RPi_BCM2835_GPIOs#GPIO2|2]], [[RPi_BCM2835_GPIOs#GPIO3|3]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]], [[RPi_BCM2835_GPIOs#GPIO27|27]], with [[RPi_BCM2835_GPIOs#GPIO28|28]], [[RPi_BCM2835_GPIOs#GPIO29|29]], [[RPi_BCM2835_GPIOs#GPIO30|30]], [[RPi_BCM2835_GPIOs#GPIO31|31]] additionally available on the [[#P5_header|P5 header]])

As noted above, P1-03 and P1-05 (SDA0 and SCL0 / SDA1 and SCL1) have 1.8 kilohm pull-up resistors to 3.3 V.

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:

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 3.3 V.

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.

There are a few other chipset GPIO pins accessible on the PCB but are in use:

* GPIO16 drives status LED D5 (usually SD card access indicator)
* GPIO28-31 are used by the board ID and are connected to resistors R3 to R10 (only on Rev1.0 boards).
* GPIO40 and 45 are used by analogue audio and support [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM]. They connect to the analogue audio circuitry via R21 and R27 respectively.
* GPIO46 is HDMI hotplug detect (goes to pin 6 of IC1).
* 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.

=== P2 header ===

The P2 header is the VideoCore JTAG and used only during the production of the board. It cannot be used as the ARM JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>. This connector is unpopulated in Rev 2.0 boards.

[[File:RPi_P2_header.png]]

Useful P2 pins:

* Pin 1 - 3.3V (same as P1-01, 50 mA max current draw across both of them)
* Pin 7 - GND
* Pin 8 - GND

=== P3 header ===

The P3 header, unpopulated, is the LAN9512 JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>.

[[File:RPi_P3_header.png]]

Useful P3 pins:

* Pin 7 - GND

=== P5 header ===

The P5 header was added with the release of the Revision 2.0 PCB design.

[[File:RPi_P5_header.png]]

'''P5 Header Pinout (seen from the back of the board), top row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P5-01 || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P5-03 || bgcolor="lime" | GPIO28 || || bgcolor="cyan" | I2C0_SDA || ALT2 = PCM_CLK
|-
| P5-05 || bgcolor="lime" | GPIO30 || || || ALT2 = PCM_DIN ALT3 = UART0_CTS ALT5 = UART1_CTS
|-
| P5-07 || bgcolor="black" | <span style="color:white">GND</span>
|}

'''P5 Header Pinout (seen from the back of the board), bottom row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P5-02 || bgcolor="orange" | 3.3 V || 50 mA max (combined with P1)
|-
| P5-04 || bgcolor="lime" | GPIO29 || || bgcolor="cyan" | I2C0_SCL || ALT2 = PCM_FS
|-
| P5-06 || bgcolor="lime" | GPIO31 || || || ALT2 = PCM_DOUT ALT3 = UART0_RTS ALT5 = UART1_RTS
|-
| P5-08 || bgcolor="black" | <span style="color:white">GND</span>
|}

Note that the connector is intended to be mounted on the '''bottom''' of the PCB, so that for those who put the connector on the top side, the pin numbers are swapped. Pin 1 and pin 2 are swapped, pin 3 and 4, etc.

The new header can provide a second I2C channel (SDA + SCL) and handshake lines for the existing UART (TxD and RxD), or it can be used for an I2S (audio codec chip) interface using the PCM signals CLK, FS (Frame Sync), Din and Dout.

Note that the connector is placed JUST off-grid with respect to the P1 connector.

=== P6 header ===

The P6 header was added with the release of the Revision 2.0 PCB design.

[[File:RPi_P6_header.png]]

'''P6 Pinout:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev2''' || '''Hardware Notes'''
|-
| P6-01 || RUN || Short to ground to reset the BCM2835
|-
| P6-02 || bgcolor="black" | <span style="color:white">GND</span>
|}

[http://raspi.tv/2012/making-a-reset-switch-for-your-rev-2-raspberry-pi A reset button can be attached to the P6 header], with which the Pi can be reset.
Momentarily shorting the two pins of P6 together will cause a soft reset of the CPU (which can also 'wake' the Pi from halt/shutdown state).

===Driver support===

The Foundation will not include a GPIO driver in the initial release, standard Linux GPIO drivers should work with minimal modification.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1278.0</ref>

The community implemented SPI and I²C drivers <ref>http://www.bootc.net/projects/raspberry-pi-kernel/</ref>, which will be integrated with the new Linux pinctrl concept in a later version of the kernel. (On Oct. 14 2012, it was already included in the latest raspbian image.) A first compiled version as Linux modules is available to install on the 19/04/2012 Debian image, including 1-wire support<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=86172#p86172</ref>. The I²C and SPI driver uses the hardware modules of the microcontroller and interrupts for low CPU usage, the 1-wire support uses bitbanging on the GPIO ports, which results in higher CPU usage.

GordonH<ref>http://www.raspberrypi.org/forum/general-discussion/wiring-for-the-raspberry-pis-gpio</ref> wrote a (mostly) Arduino compatible/style [https://projects.drogon.net/raspberry-pi/wiringpi/ WiringPi library] in C for controlling the GPIO pins.

A useful tutorial on setting up I²C driver support can be found at [http://www.robot-electronics.co.uk/htm/raspberry_pi_examples.htm Robot Electronics] - look for the downloadable document rpi_i2c_setup.doc

===Graphical User Interfaces===
====WebIOPi====
[http://code.google.com/p/webiopi/ WebIOPi] allows you to control each GPIO with a simple web interface that you can use with any browser. Available in PHP and Python, they both require root access, but Python version serves HTTP itself. You can setup each GPIO as input or output and change their states (LOW/HIGH). WebIOPi is fully customizable, so you can use it for home remote control. It also work over Internet. UART/SPI/I2C support will be added later. If you need some computing for your GPIO go to code examples below.

==GPIO Code examples==
=== C ===
Examples in different C-Languages.
==== C ====
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo & Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)
Example GPIO code:

<pre>
//
// How to access GPIO registers from C-code on the Raspberry-Pi
// Example program
// 15-January-2012
// Dom and Gert
// Revised: 15-Feb-2013

// Access from ARM Running Linux

#define BCM2708_PERI_BASE 0x20000000
#define GPIO_BASE (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/mman.h>
#include <unistd.h>

#define PAGE_SIZE (4*1024)
#define BLOCK_SIZE (4*1024)

int mem_fd;
void *gpio_map;

// I/O access
volatile unsigned *gpio;

// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)
#define INP_GPIO(g) *(gpio+((g)/10)) &= ~(7<<(((g)%10)*3))
#define OUT_GPIO(g) *(gpio+((g)/10)) |= (1<<(((g)%10)*3))
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)<=3?(a)+4:(a)==4?3:2)<<(((g)%10)*3))

#define GPIO_SET *(gpio+7) // sets bits which are 1 ignores bits which are 0
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0

void setup_io();

int main(int argc, char **argv)
{
int g,rep;

// Set up gpi pointer for direct register access
setup_io();

// Switch GPIO 7..11 to output mode

/************************************************************************\
* You are about to change the GPIO settings of your computer. *
* Mess this up and it will stop working! *
* It might be a good idea to 'sync' before running this program *
* so at least you still have your code changes written to the SD-card! *
\************************************************************************/

// Set GPIO pins 7-11 to output
for (g=7; g<=11; g++)
{
INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO
OUT_GPIO(g);
}

for (rep=0; rep<10; rep++)
{
for (g=7; g<=11; g++)
{
GPIO_SET = 1<<g;
sleep(1);
}
for (g=7; g<=11; g++)
{
GPIO_CLR = 1<<g;
sleep(1);
}
}

return 0;

} // main

//
// Set up a memory regions to access GPIO
//
void setup_io()
{
/* open /dev/mem */
if ((mem_fd = open("/dev/mem", O_RDWR|O_SYNC) ) < 0) {
printf("can't open /dev/mem \n");
exit(-1);
}

/* mmap GPIO */
gpio_map = mmap(
NULL, //Any adddress in our space will do
BLOCK_SIZE, //Map length
PROT_READ|PROT_WRITE,// Enable reading & writting to mapped memory
MAP_SHARED, //Shared with other processes
mem_fd, //File to map
GPIO_BASE //Offset to GPIO peripheral
);

close(mem_fd); //No need to keep mem_fd open after mmap

if (gpio_map == MAP_FAILED) {
printf("mmap error %d\n", (int)gpio_map);//errno also set!
exit(-1);
}

// Always use volatile pointer!
gpio = (volatile unsigned *)gpio_map;

} // setup_io

</pre>

===== GPIO Pull Up/Pull Down Register Example =====
<pre>
// enable pull-up on GPIO24&25
GPIO_PULL = 2;
short_wait();
// clock on GPIO 24 & 25 (bit 24 & 25 set)
GPIO_PULLCLK0 = 0x03000000;
short_wait();
GPIO_PULL = 0;
GPIO_PULLCLK0 = 0;
</pre>

==== C + wiringPi ====
Get and install wiringPi: https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/

Save this, and compile with:
<pre>
gcc -o blink blink.c -lwiringPi
</pre>
and run with:
<pre>
sudo ./blink
</pre>

<pre>
/*
* blink.c:
* blinks the first LED
* Gordon Henderson, projects@drogon.net
*/

#include <stdio.h>
#include <wiringPi.h>

int main (void)
{
printf ("Raspberry Pi blink\n") ;

if (wiringPiSetup () == -1)
return 1 ;

pinMode (0, OUTPUT) ; // aka BCM_GPIO pin 17

for (;;)
{
digitalWrite (0, 1) ; // On
delay (500) ; // mS
digitalWrite (0, 0) ; // Off
delay (500) ;
}
return 0 ;
}
</pre>

==== C ====
This must be done as root. To change to the root user:
<pre>sudo -i</pre>
You must also get and install the bcm2835 library, which supports
GPIO and SPI interfaces. Details and downloads
from http://www.open.com.au/mikem/bcm2835

<pre>

// blink.c
//
// Example program for bcm2835 library
// Blinks a pin on an off every 0.5 secs
//
// After installing bcm2835, you can build this
// with something like:
// gcc -o blink -l rt blink.c -l bcm2835
// sudo ./blink
//
// Or you can test it before installing with:
// gcc -o blink -l rt -I ../../src ../../src/bcm2835.c blink.c
// sudo ./blink
//
// Author: Mike McCauley (mikem@open.com.au)
// Copyright (C) 2011 Mike McCauley
// $Id: RF22.h,v 1.21 2012/05/30 01:51:25 mikem Exp $

#include <bcm2835.h>

// Blinks on RPi pin GPIO 11
#define PIN RPI_GPIO_P1_11

int main(int argc, char **argv)
{
// If you call this, it will not actually access the GPIO
// Use for testing
// bcm2835_set_debug(1);

if (!bcm2835_init())
return 1;

// Set the pin to be an output
bcm2835_gpio_fsel(PIN, BCM2835_GPIO_FSEL_OUTP);

// Blink
while (1)
{
// Turn it on
bcm2835_gpio_write(PIN, HIGH);

// wait a bit
delay(500);

// turn it off
bcm2835_gpio_write(PIN, LOW);

// wait a bit
delay(500);
}

return 0;
}
</pre>

==== C# ====
RaspberryPiDotNet library is available at https://github.com/cypherkey/RaspberryPi.Net/.
The library includes a GPIOFile and GPIOMem class. The GPIOMem requires compiling Mike McCauley's bcm2835 library above in to a shared object.

<pre>
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using RaspberryPiDotNet;
using System.Threading;

namespace RaspPi
{
class Program
{
static void Main(string[] args)
{
// Access the GPIO pin using a static method
GPIOFile.Write(GPIO.GPIOPins.GPIO00, true);

// Create a new GPIO object
GPIOMem gpio = new GPIOMem(GPIO.GPIOPins.GPIO01);
gpio.Write(false);
}
}
}
</pre>

=== Ruby ===

This example uses the WiringPi Ruby Gem: http://pi.gadgetoid.co.uk/post/015-wiringpi-now-with-serial which you can install on your Pi with "gem install wiringpi"

<pre>
MY_PIN = 1

require 'wiringpi'
io = WiringPi::GPIO.new
io.mode(MY_PIN,OUTPUT)
io.write(MY_PIN,HIGH)
io.read(MY_PIN)
</pre>

Alternatively the Pi Piper Gem (https://github.com/jwhitehorn/pi_piper) allows for event driven programming:

<pre>
require 'pi_piper'
include PiPiper

watch :pin => 23 do
puts "Pin changed from #{last_value} to #{value}"
end

PiPiper.wait
</pre>

=== Perl ===
This must be done as root. To change to the root user:
<pre>sudo su -</pre>
Supports GPIO and SPI interfaces.
You must also get and install the bcm2835 library. Details and downloads
from http://www.open.com.au/mikem/bcm2835
You must then get and install the Device::BCM2835 perl library from CPAN
http://search.cpan.org/~mikem/Device-BCM2835-1.0/lib/Device/BCM2835.pm
<pre>
use Device::BCM2835;
use strict;

# call set_debug(1) to do a non-destructive test on non-RPi hardware
#Device::BCM2835::set_debug(1);
Device::BCM2835::init()
|| die "Could not init library";

# Blink pin 11:
# Set RPi pin 11 to be an output
Device::BCM2835::gpio_fsel(&Device::BCM2835::RPI_GPIO_P1_11,
&Device::BCM2835::BCM2835_GPIO_FSEL_OUTP);

while (1)
{
# Turn it on
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 1);
Device::BCM2835::delay(500); # Milliseconds
# Turn it off
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 0);
Device::BCM2835::delay(500); # Milliseconds
}

</pre>

=== Python ===
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO
Any Python script that controls GPIO must be run as root.
<pre>import RPi.GPIO as GPIO

# Set up the GPIO channels - one input and one output
GPIO.setup(11, GPIO.IN)
GPIO.setup(12, GPIO.OUT)

# Input from pin 11
input_value = GPIO.input(11)

# Output to pin 12
GPIO.output(12, True)

# The same script as above but using BCM GPIO 00..nn numbers
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.IN)
GPIO.setup(18, GPIO.OUT)
input_value = GPIO.input(17)
GPIO.output(18, True)</pre>

=== Java ===
==== Java using the Pi4J Library ====
This uses the Java library available at http://www.pi4j.com/.
(Any Java application that controls GPIO must be run as root.)

Please note that the Pi4J library uses the WiringPi GPIO pin numbering scheme <ref>http://pi4j.com/usage.html#Pin_Numbering</ref> <ref>https://projects.drogon.net/raspberry-pi/wiringpi/pins/</ref>. Please see the usage documentation for more details: http://pi4j.com/usage.html

<pre>

public static void main(String[] args) {

// create gpio controller
GpioController gpio = GpioFactory.getInstance();

// provision gpio pin #01 as an output pin and turn off
GpioPinDigitalOutput outputPin = gpio.provisionDigitalOutputPin(RaspiPin.GPIO_01, "MyLED", PinState.LOW);

// turn output to LOW/OFF state
outputPin.low();

// turn output to HIGH/ON state
outputPin.high();

// provision gpio pin #02 as an input pin with its internal pull down resistor enabled
GpioPinDigitalInput inputPin = gpio.provisionDigitalInputPin(RaspiPin.GPIO_02, "MyButton", PinPullResistance.PULL_DOWN);

// get input state from pin 2
boolean input_value = inputPin.isHigh();
}
</pre>

More complete and detailed examples are included on the Pi4J website at http://www.pi4j.com/.

The Pi4J library includes support for:
* GPIO Control
* GPIO Listeners
* Serial Communication
* I2C Communication
* SPI Communication

==== Java ====
This uses the Java library available at https://github.com/jkransen/framboos. It does not depend on (or use) the wiringPi driver, but uses the same numbering scheme. Instead it uses the default driver under /sys/class/gpio that ships with the distro, so it works out of the box. Any Java application that controls GPIO must be run as root.
<pre>
public static void main(String[] args) {
// reading from an in pin
InPin button = new InPin(8);
boolean isButtonPressed = button.getValue();
button.close();

// writing to an out pin
OutPin led = new Outpin(0);
led.setValue(true);
led.setValue(false);
led.close();
}
</pre>

==== Java Webapp GPIO web control via http ====
This uses the Java Webapp available at https://bitbucket.org/sbub/raspberry-pi-gpio-web-control/overview. You can control your GPIO over the internet. Any Java application that controls GPIO must be run as root.
<pre>

host:~ sb$ curl 'http://raspberrypi:8080/handle?g0=1&g1=0'
{"g1":0,"g0":1}

</pre>

=== Bash shell script, using sysfs, part of the raspbian operating system ===
The export and unexport of pins must be done as root.
To change to the root user see below: To change back, the word exit must be entered.
<pre>sudo -i</pre>
Export creates a new folder for the exported pin, and creates files for each of its control functions (i.e. active_low, direction, edge, power, subsystem, uevent, and value). Upon creation, the control files can be read by all users (not just root), but can only be written to by user root, the file's owner. Nevertheless, once created, it is possible to allow users other than root, to also write inputs to the control files, by changing the ownership or permissions of these files. Changes to the file's ownership or permissions must initially be done as root, as their owner and group is set to root upon creation. Typically you might change the owner to be the (non root) user controlling the GPIO, or you might add write permission, and change the group ownership to one of which the user controlling the GPIO is a member. By such means, using only packages provided in the recommended rasbian distribution, it is possible for Python CGI scripts, which are typically run as user nobody, to be used for control of the GPIO over the internet from a browser at a remote location.
<pre>
#!/bin/sh

# GPIO numbers should be from this list
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25

# Note that the GPIO numbers that you program here refer to the pins
# of the BCM2835 and *not* the numbers on the pin header.
# So, if you want to activate GPIO7 on the header you should be
# using GPIO4 in this script. Likewise if you want to activate GPIO0
# on the header you should be using GPIO17 here.

# Set up GPIO 4 and set to output
echo "4" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio4/direction

# Set up GPIO 7 and set to input
echo "7" > /sys/class/gpio/export
echo "in" > /sys/class/gpio/gpio7/direction

# Write output
echo "1" > /sys/class/gpio/gpio4/value

# Read from input
cat /sys/class/gpio/gpio7/value

# Clean up
echo "4" > /sys/class/gpio/unexport
echo "7" > /sys/class/gpio/unexport
</pre>

=== Shell script - take 2 ===
You need the wiringPi library from
https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/. Once installed, there is a new command '''gpio''' which can be used
as a '''non-root''' user to control the GPIO pins.

The man page <pre>man gpio</pre> has full details, but briefly:

<pre>
gpio -g mode 17 out
gpio -g mode 18 pwm

gpio -g write 17 1
gpio -g pwm 18 512
</pre>

The '''-g''' flag tells the '''gpio''' program to use the BCM GPIO pin numbering
scheme (otherwise it will use the wiringPi numbering scheme by default).

The gpio command can also control the internal pull-up and pull-down
resistors:

<pre>
gpio -g mode 17 up
</pre>

This sets the pull-up resistor - however any change of mode, even
setting a pin that's already set as an input to an input will remove
the pull-up/pull-down resistors, so they may need to be reset.

Additionally, it can export/un-export the GPIO devices for use by
other non-root programms - e.g. Python scripts. (Although you
may need to drop the calls to GPIO.Setup() in the Python scripts, and
do the setup separately in a little shell script, or call the '''gpio''' program
from inside Python).

<pre>
gpio export 17 out
gpio export 18 in
</pre>

These exports GPIO-17 and sets it to output, and exports GPIO-18
and sets it to input.

And when done:

<pre>
gpio unexport 17
</pre>

The export/unexport commands always use the BCM GPIO pin numbers regardless of the
presence of the '''-g''' flag or not.

If you want to use the internal pull-up/down's with the /sys/class/gpio mechanisms,
then you can set them after exporting them. So:

<pre>
gpio -g export 4 in
gpio -g mode 4 up
</pre>

You can then use GPIO-4 as an input in your Python, Shell, Java, etc. programs without the use
of an external resistor to pull the pin high. (If that's what you were after - for example, a simple push
button switch taking the pin to ground.)

A fully working example of a shell script using the GPIO pins
can be found at http://project-downloads.drogon.net/files/gpioExamples/tuxx.sh.

=== Lazarus / Free Pascal ===
[[File:RPI GPIO testprogram with lazarus.png|thumb|254px|right|A simple app for controlling GPIO pin 17 with Lazarus]]

The GPIO pins are accessible from [[Lazarus on RPi|Lazarus]] without any third-party software. This is performed by means of the [http://www.freepascal.org/docs-html/rtl/baseunix/index.html BaseUnix] unit that is part of every distribution of Lazarus and Free Pascal or by invoking Unix shell commands with '''fpsystem'''. The following example uses GPIO pin 17 as output port. It is assumed that you created a form with a TToggleBox named GPIO17ToggleBox and for logging purposes a TMemo with name LogMemo (optional). The program has to be executed with root privileges.

''Unit for controlling the GPIO port:''
<pre>
unit Unit1;

{Demo application for GPIO on Raspberry Pi}
{Inspired by the Python input/output demo application by Gareth Halfacree}
{written for the Raspberry Pi User Guide, ISBN 978-1-118-46446-5}

{$mode objfpc}{$H+}

interface

uses
Classes, SysUtils, FileUtil, Forms, Controls, Graphics, Dialogs, StdCtrls,
Unix, BaseUnix;

type

{ TForm1 }

TForm1 = class(TForm)
LogMemo: TMemo;
GPIO17ToggleBox: TToggleBox;
procedure FormActivate(Sender: TObject);
procedure FormClose(Sender: TObject; var CloseAction: TCloseAction);
procedure GPIO17ToggleBoxChange(Sender: TObject);
private
{ private declarations }
public
{ public declarations }
end;

const
PIN_17: PChar = '17';
PIN_ON: PChar = '1';
PIN_OFF: PChar = '0';
OUT_DIRECTION: PChar = 'out';

var
Form1: TForm1;
gReturnCode: longint; {stores the result of the IO operation}

implementation

{$R *.lfm}

{ TForm1 }

procedure TForm1.FormActivate(Sender: TObject);
var
fileDesc: integer;
begin
{ Prepare SoC pin 17 (pin 11 on GPIO port) for access: }
try
fileDesc := fpopen('/sys/class/gpio/export', O_WrOnly);
gReturnCode := fpwrite(fileDesc, PIN_17[0], 2);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
{ Set SoC pin 17 as output: }
try
fileDesc := fpopen('/sys/class/gpio/gpio17/direction', O_WrOnly);
gReturnCode := fpwrite(fileDesc, OUT_DIRECTION[0], 3);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;

procedure TForm1.FormClose(Sender: TObject; var CloseAction: TCloseAction);
var
fileDesc: integer;
begin
{ Free SoC pin 17: }
try
fileDesc := fpopen('/sys/class/gpio/unexport', O_WrOnly);
gReturnCode := fpwrite(fileDesc, PIN_17[0], 2);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;

procedure TForm1.GPIO17ToggleBoxChange(Sender: TObject);
var
fileDesc: integer;
begin
if GPIO17ToggleBox.Checked then
begin
{ Swith SoC pin 17 on: }
try
fileDesc := fpopen('/sys/class/gpio/gpio17/value', O_WrOnly);
gReturnCode := fpwrite(fileDesc, PIN_ON[0], 1);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end
else
begin
{ Switch SoC pin 17 off: }
try
fileDesc := fpopen('/sys/class/gpio/gpio17/value', O_WrOnly);
gReturnCode := fpwrite(fileDesc, PIN_OFF[0], 1);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;
end;

end.
</pre>

''Main program:''
<pre>
program io_test;

{$mode objfpc}{$H+}

uses
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Interfaces, // this includes the LCL widgetset
Forms, Unit1
{ you can add units after this };

{$R *.res}

begin
Application.Initialize;
Application.CreateForm(TForm1, Form1);
Application.Run;
end.
</pre>

An alternative way to access the GPIO port with Lazarus / Free Pascal is by using [http://www.lazarus.freepascal.org/index.php/topic,17404.0.html Lazarus wrapper unit for Gordon Henderson's wiringPi C library].

=== BASIC ===
==== BASIC - Return to BASIC ====

'''RTB''' or Return to Basic can be found here: https://projects.drogon.net/return-to-basic/

It's a new BASIC featuring modern looping constructs, switch statements, named procedures and functions as well as graphics (caresian and turtle), file handling and more. It also supports the Pi's on-board GPIO without needing to be run as root. (You don't need any special setup routines either)

Sample blink program:

<pre>
// blink.rtb:
// Blink program in Return to Basic
// Gordon Henderson, projects@drogon.net
//
PinMode (0, 1) // Output
CYCLE
DigitalWrite (0, 1) // Pin 0 ON
WAIT (0.5) // 0.5 seconds
DigitalWrite (0, 0)
WAIT (0.5)
REPEAT
END
</pre>

==== BASIC ====

'''Bywater BASIC Interpreter'''

The Bywater BASIC Interpreter (bwBASIC) implements a large superset of the ANSI Standard for Minimal BASIC (X3.60-1978) and a significant subset of the ANSI Standard for Full BASIC (X3.113-1987) in C. It also offers shell programming facilities as an extension of BASIC. bwBASIC seeks to be as portable as possible.
You can download it at.
http://packages.debian.org/stable/interpreters/bwbasic

'''BASIC programming of the I/O'''

'''Setting up a GPIO pin to be used for inputs or for outputs.'''

We cannot load the control words directly into the 32 bit ARM registers with 32 bit addresses, as bwBASIC has no POKE and PEEK commands and other versions of BASIC (as far as I know) only handle 8 bit registers with 16 bit addresses with these commands. So we need to export the GPIO pins, so that they exist in a file structure which we can access from basic with the OPEN command.(ref 2)

We need to do this in Linux root.
We need to run BASIC in the root too. First we go to the root, then we load bwbasic into root.
<pre>
sudo -1
sudo bwbasic
</pre>

REM Now to export the no4 GPIO pin for example, using a Shell command.

<pre>echo “4” > /sys/class/gpio/export</pre>

Whilst bwbasic can accommodate shell commands, and we can store a set of these commands (eg. to export a number of GPIO pins at the outset) as numbered statements in a file that can be loaded with the basic command LOAD “filename” and RUN (ref 2), the shell commands have to run as a separate file, as they cannot be run from within, as part of a basic programme.

'''Now we can access the file containing the pin direction setting from BASIC'''

We can set GPIO pin 4 to input or to output by OPENing its pin direction file for output and writing “in” or “out” with a PRINT# command. (ref 2 )
<syntaxhighlight lang="basic4gl">
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 PRINT #1,”out”
30 CLOSE #1
</syntaxhighlight>

REM closes the open direction file, whereupon the system performs the action of setting the direction to “out”. NB the system only carries out the action as the file is closed.(ref 3)

'''We are now able to control the output of the gpio 4 pin from BASIC'''

We can set the GPIO 4 pin to 1 or to 0 by OPENing its pin value file for output and writing “1” or “0” with a PRINT# command.
<syntaxhighlight lang="basic4gl">
40 OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
50 PRINT #4,”1”
60 CLOSE #4
</syntaxhighlight>

REM turns on the output of GPIO pin 4.

REM similarly we can turn off the output of GPIO pin 4.
OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
PRINT #4,”0”
CLOSE #4.

'''Example of an (unstructured) BASIC programme'''

To read the state of a switch and control the power to two LEDs connected to GPIO pins 8,7 and 4 respectively.

Programme to set 2 pins as outputs and 1 pin as input and to read the input turning on two different combinations of the two outputs (ie output 0,1 or 1,0) depending on the state of the input (1 or 0).
<syntaxhighlight lang="basic4gl">
sudo –i
sudo bwbasic
LOAD “export.bas”
LIST
REM a set of Shell statements to export the three GPIO pins.
10 echo “4” > /sys/class/gpio/export
20 echo “7” > /sys/class/gpio/export
30 echo “8” > /sys/class/gpio/export
RUN
</syntaxhighlight>

NEW REM clears the export.bas programme from memory
<syntaxhighlight lang="basic4gl">
.
LOAD “demo1.bas”
LIST
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 OPEN ”O”,#2, “/sys/devices/virtual/gpio/gpio7/direction”,2
30 OPEN ”O”,#3, “/sys/devices/virtual/gpio/gpio8/direction”,2
REM opens the three pin direction files
40 PRINT #1, “out”
50 PRINT #2, “out”
60 PRINT #3, “in”
REM sets GPIO pins 4 and 7 as outputs and GPIO pin 8 as input.
70 CLOSE #1
80 CLOSE #2
90 CLOSE #3
REM closes all open files, allowing the system to perform the direction settings.
100 OPEN ”I”,#8, “/sys/devices/virtual/gpio/gpio8/value”,1
REM opens the GPIO pin 8 value file
110 INPUT #8,x
REM reads the value of the input pin and stores the value in numerical variable x
120 CLOSE #8
REM closes the open file, allowing the system to read the value of the input pin and store the value in numerical variable x.
130 OPEN “O”,#1, “/sys/devices/virtual/gpio/gpio4/value”,1
140 OPEN “O”,#2, “/sys/devices/virtual/gpio/gpio7/value”,1
REM opens the GPIO pins 4 and value files ready for outputting 1s and 0s.
150 IF x<1 THEN GOTO 160 ELSE GOTO 190
REM tests the state of the switch (1 or0) and directs the program to generate the appropriate outputs
160 PRINT #1,”1”
170 PRINT #2,”0”
180 GOTO 210
190 PRINT#1,"0"
200 PRINT #2,"1"
210 CLOSE #1
220 CLOSE #2
REM Closes the files and allows the outputs to light the LED
230 END.
</syntaxhighlight>

When all is done, we should unexport the GPIO pins, to leave the R-Pi as we found it.(Ref 1.)
<syntaxhighlight lang="basic4gl">
NEW
LOAD “unexport.bas”
LIST
REM a set of Shell statements to unexport the three GPIO pins.
10 echo “4” > /sys/class/gpio/unexport
20 echo “7” > /sys/class/gpio/unexport
30 echo “8” > /sys/class/gpio/unexport
RUN
</syntaxhighlight>
A simple circuit to provide the switched input and the two LED outputs.

Ancient Mariner. Dec. 2012

References.

1. This paper RPi Low-level peripherals.

2. Ed Beynon. [http://www.ybw.com/forums/showthread.php?t=331320&page=5 http://www.ybw.com/forums/showthread.php?t=331320&page=5]

3. Arthur Kaletzky. Private communication. 25/10/2012

4. bwbasic manual.<br/>

For the two original documents this example has been copied from see:<br/>
[[Media:GPIO_Driving_Example_(BASIC)_.doc | GPIO_Driving_Example_(BASIC)_.doc]]

[[Media:Raspberry_Pi_I-O_viii.doc | Raspberry_Pi_I-O_viii.doc]]

==MIPI CSI-2==

On the production board<ref>http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf</ref>, the Raspberry Pi Foundation design brings out the MIPI CSI-2 (Camera Serial Interface<ref>http://www.mipi.org/specifications/camera-interface</ref>) to a 15-way flat flex connector S5, between the Ethernet and HDMI connectors. A compatible camera has been discussed as working in tests and is planned for release at a later date.<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/complex-camera-peripherials#p72602</ref>.


==DSI==

On the production board, the Raspberry Pi Foundation design brings out the DSI (Display Serial Interface<ref>http://www.mipi.org/specifications/display-interface</ref>) to a 15-way flat flex connector labelled S2, next to Raspberry Pi logo. It has two data lanes and a clock lane, to drive a possible future LCD screen device. Some smart phone screens use DSI<ref>http://en.wikipedia.org/wiki/Display_Serial_Interface</ref>.

==CEC==

[[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.
Eben notes that he has seen CEC demos on the Broadcom SoC they are using.

libCEC with Raspberry Pi support has been included in OpenELEC and will be included in Raspbmc RC4.<ref>http://blog.pulse-eight.com/2012/08/01/libcec-1-8-0-a-firmware-upgrade-and-raspberry-pi-support/</ref>

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.

== References ==
<references/>

{{Template:Raspberry Pi}}

RPi Low-level peripherals

2013-03-10T22:20:28Z

AndrewS: /* General Purpose Input/Output (GPIO) */ Added pin-orientation images for the P5 and P6 headers

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

==Introduction==
In addition to the familiar USB, Ethernet and HDMI ports, the R-Pi offers lower-level interfaces intended to connect more directly with chips and subsystem modules. These GPIO (general purpose I/O) signals on the 2x13 header pins include SPI, I2C, serial UART, 3V3 and 5V power. These interfaces are not "plug and play" and require care to avoid miswiring. The pins use a 3V3 logic level and are not tolerant of 5V levels, such as you might find on a 5V powered Arduino. Not yet software-enabled are the flex cable connectors with CSI (camera serial interface) and DSI (display serial interface), and a serial link inside the HDMI connector called CEC. (consumer electronics control)

==General Purpose Input/Output (GPIO)==
[[File:GPIOs.png|thumb|254px|right|The layout of the Raspberry Pi Revision 1 P1 pin-header seen from the top, containing pins useable for general purpose I/O. Colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs2.gif Source] ]]

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.

The Raspberry Pi allows peripherals and expansion boards (such as the [[Rpi Gertboard]]) to access the CPU by exposing the inputs and outputs.

For further general information about GPIOs, see: [http://en.wikipedia.org/wiki/GPIO the wikipedia article].<BR>
For further specific information about the Raspberry Pi's BCM2835 GPIOs, see: [[RPi_BCM2835_GPIOs|this wiki article]].

The production Raspberry Pi board has a 26-pin 2.54 mm (100 mil)<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907</ref> expansion header, marked as P1, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I²C, SPI, UART), as well as +3.3 V, +5 V and GND supply lines. Pin one is the pin in the first column and on the bottom row. <ref>http://www.raspberrypi.org/archives/384</ref>

[[File:RPi_P1_header.png]]

'''GPIO voltage levels are 3.3 V and are not 5 V 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.

All the GPIO pins can be reconfigured to provide alternate functions, SPI, [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM], I²C and so. At reset only pins GPIO 14 & 15 are assigned to the alternate function UART, these two can be switched back to GPIO to provide a total of 17 GPIO pins<ref>http://www.raspberrypi.org/archives/384</ref>. Each of their functions and full details of how to access are detailed in the chipset datasheet <ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref>.

Each GPIO can interrupt, high/low/rise/fall/change.<ref>http://www.raspberrypi.org/archives/384#comment-5217</ref><ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref> There is currently no support for GPIO interrupts in the official kernel, howewer a patch exists, requiring compilation of modified source tree.<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=44&t=7509</ref> The 'Raspbian "wheezy"' <ref>http://www.raspberrypi.org/downloads</ref> version that is currently recommended for starters already includes GPIO interrupts.

GPIO input hysteresis (Schmitt trigger) can be on or off, output slew rate can be fast or limited, and source and sink current is configurable from 2 mA up to 16 mA. Note that chipset GPIO pins 0-27 are in the same block and these properties are set per block, not per pin. See [http://www.scribd.com/doc/101830961/GPIO-Pads-Control2 GPIO Datasheet Addendum - GPIO Pads Control]. Particular attention should be applied to the note regarding SSO (Simultaneous Switching Outputs): to avoid interference, driving currents should be kept as low as possible.

The available [[RPi_BCM2835_GPIOs|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.

There is also some information on the [[RPi Tutorial Easy GPIO Hardware & Software|Tutorial on Easy GPIO Hardware & Software]].

Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200 bit/s.

'''R-Pi PCB Revision 2 UPDATE:''' According to Eben at [http://www.raspberrypi.org/archives/1929#comment-31646] the R-Pi Rev.2 board being rolled out starting in September 2012 adds 4 more GPIO on a new connector called P5, and changes some of the existing P1 GPIO pinouts. On Rev2, GPIO_GEN2 [BCM2835/GPIO27] is routed to P1 pin 13, and changes what was SCL0/SDA0 to SCL1/SDA1: SCL1 [BCM2835/GPIO3] is routed to P1 pin 5, SDA1 [BCM2835/GPIO2] is routed to P1 pin 3. Also the power and ground connections previously marked "Do Not Connect" on P1 will remain as connected, specifically: P1-04:+5V0, P1-09:GND, P1-14:GND, P1-17:+3V3, P1-20:GND, P1-25:GND. According to this comment [http://www.raspberrypi.org/archives/2081#comment-33577] (and confirmed in this post [http://www.raspberrypi.org/archives/2233]) the P1 pinout is not expected to change in future beyond the current Rev.2 layout.

'''Header Pinout, top row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-02 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-04 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-06 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
|-
| P1-08 || bgcolor="lime" | GPIO 14 || bgcolor="lime" | GPIO 14 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_TXD || ALT5 = UART1_TXD
|-
| P1-10 || bgcolor="lime" | GPIO 15 || bgcolor="lime" | GPIO 15 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_RXD || ALT5 = UART1_RXD
|-
| P1-12 || bgcolor="lime" | GPIO 18 || bgcolor="lime" | GPIO 18 || || PCM_CLK || ALT4 = SPI1_CE0_N ALT5 = PWM0
|-
| P1-14 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-16 || bgcolor="lime" | GPIO23 || bgcolor="lime" | GPIO23 || || || ALT3 = SD1_CMD ALT4 = ARM_RTCK
|-
| P1-18 || bgcolor="lime" | GPIO24 || bgcolor="lime" | GPIO24 || || || ALT3 = SD1_DAT0 ALT4 = ARM_TDO
|-
| P1-20 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-22 || bgcolor="lime" | GPIO25 || bgcolor="lime" | GPIO25 || || || ALT3 = SD1_DAT1 ALT4 = ARM_TCK
|-
| P1-24 || bgcolor="lime" | GPIO08 || bgcolor="lime" | GPIO08 || || bgcolor="purple" | <span style="color:white">SPI0_CE0_N</span> ||
|-
| P1-26 || bgcolor="lime" | GPIO07 || bgcolor="lime" | GPIO07 || || bgcolor="purple" | <span style="color:white">SPI0_CE1_N</span> ||
|}

'''Header Pinout, bottom row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-01 || bgcolor="orange" | 3.3 V ||bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-03 || bgcolor="lime" | GPIO 0 || bgcolor="lime" | '''GPIO 2'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SDA / '''I2C1_SDA''' ||
|-
| P1-05 || bgcolor="lime" | GPIO 1 || bgcolor="lime" | '''GPIO 3'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SCL / '''I2C1_SCL''' ||
|-
| P1-07 || bgcolor="lime" | GPIO 4 || bgcolor="lime" | GPIO 4 || || GPCLK0 || ALT5 = ARM_TDI
|-
| P1-09 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-11 || bgcolor="lime" | GPIO17 || bgcolor="lime" | GPIO17 || || ||| ALT3 = UART0_RTS ALT4 = SPI1_CE1_N ALT5 = UART1_RTS
|-
| P1-13 || bgcolor="lime" | GPIO21 || bgcolor="lime" | '''GPIO27''' || || PCM_DOUT / '''reserved''' || ALT4 = SPI1_SCLK ALT5 = GPCLK1 / '''ALT3 = SD1_DAT3 ALT4 = ARM_TMS'''
|-
| P1-15 || bgcolor="lime" | GPIO22 || bgcolor="lime" | GPIO22 || || || ALT3 = SD1_CLK ALT4 = ARM_TRST
|-
| P1-17 || bgcolor="orange" | 3.3 V || bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-19 || bgcolor="lime" | GPIO10 || bgcolor="lime" | GPIO10 || || bgcolor="purple" | <span style="color:white">SPI0_MOSI</span> ||
|-
| P1-21 || bgcolor="lime" | GPIO9 || bgcolor="lime" | GPIO9 || || bgcolor="purple" | <span style="color:white">SPI0_MISO</span> ||
|-
| P1-23 || bgcolor="lime" | GPIO11 || bgcolor="lime" | GPIO11 || || bgcolor="purple" | <span style="color:white">SPI0_SCLK</span> ||
|-
| P1-25 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|}

{| border="1"
! Colour legend
|-
| bgcolor="red" | <span style="color:white">+5 V</span>
|-
| bgcolor="orange" | +3.3 V
|-
| bgcolor="black" | <span style="color:white">Ground, 0V</span>
|-
| bgcolor="yellow" | UART
|-
| bgcolor="lime" | GPIO
|-
| bgcolor="purple" | <span style="color:white">SPI</span>
|-
| bgcolor="cyan" | I²C
|}

KiCad symbol: [[File:Conn-raspberry.lib]]

<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2</ref>

Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as an I²C interface. So there are 1.8 kilohm pulls up resistors on the board for these pins.<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480</ref>

Pin 12 supports [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM] .

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.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.1</ref> 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.

It is also possible to reconfigure GPIO connector pins P1-12 and 13 (chipset GPIO 18 and 21) to provide an I2S (a hardware modification may be required<ref name="I2S">[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?]</ref>) or PCM interface.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.2</ref> However, PCM_FS and PCM_DIN (chipset pins 19 and 20) are needed for I2S or PCM.

A second I²C 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.

===Referring to pins on the Expansion header===

The header is referred to as "The GPIO Connector (P1)". To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended.

* The expansion header is referred to as "Expansion Header" or "GPIO Connector (P1)"
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.
* Names GPIO0, GPIO1, GPIOx-ALTy, etc. refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where "x" matches BCM2835 number (without leading zero) and "y" 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 "GPIO7" to refer to a row of the table, and "GPIO7-ALT0" would refer to a specific cell of the table.
* 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 "SPI0_*" and "SPI1_*", but they didn't do the same on the I²C and UART pins. Instead of using "SDA0" and "SCL0", you should use "I2C0_SDA" and "I2C0_SCL"; and instead of "TX" or "TXD" and "RX" or "RXD", you should use "UART0_TXD" and "UART0_RXD".

===Power pins===
The maximum permitted current draw from the 3.3 V pins is 50 mA.

Maximum permitted current draw from the 5 V pin is the USB input current (usually 1 A) minus any current draw from the rest of the board.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1536#postid-21841</ref>
*Model A: 1000 mA - 500 mA -> max current draw: 500 mA
*Model B: 1000 mA - 700 mA -> max current draw: 300 mA
Be very careful with the 5 V pins P1-02 and P1-04, because if you short 5 V to any other P1 pin you may permanently damage your RasPi. Before probing P1, it's a good idea to strip short pieces of insulation off a wire and push them over the 5 V pins so you don't accidentally short them with a probe.

=== GPIO hardware hacking ===

The complete list of [[RPi_BCM2835_GPIOs|chipset GPIO pins]] which are available on the GPIO connector is: <blockquote>[[RPi_BCM2835_GPIOs#GPIO0|0]], [[RPi_BCM2835_GPIOs#GPIO1|1]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO21|21]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]]</blockquote>

(on the Revision2.0 RaspberryPis, this list changes to: [[RPi_BCM2835_GPIOs#GPIO2|2]], [[RPi_BCM2835_GPIOs#GPIO3|3]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]], [[RPi_BCM2835_GPIOs#GPIO27|27]], with [[RPi_BCM2835_GPIOs#GPIO28|28]], [[RPi_BCM2835_GPIOs#GPIO29|29]], [[RPi_BCM2835_GPIOs#GPIO30|30]], [[RPi_BCM2835_GPIOs#GPIO31|31]] additionally available on the [[#P5_header|P5 header]])

As noted above, P1-03 and P1-05 (SDA0 and SCL0 / SDA1 and SCL1) have 1.8 kilohm pull-up resistors to 3.3 V.

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:

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 3.3 V.

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.

There are a few other chipset GPIO pins accessible on the PCB but are in use:

* GPIO16 drives status LED D5 (usually SD card access indicator)
* GPIO28-31 are used by the board ID and are connected to resistors R3 to R10 (only on Rev1.0 boards).
* GPIO40 and 45 are used by analogue audio and support [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM]. They connect to the analogue audio circuitry via R21 and R27 respectively.
* GPIO46 is HDMI hotplug detect (goes to pin 6 of IC1).
* 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.

=== P2 header ===

The P2 header is the VideoCore JTAG and used only during the production of the board. It cannot be used as the ARM JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>. This connector is unpopulated in Rev 2.0 boards.

[[File:RPi_P2_header.png]]

Useful P2 pins:

* Pin 1 - 3.3V (same as P1-01, 50 mA max current draw across both of them)
* Pin 7 - GND
* Pin 8 - GND

=== P3 header ===

The P3 header, unpopulated, is the LAN9512 JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>.

[[File:RPi_P3_header.png]]

Useful P3 pins:

* Pin 7 - GND

=== P5 header ===

The P5 header was added with the release of the Revision 2.0 PCB design.

[[File:RPi_P5_header.png]]

'''P5 Pinout, seen from the bottom of the board:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P5-01 || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P5-02 || bgcolor="orange" | 3.3 V || 50 mA max (combined with P1)
|-
| P5-03 || bgcolor="lime" | GPIO28 || || bgcolor="cyan" | I2C0_SDA || ALT2 = PCM_CLK
|-
| P5-04 || bgcolor="lime" | GPIO29 || || bgcolor="cyan" | I2C0_SCL || ALT2 = PCM_FS
|-
| P5-05 || bgcolor="lime" | GPIO30 || || || ALT2 = PCM_DIN ALT3 = UART0_CTS ALT5 = UART1_CTS
|-
| P5-06 || bgcolor="lime" | GPIO31 || || || ALT2 = PCM_DOUT ALT3 = UART0_RTS ALT5 = UART1_RTS
|-
| P5-07 || bgcolor="black" | <span style="color:white">GND</span>
|-
| P5-08 || bgcolor="black" | <span style="color:white">GND</span>
|}

Note that the connector is intended to be mounted on the '''bottom''' of the PCB, so that for those who put the connector on the top side, the pin numbers are swapped. Pin 1 and pin 2 are swapped, pin 3 and 4, etc.

The new header can provide a second I2C channel (SDA + SCL) and handshake lines for the existing UART (TxD and RxD), or it can be used for an I2S (audio codec chip) interface using the PCM signals CLK, FS (Frame Sync), Din and Dout.

Note that the connector is placed JUST off-grid with respect to the P1 connector.

=== P6 header ===

The P6 header was added with the release of the Revision 2.0 PCB design.

[[File:RPi_P6_header.png]]

'''P6 Pinout:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev2''' || '''Hardware Notes'''
|-
| P6-01 || RUN || Short to ground to reset the BCM2835
|-
| P6-02 || bgcolor="black" | <span style="color:white">GND</span>
|}

[http://raspi.tv/2012/making-a-reset-switch-for-your-rev-2-raspberry-pi A reset button can be attached to the P6 header], with which the Pi can be reset.
Momentarily shorting the two pins of P6 together will cause a soft reset of the CPU.

===Driver support===

The Foundation will not include a GPIO driver in the initial release, standard Linux GPIO drivers should work with minimal modification.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1278.0</ref>

The community implemented SPI and I²C drivers <ref>http://www.bootc.net/projects/raspberry-pi-kernel/</ref>, which will be integrated with the new Linux pinctrl concept in a later version of the kernel. (On Oct. 14 2012, it was already included in the latest raspbian image.) A first compiled version as Linux modules is available to install on the 19/04/2012 Debian image, including 1-wire support<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=86172#p86172</ref>. The I²C and SPI driver uses the hardware modules of the microcontroller and interrupts for low CPU usage, the 1-wire support uses bitbanging on the GPIO ports, which results in higher CPU usage.

GordonH<ref>http://www.raspberrypi.org/forum/general-discussion/wiring-for-the-raspberry-pis-gpio</ref> wrote a (mostly) Arduino compatible/style [https://projects.drogon.net/raspberry-pi/wiringpi/ WiringPi library] in C for controlling the GPIO pins.

A useful tutorial on setting up I²C driver support can be found at [http://www.robot-electronics.co.uk/htm/raspberry_pi_examples.htm Robot Electronics] - look for the downloadable document rpi_i2c_setup.doc

===Graphical User Interfaces===
====WebIOPi====
[http://code.google.com/p/webiopi/ WebIOPi] allows you to control each GPIO with a simple web interface that you can use with any browser. Available in PHP and Python, they both require root access, but Python version serves HTTP itself. You can setup each GPIO as input or output and change their states (LOW/HIGH). WebIOPi is fully customizable, so you can use it for home remote control. It also work over Internet. UART/SPI/I2C support will be added later. If you need some computing for your GPIO go to code examples below.

==GPIO Code examples==
=== C ===
Examples in different C-Languages.
==== C ====
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo & Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)
Example GPIO code:

<pre>
//
// How to access GPIO registers from C-code on the Raspberry-Pi
// Example program
// 15-January-2012
// Dom and Gert
// Revised: 15-Feb-2013

// Access from ARM Running Linux

#define BCM2708_PERI_BASE 0x20000000
#define GPIO_BASE (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/mman.h>
#include <unistd.h>

#define PAGE_SIZE (4*1024)
#define BLOCK_SIZE (4*1024)

int mem_fd;
void *gpio_map;

// I/O access
volatile unsigned *gpio;

// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)
#define INP_GPIO(g) *(gpio+((g)/10)) &= ~(7<<(((g)%10)*3))
#define OUT_GPIO(g) *(gpio+((g)/10)) |= (1<<(((g)%10)*3))
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)<=3?(a)+4:(a)==4?3:2)<<(((g)%10)*3))

#define GPIO_SET *(gpio+7) // sets bits which are 1 ignores bits which are 0
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0

void setup_io();

int main(int argc, char **argv)
{
int g,rep;

// Set up gpi pointer for direct register access
setup_io();

// Switch GPIO 7..11 to output mode

/************************************************************************\
* You are about to change the GPIO settings of your computer. *
* Mess this up and it will stop working! *
* It might be a good idea to 'sync' before running this program *
* so at least you still have your code changes written to the SD-card! *
\************************************************************************/

// Set GPIO pins 7-11 to output
for (g=7; g<=11; g++)
{
INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO
OUT_GPIO(g);
}

for (rep=0; rep<10; rep++)
{
for (g=7; g<=11; g++)
{
GPIO_SET = 1<<g;
sleep(1);
}
for (g=7; g<=11; g++)
{
GPIO_CLR = 1<<g;
sleep(1);
}
}

return 0;

} // main

//
// Set up a memory regions to access GPIO
//
void setup_io()
{
/* open /dev/mem */
if ((mem_fd = open("/dev/mem", O_RDWR|O_SYNC) ) < 0) {
printf("can't open /dev/mem \n");
exit(-1);
}

/* mmap GPIO */
gpio_map = mmap(
NULL, //Any adddress in our space will do
BLOCK_SIZE, //Map length
PROT_READ|PROT_WRITE,// Enable reading & writting to mapped memory
MAP_SHARED, //Shared with other processes
mem_fd, //File to map
GPIO_BASE //Offset to GPIO peripheral
);

close(mem_fd); //No need to keep mem_fd open after mmap

if (gpio_map == MAP_FAILED) {
printf("mmap error %d\n", (int)gpio_map);//errno also set!
exit(-1);
}

// Always use volatile pointer!
gpio = (volatile unsigned *)gpio_map;

} // setup_io

</pre>

===== GPIO Pull Up/Pull Down Register Example =====
<pre>
// enable pull-up on GPIO24&25
GPIO_PULL = 2;
short_wait();
// clock on GPIO 24 & 25 (bit 24 & 25 set)
GPIO_PULLCLK0 = 0x03000000;
short_wait();
GPIO_PULL = 0;
GPIO_PULLCLK0 = 0;
</pre>

==== C + wiringPi ====
Get and install wiringPi: https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/

Save this, and compile with:
<pre>
gcc -o blink blink.c -lwiringPi
</pre>
and run with:
<pre>
sudo ./blink
</pre>

<pre>
/*
* blink.c:
* blinks the first LED
* Gordon Henderson, projects@drogon.net
*/

#include <stdio.h>
#include <wiringPi.h>

int main (void)
{
printf ("Raspberry Pi blink\n") ;

if (wiringPiSetup () == -1)
return 1 ;

pinMode (0, OUTPUT) ; // aka BCM_GPIO pin 17

for (;;)
{
digitalWrite (0, 1) ; // On
delay (500) ; // mS
digitalWrite (0, 0) ; // Off
delay (500) ;
}
return 0 ;
}
</pre>

==== C ====
This must be done as root. To change to the root user:
<pre>sudo -i</pre>
You must also get and install the bcm2835 library, which supports
GPIO and SPI interfaces. Details and downloads
from http://www.open.com.au/mikem/bcm2835

<pre>

// blink.c
//
// Example program for bcm2835 library
// Blinks a pin on an off every 0.5 secs
//
// After installing bcm2835, you can build this
// with something like:
// gcc -o blink -l rt blink.c -l bcm2835
// sudo ./blink
//
// Or you can test it before installing with:
// gcc -o blink -l rt -I ../../src ../../src/bcm2835.c blink.c
// sudo ./blink
//
// Author: Mike McCauley (mikem@open.com.au)
// Copyright (C) 2011 Mike McCauley
// $Id: RF22.h,v 1.21 2012/05/30 01:51:25 mikem Exp $

#include <bcm2835.h>

// Blinks on RPi pin GPIO 11
#define PIN RPI_GPIO_P1_11

int main(int argc, char **argv)
{
// If you call this, it will not actually access the GPIO
// Use for testing
// bcm2835_set_debug(1);

if (!bcm2835_init())
return 1;

// Set the pin to be an output
bcm2835_gpio_fsel(PIN, BCM2835_GPIO_FSEL_OUTP);

// Blink
while (1)
{
// Turn it on
bcm2835_gpio_write(PIN, HIGH);

// wait a bit
delay(500);

// turn it off
bcm2835_gpio_write(PIN, LOW);

// wait a bit
delay(500);
}

return 0;
}
</pre>

==== C# ====
RaspberryPiDotNet library is available at https://github.com/cypherkey/RaspberryPi.Net/.
The library includes a GPIOFile and GPIOMem class. The GPIOMem requires compiling Mike McCauley's bcm2835 library above in to a shared object.

<pre>
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using RaspberryPiDotNet;
using System.Threading;

namespace RaspPi
{
class Program
{
static void Main(string[] args)
{
// Access the GPIO pin using a static method
GPIOFile.Write(GPIO.GPIOPins.GPIO00, true);

// Create a new GPIO object
GPIOMem gpio = new GPIOMem(GPIO.GPIOPins.GPIO01);
gpio.Write(false);
}
}
}
</pre>

=== Ruby ===

This example uses the WiringPi Ruby Gem: http://pi.gadgetoid.co.uk/post/015-wiringpi-now-with-serial which you can install on your Pi with "gem install wiringpi"

<pre>
MY_PIN = 1

require 'wiringpi'
io = WiringPi::GPIO.new
io.mode(MY_PIN,OUTPUT)
io.write(MY_PIN,HIGH)
io.read(MY_PIN)
</pre>

Alternatively the Pi Piper Gem (https://github.com/jwhitehorn/pi_piper) allows for event driven programming:

<pre>
require 'pi_piper'
include PiPiper

watch :pin => 23 do
puts "Pin changed from #{last_value} to #{value}"
end

PiPiper.wait
</pre>

=== Perl ===
This must be done as root. To change to the root user:
<pre>sudo su -</pre>
Supports GPIO and SPI interfaces.
You must also get and install the bcm2835 library. Details and downloads
from http://www.open.com.au/mikem/bcm2835
You must then get and install the Device::BCM2835 perl library from CPAN
http://search.cpan.org/~mikem/Device-BCM2835-1.0/lib/Device/BCM2835.pm
<pre>
use Device::BCM2835;
use strict;

# call set_debug(1) to do a non-destructive test on non-RPi hardware
#Device::BCM2835::set_debug(1);
Device::BCM2835::init()
|| die "Could not init library";

# Blink pin 11:
# Set RPi pin 11 to be an output
Device::BCM2835::gpio_fsel(&Device::BCM2835::RPI_GPIO_P1_11,
&Device::BCM2835::BCM2835_GPIO_FSEL_OUTP);

while (1)
{
# Turn it on
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 1);
Device::BCM2835::delay(500); # Milliseconds
# Turn it off
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 0);
Device::BCM2835::delay(500); # Milliseconds
}

</pre>

=== Python ===
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO
Any Python script that controls GPIO must be run as root.
<pre>import RPi.GPIO as GPIO

# Set up the GPIO channels - one input and one output
GPIO.setup(11, GPIO.IN)
GPIO.setup(12, GPIO.OUT)

# Input from pin 11
input_value = GPIO.input(11)

# Output to pin 12
GPIO.output(12, True)

# The same script as above but using BCM GPIO 00..nn numbers
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.IN)
GPIO.setup(18, GPIO.OUT)
input_value = GPIO.input(17)
GPIO.output(18, True)</pre>

=== Java ===
==== Java using the Pi4J Library ====
This uses the Java library available at http://www.pi4j.com/.
(Any Java application that controls GPIO must be run as root.)

Please note that the Pi4J library uses the WiringPi GPIO pin numbering scheme <ref>http://pi4j.com/usage.html#Pin_Numbering</ref> <ref>https://projects.drogon.net/raspberry-pi/wiringpi/pins/</ref>. Please see the usage documentation for more details: http://pi4j.com/usage.html

<pre>

public static void main(String[] args) {

// create gpio controller
GpioController gpio = GpioFactory.getInstance();

// provision gpio pin #01 as an output pin and turn off
GpioPinDigitalOutput outputPin = gpio.provisionDigitalOutputPin(RaspiPin.GPIO_01, "MyLED", PinState.LOW);

// turn output to LOW/OFF state
outputPin.low();

// turn output to HIGH/ON state
outputPin.high();

// provision gpio pin #02 as an input pin with its internal pull down resistor enabled
GpioPinDigitalInput inputPin = gpio.provisionDigitalInputPin(RaspiPin.GPIO_02, "MyButton", PinPullResistance.PULL_DOWN);

// get input state from pin 2
boolean input_value = inputPin.isHigh();
}
</pre>

More complete and detailed examples are included on the Pi4J website at http://www.pi4j.com/.

The Pi4J library includes support for:
* GPIO Control
* GPIO Listeners
* Serial Communication
* I2C Communication
* SPI Communication

==== Java ====
This uses the Java library available at https://github.com/jkransen/framboos. It does not depend on (or use) the wiringPi driver, but uses the same numbering scheme. Instead it uses the default driver under /sys/class/gpio that ships with the distro, so it works out of the box. Any Java application that controls GPIO must be run as root.
<pre>
public static void main(String[] args) {
// reading from an in pin
InPin button = new InPin(8);
boolean isButtonPressed = button.getValue();
button.close();

// writing to an out pin
OutPin led = new Outpin(0);
led.setValue(true);
led.setValue(false);
led.close();
}
</pre>

==== Java Webapp GPIO web control via http ====
This uses the Java Webapp available at https://bitbucket.org/sbub/raspberry-pi-gpio-web-control/overview. You can control your GPIO over the internet. Any Java application that controls GPIO must be run as root.
<pre>

host:~ sb$ curl 'http://raspberrypi:8080/handle?g0=1&g1=0'
{"g1":0,"g0":1}

</pre>

=== Bash shell script, using sysfs, part of the raspbian operating system ===
The export and unexport of pins must be done as root.
To change to the root user see below: To change back, the word exit must be entered.
<pre>sudo -i</pre>
Export creates a new folder for the exported pin, and creates files for each of its control functions (i.e. active_low, direction, edge, power, subsystem, uevent, and value). Upon creation, the control files can be read by all users (not just root), but can only be written to by user root, the file's owner. Nevertheless, once created, it is possible to allow users other than root, to also write inputs to the control files, by changing the ownership or permissions of these files. Changes to the file's ownership or permissions must initially be done as root, as their owner and group is set to root upon creation. Typically you might change the owner to be the (non root) user controlling the GPIO, or you might add write permission, and change the group ownership to one of which the user controlling the GPIO is a member. By such means, using only packages provided in the recommended rasbian distribution, it is possible for Python CGI scripts, which are typically run as user nobody, to be used for control of the GPIO over the internet from a browser at a remote location.
<pre>
#!/bin/sh

# GPIO numbers should be from this list
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25

# Note that the GPIO numbers that you program here refer to the pins
# of the BCM2835 and *not* the numbers on the pin header.
# So, if you want to activate GPIO7 on the header you should be
# using GPIO4 in this script. Likewise if you want to activate GPIO0
# on the header you should be using GPIO17 here.

# Set up GPIO 4 and set to output
echo "4" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio4/direction

# Set up GPIO 7 and set to input
echo "7" > /sys/class/gpio/export
echo "in" > /sys/class/gpio/gpio7/direction

# Write output
echo "1" > /sys/class/gpio/gpio4/value

# Read from input
cat /sys/class/gpio/gpio7/value

# Clean up
echo "4" > /sys/class/gpio/unexport
echo "7" > /sys/class/gpio/unexport
</pre>

=== Shell script - take 2 ===
You need the wiringPi library from
https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/. Once installed, there is a new command '''gpio''' which can be used
as a '''non-root''' user to control the GPIO pins.

The man page <pre>man gpio</pre> has full details, but briefly:

<pre>
gpio -g mode 17 out
gpio -g mode 18 pwm

gpio -g write 17 1
gpio -g pwm 18 512
</pre>

The '''-g''' flag tells the '''gpio''' program to use the BCM GPIO pin numbering
scheme (otherwise it will use the wiringPi numbering scheme by default).

The gpio command can also control the internal pull-up and pull-down
resistors:

<pre>
gpio -g mode 17 up
</pre>

This sets the pull-up resistor - however any change of mode, even
setting a pin that's already set as an input to an input will remove
the pull-up/pull-down resistors, so they may need to be reset.

Additionally, it can export/un-export the GPIO devices for use by
other non-root programms - e.g. Python scripts. (Although you
may need to drop the calls to GPIO.Setup() in the Python scripts, and
do the setup separately in a little shell script, or call the '''gpio''' program
from inside Python).

<pre>
gpio export 17 out
gpio export 18 in
</pre>

These exports GPIO-17 and sets it to output, and exports GPIO-18
and sets it to input.

And when done:

<pre>
gpio unexport 17
</pre>

The export/unexport commands always use the BCM GPIO pin numbers regardless of the
presence of the '''-g''' flag or not.

If you want to use the internal pull-up/down's with the /sys/class/gpio mechanisms,
then you can set them after exporting them. So:

<pre>
gpio -g export 4 in
gpio -g mode 4 up
</pre>

You can then use GPIO-4 as an input in your Python, Shell, Java, etc. programs without the use
of an external resistor to pull the pin high. (If that's what you were after - for example, a simple push
button switch taking the pin to ground.)

A fully working example of a shell script using the GPIO pins
can be found at http://project-downloads.drogon.net/files/gpioExamples/tuxx.sh.

=== Lazarus / Free Pascal ===
[[File:RPI GPIO testprogram with lazarus.png|thumb|254px|right|A simple app for controlling GPIO pin 17 with Lazarus]]

The GPIO pins are accessible from [[Lazarus on RPi|Lazarus]] without any third-party software. This is performed by means of the [http://www.freepascal.org/docs-html/rtl/baseunix/index.html BaseUnix] unit that is part of every distribution of Lazarus and Free Pascal or by invoking Unix shell commands with '''fpsystem'''. The following example uses GPIO pin 17 as output port. It is assumed that you created a form with a TToggleBox named GPIO17ToggleBox and for logging purposes a TMemo with name LogMemo (optional). The program has to be executed with root privileges.

''Unit for controlling the GPIO port:''
<pre>
unit Unit1;

{Demo application for GPIO on Raspberry Pi}
{Inspired by the Python input/output demo application by Gareth Halfacree}
{written for the Raspberry Pi User Guide, ISBN 978-1-118-46446-5}

{$mode objfpc}{$H+}

interface

uses
Classes, SysUtils, FileUtil, Forms, Controls, Graphics, Dialogs, StdCtrls,
Unix, BaseUnix;

type

{ TForm1 }

TForm1 = class(TForm)
LogMemo: TMemo;
GPIO17ToggleBox: TToggleBox;
procedure FormActivate(Sender: TObject);
procedure FormClose(Sender: TObject; var CloseAction: TCloseAction);
procedure GPIO17ToggleBoxChange(Sender: TObject);
private
{ private declarations }
public
{ public declarations }
end;

const
PIN_17: PChar = '17';
PIN_ON: PChar = '1';
PIN_OFF: PChar = '0';
OUT_DIRECTION: PChar = 'out';

var
Form1: TForm1;
gReturnCode: longint; {stores the result of the IO operation}

implementation

{$R *.lfm}

{ TForm1 }

procedure TForm1.FormActivate(Sender: TObject);
var
fileDesc: integer;
begin
{ Prepare SoC pin 17 (pin 11 on GPIO port) for access: }
try
fileDesc := fpopen('/sys/class/gpio/export', O_WrOnly);
gReturnCode := fpwrite(fileDesc, PIN_17[0], 2);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
{ Set SoC pin 17 as output: }
try
fileDesc := fpopen('/sys/class/gpio/gpio17/direction', O_WrOnly);
gReturnCode := fpwrite(fileDesc, OUT_DIRECTION[0], 3);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;

procedure TForm1.FormClose(Sender: TObject; var CloseAction: TCloseAction);
var
fileDesc: integer;
begin
{ Free SoC pin 17: }
try
fileDesc := fpopen('/sys/class/gpio/unexport', O_WrOnly);
gReturnCode := fpwrite(fileDesc, PIN_17[0], 2);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;

procedure TForm1.GPIO17ToggleBoxChange(Sender: TObject);
var
fileDesc: integer;
begin
if GPIO17ToggleBox.Checked then
begin
{ Swith SoC pin 17 on: }
try
fileDesc := fpopen('/sys/class/gpio/gpio17/value', O_WrOnly);
gReturnCode := fpwrite(fileDesc, PIN_ON[0], 1);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end
else
begin
{ Switch SoC pin 17 off: }
try
fileDesc := fpopen('/sys/class/gpio/gpio17/value', O_WrOnly);
gReturnCode := fpwrite(fileDesc, PIN_OFF[0], 1);
LogMemo.Lines.Add(IntToStr(gReturnCode));
finally
gReturnCode := fpclose(fileDesc);
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;
end;

end.
</pre>

''Main program:''
<pre>
program io_test;

{$mode objfpc}{$H+}

uses
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Interfaces, // this includes the LCL widgetset
Forms, Unit1
{ you can add units after this };

{$R *.res}

begin
Application.Initialize;
Application.CreateForm(TForm1, Form1);
Application.Run;
end.
</pre>

An alternative way to access the GPIO port with Lazarus / Free Pascal is by using [http://www.lazarus.freepascal.org/index.php/topic,17404.0.html Lazarus wrapper unit for Gordon Henderson's wiringPi C library].

=== BASIC ===
==== BASIC - Return to BASIC ====

'''RTB''' or Return to Basic can be found here: https://projects.drogon.net/return-to-basic/

It's a new BASIC featuring modern looping constructs, switch statements, named procedures and functions as well as graphics (caresian and turtle), file handling and more. It also supports the Pi's on-board GPIO without needing to be run as root. (You don't need any special setup routines either)

Sample blink program:

<pre>
// blink.rtb:
// Blink program in Return to Basic
// Gordon Henderson, projects@drogon.net
//
PinMode (0, 1) // Output
CYCLE
DigitalWrite (0, 1) // Pin 0 ON
WAIT (0.5) // 0.5 seconds
DigitalWrite (0, 0)
WAIT (0.5)
REPEAT
END
</pre>

==== BASIC ====

'''Bywater BASIC Interpreter'''

The Bywater BASIC Interpreter (bwBASIC) implements a large superset of the ANSI Standard for Minimal BASIC (X3.60-1978) and a significant subset of the ANSI Standard for Full BASIC (X3.113-1987) in C. It also offers shell programming facilities as an extension of BASIC. bwBASIC seeks to be as portable as possible.
You can download it at.
http://packages.debian.org/stable/interpreters/bwbasic

'''BASIC programming of the I/O'''

'''Setting up a GPIO pin to be used for inputs or for outputs.'''

We cannot load the control words directly into the 32 bit ARM registers with 32 bit addresses, as bwBASIC has no POKE and PEEK commands and other versions of BASIC (as far as I know) only handle 8 bit registers with 16 bit addresses with these commands. So we need to export the GPIO pins, so that they exist in a file structure which we can access from basic with the OPEN command.(ref 2)

We need to do this in Linux root.
We need to run BASIC in the root too. First we go to the root, then we load bwbasic into root.
<pre>
sudo -1
sudo bwbasic
</pre>

REM Now to export the no4 GPIO pin for example, using a Shell command.

<pre>echo “4” > /sys/class/gpio/export</pre>

Whilst bwbasic can accommodate shell commands, and we can store a set of these commands (eg. to export a number of GPIO pins at the outset) as numbered statements in a file that can be loaded with the basic command LOAD “filename” and RUN (ref 2), the shell commands have to run as a separate file, as they cannot be run from within, as part of a basic programme.

'''Now we can access the file containing the pin direction setting from BASIC'''

We can set GPIO pin 4 to input or to output by OPENing its pin direction file for output and writing “in” or “out” with a PRINT# command. (ref 2 )
<syntaxhighlight lang="basic4gl">
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 PRINT #1,”out”
30 CLOSE #1
</syntaxhighlight>

REM closes the open direction file, whereupon the system performs the action of setting the direction to “out”. NB the system only carries out the action as the file is closed.(ref 3)

'''We are now able to control the output of the gpio 4 pin from BASIC'''

We can set the GPIO 4 pin to 1 or to 0 by OPENing its pin value file for output and writing “1” or “0” with a PRINT# command.
<syntaxhighlight lang="basic4gl">
40 OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
50 PRINT #4,”1”
60 CLOSE #4
</syntaxhighlight>

REM turns on the output of GPIO pin 4.

REM similarly we can turn off the output of GPIO pin 4.
OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
PRINT #4,”0”
CLOSE #4.

'''Example of an (unstructured) BASIC programme'''

To read the state of a switch and control the power to two LEDs connected to GPIO pins 8,7 and 4 respectively.

Programme to set 2 pins as outputs and 1 pin as input and to read the input turning on two different combinations of the two outputs (ie output 0,1 or 1,0) depending on the state of the input (1 or 0).
<syntaxhighlight lang="basic4gl">
sudo –i
sudo bwbasic
LOAD “export.bas”
LIST
REM a set of Shell statements to export the three GPIO pins.
10 echo “4” > /sys/class/gpio/export
20 echo “7” > /sys/class/gpio/export
30 echo “8” > /sys/class/gpio/export
RUN
</syntaxhighlight>

NEW REM clears the export.bas programme from memory
<syntaxhighlight lang="basic4gl">
.
LOAD “demo1.bas”
LIST
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 OPEN ”O”,#2, “/sys/devices/virtual/gpio/gpio7/direction”,2
30 OPEN ”O”,#3, “/sys/devices/virtual/gpio/gpio8/direction”,2
REM opens the three pin direction files
40 PRINT #1, “out”
50 PRINT #2, “out”
60 PRINT #3, “in”
REM sets GPIO pins 4 and 7 as outputs and GPIO pin 8 as input.
70 CLOSE #1
80 CLOSE #2
90 CLOSE #3
REM closes all open files, allowing the system to perform the direction settings.
100 OPEN ”I”,#8, “/sys/devices/virtual/gpio/gpio8/value”,1
REM opens the GPIO pin 8 value file
110 INPUT #8,x
REM reads the value of the input pin and stores the value in numerical variable x
120 CLOSE #8
REM closes the open file, allowing the system to read the value of the input pin and store the value in numerical variable x.
130 OPEN “O”,#1, “/sys/devices/virtual/gpio/gpio4/value”,1
140 OPEN “O”,#2, “/sys/devices/virtual/gpio/gpio7/value”,1
REM opens the GPIO pins 4 and value files ready for outputting 1s and 0s.
150 IF x<1 THEN GOTO 160 ELSE GOTO 190
REM tests the state of the switch (1 or0) and directs the program to generate the appropriate outputs
160 PRINT #1,”1”
170 PRINT #2,”0”
180 GOTO 210
190 PRINT#1,"0"
200 PRINT #2,"1"
210 CLOSE #1
220 CLOSE #2
REM Closes the files and allows the outputs to light the LED
230 END.
</syntaxhighlight>

When all is done, we should unexport the GPIO pins, to leave the R-Pi as we found it.(Ref 1.)
<syntaxhighlight lang="basic4gl">
NEW
LOAD “unexport.bas”
LIST
REM a set of Shell statements to unexport the three GPIO pins.
10 echo “4” > /sys/class/gpio/unexport
20 echo “7” > /sys/class/gpio/unexport
30 echo “8” > /sys/class/gpio/unexport
RUN
</syntaxhighlight>
A simple circuit to provide the switched input and the two LED outputs.

Ancient Mariner. Dec. 2012

References.

1. This paper RPi Low-level peripherals.

2. Ed Beynon. [http://www.ybw.com/forums/showthread.php?t=331320&page=5 http://www.ybw.com/forums/showthread.php?t=331320&page=5]

3. Arthur Kaletzky. Private communication. 25/10/2012

4. bwbasic manual.<br/>

For the two original documents this example has been copied from see:<br/>
[[Media:GPIO_Driving_Example_(BASIC)_.doc | GPIO_Driving_Example_(BASIC)_.doc]]

[[Media:Raspberry_Pi_I-O_viii.doc | Raspberry_Pi_I-O_viii.doc]]

==MIPI CSI-2==

On the production board<ref>http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf</ref>, the Raspberry Pi Foundation design brings out the MIPI CSI-2 (Camera Serial Interface<ref>http://www.mipi.org/specifications/camera-interface</ref>) to a 15-way flat flex connector S5, between the Ethernet and HDMI connectors. A compatible camera has been discussed as working in tests and is planned for release at a later date.<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/complex-camera-peripherials#p72602</ref>.


==DSI==

On the production board, the Raspberry Pi Foundation design brings out the DSI (Display Serial Interface<ref>http://www.mipi.org/specifications/display-interface</ref>) to a 15-way flat flex connector labelled S2, next to Raspberry Pi logo. It has two data lanes and a clock lane, to drive a possible future LCD screen device. Some smart phone screens use DSI<ref>http://en.wikipedia.org/wiki/Display_Serial_Interface</ref>.

==CEC==

[[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.
Eben notes that he has seen CEC demos on the Broadcom SoC they are using.

libCEC with Raspberry Pi support has been included in OpenELEC and will be included in Raspbmc RC4.<ref>http://blog.pulse-eight.com/2012/08/01/libcec-1-8-0-a-firmware-upgrade-and-raspberry-pi-support/</ref>

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.

== References ==
<references/>

{{Template:Raspberry Pi}}

File:RPi P6 header.png

2013-03-10T19:51:03Z

AndrewS: The P6 header on the RaspberryPi, showing the orientation of the pin numbers Category:RaspberryPi

The P6 header on the RaspberryPi, showing the orientation of the pin numbers

[[Category:RaspberryPi]]

File:RPi P5 header.png

2013-03-10T19:50:23Z

AndrewS: The P5 header on the RaspberryPi, showing the orientation of the pin numbers Category:RaspberryPi

The P5 header on the RaspberryPi, showing the orientation of the pin numbers

[[Category:RaspberryPi]]

RPi VideoCore APIs

2013-03-10T15:51:47Z

AndrewS: Updated image to reflect the current state of affairs

{{Template:RPi_Software}}

[[File:VideoCore-Architecture-and-Source.png|500px|thumb|Source: http://www.raspberrypi.org/wp-content/uploads/2012/10/Architecture-and-Source.png]]

The Raspberry Pi contains 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.

Currently C header files and libraries for many of the Broadcom APIs are located in <code>/opt/vc/include</code> and <code>/opt/vc/lib</code> respectively, or available from [https://github.com/raspberrypi/firmware GitHub] within the same directory structure. Some documentation is contained within comments in the header files, as well as documentation for the OpenMAX IL components in the [https://github.com/raspberrypi/firmware/tree/master/documentation/ilcomponents documentation directory on Github], however it is severely lacking and difficult to understand in a general sense for people wanting to experiment with the device due to it being proprietary. As such, we encourage you to [http://elinux.org/index.php?title=RPi_VideoCore_APIs&action=edit edit this page] to help us build a much better open documentation.

==Quirks==

* The Raspberry Pi requires that the <code>bcm_host_init()</code> function is called first before any GPU calls can be made.
* Before calling any of the vc_* functions, you need to initialise vcos and vchi, and make a vchi connection, before then calling the corresponding vc_*_init function for the part of the library you want to use: <code>vc_vchi_dispmanx_init</code>, <code>vc_vchi_tv_init</code>, <code>vc_vchi_cec_init</code> or <code>vc_vchi_gencmd_init</code>.<br />(See this [https://github.com/adammw/rpi-output-swapper/blob/master/video_swap.c#L152-169 sample code] which does initialisation for vc_tvservice_* APIs)
* Linking against the EGL library (-lEGL) also requires you to link against the GLESv2 library (-lGLESv2).
* <code>[[#graphics_get_display_size|graphics_get_display_size()]]</code> is a broadcom-specific function

== Built-in Sample Programs==
The Raspberry Pi comes with 7 sample programs and two helper libraries in the /opt/vc/src/hello_pi directory showing some of the system's capabilities and sample code.
===hello_encode===
This sample is a GPU-assisted h.264 encoder using the OpenMAX APIs , and currently
works with raw frames. It outputs a raw h.264 file.

===hello_video===
This sample decodes h264 video using the OpenMAX APIs and the ilclient library, and is distributed with a short scene of [http://www.bigbuckbunny.org/ Big Buck Bunny]
===hello_audio===
This sample plays a sine wave for ten seconds using the ??? APIs.
===hello_triangle===
This sample shows how to get a OpenGL ES context on the Raspberry Pi.
===ilclient helper library===
This library is described as:
<code>This API defines helper functions for writing IL clients.
*
* This file defines an IL client side library. This is useful when
* writing IL clients, since there tends to be much repeated and
* common code across both single and multiple clients. This library
* seeks to remove that common code and abstract some of the
* interactions with components. There is a wrapper around a
* component and tunnel, and some operations can be done on lists of
* these. The callbacks from components are handled, and specific
* events can be checked or waited for.
*/</code>

== Libraries ==
{| border="1"
| ''' The userland libraries have been [http://www.raspberrypi.org/archives/2221 open-sourced] ! Code can be found at [https://github.com/raspberrypi/userland github.com/raspberrypi/userland]'''
|}

=== libbcm_host ===
bcm_host is the Broadcom hardware interface library.

=== vc_dispmanx_*===
Dispmanx is a windowing system in the process of being deprecated in favour of [http://www.khronos.org/openwf/ OpenWF] (or similar), however dispmanx is still used in all API demos and it's replacement may not yet be available. <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5621&p=77981</ref>(confirmation required?)
=== vc_tvservice_* ===
These APIs allow controlling the HDMI and SDTV video outputs of the Raspberry Pi, as well as allowing the user to query the supported HDMI resolutions and audio formats and turn on/off copy protection. The Raspberry Pi can only have one output active at a time - turning on the HDMI automatically turns off the SDTV and vice-versa. However either can be turned off using the <code>vc_tv_power_off()</code> function.

The header file [https://github.com/raspberrypi/firmware/blob/master/opt/vc/include/interface/vmcs_host/vc_tvservice.h vc_tvservice.h] documents the functions quite well via comments above each prototype function, however before any of these functions will succeed you must initialise the connection to the host API like so:

void tvservice_init() {
VCHI_INSTANCE_T vchi_instance;
VCHI_CONNECTION_T *vchi_connections;

// initialise bcm_host
bcm_host_init();

// initialise vcos/vchi
vcos_init();
if (vchi_initialise(&vchi_instance) != VCHIQ_SUCCESS) {
fprintf(stderr, "failed to open vchiq instance\n");
exit(-2);
}

// create a vchi connection
if ( vchi_connect( NULL, 0, vchi_instance ) != 0) {
fprintf(stderr, "failed to connect to VCHI\n");
exit(-3);
}

// connect to tvservice
if ( vc_vchi_tv_init( vchi_instance, &vchi_connections, 1) != 0) {
fprintf(stderr, "failed to connect to tvservice\n");
exit(-4);
}
}

''TODO: Deinitialization''
==== Samples ====
* [https://github.com/adammw/rpi-output-swapper rpi-output-swapper] Uses tvservice apis to power on HDMI or SDTV display in specific or preferred mode.

=== vc_cec_* ===
The vc_cec APIs allow programs to interface with the [http://en.wikipedia.org/wiki/Consumer_Electronics_Control#CEC Consumer Electronics Control (CEC)] host middleware on the system to send CEC packets, set strings for the middleware to auto-respond to certain requests or override the middleware handling by adding custom callbacks.

''TODO: Samples/Howto''

=== vc_gencmd_* ===
''TODO''

=== EGL ===
[http://www.khronos.org/egl/ EGL (Native Platform Graphics Interface)] is an interface between Khronos rendering APIs such as OpenGL ES or OpenVG and the underlying native platform. The Raspberry Pi supports [http://www.khronos.org/registry/egl/specs/eglspec.1.4.20110406.pdf EGL Version 1.4] and the following EGL extensions (links are to EGL registry documentation):<ref name="egl-info">eglinfo, http://www.raspberrypi.org/phpBB3/viewtopic.php?p=35942#p35942 , http://www.raspberrypi.org/phpBB3/viewtopic.php?p=36318#p36318</ref>
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_image.txt EGL_KHR_image]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_image_base.txt EGL_KHR_image_base]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_image_pixmap.txt EGL_KHR_image_pixmap]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_vg_parent_image.txt EGL_KHR_vg_parent_image]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_gl_image.txt EGL_KHR_gl_texture_2D_image]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_gl_image.txt EGL_KHR_gl_texture_cubemap_image]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_lock_surface.txt EGL_KHR_lock_surface]

Creating an on-screen EGL rendering surface requires you to to use the eglCreateWindowSurface function, which takes a EGLNativeWindowType parameter. On the Raspberry Pi, this is implemented as a EGL_DISPMANX_WINDOW_T struct, which is defined in eglplatform.h as:

typedef struct {
DISPMANX_ELEMENT_HANDLE_T element;
int width; /* This is necessary because dispmanx elements are not queriable. */
int height;
} EGL_DISPMANX_WINDOW_T;

Therefore, to create a EGL surface you must also use the Dispmanx library to get a dispmanx element handle. The [https://github.com/raspberrypi/firmware/blob/master/opt/vc/src/hello_pi/hello_triangle/triangle.c#L147-173 hello_triangle source code] provides example code to do this.

==== Samples====

See [http://jonmacey.blogspot.com.au/2012/05/getting-started-with-egl-on-raspberry.html Getting Started with EGL] post by Jon Macey.
Extended documentation available in the [http://www.khronos.org/registry/egl/specs/eglspec.1.4.20110406.pdf EGL Version 1.4 Specification] and Simple Reference available in the [http://www.khronos.org/files/egl-1-4-quick-reference-card.pdf EGL 1.4 API Quick Reference Card].

==== Function Documentation====
====={{anchor|graphics_get_display_size}}<code>int32_t graphics_get_display_size( const uint16_t display_number, uint32_t *width, uint32_t *height);</code>=====

This function allows you to get the size of the display, and is often used in creating an EGL Surface. width and height are pointers that you pass in to where you want the response values to be written to, display number 0 is usually used for the Raspberry Pi. return value of >= 0 indicates success, <0 indicates failure.

This function is implemented in libbcm_host, and the implementation has been made [https://github.com/raspberrypi/firmware/issues/14#issuecomment-5652185 public] showing that it internally calls the vc_dispmanx_display_get_info function to get the width and height of the current mode.

Bugs present in early versions of the firmware caused this function to always return 1920x1080, however this can easily be fixed by updating the firmware with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update] (see the [[R-Pi_Troubleshooting#Updating_firmware|Updating firmware]] page for help).<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=68&t=8252</ref><ref>https://github.com/raspberrypi/firmware/issues/14</ref>

=== OpenGL ES ===
The Raspberry Pi supports OpenGL ES 2.0 with the following extensions: <ref name="egl-info" />
*GL_OES_compressed_ETC1_RGB8_texture
*GL_OES_compressed_paletted_texture
*GL_OES_texture_npot GL_OES_depth24
*GL_OES_vertex_half_float
*GL_OES_EGL_image
*GL_OES_EGL_image_external
*GL_EXT_discard_framebuffer
*GL_OES_rgb8_rgba8
*GL_OES_depth32
*GL_OES_mapbuffer
*GL_EXT_texture_format_BGRA8888
*GL_APPLE_rgb_422
*GL_EXT_debug_marker

''TODO: Sample of how to use/initalise OpenGL ES''

=== OpenVG ===
The Raspberry Pi supports OpenVG 1.1 for hardware-accelerated two-dimensional vector and raster graphics. See the full specification [http://www.khronos.org/registry/vg/specs/openvg-1.1.pdf here] or [http://www.khronos.org/files/openvg-quick-reference-card.pdf the API quick reference card].

==== Samples ====
* [http://docs.blackberry.com/en/developers/deliverables/17967/CS_Drawing_a_triangle_using_OpenVG_1241146_11.jsp Code sample: Drawing a triangle by using OpenVG] ''(Java implentation for RIM devices, however should be able to get a grasp on how it works and be able to port it to the Raspberry Pi)''

=== OpenMAX ===
See [https://github.com/raspberrypi/firmware/tree/master/documentation/ilcomponents /documentation/ilcomponents] on GitHub firmware repository for official documentation.

''TODO: Sample of how to use OpenMAX to decode audio/video/images, etc.''

== Bindings for Other Programming Languages ==
'''Python'''
* [https://bitbucket.org/bryancole/rpi_vid_core/ RPi_Vid_Core] - ''python bindings of EGL, OpenGL ES, OpenVG and bcm_host for Raspberry Pi implemented using Cython''
'''Java'''
* [http://www.jogamp.org JogAmp JOGL] - ''JogAmp JOGL Java bindings for EGL and OpenGL ES for Raspberry Pi implemented using Gluegen.
** Raspberry Pi autodetection is included in JogAmp JOGL RC11 and later. http://forum.jogamp.org/Release-v2-0-rc11-td4026703.html
* [http://www.lwjgl.org LWJGL] - http://www.raspberrypi.org/phpBB3/viewtopic.php?p=211087 Raspberry Pi community port by '''spsn'''

== Open Source Software compatible with the VideoCore APIs ==
* '''[https://github.com/huceke/omxplayer omxplayer]''' - ''a command line a/v player for the Raspberry Pi utilising the OpenMAX APIs and ffmpeg''
* '''[http://wiki.xbmc.org/index.php?title=Raspberry_Pi XBMC]''' - ''a media center, omxplayer's "big brother" ''
* '''[http://nccastaff.bournemouth.ac.uk/jmacey/GraphicsLib/piNGL/index.html piNGL]''' - ''port of the NGL graphics library to Raspberry Pi''
* '''[http://qt-project.org/wiki/Qt-RaspberryPi Qt on Pi]''' - ''Raspberry Pi port of the Qt toolkit''

==References==
<references/>

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

File:VideoCore-Architecture-and-Source.png

2013-03-10T15:46:34Z

AndrewS: The structure of the VideoCore driver stack Category:RaspberryPi

The structure of the VideoCore driver stack

[[Category:RaspberryPi]]

RPi VideoCore APIs

2013-03-10T15:39:20Z

AndrewS: /* Libraries */ Added link to open-sourcing announcement

{{Template:RPi_Software}}

[[File:Raspberrypi_video_API_03.svg|500px|thumb|Source: http://elinux.org/images/b/be/Raspberrypi_video_API_03.svg]]

The Raspberry Pi contains 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.

Currently C header files and libraries for many of the Broadcom APIs are located in <code>/opt/vc/include</code> and <code>/opt/vc/lib</code> respectively, or available from [https://github.com/raspberrypi/firmware GitHub] within the same directory structure. Some documentation is contained within comments in the header files, as well as documentation for the OpenMAX IL components in the [https://github.com/raspberrypi/firmware/tree/master/documentation/ilcomponents documentation directory on Github], however it is severely lacking and difficult to understand in a general sense for people wanting to experiment with the device due to it being proprietary. As such, we encourage you to [http://elinux.org/index.php?title=RPi_VideoCore_APIs&action=edit edit this page] to help us build a much better open documentation.

==Quirks==

* The Raspberry Pi requires that the <code>bcm_host_init()</code> function is called first before any GPU calls can be made.
* Before calling any of the vc_* functions, you need to initialise vcos and vchi, and make a vchi connection, before then calling the corresponding vc_*_init function for the part of the library you want to use: <code>vc_vchi_dispmanx_init</code>, <code>vc_vchi_tv_init</code>, <code>vc_vchi_cec_init</code> or <code>vc_vchi_gencmd_init</code>.<br />(See this [https://github.com/adammw/rpi-output-swapper/blob/master/video_swap.c#L152-169 sample code] which does initialisation for vc_tvservice_* APIs)
* Linking against the EGL library (-lEGL) also requires you to link against the GLESv2 library (-lGLESv2).
* <code>[[#graphics_get_display_size|graphics_get_display_size()]]</code> is a broadcom-specific function

== Built-in Sample Programs==
The Raspberry Pi comes with 7 sample programs and two helper libraries in the /opt/vc/src/hello_pi directory showing some of the system's capabilities and sample code.
===hello_encode===
This sample is a GPU-assisted h.264 encoder using the OpenMAX APIs , and currently
works with raw frames. It outputs a raw h.264 file.

===hello_video===
This sample decodes h264 video using the OpenMAX APIs and the ilclient library, and is distributed with a short scene of [http://www.bigbuckbunny.org/ Big Buck Bunny]
===hello_audio===
This sample plays a sine wave for ten seconds using the ??? APIs.
===hello_triangle===
This sample shows how to get a OpenGL ES context on the Raspberry Pi.
===ilclient helper library===
This library is described as:
<code>This API defines helper functions for writing IL clients.
*
* This file defines an IL client side library. This is useful when
* writing IL clients, since there tends to be much repeated and
* common code across both single and multiple clients. This library
* seeks to remove that common code and abstract some of the
* interactions with components. There is a wrapper around a
* component and tunnel, and some operations can be done on lists of
* these. The callbacks from components are handled, and specific
* events can be checked or waited for.
*/</code>

== Libraries ==
{| border="1"
| ''' The userland libraries have been [http://www.raspberrypi.org/archives/2221 open-sourced] ! Code can be found at [https://github.com/raspberrypi/userland github.com/raspberrypi/userland]'''
|}

=== libbcm_host ===
bcm_host is the Broadcom hardware interface library.

=== vc_dispmanx_*===
Dispmanx is a windowing system in the process of being deprecated in favour of [http://www.khronos.org/openwf/ OpenWF] (or similar), however dispmanx is still used in all API demos and it's replacement may not yet be available. <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?t=5621&p=77981</ref>(confirmation required?)
=== vc_tvservice_* ===
These APIs allow controlling the HDMI and SDTV video outputs of the Raspberry Pi, as well as allowing the user to query the supported HDMI resolutions and audio formats and turn on/off copy protection. The Raspberry Pi can only have one output active at a time - turning on the HDMI automatically turns off the SDTV and vice-versa. However either can be turned off using the <code>vc_tv_power_off()</code> function.

The header file [https://github.com/raspberrypi/firmware/blob/master/opt/vc/include/interface/vmcs_host/vc_tvservice.h vc_tvservice.h] documents the functions quite well via comments above each prototype function, however before any of these functions will succeed you must initialise the connection to the host API like so:

void tvservice_init() {
VCHI_INSTANCE_T vchi_instance;
VCHI_CONNECTION_T *vchi_connections;

// initialise bcm_host
bcm_host_init();

// initialise vcos/vchi
vcos_init();
if (vchi_initialise(&vchi_instance) != VCHIQ_SUCCESS) {
fprintf(stderr, "failed to open vchiq instance\n");
exit(-2);
}

// create a vchi connection
if ( vchi_connect( NULL, 0, vchi_instance ) != 0) {
fprintf(stderr, "failed to connect to VCHI\n");
exit(-3);
}

// connect to tvservice
if ( vc_vchi_tv_init( vchi_instance, &vchi_connections, 1) != 0) {
fprintf(stderr, "failed to connect to tvservice\n");
exit(-4);
}
}

''TODO: Deinitialization''
==== Samples ====
* [https://github.com/adammw/rpi-output-swapper rpi-output-swapper] Uses tvservice apis to power on HDMI or SDTV display in specific or preferred mode.

=== vc_cec_* ===
The vc_cec APIs allow programs to interface with the [http://en.wikipedia.org/wiki/Consumer_Electronics_Control#CEC Consumer Electronics Control (CEC)] host middleware on the system to send CEC packets, set strings for the middleware to auto-respond to certain requests or override the middleware handling by adding custom callbacks.

''TODO: Samples/Howto''

=== vc_gencmd_* ===
''TODO''

=== EGL ===
[http://www.khronos.org/egl/ EGL (Native Platform Graphics Interface)] is an interface between Khronos rendering APIs such as OpenGL ES or OpenVG and the underlying native platform. The Raspberry Pi supports [http://www.khronos.org/registry/egl/specs/eglspec.1.4.20110406.pdf EGL Version 1.4] and the following EGL extensions (links are to EGL registry documentation):<ref name="egl-info">eglinfo, http://www.raspberrypi.org/phpBB3/viewtopic.php?p=35942#p35942 , http://www.raspberrypi.org/phpBB3/viewtopic.php?p=36318#p36318</ref>
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_image.txt EGL_KHR_image]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_image_base.txt EGL_KHR_image_base]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_image_pixmap.txt EGL_KHR_image_pixmap]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_vg_parent_image.txt EGL_KHR_vg_parent_image]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_gl_image.txt EGL_KHR_gl_texture_2D_image]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_gl_image.txt EGL_KHR_gl_texture_cubemap_image]
*[http://www.khronos.org/registry/egl/extensions/KHR/EGL_KHR_lock_surface.txt EGL_KHR_lock_surface]

Creating an on-screen EGL rendering surface requires you to to use the eglCreateWindowSurface function, which takes a EGLNativeWindowType parameter. On the Raspberry Pi, this is implemented as a EGL_DISPMANX_WINDOW_T struct, which is defined in eglplatform.h as:

typedef struct {
DISPMANX_ELEMENT_HANDLE_T element;
int width; /* This is necessary because dispmanx elements are not queriable. */
int height;
} EGL_DISPMANX_WINDOW_T;

Therefore, to create a EGL surface you must also use the Dispmanx library to get a dispmanx element handle. The [https://github.com/raspberrypi/firmware/blob/master/opt/vc/src/hello_pi/hello_triangle/triangle.c#L147-173 hello_triangle source code] provides example code to do this.

==== Samples====

See [http://jonmacey.blogspot.com.au/2012/05/getting-started-with-egl-on-raspberry.html Getting Started with EGL] post by Jon Macey.
Extended documentation available in the [http://www.khronos.org/registry/egl/specs/eglspec.1.4.20110406.pdf EGL Version 1.4 Specification] and Simple Reference available in the [http://www.khronos.org/files/egl-1-4-quick-reference-card.pdf EGL 1.4 API Quick Reference Card].

==== Function Documentation====
====={{anchor|graphics_get_display_size}}<code>int32_t graphics_get_display_size( const uint16_t display_number, uint32_t *width, uint32_t *height);</code>=====

This function allows you to get the size of the display, and is often used in creating an EGL Surface. width and height are pointers that you pass in to where you want the response values to be written to, display number 0 is usually used for the Raspberry Pi. return value of >= 0 indicates success, <0 indicates failure.

This function is implemented in libbcm_host, and the implementation has been made [https://github.com/raspberrypi/firmware/issues/14#issuecomment-5652185 public] showing that it internally calls the vc_dispmanx_display_get_info function to get the width and height of the current mode.

Bugs present in early versions of the firmware caused this function to always return 1920x1080, however this can easily be fixed by updating the firmware with [https://github.com/Hexxeh/rpi-update Hexxeh's rpi-update] (see the [[R-Pi_Troubleshooting#Updating_firmware|Updating firmware]] page for help).<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=68&t=8252</ref><ref>https://github.com/raspberrypi/firmware/issues/14</ref>

=== OpenGL ES ===
The Raspberry Pi supports OpenGL ES 2.0 with the following extensions: <ref name="egl-info" />
*GL_OES_compressed_ETC1_RGB8_texture
*GL_OES_compressed_paletted_texture
*GL_OES_texture_npot GL_OES_depth24
*GL_OES_vertex_half_float
*GL_OES_EGL_image
*GL_OES_EGL_image_external
*GL_EXT_discard_framebuffer
*GL_OES_rgb8_rgba8
*GL_OES_depth32
*GL_OES_mapbuffer
*GL_EXT_texture_format_BGRA8888
*GL_APPLE_rgb_422
*GL_EXT_debug_marker

''TODO: Sample of how to use/initalise OpenGL ES''

=== OpenVG ===
The Raspberry Pi supports OpenVG 1.1 for hardware-accelerated two-dimensional vector and raster graphics. See the full specification [http://www.khronos.org/registry/vg/specs/openvg-1.1.pdf here] or [http://www.khronos.org/files/openvg-quick-reference-card.pdf the API quick reference card].

==== Samples ====
* [http://docs.blackberry.com/en/developers/deliverables/17967/CS_Drawing_a_triangle_using_OpenVG_1241146_11.jsp Code sample: Drawing a triangle by using OpenVG] ''(Java implentation for RIM devices, however should be able to get a grasp on how it works and be able to port it to the Raspberry Pi)''

=== OpenMAX ===
See [https://github.com/raspberrypi/firmware/tree/master/documentation/ilcomponents /documentation/ilcomponents] on GitHub firmware repository for official documentation.

''TODO: Sample of how to use OpenMAX to decode audio/video/images, etc.''

== Bindings for Other Programming Languages ==
'''Python'''
* [https://bitbucket.org/bryancole/rpi_vid_core/ RPi_Vid_Core] - ''python bindings of EGL, OpenGL ES, OpenVG and bcm_host for Raspberry Pi implemented using Cython''
'''Java'''
* [http://www.jogamp.org JogAmp JOGL] - ''JogAmp JOGL Java bindings for EGL and OpenGL ES for Raspberry Pi implemented using Gluegen.
** Raspberry Pi autodetection is included in JogAmp JOGL RC11 and later. http://forum.jogamp.org/Release-v2-0-rc11-td4026703.html
* [http://www.lwjgl.org LWJGL] - http://www.raspberrypi.org/phpBB3/viewtopic.php?p=211087 Raspberry Pi community port by '''spsn'''

== Open Source Software compatible with the VideoCore APIs ==
* '''[https://github.com/huceke/omxplayer omxplayer]''' - ''a command line a/v player for the Raspberry Pi utilising the OpenMAX APIs and ffmpeg''
* '''[http://wiki.xbmc.org/index.php?title=Raspberry_Pi XBMC]''' - ''a media center, omxplayer's "big brother" ''
* '''[http://nccastaff.bournemouth.ac.uk/jmacey/GraphicsLib/piNGL/index.html piNGL]''' - ''port of the NGL graphics library to Raspberry Pi''
* '''[http://qt-project.org/wiki/Qt-RaspberryPi Qt on Pi]''' - ''Raspberry Pi port of the Qt toolkit''

==References==
<references/>

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

Template:Raspberry Pi

2013-03-10T14:55:38Z

AndrewS: Removed Model Wizard link

{{Navbox
| name = Raspberry Pi
| title = [[R-Pi Hub|<span style="color:#FFFFFF">Raspberry Pi</span>]]
|listclass = hlist
| state = plain
| style = width:100%
| image = [[File:RpiFront.jpg|167px]]

| basestyle = background:#00CC00;
| groupstyle = background:#AA0033
| liststyle = background:#FFE0FF;

| group1 = '''<span style="color:#FFFFFF">Startup</span>'''
| list1 =
[[RPi Buying Guide|Buying Guide]] - [[RPi Easy SD Card Setup|SD Card Setup]] - [[RPi Hardware Basic Setup|Basic Setup]] - [[RPi Advanced Setup|Advanced Setup]] - [[RPi Beginners|Beginners Guide]] - [[R-Pi Troubleshooting|Troubleshooting]]

| group2 = '''<span style="color:#FFFFFF">Hardware</span>'''
| list2 = [[RPi Hardware|Hardware]] - [[RPi HardwareHistory|Hardware History]] - [[RPi Low-level peripherals|Low-level peripherals]] - [[RPi Expansion Boards|Expansion Boards]]

| group3 = '''<span style="color:#FFFFFF">Peripherals</span>'''
| list3 =
[[RPi Screens|Screens]] - [[RPi Cases|Cases]] - [[RPi VerifiedPeripherals|Other Peripherals]]

| group4 = '''<span style="color:#FFFFFF">Software</span>'''
| list4 =
[[RPi Software|Software]] - [[RPi Distributions|Distributions]] - [[RPi Kernel Compilation|Kernel]] - [[RPi Performance|Performance]] - [[RPi Programming|Programming]] - [[RPi_VideoCore_APIs|VideoCore APIs]]

| group5 = '''<span style="color:#FFFFFF">Projects</span>'''
| list5 =
[[RPi Tutorials|Tutorials]] - [[RPi Guides|Guides]] - [[RPi Projects|Projects]] - [[RPi Tasks|Tasks]] - [[RPi DatasheetCategories|DataSheets]] - [[RPi Education|Education]] - [[RPi Community|Communities]]

| below =

}}<noinclude>'''''Please use this template only for the English language version''''', and make a copy if you wish to use it for another language. Please be careful when editing and use preview, as this template appears on a number of pages.

To add this to a page, use <nowiki>{{Raspberry Pi}}</nowiki>

As the RaspberryPi category is included below, every article using this links table template should be forced to become a member of the category, but feel free to add the category tag to the article anyway as it does no harm.

If you're wondering how this template is possible - it uses the Navbar, Navbox and Transclude templates from wikipedia under Creative Commons Sharealike licence, with CSS info added manually as eLinux doesn't allow editing of the master CSS.</noinclude>

[[Category:RaspberryPi]]

RPi Buying Guide

2013-03-10T14:52:36Z

AndrewS: Added details about Egoman Technology Corp and the Red Pis. Also added links to Maplin.

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

Raspberry Pi has appointed [http://www.element14.com/raspberrypi Farnell], [http://rswww.com RS Components] and (recently) [http://www.egoman.com.cn/ Egoman Technology Corp]<ref>http://www.raspberrypi.org/archives/3195</ref> as its authorised manufacturing partners & distributors.

As of July 16th 2012, both [http://www.element14.com/raspberrypi Premier Farnell] and [http://rswww.com RS Components] have removed their "one per customer" restriction. Both consumers and businesses alike should now be able to buy bulk stock of the Raspberry Pi.

Raspberry Pi's distributors will ship worldwide to the best of their ability (ie subject to origin export and local import laws).

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]

Farnell have also been refusing to sell direct to some consumers in the EU, to the best of my knowlage they have not given full details of why.

There are three main options for buying a Raspberry Pi, buying direct from the distributor, buying from a subsidary or sister company of the distributor or buying from a third party reseller which option is best will depend on the location of the customer, the number of Raspberry Pi's being purchased, and the urgency of the order.

All new orders from the main distributors should now be filled with 512 MB rev 2 Raspberry Pi's. However, some third-party resellers may still have stock of the older models.

Note that stock status may change quickly. It may be worth checking a local supplier even if they are listed as out of stock here.

==Main distributors and subsidaries/sister companies==
==Farnell==
http://www.farnell.com/
Farnell are one of the two main distributors, as of 2012-11-21 their main European operation is out of stock and quoting a three-week lead time. Reports from the forum are that Farnell usually beat their delivery estimates.

For European customers, the customer is asked whether they are "consumer" or "business". If the customer selects business, they are taken back to Farnell's regular website to order. If the customer selects consumer, they are taken to a dedicated Raspberry Pi site which only offers a small selection of Raspberry Pi related products and gives no information on stock status. Farnell's site claims that consumers who do not have a previous account cannot use the "business" option but it is not clear if this is actually true for all countries. For some countries consumers are directed to third party resellers. The order code for the Raspberry Pi is 2191863.

===Element14===
http://www.element14.com
The "Element14" brand is used by a number of different operations within the Premier Farnell group and is also used for the groups "social" operation. In the Asia-Pacific region the Element 14 brand has completely replaced the previous "Premier Electronics" brand for asia and the previous "Farnell" brand for australia and new-zealand. In Europe, the Element14 brand is used in paralell with the Farnell brand. In North america the Element14 brand is used in parallel with the Newark brand.

===Newark===
http://www.newark.com/
Newark is the main American branch of the Premier Farnell group (Farnell's parent company). As of 2012-11-21, they are out of stock of Raspberry Pi's, but claim 1321 Expected to ship 2012-11-26 and Further stock expected to ship 2012-12-20.

===Element14 AU/NZ===
http://au.element14.com/ http://nz.element14.com/
On Element14's Australian operation (which also serves New Zealand) as of 2012-11-21 availability is listed as "please call" and "supplier lead time" is listed as 30 days. The order code for the Raspberry Pi is 2191863.

===Element 14 Asia===
http://cn.element14.com/ http://hk.element14.com/ http://in.element14.com/ http://cn.element14.com/ http://kr.element14.com/ http://my.element14.com/ http://ph.element14.com/ http://sg.element14.com/ http://tw.element14.com/ http://th.element14.com/
Element14 have warehouses in Singapore and Shanghi. It appears that some countries are served from both warehouses while others are served from only one or the other. UK stock is also listed on these sites. As of 2012-11-21, Element14's Asian operation has 331 Raspberry Pi's in stock in Shanghi and 617 Raspberry Pi's in stock in Singapore. The order code for the Raspberry Pi is 2191863.

===CPC===
http://cpc.farnell.com/
CPC is a branch of the Premier Farnell group in the UK based in Preston. As of 2012-11-21, they have 3100 Raspberry Pi's in stock. The order code for the Raspberry Pi is SC12590.

===MCM===
http://www.mcmelectronics.com/
MCM is a branch of the Premier Farnell group in the US based in Centerville, Ohio. As of 2012-11-21, they are out of stock and give an estimated ship date of 2012-12-07.

==RS components==
http://rswww.com/
RS are the other main distributor. Like Farnell they have a consumer site and business option with the consumer option taking users to a dedicated Raspberry Pi store while the business option takes them back to the regular RS site. They do not state whether consumers must use the consumer site or not. The order code for the Raspberry Pi is 756-8308. As of 2012-11-21, the Raspberry Pi is listed as "Temporarily out of stock - back order for despatch 21/12/2012".

RS has delayed existing orders on several occasions and are reported on the forum as being very difficult to communicate with.

===Allied electronics===
http://www.alliedelec.com/
Allied electronics is the US sister company of RS. The order code for the Raspberry Pi is 70229569. They website does not give a predicted dispatch date and state that "the estimated delivery time is uncertain and will likely take several months".

Reports from the forum are that Allied are easier to communicate with than RS, but they do not appear to be being kept will informed of the stock situation by RS.

==Egoman Technology Corp==
http://www.egoman.com.cn/
On 1st February 2013 the Raspberry Pi Foundation announced they had "granted Egoman Technology Corp a licence to produce and distribute Pis in China and Taiwan" and to differentiate these boards, they would only be produced with red PCBs - [http://www.raspberrypi.org/archives/3195 Red Pi at night]. "Egoman are aiming to make these Pis widely available in China, Hong Kong, Macau and Taiwan."

==Resellers==
There are now many companies reselling the Raspberry Pi.

===RPF endorsed resellers===
====Maplin====
http://www.maplin.co.uk/
Maplin sells the Raspberry Pi in the UK but only as part of a kit including power supply, keyboard and mouse, programmed 4 GB SD card, HDMI cable and wireless dongle. As of 2012-11-21, they list their [http://www.maplin.co.uk/raspberry-piandreg-board-and-starter-kit-652805 Raspberry Pi kit] as in stock for home delivery and also in stock in some stores.

===Farnell Approved resellers===
Farnell now direct consumers in many countries to "approved retailers" rather than selling to them directly. Some of these suppliers specialise in the Raspberry Pi while others are general Farnell resellers.

====Electrocomponentes S.A====
http://www.electrocomponentes.com/
Electrocomponentes S.A sells Farnell producs in Argentina.

====Arabian Electric & Electronics Est.====
fisuoyla@batelco.com.bh
Arabian Electric & Electronics Est sells Farnell products in Bahrain.

====Minifo====
http://www.minifo.com/
Minifo is a Raspberry Pi retailer in Belgium. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Electromin S.A.====
http://www.electromin.cl/
Electromin S.A. sells Farnell producs in Chile.

====Betatech Ltd====
http://www.farnell.com/distributors/cyprus_bet.htm
Betatech Ltd sells Farnell products in Cyprus.

====Grand soloutions====
http://www.gs.com.eg/
Grand soloutions sells Farnell producs in Egypt. Unfortunately, searching their website by Farnell part number seems to be currently broken.

====Partco Oy====
http://www.partco.biz/
Partco sells the Raspberry Pi, Arduino and a selection of electronic components in Finland. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

==== kubii ====
http://www.kubii.fr/
kubii sells the Raspberry Pi, together with a selection of accessories. The website was created when Farnell changed their distribution policy.

====Málna PC Magyarország ====
http://malnapc.hu/
Málna PC Magyarország is a Raspberry Pi reseller in Hungary.

====Midbaejarradio EHF====
Midbaejarradio EHF is the authorised Farnell distributor for Iceland.

====Lion====
http://www.lion.co.il/h?q=RASPBERRY
Lion sells the Raspberry Pi in Israel. As of 2012-11-21, they do not appear to have stock.

====International Oilfield Supplies====
http://www.farnell.com/distributors/malta_int.htm
International Oilfield Supplies are the authorised Farnell distributor for Malta.

====Makkays====
http://www.farnell.com/distributors/pakistan_mak.htm
Makkays is the authorised Farnell distributor for Pakistan.

====kamami====
http://www.kamami.pl/
kamami sells the Raspberry Pi in Poland.

====Mixtronica====
http://www.mixtronica.com/
Mixtronica sell Farnell products in Portugal.

====Computer and Engineering Specialists Co====
http://www.farnell.com/distributors/saudiarabia_ces.htm
CESCO Group is an authorised Farnell distributor for Saudi Arabia.

====Dialogue s.r.o====
http://www.dialogue.sk/index.php?page=textaktual&id=71
Dialogue s.r.o sells the Raspberry Pi and accessories in Slovakia.

====IC elektronika d.o.o.====
http://www.ic-elect.si/
IC elektronika d.o.o. sells Farnell products in Slovenia.

====Electrocomp express====
http://www.eexpress.co.za/
Electrocomp express sells Farnell products in South Africa. As of 2012-11-21, they list the Raspberry Pi as awaiting delivery and do not give a lead time.

====Orel Solutions (PVT) Ltd====
http://www.farnell.com/distributors/srilanka_osp.htm
Orel Solutions (PVT) Ltd is the authorised Farnell distributor for Sri Lanka.

====Mikro-Kit Elektronik AB====
https://www.microkit.se/
Mikro-Kit Elektronik AB sells the Raspberry Pi (and it would appear other farnell producs too) in Sweeden. As of 2012-11-21, they list the Raspberry Pi as out of stock with expected delivery 2012-12-11.

====digitec====
http://www.digitec.ch/
Digitec sells the Raspberry Pi in Switzerland.

====Yildrim====
http://www.yildirimelektronik.com/
Yildrim sells Farnell products in Turkey.

====DGM distribution====
http://www.farnell.com/distributors/unitedarabemirates_dgm.htm
DGM distribution is the authorised Farnell distributor for Dubai.

===Other resellers===
====Newit====
http://www.newit.co.uk/
Newit are a British company selling a variety of ARM hardware and accessories, including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Makershed====
http://www.makershed.com/
Makershed is a US company that sells various stuff aimed at hardware hackers including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as out of stock.

====Tandy====
http://www.tandyonline.co.uk/
Tandy is a UK company that sells a small selection of electronics stuff. As of 2012-12-08, Tandy has both 256MV rev 1.1 boards and 512MB rev 2 boards in stock.

Note that the current Tandy is a division of adslnation and other than buying the name has little relationship to the Tandy of old.

====Adafruit====
http://www.adafruit.com/
Adafruit is a US company that makes a variety of boards for hardware hackers and tinkerers, some specifically designed for use with the Raspberry Pi. They sell the Raspberry Pi separately, as well as part of a large starter kit including everything needed to start experimenting with the Raspberry Pi and external hardware on the GPIO. They also currently include a free Raspberry Pi with orders over $350.

====SNOOTLAB====
SNOOTLAB
http://snootlab.com/
Sells products in French as well as English. They also sell a number of different components and products such as Arduinos too.

====Tenettech====
Tenettech
http://www.tenettech.com/product/2184/raspberry-pi
Tenettech is Bangalore based company who sells software/hardware based solutions in India. They sell Raspberry Pi and Raspberry Pi kit (which include the Raspberry Pi, SD card, card reader, HDMI cable, and video cable).

====AVIES Tech====
http://www.shopavies.com
AVIES Tech is a US company that provides installation and integration solutions for a variety of media centric hardware. They also carry the Raspberry Pi and related accessories.

====Amazon====
[http://www.amazon.com/ Amazon] also sells boards through the Raspberry Pi name for U$D 48.03. You can buy one [http://www.amazon.com/Raspberry-Pi-Model-Revision-512MB/dp/B009SQQF9C/ref=sr_1_1?ie=UTF8&qid=1361718715&sr=8-1&keywords=raspberry+pi here].

====Bitcrafts====
[http://etsy.com/shop/bitcrafts Bitcrafts] ships the '''Model A''' worldwide. You can buy one [http://www.etsy.com/listing/124198601/raspberry-pi-model-a? here]. They also sell cases, pIO micro SD adapters and other related accessories.

==Licensed Manufacture==
The foundation has chosen to license manufacture of the Raspberry Pi, which should provide several advantages including:

# 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 Pi's; the Raspberry Pi will now be being built to match demand.
# 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.
# Both RS Components and Premier Farnell will be taking preorders, something which the foundation would otherwise be unable to do.
# The foundation will still receive a percentage from the sale of every Raspberry Pi sold, which will be put straight back into the charity.
# 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.

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 (2012-02-28)].

Unfortunately the switch to licensed manufacture has also resulted in a marked reduction in transparency of the process as Farnell and RS consider detailed information of what is going on to be confidential.

==What You Get In The Box==
1. Pre-Assembled Raspberry Pi board

2. A sheet containing a combination of regulatory information and some very brief instructions. 

''Note:''

''1. The board will be supplied assembled (since most of the components are not suitable for home builds, including the BGA<ref name="BGA">http://en.wikipedia.org/wiki/Ball_grid_array</ref>package mounted SoC<ref name="SoC">http://en.wikipedia.org/wiki/System_on_a_chip</ref> and PoP<ref name="PoP">http://en.wikipedia.org/wiki/Package_on_package</ref> memory).''
''2. The board has the GPIO header pins for the primary GPIO header (but not the secondary GPIO header added on the revision 2 boards) populated. The SoC JTAG may or may not be present depending on when the board was manufactured and at which factory but aren't really of use to end users anyway due to the lack of Broadcom documentation. The LAN JTAG header does not seem to be present on any boards.
''3. All other connectors will be assembled in place.''

==Accessories==
To use the Raspberry Pi, a user will typically require some accessories. All of the Raspberry Pi vendors listed above sell some accessories, but the exact range varies. Accessories you should consider include.
* USB Power Supply (UK/EU/US Compatible; 5V, 700mA-1500mA(1.5A))<ref>http://www.raspberrypi.org/forum/general-discussion/is-the-raspberrypi-going-to-be-sold-as-a-kit/#p32289</ref>
* SD card. Most distributors are selling pre-prepared SD cards which are usually 4 GB. Software is available to prepare your own SD cards.
* There is a wide choice of [[RPi_Cases|cases]], most distributors will have some but shopping around for one you like is suggested.
* There are a variety of [[Rpi expansion boards|AddOn/Expansion Boards]] now available, see that page for more details.
''See [[RPi Hardware Basic Setup#Typical Hardware You Will Need | Typical Hardware You Will Need]] for details about other items you may require.''

==Price==
The price is $35USD before shipping, duty, and tax, about $60 after.

Although the foundation is UK based, the guide price of the units are in USD since the Raspberry Pi components are sourced in USD$.

The price is $25USD (~£16GBP) for model A, and $35USD (~£23GBP) for model B.

Items will be subject to local tax (that is, UK will have 20% VAT added) and shipping cost is not included.

See the following update on [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

==Clones & Copies==
The foundation plans to release all the required [[RPi_Hardware#Schematic_.2F_Layout|schematics]] and plans to reproduce the Raspberry Pi hardware, so clones and copies will be welcome.

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.

==Historic information==

# The foundation have built an initial run of 10,000 Model-B units.
# Due to extreme demand, the units were NOT sold directly from the [http://www.raspberrypi.com shop] (see [[#Licensed Manufacture]] below).
# You may buy a Raspberry Pi from [http://www.element14.com/raspberrypi Farnell] or from [http://rswww.com RS Components]
# A limit of one unit per person was applied for the first batch and some time afterwards

* There were reports that several people ordered multiple units at launch,
however it appears that Farnell removed any excess items when they reviewed
and confirmed the order for shipping dates.
This has also appears to apply for the pre-orders they have taken.
Many customers also ordered from both Farnell and RS.

===1st Batch Order FAQ===
NOTE: While every attempt has been made to provide accurate information,
this FAQ is not official and is based on what information is available at the time of writing.

====Press Releases====
'''Farnell:'''

[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.

'''RS Components:'''

[http://www.electrocomponents.com/media/press-releases/2012/02/29th/ Post-Launch statement by RS Components]

[http://uk.rs-online.com/web/generalDisplay.html?id=raspberrypi&file=questions&cm_sp=raspberrypi-_--_-questions Raspberry Pi, Your Questions Answered by RS Components]

====Q: Couldn't this have been handled better, I couldn't get on the site to order and they sold too quickly?====
Both distributors were indeed unprepared for the volume of traffic the launch generated (they were warned by the foundation before hand).

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.

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).
Even if it is half of that, it means the number of available units was less than 1% of the demand.

====Q: If interest was obviously so high, why only build 10,000 units?====
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 task in itself. Much of that funding came from the Foundation Trustees' own personal investment.

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.

====Q: I've been unable to register an account with the distributor, as I am not a company?====
There have been several reported problems with individuals placing orders (that is, not having company accounts or details).

Both distributors "should" 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.

Often, many of the company related fields on application are optional. If in doubt, contact their sales team for help.

====Q: Worldwide launch? It was not available here! ====
The distributors decided to make the units only available from selected locations. It appears the foundation were not made aware of this beforehand.

Considering the small number of available units, it would have been unlikely to have improved the situation.

Worldwide availability will be monitored, it is expected that they will be made available as soon as possible.

====Q: The price for the Raspberry Pi from Farnell versus the price from RS Components is different, why?====
Please see the following page for details about [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

====Q: I've only been able to register my interest, what now?====
Be patient, both distributors have said they will contact people when they have more details (alternatively keep an eye on their sites for news).

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.

====Q: I registered on the Raspberry Pi Site's Mailing List, but I didn't get an email====
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.

The email contained the same information about the announcement as was publicly posted on the website (2012-02-28) before launch day, no additional or extra information was given through the email.

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Hub

2013-03-10T14:28:50Z

AndrewS: /* About */ Added link to Egoman Technology Corp

{{TOC right}}
{{Hub Flags}} 
<div style="margin:0; border:1px solid #f80033; padding:0 1em 1em 1em; background-color:#cd5555; align:right; width:50%;">
<font color="ffffff">Notice: The Raspberry Pi Wiki pages on this site is collaborative work - the Raspberry Pi Foundation is '''not''' responsible for content on these pages.</font>
</div>



== Now shipping to customers ==

'''Update on lead times as of 17 November 2012:''' The lead time is around 2 days from Farnell and RS.


See the [[RPi Buying Guide|Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]

== About ==
[[File:RpiFront.jpg|300px|thumb|right|The Raspberry Pi production board (model B Rev 2.0)]]

The Raspberry Pi (short: RPi or RasPi) is an ultra-low-cost ($25-$35) 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 [http://www.charity-commission.gov.uk/Showcharity/RegisterOfCharities/CharityWithoutPartB.aspx?RegisteredCharityNumber=1129409&SubsidiaryNumber=0 1129409]). The foundation exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. The device is expected to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).

Raspberry Pi is manufactured and sold in partnership with the worldwide industrial distributors [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components], and the Chinese distributor [http://www.egoman.com.cn/ Egoman Technology Corp]<ref>http://www.raspberrypi.org/archives/3195</ref>.

* You can get the latest news from the [http://www.raspberrypi.org Foundation Home Page], the [http://twitter.com/intent/user?screen_name=Raspberry_Pi Twitter Feed] or in the [http://www.raspberrypi.org/forum/general-discussion/news-articles-and-blog-posts-about-raspberry-pi forums].
* For Raspberry Pi frequently asked questions see the [[RPi FAQ|FAQ section]] or the [http://www.raspberrypi.org/?page_id=8 Raspberry Pi Foundation's FAQ] page.
* Both manufacturing partners provide community areas for more technically focused discussions, articles, FAQs and related information:
:* Premier Farnell: [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group]
:* RS-Components: [http://www.designspark.com/theme/raspberrypi DesignSpark - Raspberry Pi]
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant<ref>http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet</ref>. In common with all Electronic and Electrical products the Raspberry Pi should not be disposed of in household waste. Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.
* Price: 25USD Model A, 35USD for Model B, excluding taxes, postage and packaging. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].

=== History ===

If you are interested in why the Raspberry Pi was created, and why it is what it is, check the [[RPi General History|General History]] page, which highlights relevant events in its history. It is not intended to be a detailed history, so it can be read quickly. You could also check the [[Rpi_HardwareHistory | design changes]] page for how the Raspberry Pi has evolved, and the [[RaspberryPi_Boards | manufacturing differences]] page that may help if you are having problems with your board.

== Getting Started ==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa;" |
=== [[Buying RPi|Buying Guide]] ===

----
Where can I get one and for how much?
* The Raspberry Pi can no longer only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.

* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop], as well as [http://thepihut.com/ The Pi Hut's Raspberry Pi Store], [http://easyaspistore.com/ the EasyAsPi Store], and many others on Amazon [http://www.amazon.co.uk/ Amazon UK] and eBay [http://www.ebay.co.uk/ eBay UK] websites.

* You can find out which peripherals and such are tested to work with the PI in the [[RPi_VerifiedPeripherals]] section

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

=== [[RPi Hardware Basic Setup|Basic Setup]] ===
----
First little Raspberry Pi Steps...
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]
* Note: On the Debian OS after you log in you need to type '''startx''' at the prompt to get a graphic desktop.
* Particularly after first boot its important to do a clean shutdown with the command '''sudo halt'''

* '''Having problems? Try the [[R-Pi_Troubleshooting | Troubleshooting]] page.'''

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

=== [[RPi Beginners|Beginners Guide]] ===
----
You've just got your new Raspberry Pi device - what now?
* [[RPi Beginners|Beginners Guide]]

* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.

* Read a small book for the Raspberry Pi Beginner [http://bitkistl.blogspot.co.at/2013/01/raspberry-pi-e-book.html]

* Get started with some basic projects and tutorials:
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials]<br />
[http://www.youtube.com/user/RaspberryPiBeginners Another set of video tutorials]<br />
[http://www.youtube.com/playlist?list=PLgyU3jNA6VjS3ij6ZXbb2x4GdEP3bAWzO My First Raspberry Pi Game]

[[RPi Tutorial Easy GPIO Hardware & Software|Easy GPIO Hardware & Software]] - in-progress at the moment
Example projects/tuts which can be linked from here
(or from within a beginners guide page perhaps):
Setup XBMC media centre
Programming tutorials (Liams YouTube etc)
Easy GPIO (when complete or similar thing).
Also links to some basic linux user guides.

* Take a look through the [[#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.

|}

== Resources ==
{| border="1" style="background:transparent;"

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Hardware|Hardware]] & [[RPi VerifiedPeripherals|Peripherals]] ===
----

* The Model B is more advanced than the Model A - see [[RPi Hardware]].
* The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].
* The unit will support a range of [[RPi VerifiedPeripherals|devices, peripherals and accessories]].
* The [[Rpi Low-level peripherals|Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.
* For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].
* [[RPi Peripherals|Setting up peripherals - examples/HowTos]]
* [[RaspberryPi Boards|List of boards and user feedback]]
* [[RPi 5V PSU construction|Power Supply construction - HowTo]]
* [[RaspberryPi_Comparison|Comparison]] to other hardware
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[Rpi_Software|Software]] & [[RPi_Distributions|OS Distributions]] ===
----
The Raspberry Pi will run a range of OS Distributions and run a variety of software.
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/Puppi Puppi] from Puppy Linux.
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]], [[RPi_U-Boot|boot from the network using U-Boot]], or [[RPi_Performance|test the Pi's performance]].
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.
*Information about installing specific [[RPi_applications|applications]] is available through the link.
*Extensive (boot) configuration info (config.txt) is available [[RPi_config.txt|here]].
*Monitor your Raspberry Pi with Raspcontrol [[Raspcontrol|here]]

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Documentation|Documentation]] ===
----
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].

[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]

Example documents which can be linked from here (or sub page):
Official Datasheets
White Papers
User Manuals
Recommended books (perhaps)

=== RPi Troubleshooting ===

Head over to the [[R-Pi Troubleshooting|troubleshooting page]] for help fixing common problems.

=== RPi Bugs ===

Head over to the [[RPi_Bugs|bugs page]] for a list of known bugs.

=== RPi Model B 3D CAD files ===
Theses are various 3D CAD Versions in both RAR and ZIP.

* CATIA V5 RAR http://sdrv.ms/JqdhMb
* CATIA V5 ZIP http://sdrv.ms/LjyLGD
* ProE RAR http://sdrv.ms/KCv1hZ
* ProE ZIP http://sdrv.ms/KCvhxq
* STEP RAR http://sdrv.ms/KCvv7T
* STEP ZIP http://sdrv.ms/JMhv18
* SketchUp http://scc.jezmckean.com/item/581
* SketchUp8 http://sketchup.google.com/3dwarehouse/details?mid=327d6b1d8bd6130d6fbd6b70c7f1d3e0
* Eagle 5 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=4457
|}

== Community ==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Projects|Projects]], [[RPi Guides|Guides]] & [[RPi Tutorials|Tutorials]] ===
----
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].
*Get started by following some of the many [[RPi Tutorials | Tutorials]].
*Common tasks and useful tips are available through the [[RPi Guides | Guides page]].
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].
*Raspberry Pi Datasheets can be found on the [[RPi DatasheetCategories |DataSheets page]].
*Knowledgeable users may want to review and help out with project wishlist items on the [[RPi Tasks |Tasks page]].
*[[Configuring a Static IP address on your Raspberry Pi]]

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Education|Schools, Universities, Clubs & Groups]] ===
----
*The Raspberry Pi Foundation's aims include encouraging education. Several groups including [http://www.computingatschool.org.uk/ Computing At School] aim to bring Computing Science back into schools.
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |
=== [[RPi Community|Supporting Communities]] ===
----
The [[RPi Community|Raspberry Pi Community]] is steadily growing:
* [http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]
* [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group], community site of Premier Farnell
* [http://www.designspark.com/theme/raspberrypi DesignSpark], community site of RS-Components
* [http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]
* [http://raspberrypi.stackexchange.com/ Stack Exchange Forum]
* [http://www.raspberrypiforums.com/forum RaspberryPiForums] Un-Official Raspberry Pi Discussion Board
* [http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]
* [http://www.worldofpi.com/ World Of Pi] A forum based on all things Raspberry Pi.
* [[RPi Community Magazine]] - User contributed eMagazine, get involved!
* [[RaspberryPi Osdev]] - Hardware specific OS-development community, sitting in freenode.net#raspberrypi-osdev.
|}

== About the RPi Wiki ==
'''Do not be afraid to add your bit, content is vital for the wiki to function.'''

[[File:Rasp_turn_around.gif|200px|thumb|right|A 3D rendering of the Raspberry Pi logo]]


=== Translations ===

The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:

* English: [[R-Pi Hub]]
* Français: [[FR:R-Pi Hub]]
Any help translating would be greatly appreciated. Thank you to those who have already contributed!

=== Admins/Contributors ===
<del>The wiki is governed by the [[Project:RPi_Council|Raspberry Pi Wiki Council]].</del>

:NOTE - This wiki is NOT governed by the [[Project:RPi_Council|Raspberry Pi Wiki Council]]. The whole of elinux.org is community driven. It always has been. If you have any questions, contact [[User:Wmat]].

= References =
<references/>

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

RPi Hub

2013-03-10T14:18:16Z

AndrewS: Added link to charity-commission

{{TOC right}}
{{Hub Flags}} 
<div style="margin:0; border:1px solid #f80033; padding:0 1em 1em 1em; background-color:#cd5555; align:right; width:50%;">
<font color="ffffff">Notice: The Raspberry Pi Wiki pages on this site is collaborative work - the Raspberry Pi Foundation is '''not''' responsible for content on these pages.</font>
</div>



== Now shipping to customers ==

'''Update on lead times as of 17 November 2012:''' The lead time is around 2 days from Farnell and RS.


See the [[RPi Buying Guide|Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]

== About ==
[[File:RpiFront.jpg|300px|thumb|right|The Raspberry Pi production board (model B Rev 2.0)]]

The Raspberry Pi (short: RPi or RasPi) is an ultra-low-cost ($25-$35) 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 [http://www.charity-commission.gov.uk/Showcharity/RegisterOfCharities/CharityWithoutPartB.aspx?RegisteredCharityNumber=1129409&SubsidiaryNumber=0 1129409]). The foundation exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. The device is expected to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).

Raspberry Pi is manufactured and sold in partnership with the worldwide industrial distributors [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components].

* You can get the latest news from the [http://www.raspberrypi.org Foundation Home Page], the [http://twitter.com/intent/user?screen_name=Raspberry_Pi Twitter Feed] or in the [http://www.raspberrypi.org/forum/general-discussion/news-articles-and-blog-posts-about-raspberry-pi forums].
* For Raspberry Pi frequently asked questions see the [[RPi FAQ|FAQ section]] or the [http://www.raspberrypi.org/?page_id=8 Raspberry Pi Foundation's FAQ] page.
* Both manufacturing partners provide community areas for more technically focused discussions, articles, FAQs and related information:
:* Premier Farnell: [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group]
:* RS-Components: [http://www.designspark.com/theme/raspberrypi DesignSpark - Raspberry Pi]
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant<ref>http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet</ref>. In common with all Electronic and Electrical products the Raspberry Pi should not be disposed of in household waste. Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.
* Price: 25USD Model A, 35USD for Model B, excluding taxes, postage and packaging. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].

=== History ===

If you are interested in why the Raspberry Pi was created, and why it is what it is, check the [[RPi General History|General History]] page, which highlights relevant events in its history. It is not intended to be a detailed history, so it can be read quickly. You could also check the [[Rpi_HardwareHistory | design changes]] page for how the Raspberry Pi has evolved, and the [[RaspberryPi_Boards | manufacturing differences]] page that may help if you are having problems with your board.

== Getting Started ==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa;" |
=== [[Buying RPi|Buying Guide]] ===

----
Where can I get one and for how much?
* The Raspberry Pi can no longer only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.

* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop], as well as [http://thepihut.com/ The Pi Hut's Raspberry Pi Store], [http://easyaspistore.com/ the EasyAsPi Store], and many others on Amazon [http://www.amazon.co.uk/ Amazon UK] and eBay [http://www.ebay.co.uk/ eBay UK] websites.

* You can find out which peripherals and such are tested to work with the PI in the [[RPi_VerifiedPeripherals]] section

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

=== [[RPi Hardware Basic Setup|Basic Setup]] ===
----
First little Raspberry Pi Steps...
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]
* Note: On the Debian OS after you log in you need to type '''startx''' at the prompt to get a graphic desktop.
* Particularly after first boot its important to do a clean shutdown with the command '''sudo halt'''

* '''Having problems? Try the [[R-Pi_Troubleshooting | Troubleshooting]] page.'''

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

=== [[RPi Beginners|Beginners Guide]] ===
----
You've just got your new Raspberry Pi device - what now?
* [[RPi Beginners|Beginners Guide]]

* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.

* Read a small book for the Raspberry Pi Beginner [http://bitkistl.blogspot.co.at/2013/01/raspberry-pi-e-book.html]

* Get started with some basic projects and tutorials:
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials]<br />
[http://www.youtube.com/user/RaspberryPiBeginners Another set of video tutorials]<br />
[http://www.youtube.com/playlist?list=PLgyU3jNA6VjS3ij6ZXbb2x4GdEP3bAWzO My First Raspberry Pi Game]

[[RPi Tutorial Easy GPIO Hardware & Software|Easy GPIO Hardware & Software]] - in-progress at the moment
Example projects/tuts which can be linked from here
(or from within a beginners guide page perhaps):
Setup XBMC media centre
Programming tutorials (Liams YouTube etc)
Easy GPIO (when complete or similar thing).
Also links to some basic linux user guides.

* Take a look through the [[#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.

|}

== Resources ==
{| border="1" style="background:transparent;"

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Hardware|Hardware]] & [[RPi VerifiedPeripherals|Peripherals]] ===
----

* The Model B is more advanced than the Model A - see [[RPi Hardware]].
* The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].
* The unit will support a range of [[RPi VerifiedPeripherals|devices, peripherals and accessories]].
* The [[Rpi Low-level peripherals|Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.
* For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].
* [[RPi Peripherals|Setting up peripherals - examples/HowTos]]
* [[RaspberryPi Boards|List of boards and user feedback]]
* [[RPi 5V PSU construction|Power Supply construction - HowTo]]
* [[RaspberryPi_Comparison|Comparison]] to other hardware
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[Rpi_Software|Software]] & [[RPi_Distributions|OS Distributions]] ===
----
The Raspberry Pi will run a range of OS Distributions and run a variety of software.
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/Puppi Puppi] from Puppy Linux.
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]], [[RPi_U-Boot|boot from the network using U-Boot]], or [[RPi_Performance|test the Pi's performance]].
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.
*Information about installing specific [[RPi_applications|applications]] is available through the link.
*Extensive (boot) configuration info (config.txt) is available [[RPi_config.txt|here]].
*Monitor your Raspberry Pi with Raspcontrol [[Raspcontrol|here]]

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Documentation|Documentation]] ===
----
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].

[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]

Example documents which can be linked from here (or sub page):
Official Datasheets
White Papers
User Manuals
Recommended books (perhaps)

=== RPi Troubleshooting ===

Head over to the [[R-Pi Troubleshooting|troubleshooting page]] for help fixing common problems.

=== RPi Bugs ===

Head over to the [[RPi_Bugs|bugs page]] for a list of known bugs.

=== RPi Model B 3D CAD files ===
Theses are various 3D CAD Versions in both RAR and ZIP.

* CATIA V5 RAR http://sdrv.ms/JqdhMb
* CATIA V5 ZIP http://sdrv.ms/LjyLGD
* ProE RAR http://sdrv.ms/KCv1hZ
* ProE ZIP http://sdrv.ms/KCvhxq
* STEP RAR http://sdrv.ms/KCvv7T
* STEP ZIP http://sdrv.ms/JMhv18
* SketchUp http://scc.jezmckean.com/item/581
* SketchUp8 http://sketchup.google.com/3dwarehouse/details?mid=327d6b1d8bd6130d6fbd6b70c7f1d3e0
* Eagle 5 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=4457
|}

== Community ==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Projects|Projects]], [[RPi Guides|Guides]] & [[RPi Tutorials|Tutorials]] ===
----
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].
*Get started by following some of the many [[RPi Tutorials | Tutorials]].
*Common tasks and useful tips are available through the [[RPi Guides | Guides page]].
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].
*Raspberry Pi Datasheets can be found on the [[RPi DatasheetCategories |DataSheets page]].
*Knowledgeable users may want to review and help out with project wishlist items on the [[RPi Tasks |Tasks page]].
*[[Configuring a Static IP address on your Raspberry Pi]]

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Education|Schools, Universities, Clubs & Groups]] ===
----
*The Raspberry Pi Foundation's aims include encouraging education. Several groups including [http://www.computingatschool.org.uk/ Computing At School] aim to bring Computing Science back into schools.
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |
=== [[RPi Community|Supporting Communities]] ===
----
The [[RPi Community|Raspberry Pi Community]] is steadily growing:
* [http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]
* [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group], community site of Premier Farnell
* [http://www.designspark.com/theme/raspberrypi DesignSpark], community site of RS-Components
* [http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]
* [http://raspberrypi.stackexchange.com/ Stack Exchange Forum]
* [http://www.raspberrypiforums.com/forum RaspberryPiForums] Un-Official Raspberry Pi Discussion Board
* [http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]
* [http://www.worldofpi.com/ World Of Pi] A forum based on all things Raspberry Pi.
* [[RPi Community Magazine]] - User contributed eMagazine, get involved!
* [[RaspberryPi Osdev]] - Hardware specific OS-development community, sitting in freenode.net#raspberrypi-osdev.
|}

== About the RPi Wiki ==
'''Do not be afraid to add your bit, content is vital for the wiki to function.'''

[[File:Rasp_turn_around.gif|200px|thumb|right|A 3D rendering of the Raspberry Pi logo]]


=== Translations ===

The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:

* English: [[R-Pi Hub]]
* Français: [[FR:R-Pi Hub]]
Any help translating would be greatly appreciated. Thank you to those who have already contributed!

=== Admins/Contributors ===
<del>The wiki is governed by the [[Project:RPi_Council|Raspberry Pi Wiki Council]].</del>

:NOTE - This wiki is NOT governed by the [[Project:RPi_Council|Raspberry Pi Wiki Council]]. The whole of elinux.org is community driven. It always has been. If you have any questions, contact [[User:Wmat]].

= References =
<references/>

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

RPi Hub

2013-03-10T14:10:23Z

AndrewS: /* About the RPi Wiki */ Looks like the "Raspberry Pi Wiki Council" turned into a dead end - so removed links

{{TOC right}}
{{Hub Flags}} 
<div style="margin:0; border:1px solid #f80033; padding:0 1em 1em 1em; background-color:#cd5555; align:right; width:50%;">
<font color="ffffff">Notice: The Raspberry Pi Wiki pages on this site is collaborative work - the Raspberry Pi Foundation is '''not''' responsible for content on these pages.</font>
</div>

== I need help with... ==


== Now shipping to customers ==

'''Update on lead times as of 17 November 2012:''' The lead time is around 2 days from Farnell and RS.


See the [[RPi Buying Guide|Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]

== About ==
[[File:RpiFront.jpg|300px|thumb|right|The Raspberry Pi production board (model B Rev 2.0)]]

The Raspberry Pi (short: RPi or RasPi) is an ultra-low-cost ($25-$35) credit-card sized Linux computer which was conceived with the primary goal of teaching computer programming to children. It was developed by the [http://www.raspberrypi.org Raspberry Pi Foundation], which is a UK registered charity (Registration Number 1129409). The foundation exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. The device is expected to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).

Raspberry Pi is manufactured and sold in partnership with the worldwide industrial distributors [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components].

* You can get the latest news from the [http://www.raspberrypi.org Foundation Home Page], the [http://twitter.com/intent/user?screen_name=Raspberry_Pi Twitter Feed] or in the [http://www.raspberrypi.org/forum/general-discussion/news-articles-and-blog-posts-about-raspberry-pi forums].
* For Raspberry Pi frequently asked questions see the [[RPi FAQ|FAQ section]] or the [http://www.raspberrypi.org/?page_id=8 Raspberry Pi Foundation's FAQ] page.
* Both manufacturing partners provide community areas for more technically focused discussions, articles, FAQs and related information:
:* Premier Farnell: [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group]
:* RS-Components: [http://www.designspark.com/theme/raspberrypi DesignSpark - Raspberry Pi]
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant<ref>http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet</ref>. In common with all Electronic and Electrical products the Raspberry Pi should not be disposed of in household waste. Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.
* Price: 25USD Model A, 35USD for Model B, excluding taxes, postage and packaging. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].

=== History ===

If you are interested in why the Raspberry Pi was created, and why it is what it is, check the [[RPi General History|General History]] page, which highlights relevant events in its history. It is not intended to be a detailed history, so it can be read quickly. You could also check the [[Rpi_HardwareHistory | design changes]] page for how the Raspberry Pi has evolved, and the [[RaspberryPi_Boards | manufacturing differences]] page that may help if you are having problems with your board.

== Getting Started ==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa;" |
=== [[Buying RPi|Buying Guide]] ===

----
Where can I get one and for how much?
* The Raspberry Pi can no longer only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.

* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop], as well as [http://thepihut.com/ The Pi Hut's Raspberry Pi Store], [http://easyaspistore.com/ the EasyAsPi Store], and many others on Amazon [http://www.amazon.co.uk/ Amazon UK] and eBay [http://www.ebay.co.uk/ eBay UK] websites.

* You can find out which peripherals and such are tested to work with the PI in the [[RPi_VerifiedPeripherals]] section

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

=== [[RPi Hardware Basic Setup|Basic Setup]] ===
----
First little Raspberry Pi Steps...
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]
* Note: On the Debian OS after you log in you need to type '''startx''' at the prompt to get a graphic desktop.
* Particularly after first boot its important to do a clean shutdown with the command '''sudo halt'''

* '''Having problems? Try the [[R-Pi_Troubleshooting | Troubleshooting]] page.'''

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

=== [[RPi Beginners|Beginners Guide]] ===
----
You've just got your new Raspberry Pi device - what now?
* [[RPi Beginners|Beginners Guide]]

* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.

* Read a small book for the Raspberry Pi Beginner [http://bitkistl.blogspot.co.at/2013/01/raspberry-pi-e-book.html]

* Get started with some basic projects and tutorials:
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials]<br />
[http://www.youtube.com/user/RaspberryPiBeginners Another set of video tutorials]<br />
[http://www.youtube.com/playlist?list=PLgyU3jNA6VjS3ij6ZXbb2x4GdEP3bAWzO My First Raspberry Pi Game]

[[RPi Tutorial Easy GPIO Hardware & Software|Easy GPIO Hardware & Software]] - in-progress at the moment
Example projects/tuts which can be linked from here
(or from within a beginners guide page perhaps):
Setup XBMC media centre
Programming tutorials (Liams YouTube etc)
Easy GPIO (when complete or similar thing).
Also links to some basic linux user guides.

* Take a look through the [[#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.

|}

== Resources ==
{| border="1" style="background:transparent;"

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Hardware|Hardware]] & [[RPi VerifiedPeripherals|Peripherals]] ===
----

* The Model B is more advanced than the Model A - see [[RPi Hardware]].
* The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].
* The unit will support a range of [[RPi VerifiedPeripherals|devices, peripherals and accessories]].
* The [[Rpi Low-level peripherals|Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.
* For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].
* [[RPi Peripherals|Setting up peripherals - examples/HowTos]]
* [[RaspberryPi Boards|List of boards and user feedback]]
* [[RPi 5V PSU construction|Power Supply construction - HowTo]]
* [[RaspberryPi_Comparison|Comparison]] to other hardware
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[Rpi_Software|Software]] & [[RPi_Distributions|OS Distributions]] ===
----
The Raspberry Pi will run a range of OS Distributions and run a variety of software.
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/Puppi Puppi] from Puppy Linux.
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]], [[RPi_U-Boot|boot from the network using U-Boot]], or [[RPi_Performance|test the Pi's performance]].
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.
*Information about installing specific [[RPi_applications|applications]] is available through the link.
*Extensive (boot) configuration info (config.txt) is available [[RPi_config.txt|here]].
*Monitor your Raspberry Pi with Raspcontrol [[Raspcontrol|here]]

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Documentation|Documentation]] ===
----
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].

[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]

Example documents which can be linked from here (or sub page):
Official Datasheets
White Papers
User Manuals
Recommended books (perhaps)

=== RPi Troubleshooting ===

Head over to the [[R-Pi Troubleshooting|troubleshooting page]] for help fixing common problems.

=== RPi Bugs ===

Head over to the [[RPi_Bugs|bugs page]] for a list of known bugs.

=== RPi Model B 3D CAD files ===
Theses are various 3D CAD Versions in both RAR and ZIP.

* CATIA V5 RAR http://sdrv.ms/JqdhMb
* CATIA V5 ZIP http://sdrv.ms/LjyLGD
* ProE RAR http://sdrv.ms/KCv1hZ
* ProE ZIP http://sdrv.ms/KCvhxq
* STEP RAR http://sdrv.ms/KCvv7T
* STEP ZIP http://sdrv.ms/JMhv18
* SketchUp http://scc.jezmckean.com/item/581
* SketchUp8 http://sketchup.google.com/3dwarehouse/details?mid=327d6b1d8bd6130d6fbd6b70c7f1d3e0
* Eagle 5 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=4457
|}

== Community ==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Projects|Projects]], [[RPi Guides|Guides]] & [[RPi Tutorials|Tutorials]] ===
----
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].
*Get started by following some of the many [[RPi Tutorials | Tutorials]].
*Common tasks and useful tips are available through the [[RPi Guides | Guides page]].
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].
*Raspberry Pi Datasheets can be found on the [[RPi DatasheetCategories |DataSheets page]].
*Knowledgeable users may want to review and help out with project wishlist items on the [[RPi Tasks |Tasks page]].
*[[Configuring a Static IP address on your Raspberry Pi]]

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Education|Schools, Universities, Clubs & Groups]] ===
----
*The Raspberry Pi Foundation's aims include encouraging education. Several groups including [http://www.computingatschool.org.uk/ Computing At School] aim to bring Computing Science back into schools.
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |
=== [[RPi Community|Supporting Communities]] ===
----
The [[RPi Community|Raspberry Pi Community]] is steadily growing:
* [http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]
* [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group], community site of Premier Farnell
* [http://www.designspark.com/theme/raspberrypi DesignSpark], community site of RS-Components
* [http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]
* [http://raspberrypi.stackexchange.com/ Stack Exchange Forum]
* [http://www.raspberrypiforums.com/forum RaspberryPiForums] Un-Official Raspberry Pi Discussion Board
* [http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]
* [http://www.worldofpi.com/ World Of Pi] A forum based on all things Raspberry Pi.
* [[RPi Community Magazine]] - User contributed eMagazine, get involved!
* [[RaspberryPi Osdev]] - Hardware specific OS-development community, sitting in freenode.net#raspberrypi-osdev.
|}

== About the RPi Wiki ==
'''Do not be afraid to add your bit, content is vital for the wiki to function.'''

[[File:Rasp_turn_around.gif|200px|thumb|right|A 3D rendering of the Raspberry Pi logo]]


=== Translations ===

The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:

* English: [[R-Pi Hub]]
* Français: [[FR:R-Pi Hub]]
Any help translating would be greatly appreciated. Thank you to those who have already contributed!

=== Admins/Contributors ===
<del>The wiki is governed by the [[Project:RPi_Council|Raspberry Pi Wiki Council]].</del>

:NOTE - This wiki is NOT governed by the [[Project:RPi_Council|Raspberry Pi Wiki Council]]. The whole of elinux.org is community driven. It always has been. If you have any questions, contact [[User:Wmat]].

= References =
<references/>

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

RPi Hardware Basic Setup

2013-03-10T14:05:10Z

AndrewS: /* Prepared Operating System SD Card */ Added links to preloaded SD cards sold by RS & Farnell

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

=Typical Hardware You Will Need=
While the RPi can be used without any additional hardware (except perhaps a power supply of some kind), it won't be much use as a general computer. As with any normal PC, it is likely you will need some additional hardware.

'''IMPORTANT''' For USB devices other than a mouse and a simple wired keyboard (for USB devices drawing more than 100mA) a powered USB hub is strongly recommended. A technical discussion as to why can be found [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5830 here]. Specifically the RPI's built in USB hub is designed only for "Single current unit" USB devices. Note that when using Revision 2 (or later) boards the problem has been mitigated somewhat with the removal of the USB polyfuses, still due to the limited current the PI can provide to USB devices, due to its main polyfuse, its still recommended to use a hub for all USB peripherals requiring more than 100mA.

The following are more or less essential, and are all available from [http://thepihut.com/ The Pi Hut's Raspberry Pi Store]:

* [[RPi Buying Guide|Raspberry Pi board]]
* [[#Prepared Operating System SD Card|Prepared Operating System SD Card]]
* [[#Keyboard & Mouse|USB keyboard]]
* [[#Display|Display]] (with HDMI, DVI, Composite or SCART input)
* [[#Power Supply|Power Supply]]
* [[#Cables|Cables]]

Highly suggested extras include:

* [[#Keyboard & Mouse|USB mouse]]
* [[#Additional Peripherals|Internet connectivity]] - a USB WiFi adaptor (Model A/B) or a LAN cable (Model B)
* [[#Additional Peripherals|Powered USB Hub]]
* [[#Additional Peripherals|Case]]
* [[#Additional Peripherals|Real Time Clock]] - If you can't count on Network Time
* [[#Additional Peripherals|SD card reader]] - if you need to prepare your own SD card

==Prepared Operating System SD Card==
As the RPi has no internal storage or built-in [[RPi Distributions|operating system]] it requires an SD-Card that is set up to boot the RPi.

* Have a look at [[RPi Easy SD Card Setup]] to create your own preloaded SD Card.
* If you want an extensive technical explanation, look here : ''Create your own preloaded card using any [[RPi VerifiedPeripherals#SD_cards]] card you have and this [[RPi Beginners#SD_card_setup| HowTo]] . ''
* Preloaded SD cards will be available from <del>the [http://www.raspberrypi.com RPi Shop]</del>, [http://thepihut.com/ The Pi Hut's Raspberry Pi Store], [http://raspberrypi.rsdelivers.com/product/rs/4gb-sd-card-with-raspberry-pi-os-installed/7631030.aspx RS], [http://export.farnell.com/samsung/raspberry-pi-prog-4gb-sdcard/memory-sdhc-rd-raspberry-pi-4gb/dp/2113756 Farnell].
* For configuration of boot options and extensive graphic modes, look at the [[RPi_Configuration|Configuration]] page.

NOTE: An RPi SD card can only be used to boot an RPi. A normal PC will refuse to boot from an RPi SD card.

This guide will assume you have a preloaded SD card.

''To check your SD card is compatible with Linux, see [[RPi VerifiedPeripherals#SD_cards]].''

==Keyboard & Mouse==
Most standard USB keyboards and mice will work with the RPi. Wireless keyboard/mice should also function, and only require a single USB port for an RF dongle. In order to use a Bluetooth keyboard or mouse you would need to use a Bluetooth dongle, which again uses a single port.

Remember that the Model A has a single USB port and the Model B only has two (typically a keyboard and mouse will use a USB port each) - see [[RPi_Hardware_Basic_Setup#USB-Hub | USB Hub]] below.

''To check your mouse and keyboard are compatible with Linux, see [[RPi VerifiedPeripherals | RPi Verified Peripherals]].''

==Display==
There are two main connection options for the RPi display, ''HDMI'' (high definition) and ''Composite'' (low definition).

* HD TVs and most LCD Monitors can be connected using a full-size 'male' HDMI cable, and with an inexpensive adaptor if DVI is used. HDMI versions 1.3 and 1.4 are supported, and a version 1.4 cable is recommended. The RPi outputs audio and video via HMDI, but does not support HDMI input.

* Most older TVs can be connected using Composite (a yellow-to-yellow cable). PAL and NTSC TVs are supported. Note that the RCA output is composite video, not RF, so it cannot be connected directly to the antenna input of a TV, you need to connected it the the yellow video input connector, or to the SCART input using a RCA to SCART plug, (adapter).

When using composite video, audio is available from a 3.5mm (1/8 inch) socket, and can be sent to your TV, or to an amplifier. To send audio to your TV, you will need a cable which adapts from 3.5mm to double (red and white) RCA connectors. These red and white can go into the red and white RCA plug inputs of a TV, or a stereo set, or to the above mentioned RCA to SCART plug. Another option for audio (when not using HDMI) is to connect the 3.5mm jackplug to an amplified speakerset. Do not connect the 3.5 mm jack directly to a headset, as the 3.5 mm audio output isn't suitable to drive headsets, only amplifier inputs. Attaching a low impedance load, (such as a headset) to the stereo audio output may lead to distorted sound.

'''Note: There is no VGA output available, so older VGA monitors will require an expensive adaptor.'''

Using an HDMI to DVI-D (digital) adaptor plus a DVI to VGA adaptor will not work. HDMI does not supply the DVI-A (analogue) needed to convert to VGA - converting an HDMI or DVI-D source to VGA (or component) needs an active converter. (It can work out cheaper to buy a new monitor.) The lack of VGA has been acknowledged as a priority issue. In a [http://interviews.slashdot.org/story/11/09/14/1554243/Eben-Upton-Answers-Your-Questions Q/A with Slashdot] Eben said that they plan to look into providing some form of add-on.

''For detailed information see [[Rpi Screens]].''

==Power Supply==
The unit uses a Micro USB connection to power itself (only the power pins are connected - so it will not transfer data over this connection). A standard modern phone charger with a micro-USB connector will do, but needs to produce at least 700mA at 5 volts. Check your power supply's ratings carefully, and [http://www.raspberrypi.org/forum/general-discussion/power-supply-warning beware cheap knock-offs!]. Suitable mains adaptors will be available from the [http://www.raspberrypi.com RPi Shop] as well as [http://thepihut.com/collections/power-supplies The Pi Hut's Raspberry Pi Store] or [http://www.ebay.co.uk/itm/330844162509 eBay] and are recommended if you are unsure what to use.

You can use a range of other power sources (assuming they are able to provide enough current ~700mA):
* Computer USB Port or powered USB hub (will depend on power output)
* Special wall warts with USB ports
* Mobile Phone Backup Battery (will depend on power output) (in theory - needs confirmation)
* Modern TV with built-in USB (for example, it has been shown to work with the Sony KDL-40HX723 and KDL-55NX813)
* Internet Routers with USB Ports (the BT Home Hub 3 seems to run the Pi nicely)

To use the above, you'll need a USB A 'male' to USB micro 'male' cable - these are often shipped as data cables with mobile phones.

''For detailed information about power requirements see [[Rpi_Hardware#Power | RPi Hardware - Power]].''

==Cables==
You will probably need a number of cables in order to connect your RPi up.
# Micro-B USB Power Cable (see above) [http://en.wikipedia.org/wiki/File:MicroB_USB_Plug.jpg picture]. This has to be a [[On the RPi usb power cable|high quality one]]. Tested cables available at [http://thepihut.com/collections/cables The Pi Hut's Raspberry Pi Store]
# HDMI-A [http://en.wikipedia.org/wiki/File:HDMI.jpg picture] or Composite cable [http://en.wikipedia.org/wiki/File:Composite-video-cable.jpg picture], plus DVI adaptor [http://en.wikipedia.org/wiki/File:Adapter_dvi_hdmi_S7302224_wp.jpg picture] or SCART adaptor [http://en.wikipedia.org/wiki/File:Multiconnector-scart-chti.jpg picture] if required, to connect your RPi to the Display/Monitor/TV of your choice. Tested cables available at [http://thepihut.com/collections/cables The Pi Hut's Raspberry Pi Store]
# Audio cable [http://en.wikipedia.org/wiki/File:Audio-TRS-Mini-Plug.jpg picture], this is not needed if you use a HDMI TV/monitor.
# Ethernet/LAN Cable (see below) [http://en.wikipedia.org/wiki/File:Ethernet_RJ45_connector_p1160054.jpg picture].

The price you pay for an HDMI cable can very wildly and under most circumstances a low-cost cable from a reputable online or local supplier will be absolutely fine, but the definition of what constitutes 'low cost' can vary wildly - for example, in the UK, a 1m cable can be purchased for anything between £1 and £24.99.
If, however, you want to drive a display some distance from the RPi (say greater than the ubiquitous 1.8m/6ft), or you are using a video switch to share a display between several devices, then higher quality cables might be wise - for example, a pair of 1m HDMI cables purchased in a UK 'pound shop' worked fine when directly connected between the RPi and a display, but would not give a stable picture when used via an HDMI switch. Replacing the £1 1m cable with a 1.5m cable bought online for £1.30 fixed the problem.
For more insight: [http://www.techradar.com/news/video/why-you-dont-need-to-spend-more-than-2-on-an-hdmi-cable-1071343 Why you don't need to spend more than £2 on an HDMI cable]

==Additional Peripherals==
You may decide you want to use various other devices with your RPi, such as Flash Drives/Portable Hard Drives, Speakers etc.

''For detailed information see [[RPi VerifiedPeripherals | RPi Verified Peripherals]].''

===Internet Connectivity===

This may be an Ethernet/LAN cable (standard RJ45 connector) or a USB WiFi adaptor. The RPi ethernet port is auto-sensing which means that it may be connected to a router or directly to another computer (without the need for a crossover cable<ref name=autoMDIX>[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]</ref>).

''Support for USB WiFi adaptors will vary - see [[RPi VerifiedPeripherals | RPi Verified Peripherals]].''

Note: If a Netgear router has a blank in the fourth box of the subnet mask, raspbian will interpret that as a 255, not as a '0' like Ubuntu will do. This will give you a subnet mask of 255.255.255.255 and a useless network connection. Changing the router's setting to put a '0' in the last field and reinitializing the network will fix this.

===USB-Hub===
In order to connect additional devices to the RPi, you may want to obtain a USB Hub, which will allow multiple devices to be used.

It is nearly a requirement that a '''powered''' hub is used - this will provide any additional power to the devices without affecting the RPi itself. The USB ports are fused at about 140ma each without an additional external power source. This not enough to power a hard drive, and you may even have trouble powering wireless adapters and other peripherals. There is enough current out there, however, for mice and most keyboards. (see [[Rpi_Hardware#Power | RPi Hardware - Power]] section).

USB version 2.0 is recommended. USB version 1.1 is fine for keyboards and mice, but may not be fast enough for other accessories.

===Heatsink===
Not a vital accessory for your RPi, but will help to reduce the CPU's temperature whilst under load. Available from [http://www.etsy.com/shop/nhslzt Etsy] [http://thepihut.com/collections/heatsinks The Pi Hut's Raspberry Pi Store] or [http://www.ebay.co.uk/itm/330758220781 eBay]

===Case===
Since the RPi is supplied without a case, it will be important to ensure that you do not use it in places where it will come into contact with conductive metal or liquids, unless suitably protected. Some form of [[Rpi Cases | case]] should be considered, and there is a [http://www.raspberrypi.org/forum/general-discussion/cases-for-the-raspberry-pi Rpi case thread] on the forum. Cases are also available from [http://thepihut.com/collections/cases The Pi Hut's Raspberry Pi Store] and [http://store.mobileappsystems.com MobileApp Systems].

''For detailed information see [[Rpi Cases]].''

===Real Time Clock===
There are a number of possible solutions for real time clocks, but so far, most are either expensive or not particularly friendly.

One promising device is the Cymbet Evaluation board (CBC-EVAL-06) available from digikey for approximately $30.
Cymbet is in the business of making small batteries and this eval board is intended just as a demonstration of their product using COTS parts on a small board that plugs directly into the USB. Their product is actually the battery that backs up the RTC memory and oscillator when not receiving power from the USB. However, this demo board is very well suited to this application. Ideally, a maker-oriented company will pick up this reference design and start producing boards based on it at a lower cost in larger volume.

To use this board, you will need some software. libmpsse from Google Code (http://code.google.com/p/libmpsse/) is a GPL library that can talk to the board in user-space.

User friendly software is a work in progress visible on GITHub http://github.com/owendelong/Cymbet-RTC

===SD card reader===
If you will not use a preloaded SD card to boot from, you will need an SD card reader to prepare an SD card.

Note that the SD card reader will be connected to a traditional PC, not to the RPi. You may use an SD card reader integrated into your PC, or you may use a dedicated USB-connected SD card reader. Note that several peripherals may also be used as an SD card reader, for example cameras, smartphones, camcorders and GPS units.

===Expansion & Low Level Peripherals===
If you plan on making use of the low level interfaces available on the RPi, then ensure you have suitable header pins for the GPIO (and if required JTAG) suitable for your needs.

Also if you have a particular low-level project in mind, then ensure you design in suitable protection circuits to keep your RPi safe (details will be made available within the [[RaspberryPiBoardProjects | RPi Projects, Guides & Tutorials]] section).

''For detailed information see [[Rpi Low-level peripherals | Rpi Low-level Peripherals]].''

=Connecting Together=

[[File:Raspi-Model-AB-Mono-1-699x1024.png|200px|thumb|right|A diagram denoting the places of the different components on the Rpi, made by Paul Beech. Click to enlarge.]]
You can use the diagram to connect everything together, or use the following instructions:

# Plug the preloaded SD Card into the Pi.
# Plug the USB keyboard and mouse into the Pi, perhaps via a USB Hub. Connect the Hub to power, if necessary.
# Plug the video cable into the screen (TV) and into the Pi.
# Plug your extras into the Pi (USB WiFi, Ethernet cable, hard drive etc.). This is where you may really need a USB Hub.
# Ensure that your USB Hub (if any) and screen are working.
# Plug the power source into the main socket.
# With your screen on, plug the other end of the power source into the Pi.
# The Pi should boot up and display messages on the screen.

It is always recommended to connect the MicroUSB Power to the unit last (while most connections can be made live, it is best practice to connect items such as displays and other connections with the power turned off).

If you use both a R-PI power supply and a powered hub, its recommended you connect them to the same switched power bar, and use the switch on the power bar to switch off both the R-PI and hub at the exact same time.

Also, always shutdown using the software shutdown function, not by pulling the plug. When not using a GUI, (with a GUI use the GUI command) you can use the command "shutdown -h now", and power off when all the LED's on the board (except the power LED) go off. This is especially important the first time you boot, as in the process the R-PI modifies the content of the SD-card, without a clean shutdown the contents of the card may be damaged.

The RPi may take a long time to boot when powered-on for the first time, so be patient, and cleanly shutdown afterwards, as described above!

=External Links=

For a verbose guide aimed at absolute beginners, see [http://h2g2.com/A13413584 Peripherals You'll Need] and [http://h2g2.com/A9143796 Getting Started] in h2g2's 'Introducing the Raspberry Pi'.

=References=
<references/>
{{Template:Raspberry Pi}}

RPi Buying Guide

2013-03-10T13:51:37Z

AndrewS: /* Accessories */ Added link to cases page

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

Raspberry Pi has appointed [http://www.element14.com/raspberrypi Farnell] and [http://rswww.com RS Components] as its authorised manufacturing parners distributors.

As of July 16th 2012, both [http://www.element14.com/raspberrypi Premier Farnell] and [http://rswww.com RS Components] have removed their "one per customer" restriction. Both consumers and businesses alike should now be able to buy bulk stock of the Raspberry Pi.

Raspberry Pi's distributors will ship worldwide to the best of their ability (ie subject to origin export and local import laws).

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]

Farnell have also been refusing to sell direct to some consumers in the EU, to the best of my knowlage they have not given full details of why.

There are three main options for buying a Raspberry Pi, buying direct from the distributor, buying from a subsidary or sister company of the distributor or buying from a third party reseller which option is best will depend on the location of the customer, the number of Raspberry Pi's being purchased, and the urgency of the order.

All new orders from the main distributors should now be filled with 512 MB rev 2 Raspberry Pi's. However, some third-party resellers may still have stock of the older models.

Note that stock status may change quickly. It may be worth checking a local supplier even if they are listed as out of stock here.

==Main distributors and subsidaries/sister companies==
==Farnell==
http://www.farnell.com/
Farnell are one of the two main distributors, as of 2012-11-21 their main European operation is out of stock and quoting a three-week lead time. Reports from the forum are that Farnell usually beat their delivery estimates.

For European customers, the customer is asked whether they are "consumer" or "business". If the customer selects business, they are taken back to Farnell's regular website to order. If the customer selects consumer, they are taken to a dedicated Raspberry Pi site which only offers a small selection of Raspberry Pi related products and gives no information on stock status. Farnell's site claims that consumers who do not have a previous account cannot use the "business" option but it is not clear if this is actually true for all countries. For some countries consumers are directed to third party resellers. The order code for the Raspberry Pi is 2191863.

===Element14===
http://www.element14.com
The "Element14" brand is used by a number of different operations within the Premier Farnell group and is also used for the groups "social" operation. In the Asia-Pacific region the Element 14 brand has completely replaced the previous "Premier Electronics" brand for asia and the previous "Farnell" brand for australia and new-zealand. In Europe, the Element14 brand is used in paralell with the Farnell brand. In North america the Element14 brand is used in parallel with the Newark brand.

===Newark===
http://www.newark.com/
Newark is the main American branch of the Premier Farnell group (Farnell's parent company). As of 2012-11-21, they are out of stock of Raspberry Pi's, but claim 1321 Expected to ship 2012-11-26 and Further stock expected to ship 2012-12-20.

===Element14 AU/NZ===
http://au.element14.com/ http://nz.element14.com/
On Element14's Australian operation (which also serves New Zealand) as of 2012-11-21 availability is listed as "please call" and "supplier lead time" is listed as 30 days. The order code for the Raspberry Pi is 2191863.

===Element 14 Asia===
http://cn.element14.com/ http://hk.element14.com/ http://in.element14.com/ http://cn.element14.com/ http://kr.element14.com/ http://my.element14.com/ http://ph.element14.com/ http://sg.element14.com/ http://tw.element14.com/ http://th.element14.com/
Element14 have warehouses in Singapore and Shanghi. It appears that some countries are served from both warehouses while others are served from only one or the other. UK stock is also listed on these sites. As of 2012-11-21, Element14's Asian operation has 331 Raspberry Pi's in stock in Shanghi and 617 Raspberry Pi's in stock in Singapore. The order code for the Raspberry Pi is 2191863.

===CPC===
http://cpc.farnell.com/
CPC is a branch of the Premier Farnell group in the UK based in Preston. As of 2012-11-21, they have 3100 Raspberry Pi's in stock. The order code for the Raspberry Pi is SC12590.

===MCM===
http://www.mcmelectronics.com/
MCM is a branch of the Premier Farnell group in the US based in Centerville, Ohio. As of 2012-11-21, they are out of stock and give an estimated ship date of 2012-12-07.

==RS components==
http://rswww.com/
RS are the other main distributor. Like Farnell they have a consumer site and business option with the consumer option taking users to a dedicated Raspberry Pi store while the business option takes them back to the regular RS site. They do not state whether consumers must use the consumer site or not. The order code for the Raspberry Pi is 756-8308. As of 2012-11-21, the Raspberry Pi is listed as "Temporarily out of stock - back order for despatch 21/12/2012".

RS has delayed existing orders on several occasions and are reported on the forum as being very difficult to communicate with.

===Allied electronics===
http://www.alliedelec.com/
Allied electronics is the US sister company of RS. The order code for the Raspberry Pi is 70229569. They website does not give a predicted dispatch date and state that "the estimated delivery time is uncertain and will likely take several months".

Reports from the forum are that Allied are easier to communicate with than RS, but they do not appear to be being kept will informed of the stock situation by RS.

==Resellers==
There are now many companies reselling the Raspberry Pi.

===RPF endorsed resellers===
====Maplin====
Maplin sells the Raspberry Pi in the UK but only as part of a kit including power supply, keyboard and mouse, programmed 4 GB SD card, HDMI cable and wireless dongle. As of 2012-11-21, they list the Raspberry Pi kit as in stock for home delivery and also in stock in some stores.

===Farnell Approved resellers===
Farnell now direct consumers in many countries to "approved retailers" rather than selling to them directly. Some of these suppliers specialise in the Raspberry Pi while others are general Farnell resellers.

====Electrocomponentes S.A====
http://www.electrocomponentes.com/
Electrocomponentes S.A sells Farnell producs in Argentina.

====Arabian Electric & Electronics Est.====
fisuoyla@batelco.com.bh
Arabian Electric & Electronics Est sells Farnell products in Bahrain.

====Minifo====
http://www.minifo.com/
Minifo is a Raspberry Pi retailer in Belgium. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Electromin S.A.====
http://www.electromin.cl/
Electromin S.A. sells Farnell producs in Chile.

====Betatech Ltd====
http://www.farnell.com/distributors/cyprus_bet.htm
Betatech Ltd sells Farnell products in Cyprus.

====Grand soloutions====
http://www.gs.com.eg/
Grand soloutions sells Farnell producs in Egypt. Unfortunately, searching their website by Farnell part number seems to be currently broken.

====Partco Oy====
http://www.partco.biz/
Partco sells the Raspberry Pi, Arduino and a selection of electronic components in Finland. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

==== kubii ====
http://www.kubii.fr/
kubii sells the Raspberry Pi, together with a selection of accessories. The website was created when Farnell changed their distribution policy.

====Málna PC Magyarország ====
http://malnapc.hu/
Málna PC Magyarország is a Raspberry Pi reseller in Hungary.

====Midbaejarradio EHF====
Midbaejarradio EHF is the authorised Farnell distributor for Iceland.

====Lion====
http://www.lion.co.il/h?q=RASPBERRY
Lion sells the Raspberry Pi in Israel. As of 2012-11-21, they do not appear to have stock.

====International Oilfield Supplies====
http://www.farnell.com/distributors/malta_int.htm
International Oilfield Supplies are the authorised Farnell distributor for Malta.

====Makkays====
http://www.farnell.com/distributors/pakistan_mak.htm
Makkays is the authorised Farnell distributor for Pakistan.

====kamami====
http://www.kamami.pl/
kamami sells the Raspberry Pi in Poland.

====Mixtronica====
http://www.mixtronica.com/
Mixtronica sell Farnell products in Portugal.

====Computer and Engineering Specialists Co====
http://www.farnell.com/distributors/saudiarabia_ces.htm
CESCO Group is an authorised Farnell distributor for Saudi Arabia.

====Dialogue s.r.o====
http://www.dialogue.sk/index.php?page=textaktual&id=71
Dialogue s.r.o sells the Raspberry Pi and accessories in Slovakia.

====IC elektronika d.o.o.====
http://www.ic-elect.si/
IC elektronika d.o.o. sells Farnell products in Slovenia.

====Electrocomp express====
http://www.eexpress.co.za/
Electrocomp express sells Farnell products in South Africa. As of 2012-11-21, they list the Raspberry Pi as awaiting delivery and do not give a lead time.

====Orel Solutions (PVT) Ltd====
http://www.farnell.com/distributors/srilanka_osp.htm
Orel Solutions (PVT) Ltd is the authorised Farnell distributor for Sri Lanka.

====Mikro-Kit Elektronik AB====
https://www.microkit.se/
Mikro-Kit Elektronik AB sells the Raspberry Pi (and it would appear other farnell producs too) in Sweeden. As of 2012-11-21, they list the Raspberry Pi as out of stock with expected delivery 2012-12-11.

====digitec====
http://www.digitec.ch/
Digitec sells the Raspberry Pi in Switzerland.

====Yildrim====
http://www.yildirimelektronik.com/
Yildrim sells Farnell products in Turkey.

====DGM distribution====
http://www.farnell.com/distributors/unitedarabemirates_dgm.htm
DGM distribution is the authorised Farnell distributor for Dubai.

===Other resellers===
====Newit====
http://www.newit.co.uk/
Newit are a British company selling a variety of ARM hardware and accessories, including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Makershed====
http://www.makershed.com/
Makershed is a US company that sells various stuff aimed at hardware hackers including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as out of stock.

====Tandy====
http://www.tandyonline.co.uk/
Tandy is a UK company that sells a small selection of electronics stuff. As of 2012-12-08, Tandy has both 256MV rev 1.1 boards and 512MB rev 2 boards in stock.

Note that the current Tandy is a division of adslnation and other than buying the name has little relationship to the Tandy of old.

====Adafruit====
http://www.adafruit.com/
Adafruit is a US company that makes a variety of boards for hardware hackers and tinkerers, some specifically designed for use with the Raspberry Pi. They sell the Raspberry Pi separately, as well as part of a large starter kit including everything needed to start experimenting with the Raspberry Pi and external hardware on the GPIO. They also currently include a free Raspberry Pi with orders over $350.

====SNOOTLAB====
SNOOTLAB
http://snootlab.com/
Sells products in French as well as English. They also sell a number of different components and products such as Arduinos too.

====Tenettech====
Tenettech
http://www.tenettech.com/product/2184/raspberry-pi
Tenettech is Bangalore based company who sells software/hardware based solutions in India. They sell Raspberry Pi and Raspberry Pi kit (which include the Raspberry Pi, SD card, card reader, HDMI cable, and video cable).

====AVIES Tech====
http://www.shopavies.com
AVIES Tech is a US company that provides installation and integration solutions for a variety of media centric hardware. They also carry the Raspberry Pi and related accessories.

====Amazon====
[http://www.amazon.com/ Amazon] also sells boards through the Raspberry Pi name for U$D 48.03. You can buy one [http://www.amazon.com/Raspberry-Pi-Model-Revision-512MB/dp/B009SQQF9C/ref=sr_1_1?ie=UTF8&qid=1361718715&sr=8-1&keywords=raspberry+pi here].

====Bitcrafts====
[http://etsy.com/shop/bitcrafts Bitcrafts] ships the '''Model A''' worldwide. You can buy one [http://www.etsy.com/listing/124198601/raspberry-pi-model-a? here]. They also sell cases, pIO micro SD adapters and other related accessories.

==Licensed Manufacture==
The foundation has chosen to license manufacture of the Raspberry Pi, which should provide several advantages including:

# 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 Pi's; the Raspberry Pi will now be being built to match demand.
# 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.
# Both RS Components and Premier Farnell will be taking preorders, something which the foundation would otherwise be unable to do.
# The foundation will still receive a percentage from the sale of every Raspberry Pi sold, which will be put straight back into the charity.
# 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.

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 (2012-02-28)].

Unfortunately the switch to licensed manufacture has also resulted in a marked reduction in transparency of the process as Farnell and RS consider detailed information of what is going on to be confidential.

==What You Get In The Box==
1. Pre-Assembled Raspberry Pi board

2. A sheet containing a combination of regulatory information and some very brief instructions. 

''Note:''

''1. The board will be supplied assembled (since most of the components are not suitable for home builds, including the BGA<ref name="BGA">http://en.wikipedia.org/wiki/Ball_grid_array</ref>package mounted SoC<ref name="SoC">http://en.wikipedia.org/wiki/System_on_a_chip</ref> and PoP<ref name="PoP">http://en.wikipedia.org/wiki/Package_on_package</ref> memory).''
''2. The board has the GPIO header pins for the primary GPIO header (but not the secondary GPIO header added on the revision 2 boards) populated. The SoC JTAG may or may not be present depending on when the board was manufactured and at which factory but aren't really of use to end users anyway due to the lack of Broadcom documentation. The LAN JTAG header does not seem to be present on any boards.
''3. All other connectors will be assembled in place.''

==Accessories==
To use the Raspberry Pi, a user will typically require some accessories. All of the Raspberry Pi vendors listed above sell some accessories, but the exact range varies. Accessories you should consider include.
* USB Power Supply (UK/EU/US Compatible; 5V, 700mA-1500mA(1.5A))<ref>http://www.raspberrypi.org/forum/general-discussion/is-the-raspberrypi-going-to-be-sold-as-a-kit/#p32289</ref>
* SD card. Most distributors are selling pre-prepared SD cards which are usually 4 GB. Software is available to prepare your own SD cards.
* There is a wide choice of [[RPi_Cases|cases]], most distributors will have some but shopping around for one you like is suggested.
* There are a variety of [[Rpi expansion boards|AddOn/Expansion Boards]] now available, see that page for more details.
''See [[RPi Hardware Basic Setup#Typical Hardware You Will Need | Typical Hardware You Will Need]] for details about other items you may require.''

==Price==
The price is $35USD before shipping, duty, and tax, about $60 after.

Although the foundation is UK based, the guide price of the units are in USD since the Raspberry Pi components are sourced in USD$.

The price is $25USD (~£16GBP) for model A, and $35USD (~£23GBP) for model B.

Items will be subject to local tax (that is, UK will have 20% VAT added) and shipping cost is not included.

See the following update on [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

==Clones & Copies==
The foundation plans to release all the required [[RPi_Hardware#Schematic_.2F_Layout|schematics]] and plans to reproduce the Raspberry Pi hardware, so clones and copies will be welcome.

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.

==Historic information==

# The foundation have built an initial run of 10,000 Model-B units.
# Due to extreme demand, the units were NOT sold directly from the [http://www.raspberrypi.com shop] (see [[#Licensed Manufacture]] below).
# You may buy a Raspberry Pi from [http://www.element14.com/raspberrypi Farnell] or from [http://rswww.com RS Components]
# A limit of one unit per person was applied for the first batch and some time afterwards

* There were reports that several people ordered multiple units at launch,
however it appears that Farnell removed any excess items when they reviewed
and confirmed the order for shipping dates.
This has also appears to apply for the pre-orders they have taken.
Many customers also ordered from both Farnell and RS.

===1st Batch Order FAQ===
NOTE: While every attempt has been made to provide accurate information,
this FAQ is not official and is based on what information is available at the time of writing.

====Press Releases====
'''Farnell:'''

[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.

'''RS Components:'''

[http://www.electrocomponents.com/media/press-releases/2012/02/29th/ Post-Launch statement by RS Components]

[http://uk.rs-online.com/web/generalDisplay.html?id=raspberrypi&file=questions&cm_sp=raspberrypi-_--_-questions Raspberry Pi, Your Questions Answered by RS Components]

====Q: Couldn't this have been handled better, I couldn't get on the site to order and they sold too quickly?====
Both distributors were indeed unprepared for the volume of traffic the launch generated (they were warned by the foundation before hand).

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.

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).
Even if it is half of that, it means the number of available units was less than 1% of the demand.

====Q: If interest was obviously so high, why only build 10,000 units?====
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 task in itself. Much of that funding came from the Foundation Trustees' own personal investment.

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.

====Q: I've been unable to register an account with the distributor, as I am not a company?====
There have been several reported problems with individuals placing orders (that is, not having company accounts or details).

Both distributors "should" 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.

Often, many of the company related fields on application are optional. If in doubt, contact their sales team for help.

====Q: Worldwide launch? It was not available here! ====
The distributors decided to make the units only available from selected locations. It appears the foundation were not made aware of this beforehand.

Considering the small number of available units, it would have been unlikely to have improved the situation.

Worldwide availability will be monitored, it is expected that they will be made available as soon as possible.

====Q: The price for the Raspberry Pi from Farnell versus the price from RS Components is different, why?====
Please see the following page for details about [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

====Q: I've only been able to register my interest, what now?====
Be patient, both distributors have said they will contact people when they have more details (alternatively keep an eye on their sites for news).

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.

====Q: I registered on the Raspberry Pi Site's Mailing List, but I didn't get an email====
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.

The email contained the same information about the announcement as was publicly posted on the website (2012-02-28) before launch day, no additional or extra information was given through the email.

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Buying Guide

2013-03-10T13:49:25Z

AndrewS: /* Clones & Copies */ Added link to schematics section

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

Raspberry Pi has appointed [http://www.element14.com/raspberrypi Farnell] and [http://rswww.com RS Components] as its authorised manufacturing parners distributors.

As of July 16th 2012, both [http://www.element14.com/raspberrypi Premier Farnell] and [http://rswww.com RS Components] have removed their "one per customer" restriction. Both consumers and businesses alike should now be able to buy bulk stock of the Raspberry Pi.

Raspberry Pi's distributors will ship worldwide to the best of their ability (ie subject to origin export and local import laws).

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]

Farnell have also been refusing to sell direct to some consumers in the EU, to the best of my knowlage they have not given full details of why.

There are three main options for buying a Raspberry Pi, buying direct from the distributor, buying from a subsidary or sister company of the distributor or buying from a third party reseller which option is best will depend on the location of the customer, the number of Raspberry Pi's being purchased, and the urgency of the order.

All new orders from the main distributors should now be filled with 512 MB rev 2 Raspberry Pi's. However, some third-party resellers may still have stock of the older models.

Note that stock status may change quickly. It may be worth checking a local supplier even if they are listed as out of stock here.

==Main distributors and subsidaries/sister companies==
==Farnell==
http://www.farnell.com/
Farnell are one of the two main distributors, as of 2012-11-21 their main European operation is out of stock and quoting a three-week lead time. Reports from the forum are that Farnell usually beat their delivery estimates.

For European customers, the customer is asked whether they are "consumer" or "business". If the customer selects business, they are taken back to Farnell's regular website to order. If the customer selects consumer, they are taken to a dedicated Raspberry Pi site which only offers a small selection of Raspberry Pi related products and gives no information on stock status. Farnell's site claims that consumers who do not have a previous account cannot use the "business" option but it is not clear if this is actually true for all countries. For some countries consumers are directed to third party resellers. The order code for the Raspberry Pi is 2191863.

===Element14===
http://www.element14.com
The "Element14" brand is used by a number of different operations within the Premier Farnell group and is also used for the groups "social" operation. In the Asia-Pacific region the Element 14 brand has completely replaced the previous "Premier Electronics" brand for asia and the previous "Farnell" brand for australia and new-zealand. In Europe, the Element14 brand is used in paralell with the Farnell brand. In North america the Element14 brand is used in parallel with the Newark brand.

===Newark===
http://www.newark.com/
Newark is the main American branch of the Premier Farnell group (Farnell's parent company). As of 2012-11-21, they are out of stock of Raspberry Pi's, but claim 1321 Expected to ship 2012-11-26 and Further stock expected to ship 2012-12-20.

===Element14 AU/NZ===
http://au.element14.com/ http://nz.element14.com/
On Element14's Australian operation (which also serves New Zealand) as of 2012-11-21 availability is listed as "please call" and "supplier lead time" is listed as 30 days. The order code for the Raspberry Pi is 2191863.

===Element 14 Asia===
http://cn.element14.com/ http://hk.element14.com/ http://in.element14.com/ http://cn.element14.com/ http://kr.element14.com/ http://my.element14.com/ http://ph.element14.com/ http://sg.element14.com/ http://tw.element14.com/ http://th.element14.com/
Element14 have warehouses in Singapore and Shanghi. It appears that some countries are served from both warehouses while others are served from only one or the other. UK stock is also listed on these sites. As of 2012-11-21, Element14's Asian operation has 331 Raspberry Pi's in stock in Shanghi and 617 Raspberry Pi's in stock in Singapore. The order code for the Raspberry Pi is 2191863.

===CPC===
http://cpc.farnell.com/
CPC is a branch of the Premier Farnell group in the UK based in Preston. As of 2012-11-21, they have 3100 Raspberry Pi's in stock. The order code for the Raspberry Pi is SC12590.

===MCM===
http://www.mcmelectronics.com/
MCM is a branch of the Premier Farnell group in the US based in Centerville, Ohio. As of 2012-11-21, they are out of stock and give an estimated ship date of 2012-12-07.

==RS components==
http://rswww.com/
RS are the other main distributor. Like Farnell they have a consumer site and business option with the consumer option taking users to a dedicated Raspberry Pi store while the business option takes them back to the regular RS site. They do not state whether consumers must use the consumer site or not. The order code for the Raspberry Pi is 756-8308. As of 2012-11-21, the Raspberry Pi is listed as "Temporarily out of stock - back order for despatch 21/12/2012".

RS has delayed existing orders on several occasions and are reported on the forum as being very difficult to communicate with.

===Allied electronics===
http://www.alliedelec.com/
Allied electronics is the US sister company of RS. The order code for the Raspberry Pi is 70229569. They website does not give a predicted dispatch date and state that "the estimated delivery time is uncertain and will likely take several months".

Reports from the forum are that Allied are easier to communicate with than RS, but they do not appear to be being kept will informed of the stock situation by RS.

==Resellers==
There are now many companies reselling the Raspberry Pi.

===RPF endorsed resellers===
====Maplin====
Maplin sells the Raspberry Pi in the UK but only as part of a kit including power supply, keyboard and mouse, programmed 4 GB SD card, HDMI cable and wireless dongle. As of 2012-11-21, they list the Raspberry Pi kit as in stock for home delivery and also in stock in some stores.

===Farnell Approved resellers===
Farnell now direct consumers in many countries to "approved retailers" rather than selling to them directly. Some of these suppliers specialise in the Raspberry Pi while others are general Farnell resellers.

====Electrocomponentes S.A====
http://www.electrocomponentes.com/
Electrocomponentes S.A sells Farnell producs in Argentina.

====Arabian Electric & Electronics Est.====
fisuoyla@batelco.com.bh
Arabian Electric & Electronics Est sells Farnell products in Bahrain.

====Minifo====
http://www.minifo.com/
Minifo is a Raspberry Pi retailer in Belgium. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Electromin S.A.====
http://www.electromin.cl/
Electromin S.A. sells Farnell producs in Chile.

====Betatech Ltd====
http://www.farnell.com/distributors/cyprus_bet.htm
Betatech Ltd sells Farnell products in Cyprus.

====Grand soloutions====
http://www.gs.com.eg/
Grand soloutions sells Farnell producs in Egypt. Unfortunately, searching their website by Farnell part number seems to be currently broken.

====Partco Oy====
http://www.partco.biz/
Partco sells the Raspberry Pi, Arduino and a selection of electronic components in Finland. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

==== kubii ====
http://www.kubii.fr/
kubii sells the Raspberry Pi, together with a selection of accessories. The website was created when Farnell changed their distribution policy.

====Málna PC Magyarország ====
http://malnapc.hu/
Málna PC Magyarország is a Raspberry Pi reseller in Hungary.

====Midbaejarradio EHF====
Midbaejarradio EHF is the authorised Farnell distributor for Iceland.

====Lion====
http://www.lion.co.il/h?q=RASPBERRY
Lion sells the Raspberry Pi in Israel. As of 2012-11-21, they do not appear to have stock.

====International Oilfield Supplies====
http://www.farnell.com/distributors/malta_int.htm
International Oilfield Supplies are the authorised Farnell distributor for Malta.

====Makkays====
http://www.farnell.com/distributors/pakistan_mak.htm
Makkays is the authorised Farnell distributor for Pakistan.

====kamami====
http://www.kamami.pl/
kamami sells the Raspberry Pi in Poland.

====Mixtronica====
http://www.mixtronica.com/
Mixtronica sell Farnell products in Portugal.

====Computer and Engineering Specialists Co====
http://www.farnell.com/distributors/saudiarabia_ces.htm
CESCO Group is an authorised Farnell distributor for Saudi Arabia.

====Dialogue s.r.o====
http://www.dialogue.sk/index.php?page=textaktual&id=71
Dialogue s.r.o sells the Raspberry Pi and accessories in Slovakia.

====IC elektronika d.o.o.====
http://www.ic-elect.si/
IC elektronika d.o.o. sells Farnell products in Slovenia.

====Electrocomp express====
http://www.eexpress.co.za/
Electrocomp express sells Farnell products in South Africa. As of 2012-11-21, they list the Raspberry Pi as awaiting delivery and do not give a lead time.

====Orel Solutions (PVT) Ltd====
http://www.farnell.com/distributors/srilanka_osp.htm
Orel Solutions (PVT) Ltd is the authorised Farnell distributor for Sri Lanka.

====Mikro-Kit Elektronik AB====
https://www.microkit.se/
Mikro-Kit Elektronik AB sells the Raspberry Pi (and it would appear other farnell producs too) in Sweeden. As of 2012-11-21, they list the Raspberry Pi as out of stock with expected delivery 2012-12-11.

====digitec====
http://www.digitec.ch/
Digitec sells the Raspberry Pi in Switzerland.

====Yildrim====
http://www.yildirimelektronik.com/
Yildrim sells Farnell products in Turkey.

====DGM distribution====
http://www.farnell.com/distributors/unitedarabemirates_dgm.htm
DGM distribution is the authorised Farnell distributor for Dubai.

===Other resellers===
====Newit====
http://www.newit.co.uk/
Newit are a British company selling a variety of ARM hardware and accessories, including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Makershed====
http://www.makershed.com/
Makershed is a US company that sells various stuff aimed at hardware hackers including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as out of stock.

====Tandy====
http://www.tandyonline.co.uk/
Tandy is a UK company that sells a small selection of electronics stuff. As of 2012-12-08, Tandy has both 256MV rev 1.1 boards and 512MB rev 2 boards in stock.

Note that the current Tandy is a division of adslnation and other than buying the name has little relationship to the Tandy of old.

====Adafruit====
http://www.adafruit.com/
Adafruit is a US company that makes a variety of boards for hardware hackers and tinkerers, some specifically designed for use with the Raspberry Pi. They sell the Raspberry Pi separately, as well as part of a large starter kit including everything needed to start experimenting with the Raspberry Pi and external hardware on the GPIO. They also currently include a free Raspberry Pi with orders over $350.

====SNOOTLAB====
SNOOTLAB
http://snootlab.com/
Sells products in French as well as English. They also sell a number of different components and products such as Arduinos too.

====Tenettech====
Tenettech
http://www.tenettech.com/product/2184/raspberry-pi
Tenettech is Bangalore based company who sells software/hardware based solutions in India. They sell Raspberry Pi and Raspberry Pi kit (which include the Raspberry Pi, SD card, card reader, HDMI cable, and video cable).

====AVIES Tech====
http://www.shopavies.com
AVIES Tech is a US company that provides installation and integration solutions for a variety of media centric hardware. They also carry the Raspberry Pi and related accessories.

====Amazon====
[http://www.amazon.com/ Amazon] also sells boards through the Raspberry Pi name for U$D 48.03. You can buy one [http://www.amazon.com/Raspberry-Pi-Model-Revision-512MB/dp/B009SQQF9C/ref=sr_1_1?ie=UTF8&qid=1361718715&sr=8-1&keywords=raspberry+pi here].

====Bitcrafts====
[http://etsy.com/shop/bitcrafts Bitcrafts] ships the '''Model A''' worldwide. You can buy one [http://www.etsy.com/listing/124198601/raspberry-pi-model-a? here]. They also sell cases, pIO micro SD adapters and other related accessories.

==Licensed Manufacture==
The foundation has chosen to license manufacture of the Raspberry Pi, which should provide several advantages including:

# 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 Pi's; the Raspberry Pi will now be being built to match demand.
# 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.
# Both RS Components and Premier Farnell will be taking preorders, something which the foundation would otherwise be unable to do.
# The foundation will still receive a percentage from the sale of every Raspberry Pi sold, which will be put straight back into the charity.
# 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.

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 (2012-02-28)].

Unfortunately the switch to licensed manufacture has also resulted in a marked reduction in transparency of the process as Farnell and RS consider detailed information of what is going on to be confidential.

==What You Get In The Box==
1. Pre-Assembled Raspberry Pi board

2. A sheet containing a combination of regulatory information and some very brief instructions. 

''Note:''

''1. The board will be supplied assembled (since most of the components are not suitable for home builds, including the BGA<ref name="BGA">http://en.wikipedia.org/wiki/Ball_grid_array</ref>package mounted SoC<ref name="SoC">http://en.wikipedia.org/wiki/System_on_a_chip</ref> and PoP<ref name="PoP">http://en.wikipedia.org/wiki/Package_on_package</ref> memory).''
''2. The board has the GPIO header pins for the primary GPIO header (but not the secondary GPIO header added on the revision 2 boards) populated. The SoC JTAG may or may not be present depending on when the board was manufactured and at which factory but aren't really of use to end users anyway due to the lack of Broadcom documentation. The LAN JTAG header does not seem to be present on any boards.
''3. All other connectors will be assembled in place.''

==Accessories==
To use the Raspberry Pi, a user will typically require some accessories. All of the Raspberry Pi vendors listed above sell some accessories, but the exact range varies. Accessories you should consider include.
* USB Power Supply (UK/EU/US Compatible; 5V, 700mA-1500mA(1.5A))<ref>http://www.raspberrypi.org/forum/general-discussion/is-the-raspberrypi-going-to-be-sold-as-a-kit/#p32289</ref>
* SD card. Most distributors are selling pre-prepared SD cards which are usually 4 GB. Software is available to prepare your own SD cards.
* There is a wide choice of cases, most distributors will have some but shopping around for one you like is suggested.
* There are a variety of [[Rpi expansion boards|AddOn/Expansion Boards]] now available, see that page for more details.
''See [[RPi Hardware Basic Setup#Typical Hardware You Will Need | Typical Hardware You Will Need]] for details about other items you may require.''

==Price==
The price is $35USD before shipping, duty, and tax, about $60 after.

Although the foundation is UK based, the guide price of the units are in USD since the Raspberry Pi components are sourced in USD$.

The price is $25USD (~£16GBP) for model A, and $35USD (~£23GBP) for model B.

Items will be subject to local tax (that is, UK will have 20% VAT added) and shipping cost is not included.

See the following update on [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

==Clones & Copies==
The foundation plans to release all the required [[RPi_Hardware#Schematic_.2F_Layout|schematics]] and plans to reproduce the Raspberry Pi hardware, so clones and copies will be welcome.

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.

==Historic information==

# The foundation have built an initial run of 10,000 Model-B units.
# Due to extreme demand, the units were NOT sold directly from the [http://www.raspberrypi.com shop] (see [[#Licensed Manufacture]] below).
# You may buy a Raspberry Pi from [http://www.element14.com/raspberrypi Farnell] or from [http://rswww.com RS Components]
# A limit of one unit per person was applied for the first batch and some time afterwards

* There were reports that several people ordered multiple units at launch,
however it appears that Farnell removed any excess items when they reviewed
and confirmed the order for shipping dates.
This has also appears to apply for the pre-orders they have taken.
Many customers also ordered from both Farnell and RS.

===1st Batch Order FAQ===
NOTE: While every attempt has been made to provide accurate information,
this FAQ is not official and is based on what information is available at the time of writing.

====Press Releases====
'''Farnell:'''

[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.

'''RS Components:'''

[http://www.electrocomponents.com/media/press-releases/2012/02/29th/ Post-Launch statement by RS Components]

[http://uk.rs-online.com/web/generalDisplay.html?id=raspberrypi&file=questions&cm_sp=raspberrypi-_--_-questions Raspberry Pi, Your Questions Answered by RS Components]

====Q: Couldn't this have been handled better, I couldn't get on the site to order and they sold too quickly?====
Both distributors were indeed unprepared for the volume of traffic the launch generated (they were warned by the foundation before hand).

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.

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).
Even if it is half of that, it means the number of available units was less than 1% of the demand.

====Q: If interest was obviously so high, why only build 10,000 units?====
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 task in itself. Much of that funding came from the Foundation Trustees' own personal investment.

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.

====Q: I've been unable to register an account with the distributor, as I am not a company?====
There have been several reported problems with individuals placing orders (that is, not having company accounts or details).

Both distributors "should" 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.

Often, many of the company related fields on application are optional. If in doubt, contact their sales team for help.

====Q: Worldwide launch? It was not available here! ====
The distributors decided to make the units only available from selected locations. It appears the foundation were not made aware of this beforehand.

Considering the small number of available units, it would have been unlikely to have improved the situation.

Worldwide availability will be monitored, it is expected that they will be made available as soon as possible.

====Q: The price for the Raspberry Pi from Farnell versus the price from RS Components is different, why?====
Please see the following page for details about [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

====Q: I've only been able to register my interest, what now?====
Be patient, both distributors have said they will contact people when they have more details (alternatively keep an eye on their sites for news).

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.

====Q: I registered on the Raspberry Pi Site's Mailing List, but I didn't get an email====
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.

The email contained the same information about the announcement as was publicly posted on the website (2012-02-28) before launch day, no additional or extra information was given through the email.

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Buying Guide

2013-03-10T13:45:20Z

AndrewS: /* Price */ ModelA *is* now available

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

Raspberry Pi has appointed [http://www.element14.com/raspberrypi Farnell] and [http://rswww.com RS Components] as its authorised manufacturing parners distributors.

As of July 16th 2012, both [http://www.element14.com/raspberrypi Premier Farnell] and [http://rswww.com RS Components] have removed their "one per customer" restriction. Both consumers and businesses alike should now be able to buy bulk stock of the Raspberry Pi.

Raspberry Pi's distributors will ship worldwide to the best of their ability (ie subject to origin export and local import laws).

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]

Farnell have also been refusing to sell direct to some consumers in the EU, to the best of my knowlage they have not given full details of why.

There are three main options for buying a Raspberry Pi, buying direct from the distributor, buying from a subsidary or sister company of the distributor or buying from a third party reseller which option is best will depend on the location of the customer, the number of Raspberry Pi's being purchased, and the urgency of the order.

All new orders from the main distributors should now be filled with 512 MB rev 2 Raspberry Pi's. However, some third-party resellers may still have stock of the older models.

Note that stock status may change quickly. It may be worth checking a local supplier even if they are listed as out of stock here.

==Main distributors and subsidaries/sister companies==
==Farnell==
http://www.farnell.com/
Farnell are one of the two main distributors, as of 2012-11-21 their main European operation is out of stock and quoting a three-week lead time. Reports from the forum are that Farnell usually beat their delivery estimates.

For European customers, the customer is asked whether they are "consumer" or "business". If the customer selects business, they are taken back to Farnell's regular website to order. If the customer selects consumer, they are taken to a dedicated Raspberry Pi site which only offers a small selection of Raspberry Pi related products and gives no information on stock status. Farnell's site claims that consumers who do not have a previous account cannot use the "business" option but it is not clear if this is actually true for all countries. For some countries consumers are directed to third party resellers. The order code for the Raspberry Pi is 2191863.

===Element14===
http://www.element14.com
The "Element14" brand is used by a number of different operations within the Premier Farnell group and is also used for the groups "social" operation. In the Asia-Pacific region the Element 14 brand has completely replaced the previous "Premier Electronics" brand for asia and the previous "Farnell" brand for australia and new-zealand. In Europe, the Element14 brand is used in paralell with the Farnell brand. In North america the Element14 brand is used in parallel with the Newark brand.

===Newark===
http://www.newark.com/
Newark is the main American branch of the Premier Farnell group (Farnell's parent company). As of 2012-11-21, they are out of stock of Raspberry Pi's, but claim 1321 Expected to ship 2012-11-26 and Further stock expected to ship 2012-12-20.

===Element14 AU/NZ===
http://au.element14.com/ http://nz.element14.com/
On Element14's Australian operation (which also serves New Zealand) as of 2012-11-21 availability is listed as "please call" and "supplier lead time" is listed as 30 days. The order code for the Raspberry Pi is 2191863.

===Element 14 Asia===
http://cn.element14.com/ http://hk.element14.com/ http://in.element14.com/ http://cn.element14.com/ http://kr.element14.com/ http://my.element14.com/ http://ph.element14.com/ http://sg.element14.com/ http://tw.element14.com/ http://th.element14.com/
Element14 have warehouses in Singapore and Shanghi. It appears that some countries are served from both warehouses while others are served from only one or the other. UK stock is also listed on these sites. As of 2012-11-21, Element14's Asian operation has 331 Raspberry Pi's in stock in Shanghi and 617 Raspberry Pi's in stock in Singapore. The order code for the Raspberry Pi is 2191863.

===CPC===
http://cpc.farnell.com/
CPC is a branch of the Premier Farnell group in the UK based in Preston. As of 2012-11-21, they have 3100 Raspberry Pi's in stock. The order code for the Raspberry Pi is SC12590.

===MCM===
http://www.mcmelectronics.com/
MCM is a branch of the Premier Farnell group in the US based in Centerville, Ohio. As of 2012-11-21, they are out of stock and give an estimated ship date of 2012-12-07.

==RS components==
http://rswww.com/
RS are the other main distributor. Like Farnell they have a consumer site and business option with the consumer option taking users to a dedicated Raspberry Pi store while the business option takes them back to the regular RS site. They do not state whether consumers must use the consumer site or not. The order code for the Raspberry Pi is 756-8308. As of 2012-11-21, the Raspberry Pi is listed as "Temporarily out of stock - back order for despatch 21/12/2012".

RS has delayed existing orders on several occasions and are reported on the forum as being very difficult to communicate with.

===Allied electronics===
http://www.alliedelec.com/
Allied electronics is the US sister company of RS. The order code for the Raspberry Pi is 70229569. They website does not give a predicted dispatch date and state that "the estimated delivery time is uncertain and will likely take several months".

Reports from the forum are that Allied are easier to communicate with than RS, but they do not appear to be being kept will informed of the stock situation by RS.

==Resellers==
There are now many companies reselling the Raspberry Pi.

===RPF endorsed resellers===
====Maplin====
Maplin sells the Raspberry Pi in the UK but only as part of a kit including power supply, keyboard and mouse, programmed 4 GB SD card, HDMI cable and wireless dongle. As of 2012-11-21, they list the Raspberry Pi kit as in stock for home delivery and also in stock in some stores.

===Farnell Approved resellers===
Farnell now direct consumers in many countries to "approved retailers" rather than selling to them directly. Some of these suppliers specialise in the Raspberry Pi while others are general Farnell resellers.

====Electrocomponentes S.A====
http://www.electrocomponentes.com/
Electrocomponentes S.A sells Farnell producs in Argentina.

====Arabian Electric & Electronics Est.====
fisuoyla@batelco.com.bh
Arabian Electric & Electronics Est sells Farnell products in Bahrain.

====Minifo====
http://www.minifo.com/
Minifo is a Raspberry Pi retailer in Belgium. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Electromin S.A.====
http://www.electromin.cl/
Electromin S.A. sells Farnell producs in Chile.

====Betatech Ltd====
http://www.farnell.com/distributors/cyprus_bet.htm
Betatech Ltd sells Farnell products in Cyprus.

====Grand soloutions====
http://www.gs.com.eg/
Grand soloutions sells Farnell producs in Egypt. Unfortunately, searching their website by Farnell part number seems to be currently broken.

====Partco Oy====
http://www.partco.biz/
Partco sells the Raspberry Pi, Arduino and a selection of electronic components in Finland. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

==== kubii ====
http://www.kubii.fr/
kubii sells the Raspberry Pi, together with a selection of accessories. The website was created when Farnell changed their distribution policy.

====Málna PC Magyarország ====
http://malnapc.hu/
Málna PC Magyarország is a Raspberry Pi reseller in Hungary.

====Midbaejarradio EHF====
Midbaejarradio EHF is the authorised Farnell distributor for Iceland.

====Lion====
http://www.lion.co.il/h?q=RASPBERRY
Lion sells the Raspberry Pi in Israel. As of 2012-11-21, they do not appear to have stock.

====International Oilfield Supplies====
http://www.farnell.com/distributors/malta_int.htm
International Oilfield Supplies are the authorised Farnell distributor for Malta.

====Makkays====
http://www.farnell.com/distributors/pakistan_mak.htm
Makkays is the authorised Farnell distributor for Pakistan.

====kamami====
http://www.kamami.pl/
kamami sells the Raspberry Pi in Poland.

====Mixtronica====
http://www.mixtronica.com/
Mixtronica sell Farnell products in Portugal.

====Computer and Engineering Specialists Co====
http://www.farnell.com/distributors/saudiarabia_ces.htm
CESCO Group is an authorised Farnell distributor for Saudi Arabia.

====Dialogue s.r.o====
http://www.dialogue.sk/index.php?page=textaktual&id=71
Dialogue s.r.o sells the Raspberry Pi and accessories in Slovakia.

====IC elektronika d.o.o.====
http://www.ic-elect.si/
IC elektronika d.o.o. sells Farnell products in Slovenia.

====Electrocomp express====
http://www.eexpress.co.za/
Electrocomp express sells Farnell products in South Africa. As of 2012-11-21, they list the Raspberry Pi as awaiting delivery and do not give a lead time.

====Orel Solutions (PVT) Ltd====
http://www.farnell.com/distributors/srilanka_osp.htm
Orel Solutions (PVT) Ltd is the authorised Farnell distributor for Sri Lanka.

====Mikro-Kit Elektronik AB====
https://www.microkit.se/
Mikro-Kit Elektronik AB sells the Raspberry Pi (and it would appear other farnell producs too) in Sweeden. As of 2012-11-21, they list the Raspberry Pi as out of stock with expected delivery 2012-12-11.

====digitec====
http://www.digitec.ch/
Digitec sells the Raspberry Pi in Switzerland.

====Yildrim====
http://www.yildirimelektronik.com/
Yildrim sells Farnell products in Turkey.

====DGM distribution====
http://www.farnell.com/distributors/unitedarabemirates_dgm.htm
DGM distribution is the authorised Farnell distributor for Dubai.

===Other resellers===
====Newit====
http://www.newit.co.uk/
Newit are a British company selling a variety of ARM hardware and accessories, including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Makershed====
http://www.makershed.com/
Makershed is a US company that sells various stuff aimed at hardware hackers including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as out of stock.

====Tandy====
http://www.tandyonline.co.uk/
Tandy is a UK company that sells a small selection of electronics stuff. As of 2012-12-08, Tandy has both 256MV rev 1.1 boards and 512MB rev 2 boards in stock.

Note that the current Tandy is a division of adslnation and other than buying the name has little relationship to the Tandy of old.

====Adafruit====
http://www.adafruit.com/
Adafruit is a US company that makes a variety of boards for hardware hackers and tinkerers, some specifically designed for use with the Raspberry Pi. They sell the Raspberry Pi separately, as well as part of a large starter kit including everything needed to start experimenting with the Raspberry Pi and external hardware on the GPIO. They also currently include a free Raspberry Pi with orders over $350.

====SNOOTLAB====
SNOOTLAB
http://snootlab.com/
Sells products in French as well as English. They also sell a number of different components and products such as Arduinos too.

====Tenettech====
Tenettech
http://www.tenettech.com/product/2184/raspberry-pi
Tenettech is Bangalore based company who sells software/hardware based solutions in India. They sell Raspberry Pi and Raspberry Pi kit (which include the Raspberry Pi, SD card, card reader, HDMI cable, and video cable).

====AVIES Tech====
http://www.shopavies.com
AVIES Tech is a US company that provides installation and integration solutions for a variety of media centric hardware. They also carry the Raspberry Pi and related accessories.

====Amazon====
[http://www.amazon.com/ Amazon] also sells boards through the Raspberry Pi name for U$D 48.03. You can buy one [http://www.amazon.com/Raspberry-Pi-Model-Revision-512MB/dp/B009SQQF9C/ref=sr_1_1?ie=UTF8&qid=1361718715&sr=8-1&keywords=raspberry+pi here].

====Bitcrafts====
[http://etsy.com/shop/bitcrafts Bitcrafts] ships the '''Model A''' worldwide. You can buy one [http://www.etsy.com/listing/124198601/raspberry-pi-model-a? here]. They also sell cases, pIO micro SD adapters and other related accessories.

==Licensed Manufacture==
The foundation has chosen to license manufacture of the Raspberry Pi, which should provide several advantages including:

# 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 Pi's; the Raspberry Pi will now be being built to match demand.
# 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.
# Both RS Components and Premier Farnell will be taking preorders, something which the foundation would otherwise be unable to do.
# The foundation will still receive a percentage from the sale of every Raspberry Pi sold, which will be put straight back into the charity.
# 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.

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 (2012-02-28)].

Unfortunately the switch to licensed manufacture has also resulted in a marked reduction in transparency of the process as Farnell and RS consider detailed information of what is going on to be confidential.

==What You Get In The Box==
1. Pre-Assembled Raspberry Pi board

2. A sheet containing a combination of regulatory information and some very brief instructions. 

''Note:''

''1. The board will be supplied assembled (since most of the components are not suitable for home builds, including the BGA<ref name="BGA">http://en.wikipedia.org/wiki/Ball_grid_array</ref>package mounted SoC<ref name="SoC">http://en.wikipedia.org/wiki/System_on_a_chip</ref> and PoP<ref name="PoP">http://en.wikipedia.org/wiki/Package_on_package</ref> memory).''
''2. The board has the GPIO header pins for the primary GPIO header (but not the secondary GPIO header added on the revision 2 boards) populated. The SoC JTAG may or may not be present depending on when the board was manufactured and at which factory but aren't really of use to end users anyway due to the lack of Broadcom documentation. The LAN JTAG header does not seem to be present on any boards.
''3. All other connectors will be assembled in place.''

==Accessories==
To use the Raspberry Pi, a user will typically require some accessories. All of the Raspberry Pi vendors listed above sell some accessories, but the exact range varies. Accessories you should consider include.
* USB Power Supply (UK/EU/US Compatible; 5V, 700mA-1500mA(1.5A))<ref>http://www.raspberrypi.org/forum/general-discussion/is-the-raspberrypi-going-to-be-sold-as-a-kit/#p32289</ref>
* SD card. Most distributors are selling pre-prepared SD cards which are usually 4 GB. Software is available to prepare your own SD cards.
* There is a wide choice of cases, most distributors will have some but shopping around for one you like is suggested.
* There are a variety of [[Rpi expansion boards|AddOn/Expansion Boards]] now available, see that page for more details.
''See [[RPi Hardware Basic Setup#Typical Hardware You Will Need | Typical Hardware You Will Need]] for details about other items you may require.''

==Price==
The price is $35USD before shipping, duty, and tax, about $60 after.

Although the foundation is UK based, the guide price of the units are in USD since the Raspberry Pi components are sourced in USD$.

The price is $25USD (~£16GBP) for model A, and $35USD (~£23GBP) for model B.

Items will be subject to local tax (that is, UK will have 20% VAT added) and shipping cost is not included.

See the following update on [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

==Clones & Copies==
The foundation plans to release all the required schematics and plans to reproduce the Raspberry Pi hardware, so clones and copies will be welcome.

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.

==Historic information==

# The foundation have built an initial run of 10,000 Model-B units.
# Due to extreme demand, the units were NOT sold directly from the [http://www.raspberrypi.com shop] (see [[#Licensed Manufacture]] below).
# You may buy a Raspberry Pi from [http://www.element14.com/raspberrypi Farnell] or from [http://rswww.com RS Components]
# A limit of one unit per person was applied for the first batch and some time afterwards

* There were reports that several people ordered multiple units at launch,
however it appears that Farnell removed any excess items when they reviewed
and confirmed the order for shipping dates.
This has also appears to apply for the pre-orders they have taken.
Many customers also ordered from both Farnell and RS.

===1st Batch Order FAQ===
NOTE: While every attempt has been made to provide accurate information,
this FAQ is not official and is based on what information is available at the time of writing.

====Press Releases====
'''Farnell:'''

[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.

'''RS Components:'''

[http://www.electrocomponents.com/media/press-releases/2012/02/29th/ Post-Launch statement by RS Components]

[http://uk.rs-online.com/web/generalDisplay.html?id=raspberrypi&file=questions&cm_sp=raspberrypi-_--_-questions Raspberry Pi, Your Questions Answered by RS Components]

====Q: Couldn't this have been handled better, I couldn't get on the site to order and they sold too quickly?====
Both distributors were indeed unprepared for the volume of traffic the launch generated (they were warned by the foundation before hand).

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.

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).
Even if it is half of that, it means the number of available units was less than 1% of the demand.

====Q: If interest was obviously so high, why only build 10,000 units?====
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 task in itself. Much of that funding came from the Foundation Trustees' own personal investment.

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.

====Q: I've been unable to register an account with the distributor, as I am not a company?====
There have been several reported problems with individuals placing orders (that is, not having company accounts or details).

Both distributors "should" 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.

Often, many of the company related fields on application are optional. If in doubt, contact their sales team for help.

====Q: Worldwide launch? It was not available here! ====
The distributors decided to make the units only available from selected locations. It appears the foundation were not made aware of this beforehand.

Considering the small number of available units, it would have been unlikely to have improved the situation.

Worldwide availability will be monitored, it is expected that they will be made available as soon as possible.

====Q: The price for the Raspberry Pi from Farnell versus the price from RS Components is different, why?====
Please see the following page for details about [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

====Q: I've only been able to register my interest, what now?====
Be patient, both distributors have said they will contact people when they have more details (alternatively keep an eye on their sites for news).

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.

====Q: I registered on the Raspberry Pi Site's Mailing List, but I didn't get an email====
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.

The email contained the same information about the announcement as was publicly posted on the website (2012-02-28) before launch day, no additional or extra information was given through the email.

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Buying Guide

2013-03-10T13:40:47Z

AndrewS: Undo revision 228296 by Tskwara (talk) MobileAppSystems only sell cases, not Raspberry Pi units (and they're already listed on the RPi Cases page)

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

Raspberry Pi has appointed [http://www.element14.com/raspberrypi Farnell] and [http://rswww.com RS Components] as its authorised manufacturing parners distributors.

As of July 16th 2012, both [http://www.element14.com/raspberrypi Premier Farnell] and [http://rswww.com RS Components] have removed their "one per customer" restriction. Both consumers and businesses alike should now be able to buy bulk stock of the Raspberry Pi.

Raspberry Pi's distributors will ship worldwide to the best of their ability (ie subject to origin export and local import laws).

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]

Farnell have also been refusing to sell direct to some consumers in the EU, to the best of my knowlage they have not given full details of why.

There are three main options for buying a Raspberry Pi, buying direct from the distributor, buying from a subsidary or sister company of the distributor or buying from a third party reseller which option is best will depend on the location of the customer, the number of Raspberry Pi's being purchased, and the urgency of the order.

All new orders from the main distributors should now be filled with 512 MB rev 2 Raspberry Pi's. However, some third-party resellers may still have stock of the older models.

Note that stock status may change quickly. It may be worth checking a local supplier even if they are listed as out of stock here.

==Main distributors and subsidaries/sister companies==
==Farnell==
http://www.farnell.com/
Farnell are one of the two main distributors, as of 2012-11-21 their main European operation is out of stock and quoting a three-week lead time. Reports from the forum are that Farnell usually beat their delivery estimates.

For European customers, the customer is asked whether they are "consumer" or "business". If the customer selects business, they are taken back to Farnell's regular website to order. If the customer selects consumer, they are taken to a dedicated Raspberry Pi site which only offers a small selection of Raspberry Pi related products and gives no information on stock status. Farnell's site claims that consumers who do not have a previous account cannot use the "business" option but it is not clear if this is actually true for all countries. For some countries consumers are directed to third party resellers. The order code for the Raspberry Pi is 2191863.

===Element14===
http://www.element14.com
The "Element14" brand is used by a number of different operations within the Premier Farnell group and is also used for the groups "social" operation. In the Asia-Pacific region the Element 14 brand has completely replaced the previous "Premier Electronics" brand for asia and the previous "Farnell" brand for australia and new-zealand. In Europe, the Element14 brand is used in paralell with the Farnell brand. In North america the Element14 brand is used in parallel with the Newark brand.

===Newark===
http://www.newark.com/
Newark is the main American branch of the Premier Farnell group (Farnell's parent company). As of 2012-11-21, they are out of stock of Raspberry Pi's, but claim 1321 Expected to ship 2012-11-26 and Further stock expected to ship 2012-12-20.

===Element14 AU/NZ===
http://au.element14.com/ http://nz.element14.com/
On Element14's Australian operation (which also serves New Zealand) as of 2012-11-21 availability is listed as "please call" and "supplier lead time" is listed as 30 days. The order code for the Raspberry Pi is 2191863.

===Element 14 Asia===
http://cn.element14.com/ http://hk.element14.com/ http://in.element14.com/ http://cn.element14.com/ http://kr.element14.com/ http://my.element14.com/ http://ph.element14.com/ http://sg.element14.com/ http://tw.element14.com/ http://th.element14.com/
Element14 have warehouses in Singapore and Shanghi. It appears that some countries are served from both warehouses while others are served from only one or the other. UK stock is also listed on these sites. As of 2012-11-21, Element14's Asian operation has 331 Raspberry Pi's in stock in Shanghi and 617 Raspberry Pi's in stock in Singapore. The order code for the Raspberry Pi is 2191863.

===CPC===
http://cpc.farnell.com/
CPC is a branch of the Premier Farnell group in the UK based in Preston. As of 2012-11-21, they have 3100 Raspberry Pi's in stock. The order code for the Raspberry Pi is SC12590.

===MCM===
http://www.mcmelectronics.com/
MCM is a branch of the Premier Farnell group in the US based in Centerville, Ohio. As of 2012-11-21, they are out of stock and give an estimated ship date of 2012-12-07.

==RS components==
http://rswww.com/
RS are the other main distributor. Like Farnell they have a consumer site and business option with the consumer option taking users to a dedicated Raspberry Pi store while the business option takes them back to the regular RS site. They do not state whether consumers must use the consumer site or not. The order code for the Raspberry Pi is 756-8308. As of 2012-11-21, the Raspberry Pi is listed as "Temporarily out of stock - back order for despatch 21/12/2012".

RS has delayed existing orders on several occasions and are reported on the forum as being very difficult to communicate with.

===Allied electronics===
http://www.alliedelec.com/
Allied electronics is the US sister company of RS. The order code for the Raspberry Pi is 70229569. They website does not give a predicted dispatch date and state that "the estimated delivery time is uncertain and will likely take several months".

Reports from the forum are that Allied are easier to communicate with than RS, but they do not appear to be being kept will informed of the stock situation by RS.

==Resellers==
There are now many companies reselling the Raspberry Pi.

===RPF endorsed resellers===
====Maplin====
Maplin sells the Raspberry Pi in the UK but only as part of a kit including power supply, keyboard and mouse, programmed 4 GB SD card, HDMI cable and wireless dongle. As of 2012-11-21, they list the Raspberry Pi kit as in stock for home delivery and also in stock in some stores.

===Farnell Approved resellers===
Farnell now direct consumers in many countries to "approved retailers" rather than selling to them directly. Some of these suppliers specialise in the Raspberry Pi while others are general Farnell resellers.

====Electrocomponentes S.A====
http://www.electrocomponentes.com/
Electrocomponentes S.A sells Farnell producs in Argentina.

====Arabian Electric & Electronics Est.====
fisuoyla@batelco.com.bh
Arabian Electric & Electronics Est sells Farnell products in Bahrain.

====Minifo====
http://www.minifo.com/
Minifo is a Raspberry Pi retailer in Belgium. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Electromin S.A.====
http://www.electromin.cl/
Electromin S.A. sells Farnell producs in Chile.

====Betatech Ltd====
http://www.farnell.com/distributors/cyprus_bet.htm
Betatech Ltd sells Farnell products in Cyprus.

====Grand soloutions====
http://www.gs.com.eg/
Grand soloutions sells Farnell producs in Egypt. Unfortunately, searching their website by Farnell part number seems to be currently broken.

====Partco Oy====
http://www.partco.biz/
Partco sells the Raspberry Pi, Arduino and a selection of electronic components in Finland. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

==== kubii ====
http://www.kubii.fr/
kubii sells the Raspberry Pi, together with a selection of accessories. The website was created when Farnell changed their distribution policy.

====Málna PC Magyarország ====
http://malnapc.hu/
Málna PC Magyarország is a Raspberry Pi reseller in Hungary.

====Midbaejarradio EHF====
Midbaejarradio EHF is the authorised Farnell distributor for Iceland.

====Lion====
http://www.lion.co.il/h?q=RASPBERRY
Lion sells the Raspberry Pi in Israel. As of 2012-11-21, they do not appear to have stock.

====International Oilfield Supplies====
http://www.farnell.com/distributors/malta_int.htm
International Oilfield Supplies are the authorised Farnell distributor for Malta.

====Makkays====
http://www.farnell.com/distributors/pakistan_mak.htm
Makkays is the authorised Farnell distributor for Pakistan.

====kamami====
http://www.kamami.pl/
kamami sells the Raspberry Pi in Poland.

====Mixtronica====
http://www.mixtronica.com/
Mixtronica sell Farnell products in Portugal.

====Computer and Engineering Specialists Co====
http://www.farnell.com/distributors/saudiarabia_ces.htm
CESCO Group is an authorised Farnell distributor for Saudi Arabia.

====Dialogue s.r.o====
http://www.dialogue.sk/index.php?page=textaktual&id=71
Dialogue s.r.o sells the Raspberry Pi and accessories in Slovakia.

====IC elektronika d.o.o.====
http://www.ic-elect.si/
IC elektronika d.o.o. sells Farnell products in Slovenia.

====Electrocomp express====
http://www.eexpress.co.za/
Electrocomp express sells Farnell products in South Africa. As of 2012-11-21, they list the Raspberry Pi as awaiting delivery and do not give a lead time.

====Orel Solutions (PVT) Ltd====
http://www.farnell.com/distributors/srilanka_osp.htm
Orel Solutions (PVT) Ltd is the authorised Farnell distributor for Sri Lanka.

====Mikro-Kit Elektronik AB====
https://www.microkit.se/
Mikro-Kit Elektronik AB sells the Raspberry Pi (and it would appear other farnell producs too) in Sweeden. As of 2012-11-21, they list the Raspberry Pi as out of stock with expected delivery 2012-12-11.

====digitec====
http://www.digitec.ch/
Digitec sells the Raspberry Pi in Switzerland.

====Yildrim====
http://www.yildirimelektronik.com/
Yildrim sells Farnell products in Turkey.

====DGM distribution====
http://www.farnell.com/distributors/unitedarabemirates_dgm.htm
DGM distribution is the authorised Farnell distributor for Dubai.

===Other resellers===
====Newit====
http://www.newit.co.uk/
Newit are a British company selling a variety of ARM hardware and accessories, including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as in stock, but they do not state how much stock they have.

====Makershed====
http://www.makershed.com/
Makershed is a US company that sells various stuff aimed at hardware hackers including the Raspberry Pi. As of 2012-11-21, they list the Raspberry Pi as out of stock.

====Tandy====
http://www.tandyonline.co.uk/
Tandy is a UK company that sells a small selection of electronics stuff. As of 2012-12-08, Tandy has both 256MV rev 1.1 boards and 512MB rev 2 boards in stock.

Note that the current Tandy is a division of adslnation and other than buying the name has little relationship to the Tandy of old.

====Adafruit====
http://www.adafruit.com/
Adafruit is a US company that makes a variety of boards for hardware hackers and tinkerers, some specifically designed for use with the Raspberry Pi. They sell the Raspberry Pi separately, as well as part of a large starter kit including everything needed to start experimenting with the Raspberry Pi and external hardware on the GPIO. They also currently include a free Raspberry Pi with orders over $350.

====SNOOTLAB====
SNOOTLAB
http://snootlab.com/
Sells products in French as well as English. They also sell a number of different components and products such as Arduinos too.

====Tenettech====
Tenettech
http://www.tenettech.com/product/2184/raspberry-pi
Tenettech is Bangalore based company who sells software/hardware based solutions in India. They sell Raspberry Pi and Raspberry Pi kit (which include the Raspberry Pi, SD card, card reader, HDMI cable, and video cable).

====AVIES Tech====
http://www.shopavies.com
AVIES Tech is a US company that provides installation and integration solutions for a variety of media centric hardware. They also carry the Raspberry Pi and related accessories.

====Amazon====
[http://www.amazon.com/ Amazon] also sells boards through the Raspberry Pi name for U$D 48.03. You can buy one [http://www.amazon.com/Raspberry-Pi-Model-Revision-512MB/dp/B009SQQF9C/ref=sr_1_1?ie=UTF8&qid=1361718715&sr=8-1&keywords=raspberry+pi here].

====Bitcrafts====
[http://etsy.com/shop/bitcrafts Bitcrafts] ships the '''Model A''' worldwide. You can buy one [http://www.etsy.com/listing/124198601/raspberry-pi-model-a? here]. They also sell cases, pIO micro SD adapters and other related accessories.

==Licensed Manufacture==
The foundation has chosen to license manufacture of the Raspberry Pi, which should provide several advantages including:

# 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 Pi's; the Raspberry Pi will now be being built to match demand.
# 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.
# Both RS Components and Premier Farnell will be taking preorders, something which the foundation would otherwise be unable to do.
# The foundation will still receive a percentage from the sale of every Raspberry Pi sold, which will be put straight back into the charity.
# 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.

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 (2012-02-28)].

Unfortunately the switch to licensed manufacture has also resulted in a marked reduction in transparency of the process as Farnell and RS consider detailed information of what is going on to be confidential.

==What You Get In The Box==
1. Pre-Assembled Raspberry Pi board

2. A sheet containing a combination of regulatory information and some very brief instructions. 

''Note:''

''1. The board will be supplied assembled (since most of the components are not suitable for home builds, including the BGA<ref name="BGA">http://en.wikipedia.org/wiki/Ball_grid_array</ref>package mounted SoC<ref name="SoC">http://en.wikipedia.org/wiki/System_on_a_chip</ref> and PoP<ref name="PoP">http://en.wikipedia.org/wiki/Package_on_package</ref> memory).''
''2. The board has the GPIO header pins for the primary GPIO header (but not the secondary GPIO header added on the revision 2 boards) populated. The SoC JTAG may or may not be present depending on when the board was manufactured and at which factory but aren't really of use to end users anyway due to the lack of Broadcom documentation. The LAN JTAG header does not seem to be present on any boards.
''3. All other connectors will be assembled in place.''

==Accessories==
To use the Raspberry Pi, a user will typically require some accessories. All of the Raspberry Pi vendors listed above sell some accessories, but the exact range varies. Accessories you should consider include.
* USB Power Supply (UK/EU/US Compatible; 5V, 700mA-1500mA(1.5A))<ref>http://www.raspberrypi.org/forum/general-discussion/is-the-raspberrypi-going-to-be-sold-as-a-kit/#p32289</ref>
* SD card. Most distributors are selling pre-prepared SD cards which are usually 4 GB. Software is available to prepare your own SD cards.
* There is a wide choice of cases, most distributors will have some but shopping around for one you like is suggested.
* There are a variety of [[Rpi expansion boards|AddOn/Expansion Boards]] now available, see that page for more details.
''See [[RPi Hardware Basic Setup#Typical Hardware You Will Need | Typical Hardware You Will Need]] for details about other items you may require.''

==Price==
The price is $35USD before shipping, duty, and tax, about $60 after.

Although the foundation is UK based, the guide price of the units are in USD since the Raspberry Pi components are sourced in USD$.

The price is $25USD (~£16GBP) for model A (not yet avalable), and $35USD (~£23GBP) for model B.

Items will be subject to local tax (that is, UK will have 20% VAT added) and shipping cost is not included.

See the following update on [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

==Clones & Copies==
The foundation plans to release all the required schematics and plans to reproduce the Raspberry Pi hardware, so clones and copies will be welcome.

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.

==Historic information==

# The foundation have built an initial run of 10,000 Model-B units.
# Due to extreme demand, the units were NOT sold directly from the [http://www.raspberrypi.com shop] (see [[#Licensed Manufacture]] below).
# You may buy a Raspberry Pi from [http://www.element14.com/raspberrypi Farnell] or from [http://rswww.com RS Components]
# A limit of one unit per person was applied for the first batch and some time afterwards

* There were reports that several people ordered multiple units at launch,
however it appears that Farnell removed any excess items when they reviewed
and confirmed the order for shipping dates.
This has also appears to apply for the pre-orders they have taken.
Many customers also ordered from both Farnell and RS.

===1st Batch Order FAQ===
NOTE: While every attempt has been made to provide accurate information,
this FAQ is not official and is based on what information is available at the time of writing.

====Press Releases====
'''Farnell:'''

[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.

'''RS Components:'''

[http://www.electrocomponents.com/media/press-releases/2012/02/29th/ Post-Launch statement by RS Components]

[http://uk.rs-online.com/web/generalDisplay.html?id=raspberrypi&file=questions&cm_sp=raspberrypi-_--_-questions Raspberry Pi, Your Questions Answered by RS Components]

====Q: Couldn't this have been handled better, I couldn't get on the site to order and they sold too quickly?====
Both distributors were indeed unprepared for the volume of traffic the launch generated (they were warned by the foundation before hand).

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.

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).
Even if it is half of that, it means the number of available units was less than 1% of the demand.

====Q: If interest was obviously so high, why only build 10,000 units?====
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 task in itself. Much of that funding came from the Foundation Trustees' own personal investment.

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.

====Q: I've been unable to register an account with the distributor, as I am not a company?====
There have been several reported problems with individuals placing orders (that is, not having company accounts or details).

Both distributors "should" 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.

Often, many of the company related fields on application are optional. If in doubt, contact their sales team for help.

====Q: Worldwide launch? It was not available here! ====
The distributors decided to make the units only available from selected locations. It appears the foundation were not made aware of this beforehand.

Considering the small number of available units, it would have been unlikely to have improved the situation.

Worldwide availability will be monitored, it is expected that they will be made available as soon as possible.

====Q: The price for the Raspberry Pi from Farnell versus the price from RS Components is different, why?====
Please see the following page for details about [http://www.raspberrypi.org/archives/826 RS Components and Farnell global pricing] (2012-03-13).

====Q: I've only been able to register my interest, what now?====
Be patient, both distributors have said they will contact people when they have more details (alternatively keep an eye on their sites for news).

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.

====Q: I registered on the Raspberry Pi Site's Mailing List, but I didn't get an email====
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.

The email contained the same information about the announcement as was publicly posted on the website (2012-02-28) before launch day, no additional or extra information was given through the email.

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Hub

2013-03-04T19:59:27Z

AndrewS: /* RPi Model B 3D CAD files */ added link to another CAD file

{{TOC right}}
{{Hub Flags}} 
<div style="margin:0; border:1px solid #f80033; padding:0 1em 1em 1em; background-color:#cd5555; align:right; width:50%;">
<font color="ffffff">Notice: The Raspberry Pi Wiki pages on this site is collaborative work - the Raspberry Pi Foundation is '''not''' responsible for content on these pages.</font>
</div>

== I need help with... ==

=== Buying a new Raspberry Pi ===
Please visit the [[RPi Model Wizard|Model Wizard]] to select your Raspberry Pi.

=== Booting an OS onto my Raspberry Pi ===
Please visit the [[RPi OS Wizard|OS Wizard]] to select your Raspberry Pi OS distribution, or if you'd like to compare the OS distros, visit [[RPi Distributions|OS Distributions]] page to select an OS to boot onto your Raspberry Pi.

== Now shipping to customers ==

'''Update on lead times as of 17 November 2012:''' The lead time is around 2 days from Farnell and RS.

Don't have an idea on which to buy? Use the [[RPi Model Wizard|Model Wizard]] to select your Raspberry Pi!

See the [[RPi Buying Guide|Buying Guide]] on how to order one, or visit the [http://www.raspberrypi.org Raspberry Pi Foundation Home Page]

== About ==
[[File:RpiFront.jpg|300px|thumb|right|The Raspberry Pi production board (model B Rev 2.0)]]

The Raspberry Pi (short: RPi or RasPi) is an ultra-low-cost ($25-$35) credit-card sized Linux computer which was conceived with the primary goal of teaching computer programming to children. It was developed by the [http://www.raspberrypi.org Raspberry Pi Foundation], which is a UK registered charity (Registration Number 1129409). The foundation exists to promote the study of computer science and related topics, especially at school level, and to put the fun back into learning computing. The device is expected to have many other applications both in the developed and the developing world ([[RPi_Philosophy|Read more]]).

Raspberry Pi is manufactured and sold in partnership with the worldwide industrial distributors [http://www.farnell.com/ Premier Farnell/Element 14] and [http://rswww.com/ RS Components].

* You can get the latest news from the [http://www.raspberrypi.org Foundation Home Page], the [http://twitter.com/intent/user?screen_name=Raspberry_Pi Twitter Feed] or in the [http://www.raspberrypi.org/forum/general-discussion/news-articles-and-blog-posts-about-raspberry-pi forums].
* For Raspberry Pi frequently asked questions see the [[RPi FAQ|FAQ section]] or the [http://www.raspberrypi.org/?page_id=8 Raspberry Pi Foundation's FAQ] page.
* Both manufacturing partners provide community areas for more technically focused discussions, articles, FAQs and related information:
:* Premier Farnell: [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group]
:* RS-Components: [http://www.designspark.com/theme/raspberrypi DesignSpark - Raspberry Pi]
* Products are RoHS, CE, FCC, CTick, CSA and WEEE compliant<ref>http://www.element14.com/community/docs/DOC-44828/l/raspberry-pi-safety-data-sheet</ref>. In common with all Electronic and Electrical products the Raspberry Pi should not be disposed of in household waste. Please contact the distributor from whom you purchased your Raspberry Pi device for details regarding WEEE in your country.
* Price: 25USD Model A, 35USD for Model B, excluding taxes, postage and packaging. For information about availability and shipping see the [[RPi Buying Guide | Buying Guide]].

=== History ===

If you are interested in why the Raspberry Pi was created, and why it is what it is, check the [[RPi General History|General History]] page, which highlights relevant events in its history. It is not intended to be a detailed history, so it can be read quickly. You could also check the [[Rpi_HardwareHistory | design changes]] page for how the Raspberry Pi has evolved, and the [[RaspberryPi_Boards | manufacturing differences]] page that may help if you are having problems with your board.

== Getting Started ==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa;" |
=== [[Buying RPi|Buying Guide]] ===
----
The [[RPi Model Wizard|Model Wizard]] will help you select your model to buy.
----
Where can I get one and for how much?
* The Raspberry Pi can no longer only be purchased via their official distribution partners - detailed information can be found on the [[Buying RPi | RPi Buying Guide]] page.

* Additional accessories, peripherals and merchandise will also be available through the [http://www.raspberrypi.com/ Raspberry Pi Shop], as well as [http://thepihut.com/ The Pi Hut's Raspberry Pi Store], [http://easyaspistore.com/ the EasyAsPi Store], and many others on Amazon [http://www.amazon.co.uk/ Amazon UK] and eBay [http://www.ebay.co.uk/ eBay UK] websites.

* You can find out which peripherals and such are tested to work with the PI in the [[RPi_VerifiedPeripherals]] section

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

=== [[RPi Hardware Basic Setup|Basic Setup]] ===
----
First little Raspberry Pi Steps...
* Ensure you have all the [[RPi Hardware Basic Setup#Typical_Hardware_You_Will_Need |equipment]] you need to go with your Raspberry Pi.
* Become familiar with the [[RPi Hardware Basic Setup#Connecting_Together | board layout and connect]] it ready for power up.
* If you have not been provided with a pre-setup SD card you will need to prepare one with your chosen [[RPi_Easy_SD_Card_Setup | Operating System distribution]]
* Note: On the Debian OS after you log in you need to type '''startx''' at the prompt to get a graphic desktop.
* Particularly after first boot its important to do a clean shutdown with the command '''sudo halt'''

* '''Having problems? Try the [[R-Pi_Troubleshooting | Troubleshooting]] page.'''

| style="width:33%; vertical-align:top; border:1px solid #aaa;" |

=== [[RPi Beginners|Beginners Guide]] ===
----
You've just got your new Raspberry Pi device - what now?
* [[RPi Beginners|Beginners Guide]]

* Learn about the basics with the [http://h2g2.com/dna/h2g2/A13735596 H2G2 - Introducing the Raspberry Pi] entry.

* Read a small book for the Raspberry Pi Beginner [http://bitkistl.blogspot.co.at/2013/01/raspberry-pi-e-book.html]

* Get started with some basic projects and tutorials:
[http://www.youtube.com/user/RaspberryPiTutorials Raspberry Pi YouTube Tutorials]<br />
[http://www.youtube.com/user/RaspberryPiBeginners Another set of video tutorials]<br />
[http://www.youtube.com/playlist?list=PLgyU3jNA6VjS3ij6ZXbb2x4GdEP3bAWzO My First Raspberry Pi Game]

[[RPi Tutorial Easy GPIO Hardware & Software|Easy GPIO Hardware & Software]] - in-progress at the moment
Example projects/tuts which can be linked from here
(or from within a beginners guide page perhaps):
Setup XBMC media centre
Programming tutorials (Liams YouTube etc)
Easy GPIO (when complete or similar thing).
Also links to some basic linux user guides.

* Take a look through the [[#Community|Community]] section, which contains a range of beginner and advanced tutorials and guides, as well as groups to help you find like-minded developers.

|}

== Resources ==
{| border="1" style="background:transparent;"

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Hardware|Hardware]] & [[RPi VerifiedPeripherals|Peripherals]] ===
----

* The Model B is more advanced than the Model A - see [[RPi Hardware]].
* The RPi can be plugged into a [[RPi Screens|suitable TV or monitor]].
* The unit will support a range of [[RPi VerifiedPeripherals|devices, peripherals and accessories]].
* The [[Rpi Low-level peripherals|Low-level interfaces]] allow the use of optional [[RPi Expansion Boards|Expansion Boards]] in a wide range of projects.
* For more advanced issues including see [[RPi Advanced Setup|Advanced Setup]].
* [[RPi Peripherals|Setting up peripherals - examples/HowTos]]
* [[RaspberryPi Boards|List of boards and user feedback]]
* [[RPi 5V PSU construction|Power Supply construction - HowTo]]
* [[RaspberryPi_Comparison|Comparison]] to other hardware
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[Rpi_Software|Software]] & [[RPi_Distributions|OS Distributions]] ===
----
The Raspberry Pi will run a range of OS Distributions and run a variety of software.
* See [[RPi Software|Software]] for an overview, and [[RPi Distributions|OS Distributions]] for supported operating system and pre-configured 'images'.
*Main OS distributions include [[RPi Distributions#Debian_ARM | Debian ARM]], [[RPi Distributions#Fedora | Fedora]], [[RPi Distributions#KidsRuby | KidsRuby]] and [http://puppylinux.org/wikka/Puppi Puppi] from Puppy Linux.
*Advice is also available if you want to [[Rpi_kernel_compilation|compile a kernel]], [[RPi_U-Boot|boot from the network using U-Boot]], or [[RPi_Performance|test the Pi's performance]].
*The Raspberry Pi supports a wide range of [[RPi Programming|programming languages]], with many tutorials available.
*Information about installing specific [[RPi_applications|applications]] is available through the link.
*Extensive (boot) configuration info (config.txt) is available [[RPi_config.txt|here]].
*Monitor your Raspberry Pi with Raspcontrol [[Raspcontrol|here]]

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Documentation|Documentation]] ===
----
Documentation relating to the Raspberry Pi can be found [[RPi Documentation|here]].

[[RPi DatasheetCategories|Frambozenier.org Documentation Project Datasheets]]

Example documents which can be linked from here (or sub page):
Official Datasheets
White Papers
User Manuals
Recommended books (perhaps)

=== RPi Troubleshooting ===

Head over to the [[R-Pi Troubleshooting|troubleshooting page]] for help fixing common problems.

=== RPi Bugs ===

Head over to the [[RPi_Bugs|bugs page]] for a list of known bugs.

=== RPi Model B 3D CAD files ===
Theses are various 3D CAD Versions in both RAR and ZIP.

* CATIA V5 RAR http://sdrv.ms/JqdhMb
* CATIA V5 ZIP http://sdrv.ms/LjyLGD
* ProE RAR http://sdrv.ms/KCv1hZ
* ProE ZIP http://sdrv.ms/KCvhxq
* STEP RAR http://sdrv.ms/KCvv7T
* STEP ZIP http://sdrv.ms/JMhv18
* SketchUp http://scc.jezmckean.com/item/581
* SketchUp8 http://sketchup.google.com/3dwarehouse/details?mid=327d6b1d8bd6130d6fbd6b70c7f1d3e0
* Eagle 5 http://www.raspberrypi.org/phpBB3/viewtopic.php?f=41&t=4457
|}

== Community ==
{| border="1" style="background:transparent;"
| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Projects|Projects]], [[RPi Guides|Guides]] & [[RPi Tutorials|Tutorials]] ===
----
*An important source of information and guides is the [http://www.raspberrypi.org/forum Official Forum].
*Get started by following some of the many [[RPi Tutorials | Tutorials]].
*Common tasks and useful tips are available through the [[RPi Guides | Guides page]].
*Projects can be found, and added to, on the [[RPi Projects |Projects page]].
*Raspberry Pi Datasheets can be found on the [[RPi DatasheetCategories |DataSheets page]].
*Knowledgeable users may want to review and help out with project wishlist items on the [[RPi Tasks |Tasks page]].
*[[Configuring a Static IP address on your Raspberry Pi]]

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |

=== [[RPi Education|Schools, Universities, Clubs & Groups]] ===
----
*The Raspberry Pi Foundation's aims include encouraging education. Several groups including [http://www.computingatschool.org.uk/ Computing At School] aim to bring Computing Science back into schools.
*Go to the [[Rpi Education|Education Page]] to add your project and find helpful links.

| style="width:33%; vertical-align:top; border:1px solid #aaa; padding-left:5px;" |
=== [[RPi Community|Supporting Communities]] ===
----
The [[RPi Community|Raspberry Pi Community]] is steadily growing:
* [http://www.raspberrypi.org/forum The Official Raspberry Pi Forum]
* [http://www.element14.com/community/groups/raspberry-pi?view=discussions Element 14 Raspberry Pi Group], community site of Premier Farnell
* [http://www.designspark.com/theme/raspberrypi DesignSpark], community site of RS-Components
* [http://www.frambozenbier.org/index.php/ 'Frambozenbier' (Raspberry Pi Homebrew)]
* [http://raspberrypi.stackexchange.com/ Stack Exchange Forum]
* [http://www.raspberrypiforums.com/forum RaspberryPiForums] Un-Official Raspberry Pi Discussion Board
* [http://www.raspberrypi-spanish.es Non-official community of Raspberry Pi in spanish language]
* [http://www.worldofpi.com/ World Of Pi] A forum based on all things Raspberry Pi.
* [[RPi Community Magazine]] - User contributed eMagazine, get involved!
* [[RaspberryPi Osdev]] - Hardware specific OS-development community, sitting in freenode.net#raspberrypi-osdev.
|}

== About the RPi Wiki ==
'''Do not be afraid to add your bit, content is vital for the wiki to function.'''

[[File:Rasp_turn_around.gif|200px|thumb|right|A 3D rendering of the Raspberry Pi logo]]
We are governed by the [[Project:RPi_Council|RPi Wiki Council]] (RPWC). New guidelines not made by Ghans alone are currently being drafted. As the RPi wiki is currently a wreck, the council's current goal is to clean up the RPi Wiki!

=== Translations ===

The wiki is being translated into several languages, some of which can be seen on the hub banner above. Current languages include:

* English: [[R-Pi Hub]]
* Français: [[FR:R-Pi Hub]]
Any help translating would be greatly appreciated. Thank you to those who have already contributed!

=== Admins/Contributors ===
The wiki is governed by the [[Project:RPi_Council|Raspberry Pi Wiki Council]].

:NOTE - This wiki is NOT governed by the [[Project:RPi_Council|Raspberry Pi Wiki Council]]. The whole of elinux.org is community driven. It always has been. If you have any questions, contact [[User:Wmat]].

= References =
<references/>

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

RPi Hardware

2013-03-04T19:56:53Z

AndrewS: /* Components */ corrected board size

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

==Introduction==
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]
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]].

Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].

Several different Hardware versions/revisions [[RaspberryPi Boards]] have been found probably from different assembly lines. Try to identify your board for better troubleshooting and update it if you have one which is not mentioned.

==Specifications==
{| class="wikitable"
!
! Model A
! Model B
|-
| Target price:<ref name="faq" >http://www.raspberrypi.org/faqs</ref>
| US$25 Ext tax (GBP £16 Exc VAT)
| US$35 Ext tax (GBP £22 Exc VAT)
|-
| System-on-a-chip (SoC):<ref name="faq" />
| colspan="2" | Broadcom BCM2835 (CPU + GPU. SDRAM is a separate chip stacked on top)
|-
| CPU:
| colspan="2" | 700 MHz ARM11 ARM1176JZF-S core
|-
| GPU:
| colspan="2" | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode
|-
| Memory (SDRAM)iB
| 256 MiB (planned with 128 MiB, upgraded to 256 MiB on 29 Feb 2012)
| 256 MiB (until 15 Oct 2012); 512 MiB (since 15 Oct 2012)
|-
| USB 2.0 ports:
| 1 (provided by the BCM2835)
| 2 (via integrated USB hub)
|-
| Video outputs:<ref name="faq" />
| colspan="2" | Composite video | Composite RCA, HDMI (not at the same time)
|-
| Audio outputs:<ref name="faq" />
| colspan="2" | TRS connector | 3.5 mm jack, HDMI
|-
| Audio inputs:
| colspan="2" | none, but a USB mic or sound-card could be added
|-
| Onboard Storage:
| colspan="2" | Secure Digital|SD / MMC / SDIO card slot
|-
| Onboard Network:<ref name="faq" />
| None
| 10/100 wired Ethernet RJ45
|-
| Low-level peripherals:
| colspan="2" | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S<ref name="i2s">[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?]</ref>, Universal asynchronous receiver/transmitter (UART)
|-
| Real-time clock:<ref name="faq" />
| colspan="2" | None
|-
| Power ratings (provisional, from alpha board):
| 500 mA, (2.5 W) <ref name="faq" />
| 700 mA, (3.5 W)
|-
| Power source:<ref name="faq" />
| colspan="2" | 5 V (DC) via Micro USB type B or GPIO header
|-
| Size:
| colspan="2" | 85.0 x 56.0 mm (two different boards, measured with callipers)
|}

==Components==
[[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
Beech, edited to show 256MB ram for both boards]]
(Provisional - some of the expansion interfaces won't be available on production boards)
(PCB IDs are those of the Model B Beta board)

* 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:
** 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].
** 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
** 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)
** 256MiB of ([http://www.hynix.com/products/mobile/view.jsp?info.ramKind=28&info.serialNo=H9TKNNN2GDMPLR&posMap=MobileDDR2 Hynix MobileDDR2] or [http://www.samsung.com/global/business/semiconductor/product/mobile-dram/detail?productId=7611&iaId=747 Samsung Mobile DRAM]) SDRAM (or 512MB [http://www.samsung.com/global/business/semiconductor/product/mobile-dram/detail?iaId=747&productId=7609 Mobile DRAM] on later boards). The RAM is physically stacked on top of the Broadcom media processor ([http://en.wikipedia.org/wiki/Package_on_package package-on-package technology]). Here is a photo of the [http://www.raspberrypi.org/wp-content/uploads/2012/01/brcm2835plusmemory.jpg SDRAM (left) and BCM2835 (right)] ball grid arrays on JamesH's finger. You are looking at the bottom side. The BCM2835 top side has a land grid array which matches the SDRAM ball grid array. Here is a highly magnified side view of the SDRAM stacked on top of the BCM2835 stacked on top of the PCB [http://www.raspberrypi.org/wp-content/uploads/2012/09/2012-09-21-10.58.22.jpg PoP stack] (you can see why it's job that can only be done by robots!).
* 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:
** 10/100Mb Ethernet (Auto-MDIX)<ref name=autoMDIX>[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]</ref>
** 2x USB 2.0
* S1: Micro USB power jack (5v - Power Only)
* 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.
* S3: HDMI connector providing type A HDMI 1.3a out
* S4: Composite Video connector: RCA
* S5: MIPI [http://www.mipi.org/specifications/camera-interface CSI-2] interface. 15-pin surface mounted flat flex connector.
* S6: Audio connector: 3.5mm stereo jack (output only)
* S8: SD/MMC/SDIO memory card slot (underside)
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''
* P1: 26-pin (2x13) 2.54 mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]
** 8 [[Rpi_Low-level_peripherals#General_Purpose_Input.2FOutput_.28GPIO.29|GPIO]]s at 3v3
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3
** I²C interface (3v3); or 2 GPIOs at 3v3
** SPI interface (3v3); or 5 GPIOs at 3v3
** 3v3, 5v and GND supply pins
** ARM JTAG (if pins are reconfigured in software - on Revision1.0 boards one signal would also need to be taken from S5)
** I²S interface (if pins are reconfigured in software, hardware hack may be required<ref name="i2s"/>)
* P2: 8-pin 2.54 mm header expansion (header not fitted on Revision 2.0 boards), providing GPU JTAG (ARM11 pinout, pin 7 is nofit for locating)
* P3: 7-pin 2.54 mm header expansion (header not fitted), providing LAN9512 JTAG (pin 6 is nofit for locating)
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''
* P5: 8-pin (2x4) 2.54 mm header expansion (header not fitted), on the ''bottom'' of the board, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]] '''(Revision 2.0 boards only)'''
** 4 [[Rpi_Low-level_peripherals#P5_header|GPIO]]s at 3v3
** 3v3, 5v and GND supply pins
** Second I²C interface (3v3) (if pins are reconfigured in software)
** I²S interface (if pins are reconfigured in software)
** Handshake signals for the UART on the P1 header (if pins are reconfigured in software)
* P6: 2-pin 2.54 mm header expansion (header not fitted), providing an option to connect a hardware-reset button '''(Revision 2.0 boards only)'''
* TP1 and TP2: Test Points giving access to +5V and GND respectively
* 5 Status LEDs<ref name="PCBs">[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]</ref><ref name="LEDs">[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]</ref><ref name="LEDsGPIO">[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?]</ref><ref name="OKGreen">[[RPi_schematic_errata]]</ref><ref name="Revision2.0">[http://www.raspberrypi.org/archives/1959 RPiBlog Post: A nice shiny photo of the rev2 board – and User Guide news]</ref>:
** D5(Green) - SDCard Access (via GPIO16) - labelled as "OK" on Rev1.0 boards and "ACT" on Rev2.0 boards
** D6(Red) - 3.3 V Power - labelled as "PWR" on both Rev1.0 and Rev2.0 boards
** D7(Green) - Full Duplex (LAN) '''(Model B)''' - labelled as "FDX" on both Rev1.0 and Rev2.0 boards
** D8(Green) - Link/Activity (LAN) '''(Model B)''' - labelled as "LNK" on both Rev1.0 and Rev2.0 boards
** D9(Yellow) - 10/100Mbit (LAN) '''(Model B)''' - labelled (incorrectly) as "10M" on Rev1.0 boards and "100" on Rev2.0 boards

* Board size: <del>85.60 mm x 53.98 mm.</del> Overall height expected to be less than 25 mm. <ref name="artwork">http://www.raspberrypi.org/archives/344</ref> Production boards measure 85.0 mm x 56.0 mm.
** A Model B between the highest points (USB connector to card slot) measured 21 mm.
** A Model A between the highest points (composite video connector to card slot) measured 18mm.
* Weight: under 40 g?
** Alpha board weighs approx. 55 g.<ref>http://www.raspberrypi.org/?page_id=43&mingleforumaction=viewtopic&t=285.0</ref>
** A sample model B weighed 39.45 g.
* 6 layer PCB <ref name="artwork" />

==Schematic / Layout==

* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot rev 1.0]
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot rev 1.0, labelled version]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]
* [http://elinux.org/File:RPi-Front-JPB.jpg High-resolution Model B PCB front photo, production board rev 1.0]
* [http://elinux.org/File:RPi-back-JPB.jpg High-resolution Model B PCB back photo, production board rev 1.0]
* [http://www.raspberrypi.org/wp-content/uploads/2012/09/sony-rasp-pi.jpg High-resolution Model B PCB front photo, production board rev 2.0]
* [http://www.raspberrypi.org/wp-content/uploads/2012/11/2012-11-29-14.48.47-HDR.jpg High-resolution Model A PCB front photo, production board rev 2.0]
* [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 (117MB)]
* [[Media:RPi beta xray.jpg|"Xray style" image of the beta board, created from the above GIMP project]] | [[RPi_xray_wallpapers|desktop wallpapers]]
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official Rev 1.0 schematics PDF] | [http://www.raspberrypi.org/wp-content/uploads/2012/10/Raspberry-Pi-R2.0-Schematics-Issue2.2_027.pdf Official Rev 2.0 schematics PDF] | [[RPi_schematic_differences|differences]] | [[RPi_schematic_errata|errata]] | [[RPi_schematics_breakdown|breakdown]] | [[RPi_Partial_BOM_Rev2.0_ModelB|partial BOM]]
* [http://www.andrewscheller.co.uk/rpi_pcb_modules.html 'Module groups' of the PCB photos]

==Power==

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).
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.

Premier Farnell recommend the following power supplies:
* Model A: 5V dc, 500-700mA
* Model B: 5V dc, 700-1200mA

Power consumption of the Raspberry Pi device is

* Board A: 5V, 500 mA (2.5W) '''without any devices connected''' (e.g. USB, Ethernet, HDMI)
* 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 "using networking and high-current USB peripherals" [http://www.raspberrypi.org/archives/260].)

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.

*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.
* 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.
* POE ([[wikipedia: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 - mind though that the Ethernet jack on the board is a 'magjack' - http://www.sparkfun.com/datasheets/Prototyping/MagJack.pdf - which means that the usual 'dumb or passive PoE' power pins 47 and 78 are *not* wired through to the board. So this is not an entirely trivial exercise).
* Back-Powering; (powering the Raspberry Pi from a USB hub through the uplink/data port, single cable) Back powering is possible on the Raspberry Pi, but not advisable. Revision 1.0 boards have to be modified to back power, this is due to the 140ma "polyfuses" that are installed in the USB port circuit. Revision 1.1 boards do not need modifications to back-power, they have replaced the polyfuses with 0ohm resistors in their place. Revision 2.0 boards do not need modification, they have neither resistors nor polyfuses. It is advised that short (12" (.3 meter) or less) USB cables be used for back-powering a Raspberry Pi. Cable resistance plus connector resistance can quickly reduce operating voltages below the proper range(5.25V to 4.75V). But do note that if you do not power the PI in the "official manner", that is through it's micro-USB port, but use any alternative way (such as through the GPIO header, the test points TP1 and TP2), but also by back-powering it, '''you are actually bypassing the PI's input polyfuse protection device!''' This can have extreme consequences if ever you manage to put more than 6V on the PI, even for a very short period. As this causes the overvoltage device D17 on the the PI to trigger and short the 5V supply! Without the polyfuse limiting the current through D17, it will burn out, probably melting the PI's enclosure with it, (if you have any) and possibly causing a fire-hazard. It will probably also create a permanent short of the 5V supply! So be warned, and if you use back power make sure your hub or its PSU has a fuse to prevent this from happening. If not, add your own fuse.

===Power Supply Problems===

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.

The power required by the Pi will vary depending on how busy it is and what peripherals are connected.
* Running a GUI will take more power.
* The USB devices and Ethernet connection will take power.
* Running the GPU will take extra power.

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.
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 of the two USB ports on the Pi has a polyfuse rated at 140 mA, so any connected USB devices should draw less than this amount of current. In addition the polyfuse will cause a significant voltage drop, so that USB devices get less voltage than is available on the RPI itself, sometimes up to half a volt less (maybe more if the fuse has recently been hot). For regular "low power" USB devices this doesn't cause a problem as they are designed to work with voltages as low as 4.4 Volt. This isn't the case however with some USB devices such as WiFi dongles which may need 4.75 Volt, and are also known to draw more than 150 mA when configured and active. Because of the problems these polyfuses caused Raspberry PI's produced after August 25, 2012 have the USB polyfuses F1 & F2 removed (replaced with shorts).

The microUSB input port also has a 1.1 A polyfuse (700mA "hold current") which may also have enough resistance (although much smaller than the 140mA fuses) to cause a significant voltage drop on the board, even below its 1.1 A total current.

A extended explanation of the consequences of the use of these polyfuses can be found here [[Polyfuses explained]]

There are several reasons why the power to the board may be inadequate:
* 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 its full power without the voltage dropping.
* The PSU is not regulated.
* 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.
* If the PSU is unregulated it can also output too high a voltage, which may trigger the overvoltage device in the PI, which will temporarily short the 5V to ground, this will then "blow" polyfuse F3, which will take several days to recover from. Meanwhile (possibly with another PSU) the PI might not get enough power because the (partly) blown polyfuse is consuming some of the power. The solution is when this happens to ways a few days to give the polyfuse time to recover before attempting to use the better PSU. If you suspect a blow polyfuse, measure the voltage across F3, which should be less than 0.05 Volt.

====How Can I tell if the power supply is inadequate?====

Common symptoms of an inadequate power supply are
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.
* SD card errors at start up seems to be another symptom of poor power.

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

Use a multimeter which is set to the range 20 volts DC (or 20v =). You should see a voltage between 4.75 and 5.25 volts. Anything outside this range indicates that you have a problem with your power supply or your power cable, or the input polyfuse F3. Anything inside, but close to the limits, of this range ''may'' indicate a problem.

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

====Things that can cause problems====
* 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.
* 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.
* A power supply that is rated for less than 700mA may work some of the time.
* 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.
* 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.

====Summary====

* If you are having unreliable operation the first thing to do is check your power supply.
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.
* Not all power supplies will deliver what they claim.

===Capacitor C6===
Behind the microUSB power connector on the Model B is a metallic grey component called a capacitor, marked as C6. This capacitor helps stabilise the DC power on the board, but for some it has also become a place for their thumb when removing the RPI's power lead; unfortunately, this can result in the capacitor breaking off! It has been stated in the forums that the type of capacitor used for C6 will be changed on later RPi models for one with sturdier leads. If you do break off your C6 capacitor, it's highly likely that your RPi will still work properly, unless you have a particularly unstable power supply, but the general advice is to not use C6 as a leverage point when removing the power connector and also take care when storing or transporting your RPi if it's not fitted in a case - try not to stow the board where C6 could be knocked by other items - for example in a laptop carry case or in amongst some books.
[[File:Rpic6.jpg|300px|thumb|center|Capacitor C6 (ringed)]]

It's unlikely that replacing a broken off C6 capacitor will be covered under warranty, but fortunately they are easy to replace if you have average [http://www.raspberrypi.org/archives/1494 soldering skills], but remember that reworking your RPi will void its warranty too. C6 is a surface mount electrolytic capacitor with a capacitance of 220 microfarad (μF) and a voltage rating of 16 volt (V). The capacitor is polarised and so must be fitted the right way round - notice the black marking on one side in the picture above. A replacement capacitor can be purchased from numerous sources - for example:

[http://uk.farnell.com/jsp/search/browse.jsp?N=202457+110114112+110119850+110141127+110200576&No=0&getResults=true&appliedparametrics=true&locale=en_UK&divisionLocale=en_UK&catalogId=&skipManufacturer=false&skipParametricAttributeId=&prevNValues=202457+110114112+110119850+110141127&mm=1000002|110114112|110114112,1001880|110119850|110119850,1002520||,1002063||,1002999||,&filtersHidden=false&appliedHidden=false&autoApply=true&originalQueryURL=%2Fjsp%2Fsearch%2Fbrowse.jsp%3FN%3D202457%26No%3D0%26getResults%3Dtrue%26appliedparametrics%3Dtrue%26locale%3Den_UK%26divisionLocale%3Den_UK%26catalogId%3D%26skipManufacturer%3Dfalse%26skipParametricAttributeId%3D%26prevNValues%3D202457 Farnell]

[http://www.rapidonline.com/Electronic-Components/220uf-16v-85deg-Smd-Electro-Capacitor-11-2264 Rapid Electronics]

[http://uk.rs-online.com/web/c/passives/capacitors/aluminium/?sort-by=default&sort-order=default&applied-dimensions=4294884868,%204294884170,%204294672278,4294885140&lastAttributeSelectedBlock=4294955811 RS Components]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Low-level peripherals

2013-03-01T01:04:30Z

AndrewS: /* General Purpose Input/Output (GPIO) */ Added pin-orientation images for the P1, P2 and P3 headers

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

==Introduction==
In addition to the familiar USB, Ethernet and HDMI ports, the R-Pi offers lower-level interfaces intended to connect more directly with chips and subsystem modules. These GPIO (general purpose I/O) signals on the 2x13 header pins include SPI, I2C, serial UART, 3V3 and 5V power. These interfaces are not "plug and play" and require care to avoid miswiring. The pins use a 3V3 logic level and are not tolerant of 5V levels, such as you might find on a 5V powered Arduino. Not yet software-enabled are the flex cable connectors with CSI (camera serial interface) and DSI (display serial interface), and a serial link inside the HDMI connector called CEC. (consumer electronics control)

==General Purpose Input/Output (GPIO)==
[[File:GPIOs.png|thumb|254px|right|The layout of the Raspberry Pi Revision 1 P1 pin-header seen from the top, containing pins useable for general purpose I/O. Colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs2.gif Source] ]]

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.

The Raspberry Pi allows peripherals and expansion boards (such as the [[Rpi Gertboard]]) to access the CPU by exposing the inputs and outputs.

For further general information about GPIOs, see: [http://en.wikipedia.org/wiki/GPIO the wikipedia article].<BR>
For further specific information about the Raspberry Pi's BCM2835 GPIOs, see: [[RPi_BCM2835_GPIOs|this wiki article]].

The production Raspberry Pi board has a 26-pin 2.54 mm (100 mil)<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907</ref> expansion header, marked as P1, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I²C, SPI, UART), as well as +3.3 V, +5 V and GND supply lines. Pin one is the pin in the first column and on the bottom row. <ref>http://www.raspberrypi.org/archives/384</ref>

[[File:RPi_P1_header.png]]

'''GPIO voltage levels are 3.3 V and are not 5 V 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.

All the GPIO pins can be reconfigured to provide alternate functions, SPI, [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM], I²C and so. At reset only pins GPIO 14 & 15 are assigned to the alternate function UART, these two can be switched back to GPIO to provide a total of 17 GPIO pins<ref>http://www.raspberrypi.org/archives/384</ref>. Each of their functions and full details of how to access are detailed in the chipset datasheet <ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref>.

Each GPIO can interrupt, high/low/rise/fall/change.<ref>http://www.raspberrypi.org/archives/384#comment-5217</ref><ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref> There is currently no support for GPIO interrupts in the official kernel, howewer a patch exists, requiring compilation of modified source tree.<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=44&t=7509</ref> The 'Raspbian "wheezy"' <ref>http://www.raspberrypi.org/downloads</ref> version that is currently recommended for starters already includes GPIO interrupts.

GPIO input hysteresis (Schmitt trigger) can be on or off, output slew rate can be fast or limited, and source and sink current is configurable from 2 mA up to 16 mA. Note that chipset GPIO pins 0-27 are in the same block and these properties are set per block, not per pin. See [http://www.scribd.com/doc/101830961/GPIO-Pads-Control2 GPIO Datasheet Addendum - GPIO Pads Control]. Particular attention should be applied to the note regarding SSO (Simultaneous Switching Outputs): to avoid interference, driving currents should be kept as low as possible.

The available [[RPi_BCM2835_GPIOs|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.

There is also some information on the [[RPi Tutorial Easy GPIO Hardware & Software|Tutorial on Easy GPIO Hardware & Software]].

Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200 bit/s.

'''R-Pi PCB Revision 2 UPDATE:''' According to Eben at [http://www.raspberrypi.org/archives/1929#comment-31646] the R-Pi Rev.2 board being rolled out starting in September 2012 adds 4 more GPIO on a new connector called P5, and changes some of the existing P1 GPIO pinouts. On Rev2, GPIO_GEN2 [BCM2835/GPIO27] is routed to P1 pin 13, and changes what was SCL0/SDA0 to SCL1/SDA1: SCL1 [BCM2835/GPIO3] is routed to P1 pin 5, SDA1 [BCM2835/GPIO2] is routed to P1 pin 3. Also the power and ground connections previously marked "Do Not Connect" on P1 will remain as connected, specifically: P1-04:+5V0, P1-09:GND, P1-14:GND, P1-17:+3V3, P1-20:GND, P1-25:GND. According to this comment [http://www.raspberrypi.org/archives/2081#comment-33577] (and confirmed in this post [http://www.raspberrypi.org/archives/2233]) the P1 pinout is not expected to change in future beyond the current Rev.2 layout.

'''Header Pinout, top row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-02 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-04 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-06 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
|-
| P1-08 || bgcolor="lime" | GPIO 14 || bgcolor="lime" | GPIO 14 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_TXD || ALT5 = UART1_TXD
|-
| P1-10 || bgcolor="lime" | GPIO 15 || bgcolor="lime" | GPIO 15 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_RXD || ALT5 = UART1_RXD
|-
| P1-12 || bgcolor="lime" | GPIO 18 || bgcolor="lime" | GPIO 18 || || PCM_CLK || ALT4 = SPI1_CE0_N ALT5 = PWM0
|-
| P1-14 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-16 || bgcolor="lime" | GPIO23 || bgcolor="lime" | GPIO23 || || || ALT3 = SD1_CMD ALT4 = ARM_RTCK
|-
| P1-18 || bgcolor="lime" | GPIO24 || bgcolor="lime" | GPIO24 || || || ALT3 = SD1_DAT0 ALT4 = ARM_TDO
|-
| P1-20 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-22 || bgcolor="lime" | GPIO25 || bgcolor="lime" | GPIO25 || || || ALT3 = SD1_DAT1 ALT4 = ARM_TCK
|-
| P1-24 || bgcolor="lime" | GPIO08 || bgcolor="lime" | GPIO08 || || bgcolor="purple" | <span style="color:white">SPI0_CE0_N</span> ||
|-
| P1-26 || bgcolor="lime" | GPIO07 || bgcolor="lime" | GPIO07 || || bgcolor="purple" | <span style="color:white">SPI0_CE1_N</span> ||
|}

'''Header Pinout, bottom row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-01 || bgcolor="orange" | 3.3 V ||bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-03 || bgcolor="lime" | GPIO 0 || bgcolor="lime" | '''GPIO 2'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SDA / '''I2C1_SDA''' ||
|-
| P1-05 || bgcolor="lime" | GPIO 1 || bgcolor="lime" | '''GPIO 3'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SCL / '''I2C1_SCL''' ||
|-
| P1-07 || bgcolor="lime" | GPIO 4 || bgcolor="lime" | GPIO 4 || || GPCLK0 || ALT5 = ARM_TDI
|-
| P1-09 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-11 || bgcolor="lime" | GPIO17 || bgcolor="lime" | GPIO17 || || ||| ALT3 = UART0_RTS ALT4 = SPI1_CE1_N ALT5 = UART1_RTS
|-
| P1-13 || bgcolor="lime" | GPIO21 || bgcolor="lime" | '''GPIO27''' || || PCM_DOUT / '''reserved''' || ALT4 = SPI1_SCLK ALT5 = GPCLK1 / '''ALT3 = SD1_DAT3 ALT4 = ARM_TMS'''
|-
| P1-15 || bgcolor="lime" | GPIO22 || bgcolor="lime" | GPIO22 || || || ALT3 = SD1_CLK ALT4 = ARM_TRST
|-
| P1-17 || bgcolor="orange" | 3.3 V || bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-19 || bgcolor="lime" | GPIO10 || bgcolor="lime" | GPIO10 || || bgcolor="purple" | <span style="color:white">SPI0_MOSI</span> ||
|-
| P1-21 || bgcolor="lime" | GPIO9 || bgcolor="lime" | GPIO9 || || bgcolor="purple" | <span style="color:white">SPI0_MISO</span> ||
|-
| P1-23 || bgcolor="lime" | GPIO11 || bgcolor="lime" | GPIO11 || || bgcolor="purple" | <span style="color:white">SPI0_SCLK</span> ||
|-
| P1-25 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|}

{| border="1"
! Colour legend
|-
| bgcolor="red" | <span style="color:white">+5 V</span>
|-
| bgcolor="orange" | +3.3 V
|-
| bgcolor="black" | <span style="color:white">Ground, 0V</span>
|-
| bgcolor="yellow" | UART
|-
| bgcolor="lime" | GPIO
|-
| bgcolor="purple" | <span style="color:white">SPI</span>
|-
| bgcolor="cyan" | I²C
|}

KiCad symbol: [[File:Conn-raspberry.lib]]

<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2</ref>

Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as an I²C interface. So there are 1.8 kilohm pulls up resistors on the board for these pins.<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480</ref>

Pin 12 supports [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM] .

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.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.1</ref> 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.

It is also possible to reconfigure GPIO connector pins P1-12 and 13 (chipset GPIO 18 and 21) to provide an I2S (a hardware modification may be required<ref name="I2S">[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?]</ref>) or PCM interface.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.2</ref> However, PCM_FS and PCM_DIN (chipset pins 19 and 20) are needed for I2S or PCM.

A second I²C 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.

===Referring to pins on the Expansion header===

The header is referred to as "The GPIO Connector (P1)". To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended.

* The expansion header is referred to as "Expansion Header" or "GPIO Connector (P1)"
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.
* Names GPIO0, GPIO1, GPIOx-ALTy, etc. refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where "x" matches BCM2835 number (without leading zero) and "y" 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 "GPIO7" to refer to a row of the table, and "GPIO7-ALT0" would refer to a specific cell of the table.
* 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 "SPI0_*" and "SPI1_*", but they didn't do the same on the I²C and UART pins. Instead of using "SDA0" and "SCL0", you should use "I2C0_SDA" and "I2C0_SCL"; and instead of "TX" or "TXD" and "RX" or "RXD", you should use "UART0_TXD" and "UART0_RXD".

===Power pins===
The maximum permitted current draw from the 3.3 V pins is 50 mA.

Maximum permitted current draw from the 5 V pin is the USB input current (usually 1 A) minus any current draw from the rest of the board.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1536#postid-21841</ref>
*Model A: 1000 mA - 500 mA -> max current draw: 500 mA
*Model B: 1000 mA - 700 mA -> max current draw: 300 mA
Be very careful with the 5 V pins P1-02 and P1-04, because if you short 5 V to any other P1 pin you may permanently damage your RasPi. Before probing P1, it's a good idea to strip short pieces of insulation off a wire and push them over the 5 V pins so you don't accidentally short them with a probe.

=== GPIO hardware hacking ===

The complete list of [[RPi_BCM2835_GPIOs|chipset GPIO pins]] which are available on the GPIO connector is: <blockquote>[[RPi_BCM2835_GPIOs#GPIO0|0]], [[RPi_BCM2835_GPIOs#GPIO1|1]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO21|21]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]]</blockquote>

(on the Revision2.0 RaspberryPis, this list changes to: [[RPi_BCM2835_GPIOs#GPIO2|2]], [[RPi_BCM2835_GPIOs#GPIO3|3]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]], [[RPi_BCM2835_GPIOs#GPIO27|27]], with [[RPi_BCM2835_GPIOs#GPIO28|28]], [[RPi_BCM2835_GPIOs#GPIO29|29]], [[RPi_BCM2835_GPIOs#GPIO30|30]], [[RPi_BCM2835_GPIOs#GPIO31|31]] additionally available on the [[#P5_header|P5 header]])

As noted above, P1-03 and P1-05 (SDA0 and SCL0 / SDA1 and SCL1) have 1.8 kilohm pull-up resistors to 3.3 V.

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:

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 3.3 V.

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.

There are a few other chipset GPIO pins accessible on the PCB but are in use:

* GPIO16 drives status LED D5 (usually SD card access indicator)
* GPIO28-31 are used by the board ID and are connected to resistors R3 to R10 (only on Rev1.0 boards).
* GPIO40 and 45 are used by analogue audio and support [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM]. They connect to the analogue audio circuitry via R21 and R27 respectively.
* GPIO46 is HDMI hotplug detect (goes to pin 6 of IC1).
* 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.

=== P2 header ===

The P2 header is the VideoCore JTAG and used only during the production of the board. It cannot be used as the ARM JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>. This connector is unpopulated in Rev 2.0 boards.

[[File:RPi_P2_header.png]]

Useful P2 pins:

* Pin 1 - 3.3V (same as P1-01, 50 mA max current draw across both of them)
* Pin 7 - GND
* Pin 8 - GND

=== P3 header ===

The P3 header, unpopulated, is the LAN9512 JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>.

[[File:RPi_P3_header.png]]

Useful P3 pins:

* Pin 7 - GND

=== P5 header ===

The P5 header was added with the release of the Revision 2.0 PCB design.

'''P5 Pinout, seen from the bottom of the board:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P5-01 || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P5-02 || bgcolor="orange" | 3.3 V || 50 mA max (combined with P1)
|-
| P5-03 || bgcolor="lime" | GPIO28 || || bgcolor="cyan" | I2C0_SDA || ALT2 = PCM_CLK
|-
| P5-04 || bgcolor="lime" | GPIO29 || || bgcolor="cyan" | I2C0_SCL || ALT2 = PCM_FS
|-
| P5-05 || bgcolor="lime" | GPIO30 || || || ALT2 = PCM_DIN ALT3 = UART0_CTS ALT5 = UART1_CTS
|-
| P5-06 || bgcolor="lime" | GPIO31 || || || ALT2 = PCM_DOUT ALT3 = UART0_RTS ALT5 = UART1_RTS
|-
| P5-07 || bgcolor="black" | <span style="color:white">GND</span>
|-
| P5-08 || bgcolor="black" | <span style="color:white">GND</span>
|}

Note that the connector is intended to be mounted on the '''bottom''' of the PCB, so that for those who put the connector on the top side, the pin numbers are swapped. Pin 1 and pin 2 are swapped, pin 3 and 4, etc.

The new header can provide a second I2C channel (SDA + SCL) and handshake lines for the existing UART (TxD and RxD), or it can be used for an I2S (audio codec chip) interface using the PCM signals CLK, FS (Frame Sync), Din and Dout.

Note that the connector is placed JUST off-grid with respect to the P1 connector.

=== P6 header ===

The P6 header was added with the release of the Revision 2.0 PCB design.

[http://raspi.tv/2012/making-a-reset-switch-for-your-rev-2-raspberry-pi A reset button can be attached to the P6 header], with which the Pi can be reset.
Momentarily shorting the two pins of P6 together will cause a soft reset of the CPU.

===Driver support===

The Foundation will not include a GPIO driver in the initial release, standard Linux GPIO drivers should work with minimal modification.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1278.0</ref>

The community implemented SPI and I²C drivers <ref>http://www.bootc.net/projects/raspberry-pi-kernel/</ref>, which will be integrated with the new Linux pinctrl concept in a later version of the kernel. (On Oct. 14 2012, it was already included in the latest raspbian image.) A first compiled version as Linux modules is available to install on the 19/04/2012 Debian image, including 1-wire support<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=86172#p86172</ref>. The I²C and SPI driver uses the hardware modules of the microcontroller and interrupts for low CPU usage, the 1-wire support uses bitbanging on the GPIO ports, which results in higher CPU usage.

GordonH<ref>http://www.raspberrypi.org/forum/general-discussion/wiring-for-the-raspberry-pis-gpio</ref> wrote a (mostly) Arduino compatible/style [https://projects.drogon.net/raspberry-pi/wiringpi/ WiringPi library] in C for controlling the GPIO pins.

A useful tutorial on setting up I²C driver support can be found at [http://www.robot-electronics.co.uk/htm/raspberry_pi_examples.htm Robot Electronics] - look for the downloadable document rpi_i2c_setup.doc

===Graphical User Interfaces===
====WebIOPi====
[http://code.google.com/p/webiopi/ WebIOPi] allows you to control each GPIO with a simple web interface that you can use with any browser. Available in PHP and Python, they both require root access, but Python version serves HTTP itself. You can setup each GPIO as input or output and change their states (LOW/HIGH). WebIOPi is fully customizable, so you can use it for home remote control. It also work over Internet. UART/SPI/I2C support will be added later. If you need some computing for your GPIO go to code examples below.

==GPIO Code examples==
====GPIO Driving Example (C)====
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo & Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)
Example GPIO code:

<pre>
//
// How to access GPIO registers from C-code on the Raspberry-Pi
// Example program
// 15-January-2012
// Dom and Gert
// Revised: 15-Feb-2013

// Access from ARM Running Linux

#define BCM2708_PERI_BASE 0x20000000
#define GPIO_BASE (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/mman.h>
#include <unistd.h>

#define PAGE_SIZE (4*1024)
#define BLOCK_SIZE (4*1024)

int mem_fd;
void *gpio_map;

// I/O access
volatile unsigned *gpio;

// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)
#define INP_GPIO(g) *(gpio+((g)/10)) &= ~(7<<(((g)%10)*3))
#define OUT_GPIO(g) *(gpio+((g)/10)) |= (1<<(((g)%10)*3))
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)<=3?(a)+4:(a)==4?3:2)<<(((g)%10)*3))

#define GPIO_SET *(gpio+7) // sets bits which are 1 ignores bits which are 0
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0

void setup_io();

int main(int argc, char **argv)
{
int g,rep;

// Set up gpi pointer for direct register access
setup_io();

// Switch GPIO 7..11 to output mode

/************************************************************************\
* You are about to change the GPIO settings of your computer. *
* Mess this up and it will stop working! *
* It might be a good idea to 'sync' before running this program *
* so at least you still have your code changes written to the SD-card! *
\************************************************************************/

// Set GPIO pins 7-11 to output
for (g=7; g<=11; g++)
{
INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO
OUT_GPIO(g);
}

for (rep=0; rep<10; rep++)
{
for (g=7; g<=11; g++)
{
GPIO_SET = 1<<g;
sleep(1);
}
for (g=7; g<=11; g++)
{
GPIO_CLR = 1<<g;
sleep(1);
}
}

return 0;

} // main

//
// Set up a memory regions to access GPIO
//
void setup_io()
{
/* open /dev/mem */
if ((mem_fd = open("/dev/mem", O_RDWR|O_SYNC) ) < 0) {
printf("can't open /dev/mem \n");
exit(-1);
}

/* mmap GPIO */
gpio_map = mmap(
NULL, //Any adddress in our space will do
BLOCK_SIZE, //Map length
PROT_READ|PROT_WRITE,// Enable reading & writting to mapped memory
MAP_SHARED, //Shared with other processes
mem_fd, //File to map
GPIO_BASE //Offset to GPIO peripheral
);

close(mem_fd); //No need to keep mem_fd open after mmap

if (gpio_map == MAP_FAILED) {
printf("mmap error %d\n", (int)gpio_map);//errno also set!
exit(-1);
}

// Always use volatile pointer!
gpio = (volatile unsigned *)gpio_map;

} // setup_io

</pre>

====GPIO Pull Up/Pull Down Register Example====
<pre>
// enable pull-up on GPIO24&25
GPIO_PULL = 2;
short_wait();
// clock on GPIO 24 & 25 (bit 24 & 25 set)
GPIO_PULLCLK0 = 0x03000000;
short_wait();
GPIO_PULL = 0;
GPIO_PULLCLK0 = 0;
</pre>

====GPIO Driving Example (Python)====
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO
Any Python script that controls GPIO must be run as root.
<pre>import RPi.GPIO as GPIO

# Set up the GPIO channels - one input and one output
GPIO.setup(11, GPIO.IN)
GPIO.setup(12, GPIO.OUT)

# Input from pin 11
input_value = GPIO.input(11)

# Output to pin 12
GPIO.output(12, True)

# The same script as above but using BCM GPIO 00..nn numbers
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.IN)
GPIO.setup(18, GPIO.OUT)
input_value = GPIO.input(17)
GPIO.output(18, True)</pre>

====GPIO Driving Example (Java using the Pi4J Library)====
This uses the Java library available at http://www.pi4j.com/.
(Any Java application that controls GPIO must be run as root.)

Please note that the Pi4J library uses the WiringPi GPIO pin numbering scheme <ref>http://pi4j.com/usage.html#Pin_Numbering</ref> <ref>https://projects.drogon.net/raspberry-pi/wiringpi/pins/</ref>. Please see the usage documentation for more details: http://pi4j.com/usage.html

<pre>

public static void main(String[] args) {

// create gpio controller
GpioController gpio = GpioFactory.getInstance();

// provision gpio pin #01 as an output pin and turn off
GpioPinDigitalOutput outputPin = gpio.provisionDigitalOutputPin(RaspiPin.GPIO_01, "MyLED", PinState.LOW);

// turn output to LOW/OFF state
outputPin.low();

// turn output to HIGH/ON state
outputPin.high();

// provision gpio pin #02 as an input pin with its internal pull down resistor enabled
GpioPinDigitalInput inputPin = gpio.provisionDigitalInputPin(RaspiPin.GPIO_02, "MyButton", PinPullResistance.PULL_DOWN);

// get input state from pin 2
boolean input_value = inputPin.isHigh();
}
</pre>

More complete and detailed examples are included on the Pi4J website at http://www.pi4j.com/.

The Pi4J library includes support for:
* GPIO Control
* GPIO Listeners
* Serial Communication
* I2C Communication
* SPI Communication

====GPIO Driving Example (Java)====
This uses the Java library available at https://github.com/jkransen/framboos. It does not depend on (or use) the wiringPi driver, but uses the same numbering scheme. Instead it uses the default driver under /sys/class/gpio that ships with the distro, so it works out of the box. Any Java application that controls GPIO must be run as root.
<pre>
public static void main(String[] args) {
// reading from an in pin
InPin button = new InPin(8);
boolean isButtonPressed = button.getValue();
button.close();

// writing to an out pin
OutPin led = new Outpin(0);
led.setValue(true);
led.setValue(false);
led.close();
}
</pre>

====GPIO Driving Example (Java Webapp GPIO web control via http)====
This uses the Java Webapp available at https://bitbucket.org/sbub/raspberry-pi-gpio-web-control/overview. You can control your GPIO over the internet. Any Java application that controls GPIO must be run as root.
<pre>

host:~ sb$ curl 'http://raspberrypi:8080/handle?g0=1&g1=0'
{"g1":0,"g0":1}

</pre>

====GPIO Driving Example (Bash shell script, using sysfs, part of the raspbian operating system)====
The export and unexport of pins must be done as root.
To change to the root user see below: To change back, the word exit must be entered.
<pre>sudo -i</pre>
Export creates a new folder for the exported pin, and creates files for each of its control functions (i.e. active_low, direction, edge, power, subsystem, uevent, and value). Upon creation, the control files can be read by all users (not just root), but can only be written to by user root, the file's owner. Nevertheless, once created, it is possible to allow users other than root, to also write inputs to the control files, by changing the ownership or permissions of these files. Changes to the file's ownership or permissions must initially be done as root, as their owner and group is set to root upon creation. Typically you might change the owner to be the (non root) user controlling the GPIO, or you might add write permission, and change the group ownership to one of which the user controlling the GPIO is a member. By such means, using only packages provided in the recommended rasbian distribution, it is possible for Python CGI scripts, which are typically run as user nobody, to be used for control of the GPIO over the internet from a browser at a remote location.
<pre>
#!/bin/sh

# GPIO numbers should be from this list
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25

# Note that the GPIO numbers that you program here refer to the pins
# of the BCM2835 and *not* the numbers on the pin header.
# So, if you want to activate GPIO7 on the header you should be
# using GPIO4 in this script. Likewise if you want to activate GPIO0
# on the header you should be using GPIO17 here.

# Set up GPIO 4 and set to output
echo "4" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio4/direction

# Set up GPIO 7 and set to input
echo "7" > /sys/class/gpio/export
echo "in" > /sys/class/gpio/gpio7/direction

# Write output
echo "1" > /sys/class/gpio/gpio4/value

# Read from input
cat /sys/class/gpio/gpio7/value

# Clean up
echo "4" > /sys/class/gpio/unexport
echo "7" > /sys/class/gpio/unexport
</pre>

====GPIO Driving Example (Shell script - take 2)====
You need the wiringPi library from
https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/. Once installed, there is a new command '''gpio''' which can be used
as a '''non-root''' user to control the GPIO pins.

The man page <pre>man gpio</pre> has full details, but briefly:

<pre>
gpio -g mode 17 out
gpio -g mode 18 pwm

gpio -g write 17 1
gpio -g pwm 18 512
</pre>

The '''-g''' flag tells the '''gpio''' program to use the BCM GPIO pin numbering
scheme (otherwise it will use the wiringPi numbering scheme by default).

The gpio command can also control the internal pull-up and pull-down
resistors:

<pre>
gpio -g mode 17 up
</pre>

This sets the pull-up resistor - however any change of mode, even
setting a pin that's already set as an input to an input will remove
the pull-up/pull-down resistors, so they may need to be reset.

Additionally, it can export/un-export the GPIO devices for use by
other non-root programms - e.g. Python scripts. (Although you
may need to drop the calls to GPIO.Setup() in the Python scripts, and
do the setup separately in a little shell script, or call the '''gpio''' program
from inside Python).

<pre>
gpio export 17 out
gpio export 18 in
</pre>

These exports GPIO-17 and sets it to output, and exports GPIO-18
and sets it to input.

And when done:

<pre>
gpio unexport 17
</pre>

The export/unexport commands always use the BCM GPIO pin numbers regardless of the
presence of the '''-g''' flag or not.

If you want to use the internal pull-up/down's with the /sys/class/gpio mechanisms,
then you can set them after exporting them. So:

<pre>
gpio -g export 4 in
gpio -g mode 4 up
</pre>

You can then use GPIO-4 as an input in your Python, Shell, Java, etc. programs without the use
of an external resistor to pull the pin high. (If that's what you were after - for example, a simple push
button switch taking the pin to ground.)

A fully working example of a shell script using the GPIO pins
can be found at http://project-downloads.drogon.net/files/gpioExamples/tuxx.sh.

====GPIO Driving Example (Lazarus / Free Pascal)====
[[File:RPI GPIO testprogram with lazarus.png|thumb|254px|right|A simple app for controlling GPIO pin 17 with Lazarus]]

The GPIO pins are accessible from [[Lazarus on RPi|Lazarus]] without any third-party software. This is performed by means of invoking Unix shell commands with '''fpsystem'''. The following example uses GPIO pin 17 as output port. It is assumed that you created a form with a TToggleBox named GPIO17ToggleBox and for logging purposes a TMemo with name LogMemo (optional). The program has to be executed with root privileges.

''Unit for controlling the GPIO port:''
<pre>
unit Unit1;

{Demo application for GPIO on Raspberry Pi}
{Inspired by the Python input/output demo application by Gareth Halfacree}
{written for the Raspberry Pi User Guide, ISBN 978-1-118-46446-5}

{$mode objfpc}{$H+}

interface

uses
Classes, SysUtils, FileUtil, Forms, Controls, Graphics, Dialogs, StdCtrls, Unix;

type

{ TForm1 }

TForm1 = class(TForm)
LogMemo: TMemo;
GPIO17ToggleBox: TToggleBox;
procedure FormActivate(Sender: TObject);
procedure FormClose(Sender: TObject; var CloseAction: TCloseAction);
procedure GPIO17ToggleBoxChange(Sender: TObject);
private
{ private declarations }
public
{ public declarations }
end;

var
Form1: TForm1;
gReturnCode: longint; {stores the result of the IO operation}

implementation

{$R *.lfm}

{ TForm1 }

procedure TForm1.FormActivate(Sender: TObject);
begin
{ Prepare SoC pin 17 (pin 11 on GPIO port) for access: }
gReturnCode := fpsystem('echo "17" > /sys/class/gpio/export');
LogMemo.Lines.Add(IntToStr(gReturnCode));
{ Set SoC pin 17 as output: }
gReturnCode := fpsystem('echo "out" > /sys/class/gpio/gpio17/direction');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;

procedure TForm1.FormClose(Sender: TObject; var CloseAction: TCloseAction);
begin
{ Free SoC pin 17: }
gReturnCode := fpsystem('echo "17" > /sys/class/gpio/unexport');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;

procedure TForm1.GPIO17ToggleBoxChange(Sender: TObject);
begin
if GPIO17ToggleBox.Checked then
begin
{ Swith SoC pin 17 on: }
gReturnCode := fpsystem('echo "1" > /sys/class/gpio/gpio17/value');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end
else
begin
{ Switch SoC pin 17 off: }
gReturnCode := fpsystem('echo "0" > /sys/class/gpio/gpio17/value');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;

end.
</pre>

''Main program:''
<pre>
program io_test;

{$mode objfpc}{$H+}

uses
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Interfaces, // this includes the LCL widgetset
Forms, Unit1
{ you can add units after this };

{$R *.res}

begin
Application.Initialize;
Application.CreateForm(TForm1, Form1);
Application.Run;
end.
</pre>

An alternative way to access the GPIO port with Lazarus / Free Pascal is by using [http://www.lazarus.freepascal.org/index.php/topic,17404.0.html Lazarus wrapper unit for Gordon Henderson's wiringPi C library].

====GPIO Driving Example (C + wiringPi)====
Get and install wiringPi: https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/

Save this, and compile with:
<pre>
gcc -o blink blink.c -lwiringPi
</pre>
and run with:
<pre>
sudo ./blink
</pre>

<pre>
/*
* blink.c:
* blinks the first LED
* Gordon Henderson, projects@drogon.net
*/

#include <stdio.h>
#include <wiringPi.h>

int main (void)
{
printf ("Raspberry Pi blink\n") ;

if (wiringPiSetup () == -1)
return 1 ;

pinMode (0, OUTPUT) ; // aka BCM_GPIO pin 17

for (;;)
{
digitalWrite (0, 1) ; // On
delay (500) ; // mS
digitalWrite (0, 0) ; // Off
delay (500) ;
}
return 0 ;
}
</pre>

====GPIO Driving Example (C)====
This must be done as root. To change to the root user:
<pre>sudo -i</pre>
You must also get and install the bcm2835 library, which supports
GPIO and SPI interfaces. Details and downloads
from http://www.open.com.au/mikem/bcm2835

<pre>

// blink.c
//
// Example program for bcm2835 library
// Blinks a pin on an off every 0.5 secs
//
// After installing bcm2835, you can build this
// with something like:
// gcc -o blink -l rt blink.c -l bcm2835
// sudo ./blink
//
// Or you can test it before installing with:
// gcc -o blink -l rt -I ../../src ../../src/bcm2835.c blink.c
// sudo ./blink
//
// Author: Mike McCauley (mikem@open.com.au)
// Copyright (C) 2011 Mike McCauley
// $Id: RF22.h,v 1.21 2012/05/30 01:51:25 mikem Exp $

#include <bcm2835.h>

// Blinks on RPi pin GPIO 11
#define PIN RPI_GPIO_P1_11

int main(int argc, char **argv)
{
// If you call this, it will not actually access the GPIO
// Use for testing
// bcm2835_set_debug(1);

if (!bcm2835_init())
return 1;

// Set the pin to be an output
bcm2835_gpio_fsel(PIN, BCM2835_GPIO_FSEL_OUTP);

// Blink
while (1)
{
// Turn it on
bcm2835_gpio_write(PIN, HIGH);

// wait a bit
delay(500);

// turn it off
bcm2835_gpio_write(PIN, LOW);

// wait a bit
delay(500);
}

return 0;
}
</pre>

====GPIO Driving Example (Perl)====
This must be done as root. To change to the root user:
<pre>sudo su -</pre>
Supports GPIO and SPI interfaces.
You must also get and install the bcm2835 library. Details and downloads
from http://www.open.com.au/mikem/bcm2835
You must then get and install the Device::BCM2835 perl library from CPAN
http://search.cpan.org/~mikem/Device-BCM2835-1.0/lib/Device/BCM2835.pm
<pre>
use Device::BCM2835;
use strict;

# call set_debug(1) to do a non-destructive test on non-RPi hardware
#Device::BCM2835::set_debug(1);
Device::BCM2835::init()
|| die "Could not init library";

# Blink pin 11:
# Set RPi pin 11 to be an output
Device::BCM2835::gpio_fsel(&Device::BCM2835::RPI_GPIO_P1_11,
&Device::BCM2835::BCM2835_GPIO_FSEL_OUTP);

while (1)
{
# Turn it on
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 1);
Device::BCM2835::delay(500); # Milliseconds
# Turn it off
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 0);
Device::BCM2835::delay(500); # Milliseconds
}

</pre>

==== GPIO Driving Example (C#) ====
RaspberryPiDotNet library is available at https://github.com/cypherkey/RaspberryPi.Net/.
The library includes a GPIOFile and GPIOMem class. The GPIOMem requires compiling Mike McCauley's bcm2835 library above in to a shared object.

<pre>
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using RaspberryPiDotNet;
using System.Threading;

namespace RaspPi
{
class Program
{
static void Main(string[] args)
{
// Access the GPIO pin using a static method
GPIOFile.Write(GPIO.GPIOPins.GPIO00, true);

// Create a new GPIO object
GPIOMem gpio = new GPIOMem(GPIO.GPIOPins.GPIO01);
gpio.Write(false);
}
}
}
</pre>

====GPIO Driving Example (Ruby)====

This example uses the WiringPi Ruby Gem: http://pi.gadgetoid.co.uk/post/015-wiringpi-now-with-serial which you can install on your Pi with "gem install wiringpi"

<pre>
MY_PIN = 1

require 'wiringpi'
io = WiringPi::GPIO.new
io.mode(MY_PIN,OUTPUT)
io.write(MY_PIN,HIGH)
io.read(MY_PIN)
</pre>

Alternatively the Pi Piper Gem (https://github.com/jwhitehorn/pi_piper) allows for event driven programming:

<pre>
require 'pi_piper'
include PiPiper

watch :pin => 23 do
puts "Pin changed from #{last_value} to #{value}"
end

PiPiper.wait
</pre>

====GPIO Driving Example (BASIC - Return to BASIC)====

'''RTB''' or Return to Basic can be found here: https://projects.drogon.net/return-to-basic/

It's a new BASIC featuring modern looping constructs, switch statements, named procedures and functions as well as graphics (caresian and turtle), file handling and more. It also supports the Pi's on-board GPIO without needing to be run as root. (You don't need any special setup routines either)

Sample blink program:

<pre>
// blink.rtb:
// Blink program in Return to Basic
// Gordon Henderson, projects@drogon.net
//
PinMode (0, 1) // Output
CYCLE
DigitalWrite (0, 1) // Pin 0 ON
WAIT (0.5) // 0.5 seconds
DigitalWrite (0, 0)
WAIT (0.5)
REPEAT
END
</pre>

====GPIO Driving Example (BASIC)====

'''Bywater BASIC Interpreter'''

The Bywater BASIC Interpreter (bwBASIC) implements a large superset of the ANSI Standard for Minimal BASIC (X3.60-1978) and a significant subset of the ANSI Standard for Full BASIC (X3.113-1987) in C. It also offers shell programming facilities as an extension of BASIC. bwBASIC seeks to be as portable as possible.
You can download it at.
http://packages.debian.org/stable/interpreters/bwbasic

'''BASIC programming of the I/O'''

'''Setting up a GPIO pin to be used for inputs or for outputs.'''

We cannot load the control words directly into the 32 bit ARM registers with 32 bit addresses, as bwBASIC has no POKE and PEEK commands and other versions of BASIC (as far as I know) only handle 8 bit registers with 16 bit addresses with these commands. So we need to export the GPIO pins, so that they exist in a file structure which we can access from basic with the OPEN command.(ref 2)

We need to do this in Linux root.
We need to run BASIC in the root too. First we go to the root, then we load bwbasic into root.
<pre>
sudo -1
sudo bwbasic
</pre>

REM Now to export the no4 GPIO pin for example, using a Shell command.

<pre>echo “4” > /sys/class/gpio/export</pre>

Whilst bwbasic can accommodate shell commands, and we can store a set of these commands (eg. to export a number of GPIO pins at the outset) as numbered statements in a file that can be loaded with the basic command LOAD “filename” and RUN (ref 2), the shell commands have to run as a separate file, as they cannot be run from within, as part of a basic programme.

'''Now we can access the file containing the pin direction setting from BASIC'''

We can set GPIO pin 4 to input or to output by OPENing its pin direction file for output and writing “in” or “out” with a PRINT# command. (ref 2 )
<syntaxhighlight lang="basic4gl">
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 PRINT #1,”out”
30 CLOSE #1
</syntaxhighlight>

REM closes the open direction file, whereupon the system performs the action of setting the direction to “out”. NB the system only carries out the action as the file is closed.(ref 3)

'''We are now able to control the output of the gpio 4 pin from BASIC'''

We can set the GPIO 4 pin to 1 or to 0 by OPENing its pin value file for output and writing “1” or “0” with a PRINT# command.
<syntaxhighlight lang="basic4gl">
40 OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
50 PRINT #4,”1”
60 CLOSE #4
</syntaxhighlight>

REM turns on the output of GPIO pin 4.

REM similarly we can turn off the output of GPIO pin 4.
OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
PRINT #4,”0”
CLOSE #4.

'''Example of an (unstructured) BASIC programme'''

To read the state of a switch and control the power to two LEDs connected to GPIO pins 8,7 and 4 respectively.

Programme to set 2 pins as outputs and 1 pin as input and to read the input turning on two different combinations of the two outputs (ie output 0,1 or 1,0) depending on the state of the input (1 or 0).
<syntaxhighlight lang="basic4gl">
sudo –i
sudo bwbasic
LOAD “export.bas”
LIST
REM a set of Shell statements to export the three GPIO pins.
10 echo “4” > /sys/class/gpio/export
20 echo “7” > /sys/class/gpio/export
30 echo “8” > /sys/class/gpio/export
RUN
</syntaxhighlight>

NEW REM clears the export.bas programme from memory
<syntaxhighlight lang="basic4gl">
.
LOAD “demo1.bas”
LIST
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 OPEN ”O”,#2, “/sys/devices/virtual/gpio/gpio7/direction”,2
30 OPEN ”O”,#3, “/sys/devices/virtual/gpio/gpio8/direction”,2
REM opens the three pin direction files
40 PRINT #1, “out”
50 PRINT #2, “out”
60 PRINT #3, “in”
REM sets GPIO pins 4 and 7 as outputs and GPIO pin 8 as input.
70 CLOSE #1
80 CLOSE #2
90 CLOSE #3
REM closes all open files, allowing the system to perform the direction settings.
100 OPEN ”I”,#8, “/sys/devices/virtual/gpio/gpio8/value”,1
REM opens the GPIO pin 8 value file
110 INPUT #8,x
REM reads the value of the input pin and stores the value in numerical variable x
120 CLOSE #8
REM closes the open file, allowing the system to read the value of the input pin and store the value in numerical variable x.
130 OPEN “O”,#1, “/sys/devices/virtual/gpio/gpio4/value”,1
140 OPEN “O”,#2, “/sys/devices/virtual/gpio/gpio7/value”,1
REM opens the GPIO pins 4 and value files ready for outputting 1s and 0s.
150 IF x<1 THEN GOTO 160 ELSE GOTO 190
REM tests the state of the switch (1 or0) and directs the program to generate the appropriate outputs
160 PRINT #1,”1”
170 PRINT #2,”0”
180 GOTO 210
190 PRINT#1,"0"
200 PRINT #2,"1"
210 CLOSE #1
220 CLOSE #2
REM Closes the files and allows the outputs to light the LED
230 END.
</syntaxhighlight>

When all is done, we should unexport the GPIO pins, to leave the R-Pi as we found it.(Ref 1.)
<syntaxhighlight lang="basic4gl">
NEW
LOAD “unexport.bas”
LIST
REM a set of Shell statements to unexport the three GPIO pins.
10 echo “4” > /sys/class/gpio/unexport
20 echo “7” > /sys/class/gpio/unexport
30 echo “8” > /sys/class/gpio/unexport
RUN
</syntaxhighlight>
A simple circuit to provide the switched input and the two LED outputs.

Ancient Mariner. Dec. 2012

References.

1. This paper RPi Low-level peripherals.

2. Ed Beynon. [http://www.ybw.com/forums/showthread.php?t=331320&page=5 http://www.ybw.com/forums/showthread.php?t=331320&page=5]

3. Arthur Kaletzky. Private communication. 25/10/2012

4. bwbasic manual.<br/>

For the two original documents this example has been copied from see:<br/>
[[Media:GPIO_Driving_Example_(BASIC)_.doc | GPIO_Driving_Example_(BASIC)_.doc]]

[[Media:Raspberry_Pi_I-O_viii.doc | Raspberry_Pi_I-O_viii.doc]]

==MIPI CSI-2==

On the production board<ref>http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf</ref>, the Raspberry Pi Foundation design brings out the MIPI CSI-2 (Camera Serial Interface<ref>http://www.mipi.org/specifications/camera-interface</ref>) to a 15-way flat flex connector S5, between the Ethernet and HDMI connectors. A compatible camera has been discussed as working in tests and is planned for release at a later date.<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/complex-camera-peripherials#p72602</ref>.


==DSI==

On the production board, the Raspberry Pi Foundation design brings out the DSI (Display Serial Interface<ref>http://www.mipi.org/specifications/display-interface</ref>) to a 15-way flat flex connector labelled S2, next to Raspberry Pi logo. It has two data lanes and a clock lane, to drive a possible future LCD screen device. Some smart phone screens use DSI<ref>http://en.wikipedia.org/wiki/Display_Serial_Interface</ref>.

==CEC==

[[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.
Eben notes that he has seen CEC demos on the Broadcom SoC they are using.

libCEC with Raspberry Pi support has been included in OpenELEC and will be included in Raspbmc RC4.<ref>http://blog.pulse-eight.com/2012/08/01/libcec-1-8-0-a-firmware-upgrade-and-raspberry-pi-support/</ref>

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.

== References ==
<references/>

{{Template:Raspberry Pi}}

File:RPi P3 header.png

2013-03-01T00:54:10Z

AndrewS: The P3 header on the RaspberryPi, showing the orientation of the pin numbers Category:RaspberryPi

The P3 header on the RaspberryPi, showing the orientation of the pin numbers

[[Category:RaspberryPi]]

File:RPi P2 header.png

2013-03-01T00:53:12Z

AndrewS: The P2 header on the RaspberryPi, showing the orientation of the pin numbers Category:RaspberryPi

The P2 header on the RaspberryPi, showing the orientation of the pin numbers

[[Category:RaspberryPi]]

File:RPi P1 header.png

2013-03-01T00:47:40Z

AndrewS:

The P1 header on the RaspberryPi, showing the orientation of the pin numbers

[[Category:RaspberryPi]]

File:RPi P1 header.png

2013-03-01T00:46:52Z

AndrewS: The P1 header on the RaspberryPi, showing the orientation of the pin numbers

The P1 header on the RaspberryPi, showing the orientation of the pin numbers

RPi Hardware

2013-02-24T16:50:31Z

AndrewS: /* Components */ Added height of Model A board

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

==Introduction==
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]
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]].

Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].

Several different Hardware versions/revisions [[RaspberryPi Boards]] have been found probably from different assembly lines. Try to identify your board for better troubleshooting and update it if you have one which is not mentioned.

==Specifications==
{| class="wikitable"
!
! Model A
! Model B
|-
| Target price:<ref name="faq" >http://www.raspberrypi.org/faqs</ref>
| US$25 Ext tax (GBP £16 Exc VAT)
| US$35 Ext tax (GBP £22 Exc VAT)
|-
| System-on-a-chip (SoC):<ref name="faq" />
| colspan="2" | Broadcom BCM2835 (CPU + GPU. SDRAM is a separate chip stacked on top)
|-
| CPU:
| colspan="2" | 700 MHz ARM11 ARM1176JZF-S core
|-
| GPU:
| colspan="2" | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode
|-
| Memory (SDRAM)iB
| 256 MiB (planned with 128 MiB, upgraded to 256 MiB on 29 Feb 2012)
| 256 MiB (until 15 Oct 2012); 512 MiB (since 15 Oct 2012)
|-
| USB 2.0 ports:
| 1 (provided by the BCM2835)
| 2 (via integrated USB hub)
|-
| Video outputs:<ref name="faq" />
| colspan="2" | Composite video | Composite RCA, HDMI (not at the same time)
|-
| Audio outputs:<ref name="faq" />
| colspan="2" | TRS connector | 3.5 mm jack, HDMI
|-
| Audio inputs:
| colspan="2" | none, but a USB mic or sound-card could be added
|-
| Onboard Storage:
| colspan="2" | Secure Digital|SD / MMC / SDIO card slot
|-
| Onboard Network:<ref name="faq" />
| None
| 10/100 wired Ethernet RJ45
|-
| Low-level peripherals:
| colspan="2" | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S<ref name="i2s">[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?]</ref>, Universal asynchronous receiver/transmitter (UART)
|-
| Real-time clock:<ref name="faq" />
| colspan="2" | None
|-
| Power ratings (provisional, from alpha board):
| 500 mA, (2.5 W) <ref name="faq" />
| 700 mA, (3.5 W)
|-
| Power source:<ref name="faq" />
| colspan="2" | 5 V (DC) via Micro USB type B or GPIO header
|-
| Size:
| colspan="2" | 85.0 x 56.0 mm (two different boards, measured with callipers)
|}

==Components==
[[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
Beech, edited to show 256MB ram for both boards]]
(Provisional - some of the expansion interfaces won't be available on production boards)
(PCB IDs are those of the Model B Beta board)

* 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:
** 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].
** 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
** 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)
** 256MiB of ([http://www.hynix.com/products/mobile/view.jsp?info.ramKind=28&info.serialNo=H9TKNNN2GDMPLR&posMap=MobileDDR2 Hynix MobileDDR2] or [http://www.samsung.com/global/business/semiconductor/product/mobile-dram/detail?productId=7611&iaId=747 Samsung Mobile DRAM]) SDRAM (or 512MB [http://www.samsung.com/global/business/semiconductor/product/mobile-dram/detail?iaId=747&productId=7609 Mobile DRAM] on later boards). The RAM is physically stacked on top of the Broadcom media processor ([http://en.wikipedia.org/wiki/Package_on_package package-on-package technology]). Here is a photo of the [http://www.raspberrypi.org/wp-content/uploads/2012/01/brcm2835plusmemory.jpg SDRAM (left) and BCM2835 (right)] ball grid arrays on JamesH's finger. You are looking at the bottom side. The BCM2835 top side has a land grid array which matches the SDRAM ball grid array. Here is a highly magnified side view of the SDRAM stacked on top of the BCM2835 stacked on top of the PCB [http://www.raspberrypi.org/wp-content/uploads/2012/09/2012-09-21-10.58.22.jpg PoP stack] (you can see why it's job that can only be done by robots!).
* 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:
** 10/100Mb Ethernet (Auto-MDIX)<ref name=autoMDIX>[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]</ref>
** 2x USB 2.0
* S1: Micro USB power jack (5v - Power Only)
* 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.
* S3: HDMI connector providing type A HDMI 1.3a out
* S4: Composite Video connector: RCA
* S5: MIPI [http://www.mipi.org/specifications/camera-interface CSI-2] interface. 15-pin surface mounted flat flex connector.
* S6: Audio connector: 3.5mm stereo jack (output only)
* S8: SD/MMC/SDIO memory card slot (underside)
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''
* P1: 26-pin (2x13) 2.54 mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]
** 8 [[Rpi_Low-level_peripherals#General_Purpose_Input.2FOutput_.28GPIO.29|GPIO]]s at 3v3
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3
** I²C interface (3v3); or 2 GPIOs at 3v3
** SPI interface (3v3); or 5 GPIOs at 3v3
** 3v3, 5v and GND supply pins
** ARM JTAG (if pins are reconfigured in software - on Revision1.0 boards one signal would also need to be taken from S5)
** I²S interface (if pins are reconfigured in software, hardware hack may be required<ref name="i2s"/>)
* P2: 8-pin 2.54 mm header expansion (header not fitted on Revision 2.0 boards), providing GPU JTAG (ARM11 pinout, pin 7 is nofit for locating)
* P3: 7-pin 2.54 mm header expansion (header not fitted), providing LAN9512 JTAG (pin 6 is nofit for locating)
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''
* P5: 8-pin (2x4) 2.54 mm header expansion (header not fitted), on the ''bottom'' of the board, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]] '''(Revision 2.0 boards only)'''
** 4 [[Rpi_Low-level_peripherals#P5_header|GPIO]]s at 3v3
** 3v3, 5v and GND supply pins
** Second I²C interface (3v3) (if pins are reconfigured in software)
** I²S interface (if pins are reconfigured in software)
** Handshake signals for the UART on the P1 header (if pins are reconfigured in software)
* P6: 2-pin 2.54 mm header expansion (header not fitted), providing an option to connect a hardware-reset button '''(Revision 2.0 boards only)'''
* TP1 and TP2: Test Points giving access to +5V and GND respectively
* 5 Status LEDs<ref name="PCBs">[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]</ref><ref name="LEDs">[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]</ref><ref name="LEDsGPIO">[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?]</ref><ref name="OKGreen">[[RPi_schematic_errata]]</ref><ref name="Revision2.0">[http://www.raspberrypi.org/archives/1959 RPiBlog Post: A nice shiny photo of the rev2 board – and User Guide news]</ref>:
** D5(Green) - SDCard Access (via GPIO16) - labelled as "OK" on Rev1.0 boards and "ACT" on Rev2.0 boards
** D6(Red) - 3.3 V Power - labelled as "PWR" on both Rev1.0 and Rev2.0 boards
** D7(Green) - Full Duplex (LAN) '''(Model B)''' - labelled as "FDX" on both Rev1.0 and Rev2.0 boards
** D8(Green) - Link/Activity (LAN) '''(Model B)''' - labelled as "LNK" on both Rev1.0 and Rev2.0 boards
** D9(Yellow) - 10/100Mbit (LAN) '''(Model B)''' - labelled (incorrectly) as "10M" on Rev1.0 boards and "100" on Rev2.0 boards

* Board size: 85.60 mm x 53.98 mm. Overall height expected to be less than 25 mm. <ref name="artwork">http://www.raspberrypi.org/archives/344</ref>
** A Model B between the highest points (USB connector to card slot) measured 21 mm.
** A Model A between the highest points (composite video connector to card slot) measured 18mm.
* Weight: under 40 g?
** Alpha board weighs approx. 55 g.<ref>http://www.raspberrypi.org/?page_id=43&mingleforumaction=viewtopic&t=285.0</ref>
** A sample model B weighed 39.45 g.
* 6 layer PCB <ref name="artwork" />

==Schematic / Layout==

* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot rev 1.0]
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot rev 1.0, labelled version]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]
* [http://elinux.org/File:RPi-Front-JPB.jpg High-resolution Model B PCB front photo, production board rev 1.0]
* [http://elinux.org/File:RPi-back-JPB.jpg High-resolution Model B PCB back photo, production board rev 1.0]
* [http://www.raspberrypi.org/wp-content/uploads/2012/09/sony-rasp-pi.jpg High-resolution Model B PCB front photo, production board rev 2.0]
* [http://www.raspberrypi.org/wp-content/uploads/2012/11/2012-11-29-14.48.47-HDR.jpg High-resolution Model A PCB front photo, production board rev 2.0]
* [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 (117MB)]
* [[Media:RPi beta xray.jpg|"Xray style" image of the beta board, created from the above GIMP project]] | [[RPi_xray_wallpapers|desktop wallpapers]]
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official Rev 1.0 schematics PDF] | [http://www.raspberrypi.org/wp-content/uploads/2012/10/Raspberry-Pi-R2.0-Schematics-Issue2.2_027.pdf Official Rev 2.0 schematics PDF] | [[RPi_schematic_differences|differences]] | [[RPi_schematic_errata|errata]] | [[RPi_schematics_breakdown|breakdown]] | [[RPi_Partial_BOM_Rev2.0_ModelB|partial BOM]]
* [http://www.andrewscheller.co.uk/rpi_pcb_modules.html 'Module groups' of the PCB photos]

==Power==

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).
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.

Premier Farnell recommend the following power supplies:
* Model A: 5V dc, 500-700mA
* Model B: 5V dc, 700-1200mA

Power consumption of the Raspberry Pi device is

* Board A: 5V, 500 mA (2.5W) '''without any devices connected''' (e.g. USB, Ethernet, HDMI)
* 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 "using networking and high-current USB peripherals" [http://www.raspberrypi.org/archives/260].)

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.

*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.
* 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.
* POE ([[wikipedia: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 - mind though that the Ethernet jack on the board is a 'magjack' - http://www.sparkfun.com/datasheets/Prototyping/MagJack.pdf - which means that the usual 'dumb or passive PoE' power pins 47 and 78 are *not* wired through to the board. So this is not an entirely trivial exercise).
* Back-Powering; (powering the Raspberry Pi from a USB hub through the uplink/data port, single cable) Back powering is possible on the Raspberry Pi. Revision 1.0 boards have to be modified to back power, this is due to the 140ma "polyfuses" that are installed in the USB port circuit. Revision 1.1 boards do not need modifications to back-power, they have replaced the polyfuses with 0ohm resistors in their place. Revision 2.0 boards do not need modification, they have neither resistors nor polyfuses. It is advised that short (12" (.3 meter) or less) USB cables be used for back-powering a Raspberry Pi. Cable resistance plus connector resistance can quickly reduce operating voltages below the proper range(5.25V to 4.75V).

===Power Supply Problems===

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.

The power required by the Pi will vary depending on how busy it is and what peripherals are connected.
* Running a GUI will take more power.
* The USB devices and Ethernet connection will take power.
* Running the GPU will take extra power.

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.
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 of the two USB ports on the Pi has a polyfuse rated at 140 mA, so any connected USB devices should draw less than this amount of current. In addition the polyfuse will cause a significant voltage drop, so that USB devices get less voltage than is available on the RPI itself, sometimes up to half a volt less (maybe more if the fuse has recently been hot). For regular "low power" USB devices this doesn't cause a problem as they are designed to work with voltages as low as 4.4 Volt. This isn't the case however with some USB devices such as WiFi dongles which may need 4.75 Volt, and are also known to draw more than 150 mA when configured and active. Because of the problems these polyfuses caused Raspberry PI's produced after August 25, 2012 have the USB polyfuses F1 & F2 removed (replaced with shorts).

The microUSB input port also has a 1.1 A polyfuse (700mA "hold current") which may also have enough resistance (although much smaller than the 140mA fuses) to cause a significant voltage drop on the board, even below its 1.1 A total current.

A extended explanation of the consequences of the use of these polyfuses can be found here [[Polyfuses explained]]

There are several reasons why the power to the board may be inadequate:
* 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 its full power without the voltage dropping.
* The PSU is not regulated.
* 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.
* If the PSU is unregulated it can also output too high a voltage, which may trigger the overvoltage device in the PI, which will temporarily short the 5V to ground, this will then "blow" polyfuse F3, which will take several days to recover from. Meanwhile (possibly with another PSU) the PI might not get enough power because the (partly) blown polyfuse is consuming some of the power. The solution is when this happens to ways a few days to give the polyfuse time to recover before attempting to use the better PSU. If you suspect a blow polyfuse, measure the voltage across F3, which should be less than 0.05 Volt.

====How Can I tell if the power supply is inadequate?====

Common symptoms of an inadequate power supply are
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.
* SD card errors at start up seems to be another symptom of poor power.

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

Use a multimeter which is set to the range 20 volts DC (or 20v =). You should see a voltage between 4.75 and 5.25 volts. Anything outside this range indicates that you have a problem with your power supply or your power cable, or the input polyfuse F3. Anything inside, but close to the limits, of this range ''may'' indicate a problem.

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

====Things that can cause problems====
* 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.
* 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.
* A power supply that is rated for less than 700mA may work some of the time.
* 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.
* 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.

====Summary====

* If you are having unreliable operation the first thing to do is check your power supply.
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.
* Not all power supplies will deliver what they claim.

===Capacitor C6===
Behind the microUSB power connector on the Model B is a metallic grey component called a capacitor, marked as C6. This capacitor helps stabilise the DC power on the board, but for some it has also become a place for their thumb when removing the RPI's power lead; unfortunately, this can result in the capacitor breaking off! It has been stated in the forums that the type of capacitor used for C6 will be changed on later RPi models for one with sturdier leads. If you do break off your C6 capacitor, it's highly likely that your RPi will still work properly, unless you have a particularly unstable power supply, but the general advice is to not use C6 as a leverage point when removing the power connector and also take care when storing or transporting your RPi if it's not fitted in a case - try not to stow the board where C6 could be knocked by other items - for example in a laptop carry case or in amongst some books.
[[File:Rpic6.jpg|300px|thumb|center|Capacitor C6 (ringed)]]

It's unlikely that replacing a broken off C6 capacitor will be covered under warranty, but fortunately they are easy to replace if you have average [http://www.raspberrypi.org/archives/1494 soldering skills], but remember that reworking your RPi will void its warranty too. C6 is a surface mount electrolytic capacitor with a capacitance of 220 microfarad (μF) and a voltage rating of 16 volt (V). The capacitor is polarised and so must be fitted the right way round - notice the black marking on one side in the picture above. A replacement capacitor can be purchased from numerous sources - for example:

[http://uk.farnell.com/jsp/search/browse.jsp?N=202457+110114112+110119850+110141127+110200576&No=0&getResults=true&appliedparametrics=true&locale=en_UK&divisionLocale=en_UK&catalogId=&skipManufacturer=false&skipParametricAttributeId=&prevNValues=202457+110114112+110119850+110141127&mm=1000002|110114112|110114112,1001880|110119850|110119850,1002520||,1002063||,1002999||,&filtersHidden=false&appliedHidden=false&autoApply=true&originalQueryURL=%2Fjsp%2Fsearch%2Fbrowse.jsp%3FN%3D202457%26No%3D0%26getResults%3Dtrue%26appliedparametrics%3Dtrue%26locale%3Den_UK%26divisionLocale%3Den_UK%26catalogId%3D%26skipManufacturer%3Dfalse%26skipParametricAttributeId%3D%26prevNValues%3D202457 Farnell]

[http://www.rapidonline.com/Electronic-Components/220uf-16v-85deg-Smd-Electro-Capacitor-11-2264 Rapid Electronics]

[http://uk.rs-online.com/web/c/passives/capacitors/aluminium/?sort-by=default&sort-order=default&applied-dimensions=4294884868,%204294884170,%204294672278,4294885140&lastAttributeSelectedBlock=4294955811 RS Components]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==References==
<references/>

{{Template:Raspberry Pi}}

RPi Hardware

2013-02-24T16:03:42Z

AndrewS: /* Components */ Extra P1 pins are no loner reserved. Added P5 and P6 for Revision 2.0 boards

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

==Introduction==
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]
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]].

Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].

Several different Hardware versions/revisions [[RaspberryPi Boards]] have been found probably from different assembly lines. Try to identify your board for better troubleshooting and update it if you have one which is not mentioned.

==Specifications==
{| class="wikitable"
!
! Model A
! Model B
|-
| Target price:<ref name="faq" >http://www.raspberrypi.org/faqs</ref>
| US$25 Ext tax (GBP £16 Exc VAT)
| US$35 Ext tax (GBP £22 Exc VAT)
|-
| System-on-a-chip (SoC):<ref name="faq" />
| colspan="2" | Broadcom BCM2835 (CPU + GPU. SDRAM is a separate chip stacked on top)
|-
| CPU:
| colspan="2" | 700 MHz ARM11 ARM1176JZF-S core
|-
| GPU:
| colspan="2" | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode
|-
| Memory (SDRAM)iB
| 256 MiB (planned with 128 MiB, upgraded to 256 MiB on 29 Feb 2012)
| 256 MiB (until 15 Oct 2012); 512 MiB (since 15 Oct 2012)
|-
| USB 2.0 ports:
| 1 (provided by the BCM2835)
| 2 (via integrated USB hub)
|-
| Video outputs:<ref name="faq" />
| colspan="2" | Composite video | Composite RCA, HDMI (not at the same time)
|-
| Audio outputs:<ref name="faq" />
| colspan="2" | TRS connector | 3.5 mm jack, HDMI
|-
| Audio inputs:
| colspan="2" | none, but a USB mic or sound-card could be added
|-
| Onboard Storage:
| colspan="2" | Secure Digital|SD / MMC / SDIO card slot
|-
| Onboard Network:<ref name="faq" />
| None
| 10/100 wired Ethernet RJ45
|-
| Low-level peripherals:
| colspan="2" | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S<ref name="i2s">[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?]</ref>, Universal asynchronous receiver/transmitter (UART)
|-
| Real-time clock:<ref name="faq" />
| colspan="2" | None
|-
| Power ratings (provisional, from alpha board):
| 500 mA, (2.5 W) <ref name="faq" />
| 700 mA, (3.5 W)
|-
| Power source:<ref name="faq" />
| colspan="2" | 5 V (DC) via Micro USB type B or GPIO header
|-
| Size:
| colspan="2" | 85.0 x 56.0 mm (two different boards, measured with callipers)
|}

==Components==
[[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
Beech, edited to show 256MB ram for both boards]]
(Provisional - some of the expansion interfaces won't be available on production boards)
(PCB IDs are those of the Model B Beta board)

* 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:
** 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].
** 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
** 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)
** 256MiB of ([http://www.hynix.com/products/mobile/view.jsp?info.ramKind=28&info.serialNo=H9TKNNN2GDMPLR&posMap=MobileDDR2 Hynix MobileDDR2] or [http://www.samsung.com/global/business/semiconductor/product/mobile-dram/detail?productId=7611&iaId=747 Samsung Mobile DRAM]) SDRAM (or 512MB [http://www.samsung.com/global/business/semiconductor/product/mobile-dram/detail?iaId=747&productId=7609 Mobile DRAM] on later boards). The RAM is physically stacked on top of the Broadcom media processor ([http://en.wikipedia.org/wiki/Package_on_package package-on-package technology]). Here is a photo of the [http://www.raspberrypi.org/wp-content/uploads/2012/01/brcm2835plusmemory.jpg SDRAM (left) and BCM2835 (right)] ball grid arrays on JamesH's finger. You are looking at the bottom side. The BCM2835 top side has a land grid array which matches the SDRAM ball grid array. Here is a highly magnified side view of the SDRAM stacked on top of the BCM2835 stacked on top of the PCB [http://www.raspberrypi.org/wp-content/uploads/2012/09/2012-09-21-10.58.22.jpg PoP stack] (you can see why it's job that can only be done by robots!).
* 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:
** 10/100Mb Ethernet (Auto-MDIX)<ref name=autoMDIX>[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]</ref>
** 2x USB 2.0
* S1: Micro USB power jack (5v - Power Only)
* 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.
* S3: HDMI connector providing type A HDMI 1.3a out
* S4: Composite Video connector: RCA
* S5: MIPI [http://www.mipi.org/specifications/camera-interface CSI-2] interface. 15-pin surface mounted flat flex connector.
* S6: Audio connector: 3.5mm stereo jack (output only)
* S8: SD/MMC/SDIO memory card slot (underside)
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''
* P1: 26-pin (2x13) 2.54 mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]
** 8 [[Rpi_Low-level_peripherals#General_Purpose_Input.2FOutput_.28GPIO.29|GPIO]]s at 3v3
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3
** I²C interface (3v3); or 2 GPIOs at 3v3
** SPI interface (3v3); or 5 GPIOs at 3v3
** 3v3, 5v and GND supply pins
** ARM JTAG (if pins are reconfigured in software - on Revision1.0 boards one signal would also need to be taken from S5)
** I²S interface (if pins are reconfigured in software, hardware hack may be required<ref name="i2s"/>)
* P2: 8-pin 2.54 mm header expansion (header not fitted on Revision 2.0 boards), providing GPU JTAG (ARM11 pinout, pin 7 is nofit for locating)
* P3: 7-pin 2.54 mm header expansion (header not fitted), providing LAN9512 JTAG (pin 6 is nofit for locating)
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''
* P5: 8-pin (2x4) 2.54 mm header expansion (header not fitted), on the ''bottom'' of the board, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]] '''(Revision 2.0 boards only)'''
** 4 [[Rpi_Low-level_peripherals#P5_header|GPIO]]s at 3v3
** 3v3, 5v and GND supply pins
** Second I²C interface (3v3) (if pins are reconfigured in software)
** I²S interface (if pins are reconfigured in software)
** Handshake signals for the UART on the P1 header (if pins are reconfigured in software)
* P6: 2-pin 2.54 mm header expansion (header not fitted), providing an option to connect a hardware-reset button '''(Revision 2.0 boards only)'''
* TP1 and TP2: Test Points giving access to +5V and GND respectively
* 5 Status LEDs<ref name="PCBs">[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]</ref><ref name="LEDs">[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]</ref><ref name="LEDsGPIO">[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?]</ref><ref name="OKGreen">[[RPi_schematic_errata]]</ref><ref name="Revision2.0">[http://www.raspberrypi.org/archives/1959 RPiBlog Post: A nice shiny photo of the rev2 board – and User Guide news]</ref>:
** D5(Green) - SDCard Access (via GPIO16) - labelled as "OK" on Rev1.0 boards and "ACT" on Rev2.0 boards
** D6(Red) - 3.3 V Power - labelled as "PWR" on both Rev1.0 and Rev2.0 boards
** D7(Green) - Full Duplex (LAN) '''(Model B)''' - labelled as "FDX" on both Rev1.0 and Rev2.0 boards
** D8(Green) - Link/Activity (LAN) '''(Model B)''' - labelled as "LNK" on both Rev1.0 and Rev2.0 boards
** D9(Yellow) - 10/100Mbit (LAN) '''(Model B)''' - labelled (incorrectly) as "10M" on Rev1.0 boards and "100" on Rev2.0 boards

* Board size: 85.60 mm x 53.98 mm. Overall height expected to be less than 25 mm. <ref name="artwork">http://www.raspberrypi.org/archives/344</ref>
** A model B between highest points (USB connector to card slot) measured 21 mm.
* Weight: under 40 g?
** Alpha board weighs approx. 55 g.<ref>http://www.raspberrypi.org/?page_id=43&mingleforumaction=viewtopic&t=285.0</ref>
** A sample model B weighed 39.45 g.
* 6 layer PCB <ref name="artwork" />

==Schematic / Layout==

* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot rev 1.0]
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot rev 1.0, labelled version]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]
* [http://elinux.org/File:RPi-Front-JPB.jpg High-resolution Model B PCB front photo, production board rev 1.0]
* [http://elinux.org/File:RPi-back-JPB.jpg High-resolution Model B PCB back photo, production board rev 1.0]
* [http://www.raspberrypi.org/wp-content/uploads/2012/09/sony-rasp-pi.jpg High-resolution Model B PCB front photo, production board rev 2.0]
* [http://www.raspberrypi.org/wp-content/uploads/2012/11/2012-11-29-14.48.47-HDR.jpg High-resolution Model A PCB front photo, production board rev 2.0]
* [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 (117MB)]
* [[Media:RPi beta xray.jpg|"Xray style" image of the beta board, created from the above GIMP project]] | [[RPi_xray_wallpapers|desktop wallpapers]]
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official Rev 1.0 schematics PDF] | [http://www.raspberrypi.org/wp-content/uploads/2012/10/Raspberry-Pi-R2.0-Schematics-Issue2.2_027.pdf Official Rev 2.0 schematics PDF] | [[RPi_schematic_differences|differences]] | [[RPi_schematic_errata|errata]] | [[RPi_schematics_breakdown|breakdown]] | [[RPi_Partial_BOM_Rev2.0_ModelB|partial BOM]]
* [http://www.andrewscheller.co.uk/rpi_pcb_modules.html 'Module groups' of the PCB photos]

==Power==

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).
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.

Premier Farnell recommend the following power supplies:
* Model A: 5V dc, 500-700mA
* Model B: 5V dc, 700-1200mA

Power consumption of the Raspberry Pi device is

* Board A: 5V, 500 mA (2.5W) '''without any devices connected''' (e.g. USB, Ethernet, HDMI)
* 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 "using networking and high-current USB peripherals" [http://www.raspberrypi.org/archives/260].)

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.

*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.
* 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.
* POE ([[wikipedia: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 - mind though that the Ethernet jack on the board is a 'magjack' - http://www.sparkfun.com/datasheets/Prototyping/MagJack.pdf - which means that the usual 'dumb or passive PoE' power pins 47 and 78 are *not* wired through to the board. So this is not an entirely trivial exercise).
* Back-Powering; (powering the Raspberry Pi from a USB hub through the uplink/data port, single cable) Back powering is possible on the Raspberry Pi. Revision 1.0 boards have to be modified to back power, this is due to the 140ma "polyfuses" that are installed in the USB port circuit. Revision 1.1 boards do not need modifications to back-power, they have replaced the polyfuses with 0ohm resistors in their place. Revision 2.0 boards do not need modification, they have neither resistors nor polyfuses. It is advised that short (12" (.3 meter) or less) USB cables be used for back-powering a Raspberry Pi. Cable resistance plus connector resistance can quickly reduce operating voltages below the proper range(5.25V to 4.75V).

===Power Supply Problems===

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.

The power required by the Pi will vary depending on how busy it is and what peripherals are connected.
* Running a GUI will take more power.
* The USB devices and Ethernet connection will take power.
* Running the GPU will take extra power.

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.
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 of the two USB ports on the Pi has a polyfuse rated at 140 mA, so any connected USB devices should draw less than this amount of current. In addition the polyfuse will cause a significant voltage drop, so that USB devices get less voltage than is available on the RPI itself, sometimes up to half a volt less (maybe more if the fuse has recently been hot). For regular "low power" USB devices this doesn't cause a problem as they are designed to work with voltages as low as 4.4 Volt. This isn't the case however with some USB devices such as WiFi dongles which may need 4.75 Volt, and are also known to draw more than 150 mA when configured and active. Because of the problems these polyfuses caused Raspberry PI's produced after August 25, 2012 have the USB polyfuses F1 & F2 removed (replaced with shorts).

The microUSB input port also has a 1.1 A polyfuse (700mA "hold current") which may also have enough resistance (although much smaller than the 140mA fuses) to cause a significant voltage drop on the board, even below its 1.1 A total current.

A extended explanation of the consequences of the use of these polyfuses can be found here [[Polyfuses explained]]

There are several reasons why the power to the board may be inadequate:
* 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 its full power without the voltage dropping.
* The PSU is not regulated.
* 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.
* If the PSU is unregulated it can also output too high a voltage, which may trigger the overvoltage device in the PI, which will temporarily short the 5V to ground, this will then "blow" polyfuse F3, which will take several days to recover from. Meanwhile (possibly with another PSU) the PI might not get enough power because the (partly) blown polyfuse is consuming some of the power. The solution is when this happens to ways a few days to give the polyfuse time to recover before attempting to use the better PSU. If you suspect a blow polyfuse, measure the voltage across F3, which should be less than 0.05 Volt.

====How Can I tell if the power supply is inadequate?====

Common symptoms of an inadequate power supply are
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.
* SD card errors at start up seems to be another symptom of poor power.

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

Use a multimeter which is set to the range 20 volts DC (or 20v =). You should see a voltage between 4.75 and 5.25 volts. Anything outside this range indicates that you have a problem with your power supply or your power cable, or the input polyfuse F3. Anything inside, but close to the limits, of this range ''may'' indicate a problem.

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

====Things that can cause problems====
* 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.
* 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.
* A power supply that is rated for less than 700mA may work some of the time.
* 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.
* 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.

====Summary====

* If you are having unreliable operation the first thing to do is check your power supply.
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.
* Not all power supplies will deliver what they claim.

===Capacitor C6===
Behind the microUSB power connector on the Model B is a metallic grey component called a capacitor, marked as C6. This capacitor helps stabilise the DC power on the board, but for some it has also become a place for their thumb when removing the RPI's power lead; unfortunately, this can result in the capacitor breaking off! It has been stated in the forums that the type of capacitor used for C6 will be changed on later RPi models for one with sturdier leads. If you do break off your C6 capacitor, it's highly likely that your RPi will still work properly, unless you have a particularly unstable power supply, but the general advice is to not use C6 as a leverage point when removing the power connector and also take care when storing or transporting your RPi if it's not fitted in a case - try not to stow the board where C6 could be knocked by other items - for example in a laptop carry case or in amongst some books.
[[File:Rpic6.jpg|300px|thumb|center|Capacitor C6 (ringed)]]

It's unlikely that replacing a broken off C6 capacitor will be covered under warranty, but fortunately they are easy to replace if you have average [http://www.raspberrypi.org/archives/1494 soldering skills], but remember that reworking your RPi will void its warranty too. C6 is a surface mount electrolytic capacitor with a capacitance of 220 microfarad (μF) and a voltage rating of 16 volt (V). The capacitor is polarised and so must be fitted the right way round - notice the black marking on one side in the picture above. A replacement capacitor can be purchased from numerous sources - for example:

[http://uk.farnell.com/jsp/search/browse.jsp?N=202457+110114112+110119850+110141127+110200576&No=0&getResults=true&appliedparametrics=true&locale=en_UK&divisionLocale=en_UK&catalogId=&skipManufacturer=false&skipParametricAttributeId=&prevNValues=202457+110114112+110119850+110141127&mm=1000002|110114112|110114112,1001880|110119850|110119850,1002520||,1002063||,1002999||,&filtersHidden=false&appliedHidden=false&autoApply=true&originalQueryURL=%2Fjsp%2Fsearch%2Fbrowse.jsp%3FN%3D202457%26No%3D0%26getResults%3Dtrue%26appliedparametrics%3Dtrue%26locale%3Den_UK%26divisionLocale%3Den_UK%26catalogId%3D%26skipManufacturer%3Dfalse%26skipParametricAttributeId%3D%26prevNValues%3D202457 Farnell]

[http://www.rapidonline.com/Electronic-Components/220uf-16v-85deg-Smd-Electro-Capacitor-11-2264 Rapid Electronics]

[http://uk.rs-online.com/web/c/passives/capacitors/aluminium/?sort-by=default&sort-order=default&applied-dimensions=4294884868,%204294884170,%204294672278,4294885140&lastAttributeSelectedBlock=4294955811 RS Components]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==References==
<references/>

{{Template:Raspberry Pi}}

eLinux.org:RPi Council

2013-02-24T13:00:05Z

AndrewS: /* If you are interested edit here */

{{Hub Flags}}
{{Clear}}
Because of the messed up stuff on the Raspberry Pi wiki, I have found it necessary to create a governing council for the RPi wiki. Please edit the below section if you'd like to become a member (alderman) of the council.

Note: This is official and is ok with the administration of eLinux.

== Supplemental guidelines ==
''If anything is wrong with these guidelines please feel free to edit them. Thank you.''
=== Guidelines are made from consensus ===
All supplemental guidelines and decisions will now be made by the RPWC and eLinux administration.

== Current council aldermen ==
* President - [[User:Jeff|Jeff]]
* [[User:TrevorGowen|Trevor Gowen]]

== Current issues ==
=== Users ===
==== Mahjongg ====
<s>As he is not answering my requests for identity, he may be impersonating Mahjongg on the forums. I propose the account be blocked indefinitely because it clearly is copying the RPi forum mod's user name.</s> --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 12:26, 5 October 2012 (UTC)
:Verified thru PM. Case closed. :) --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 21:16, 5 October 2012 (UTC)

==== Ghans ====
I propose that since he ruined a lot of formatting that he is not to edit the Raspberry Pi Wiki's formatting for 1 month. You can see clearly [[RPi Wiki Best Practice|here]]. He, in fact, misguided everyone in best practices! I want you to go to Wikipedia and take a hard stare and compare the articles! They are misleading! He clearly cannot go on with this! Anyone else agree? --[[User:Jeff|Jeff]] 02:15, 2 October 2012 (UTC)<br />'''Edit: and also add a block of 1 month if he does not comply.''' --[[User:Jeff|Jeff]] 22:39, 2 October 2012 (UTC)<br />
(Note: This decision must be concluded by Wednesday, October 3, 2012.)
:Having compared [[RPi Wiki Best Practice|Ghans' "Best Practice"]] with which, I believe, are the equivalent areas of Wikipedia and parts of the Help sections here I can see what you mean. However, using Wikipedia as a guide, one also has to assume that he was writing with the best of intentions. Unfortunately he does not reveal much about his background, experience etc. on his user page. However, having had the experience of encouraging "best practice" within a mixed group of programmer's of different backgrounds (scientific, computational) and training (formal, informal, none), I am well aware that when considering adopting such from a related area, one also has to consider the needs etc. of the intended users ie. adopt as much as is appropriate, adapt or reject the remainder. An analogy would be that when preparing a presentation one may end up with several versions depending upon the expected audience. Hence, whilst I am prepared to support your proposal, it is on the understanding that this is done so to allow us to begin to formulate more suitable guidelines, given that, eventually, hopefully, there will be younger, enthusiastic but less experienced contributers whom I would not wish to discourage. --[[User:TrevorGowen|TrevorGowen]] 14:40, 2 October 2012 (UTC)
::So you're a support? --[[User:Jeff|Jeff]] 22:32, 2 October 2012 (UTC)
:::Assuming I'm interpreting your update above correctly, to mean that he is requested to refrain from edits that change formatting aspects of the Raspbery Pi sections of the Wiki for one month and ignores that request, yes. Hopefully such a request will generate a response, therebye opening up a dialogue, which may resolve matters such that a formal block need not be imposed. --[[User:TrevorGowen|TrevorGowen]] 12:09, 3 October 2012 (UTC)
I guess I will close this with a warning to Ghans. Block not implemented. --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 12:39, 3 October 2012 (UTC)

=== Content ===
==== Shutdown of most other language "hubs" ====
'''Due to the importance of this topic, ''everyone'' is invited to post their opinions, even users that are not a council member.'''<br />
These hubs serve no purpose but to point the respective language speakers to English pages. This is utterly useless. If I only spoke Greek, I would be able to understand the hub, but the hub's purpose is to link to other pages. Unfortunately I would ask a Greek community for help because the links are to ENGLISH pages! Why don't we just tell everyone a bold message: THIS IS AN ENGLISH WIKI! I propose to redirect all these pages to the English page; as for the template Hub Flags, I propose it be renamed as the RPi Hub header, or something like so. --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:27, 11 October 2012 (UTC)<br />
'''This shall be concluded on Friday, October 12, 2012 at 9:00pm (21:00) Eastern Standard Time, or whenever an obvious consensus closes.'''
:Is this for real?... it goes against the actions of the Raspberry Pi Foundation, see http://www.raspberrypi.org/archives/1715. If they want to spread their Forum into multiple languages, then so should the wiki. [[User:Simon Small|SimonSmall]] 20:31, 11 October 2012 (UTC)
::'''THIS IS NEITHER CONTROLLED BY NOR SANCTIONED BY THE RASPI FOUNDATION'''. Unless YOU want to make all the different language pages, you really need to knock some sense into yourself. --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 22:57, 11 October 2012 (UTC)
:Whilst it is my understanding that this section of the eLinux Wiki was created by members of the Raspi Foundation's forum (who, presumably, were already active contributors here), most of the non-english language pages appear to have been created in the early part of 2012 '''before''' the Raspberry Pi was generally available. As the number of active RasPi users grew, it was somewhat inevitable that contributions to this wiki area would increase. Unfortunately this has been at such a pace that, even where there had been significant translation effort in the early stages, at present, there appear to be too few people with the necessary skills to maintain those pages. I certainly don't have them (my French skills learned some 45 years ago are far too "rusty"). From the RPWC's president's comments above, I assume he's in a similar position. Hence, until such time that there are enough RPWC members with sufficient skills and "spare" time to properly check/moderate any translated pages, I agree that it is probably necessary to "shut them down". However, out of respect for the effort put into those early pages, I hope that such a shutdown will not result in complete deletion (where there has been significant effort), just in case their restoration becomes viable. --[[User:TrevorGowen|TrevorGowen]] 17:52, 12 October 2012 (UTC)
::Yes, I will only redirect them. Very well. I guess we have finally reached consensus. --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 02:50, 19 October 2012 (UTC)

Well, yes the dictator reach a consensus. FR:RPi-Hub was maintained, I did some change as well as other during the last few months. Now what will happend when french speaking people go the this site. They will see an english only site and move on. Well Done!!

Papillon

If the non-English "hubs" have been shutdown/redirected/whatever, maybe the list at http://elinux.org/RPi_Hub#Translations should be cleaned up too? [[User:AndrewS|AndrewS]] 23:13, 23 October 2012 (UTC)

=== Supplemental guidelines ===
==== This isn't the RPi Forums ====
This will officially tell all that the RPi Forums are not how the RPi Wiki works! Closes whenever consensus is apparently reached. --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 23:01, 11 October 2012 (UTC)

==== Official language ====
'''Note: Due to the importance of this topic, all users, regardless of RPWC membership, may discuss this.'''
As amending to the above, English should be the official language of the wiki. We are in Amnet/Engnet/Euronet, not Runet or Chinet, so let's just say ENGLISH really should be the official language. --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:37, 11 October 2012 (UTC)
(closes on Friday)

I strongly disagree with that opinion. If you do make all hub page point to english, what is the point of having translation? You are not alone on this planet. A hole bunch of people don't speak (read) english at all.

The point of having translation, is to offer the same information in different languages so as much as possible persons can read thing about the RPi. I know that it is not possible (practically speaking) to have all hub pages having the same exact information but at least the info is there in as much language possible.

If you make english to only language here (even if just for the hub) people will go else where for a wiki and all your good work will be of no use. Just look around http://frenchmagpi.site-mpe.fr/index.php/Accueil, the magpi is being translated to french, issue 5 is already published and issue 6 is in good progress.

In my opinion, "my language is the official one" opinion is selfish and close minded. The goal of a public wiki on the web like this one is to let people share as much as possible their information. Look at the succes of wikipedia, it is available in I don't know many language, there are pages on the same subject in many many languages that don't have all the same information but at least there is information for every one and a lot more people can find information than if just english is available.

It is ok to have the default page point to the english hub but keep the flag and translated hub available to all. Do not trow to garbage the work of all the people who translated (updated) the hub to there own language.

Papillon
:: Thank you for your comments - I've been waiting for further contributions to this discussion since, without proper feedback from the wiki users, this "council" has no mandate for its efforts. Personally, I do not like the term "official language", and feel it would be more appropriate to use the term "primary language". Whilst this wiki has "public access", it appears to be "privately hosted", hence I do not regard it as a "public wiki" like wikipedia. I've already indicated above that I do not wish the existing translation work to be "thrown away", however, some of the "translated hubs" appear to be "skeletal forms" with minimal content. As such they are potentially misleading as to the level and quality of content of this area of work. Should such pages be marked more clearly with their "translation status" (in their "native" language '''and''' English), and with the category "needs editing" (or similar) then I'd be much happier for them to remain linked to.--[[User:TrevorGowen|TrevorGowen]] 08:34, 16 October 2012 (UTC)

Hi, I'm not an English native speaker either - and I agree with the proposal of having English as the primary language ... but also with keeping of the already created translations and the hub - in maybe some form of "unofficial" sub-pages without guarantee that they contain the same/verified/complete information. If they really posses any valuable information rather than being just a fork pointing to English articles, they should be kept available (at least as read-only), otherwise it's rational to clean up. The term "official language" may not be the best choice, "primary language" sounds much better, but in my belief this is not about any selfishness, discrimination or anything else than an effort to keep this wiki well organized, readable, oriented on quality content, brief and clear. Maybe the language-hub can be placed somewhere at the bottom or as a sidebar menu (change to official wiki style?) with a clear marking, that its purpose is to provide extra space for smaller communities of people speaking other languages, and/or as some kind of mirrored clones with basic info from the main pages. Well, if that's what this wiki's objectives are... I understand very well that, this wiki may have a specific orientation and every contributor should respect the rules. Also, one wiki cannot meet everybody's wishes. There are plenty other options for specific language oriented wikis, forums, creating own, etc. On the other hand, if there is someone who would like to take over the role of an editor for a specific language and properly maintain the contents of that pages, I'm sure he will be greatly welcome. One more note - everybody should be aware that this is not a official Raspberry Pi Foundation's wiki. It is a publicly available private wiki (notwithstanding that it is created mostly by public community) for embedded Linux systems in general (correct me if necessary), where RPi is one of such systems/devices. It just happened to be the best available place for this purpose at the time, and thus the Raspberry Pi Foundation simply provided a link to this wiki (instead of creating its own, having to maintain it, moderate, etc.). We should be happy for having this place available for public collaboration. But without proper administration, it may easily become just a mess of unreadable contributions and literally lose its point... Who would want that? ;) --[[User:Pinoccio|Pinoccio]] 14:30, 16 October 2012 (UTC)

==== Wiki Design principles ====

<s>All good things require a good design. To improve this site, we should (re)define / clarify its purpose. The following principles are suggested:

Users of the Raspberry Pi will be of three types (or a mixture of these);
(a) competent Linux user,
(b) experienced hardware and/or software modifier / hobbyist
(c) beginner

Each page should consider WHY a reader would be using that page.

A competent Linux user would only want to know how to get the Raspberry Pi working and set up, and any 'peculiarities' relating to the hardware or Linux distribution. The hobbyist would additionally want to know how to use the GPIO ports and associated software, or how to modify / build the distribution or packages not included in that distribution. There should be clear pointers on the first page for the sections relating to these groups.

The beginner will need careful guidance in their first steps. For this, instructions should be clear:
* they lead the user from what they know into what they don't, with each step being small and simple with the 'objective' clearly defined.
* they use simple steps, and should skip optional complications that are not relevant to the current 'lesson', e.g. half of the raspi-config settings are 'advanced'.
* they should include a link to complete documentation for the topic, with a warning that this may cover advanced material, e.g. full raspi-config instructions.
* the writer should take into account that the site, and users, will be global, with english as a second language.
* the writer should take into account the variations of hardware and distribution installed, e.g. the raspi-config utility is not available in many distributions.
* the instructions should clearly state if they are specific to a particular set up, or are 'date sensitive' to changes.
* pages should be separated into GUI and command line pages and flows.
* instructions should be free from point-of-view opinions.
* instructions should link to 'choice' pages that give pros and cons regarding that choice, e.g. which text editor should be used and if it is available / installable.

The beginner guidance should stop at the point where other sites can take over, e.g. once sufficient Linux has been covered, other Linux sites can provide more advanced or specific information. It should also be aligned to the objectives stated by the Raspberry Pi Foundation for why the Raspberry Pi exists.

Proposal, in absence of anything similar. [[User:Simon Small|SimonSmall]] 16:54, 4 October 2012 (UTC)</s>
:I strongly oppose this. We should NEVER split users into "social classes" and English is our official language, just as English is the Raspberry Pi's preferred language. I think this overhaul is too much right now. Why don't we focus on something else first? Also, you can't make proposals unless you already are a council alderman, in which case, as of my posting time, you currently are not. --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:40, 5 October 2012 (UTC)
::As you clearly don't know much about a wiki, I suggest you become more mature when you apply for alderman in the future. I have rejected your request for aldermanship. --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 01:43, 5 October 2012 (UTC)
:::Interesting. Explanation? Quote from above "If anything is wrong with these guidelines please feel free to edit them. Thank you." This raises two questions; (1) What is being done to fix the Wiki? (2) How will (the wiki) encourage new users to contribute, especially the enthusiastic but inexperienced who likely form the target demographic? [[User:Simon Small|SimonSmall]] 21:45, 5 October 2012 (UTC)
::::That means minor changes, not major, overhauling changes. Also, nothing is ''wrong'' with the guidelines! --[[User:Jeff|<font color="#0645ad">'''Jeff'''</font>]] • [[User_talk:Jeff|<font color="#0645ad">(talk)</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] [[Project:RPi_Council|<font color="#0645ad">RPWC President</font>]] [[File:RaspPi.png|25px|link=|Member of the RPWC]] 04:30, 7 October 2012 (UTC)

== If you are interested edit here ==
'''Please indicate your interest in joining the council below here, along with a link to your userpage.'''

I have no interest in joining the council myself (just don't have the time), but I think any self-appointed "wiki council" should give itself some validity by spending some time coming up with practical guidelines / recommendations (without being ''too'' restrictive of course) rather than the "petty squabbling" that this page seems to be about so far ;-)
For example maybe you could have a list of pages that you've already "cleaned up", so that we can at least see what "best practices" look like. And maybe you could come up with some guidelines for how pages like [[RPi_Hardware]] and [[RPi_Low-level_peripherals]] should document things which are different for the different revisions of RaspberryPi boards that exist? And Jeff, it might be useful to link to this page from your userpage :) [[User:AndrewS|AndrewS]] 23:31, 23 October 2012 (UTC)

Some more things I've spotted after a quick poke around...
* I see you reverted the change Ryanteck made when adding Rastrack, citing "Self advertising" - IMHO Rastrack is a useful link (it's been featured on the RPi blog) and shouldn't count as self-advertising. When deleting links from the wiki (e.g. if they're on "the wrong page"), maybe you could add them onto "the right page" at the same time? We '''do''' want the wiki to be newbie-friendly, don't we? :)
* In terms of "guidelines", should all pages like e.g. [[Raspcontrol]] be renamed to e.g. "RPi_Raspcontrol" ?
* Surely it'd have been better just to edit the existing [[RPi_Wiki_Best_Practice]] rather than nominating it for deletion (and removing all links to it) ? I'm afraid I'm not a wiki-expert so could you explain how it's "clearly misleading from Wikipedia's policies" and how the policies of Wikipedia are relevant to elinux.org ?
* Is the [[RPi Model Wizard]] a joke? Currently there's only one model available to buy... (and even if there ''were'' two models on sale, the "wizard" seems pretty pointless IMHO)
[[User:AndrewS|AndrewS]] 00:37, 24 October 2012 (UTC)

Hope you don't mind me adding further comments here...<br>
Something else that it might be nice for the "wiki council" to clean up, is that there are several orphaned RPi-related pages (see [http://elinux.org/index.php?title=Special:LonelyPages&limit=50&offset=100 here]) so I guess it would be nice if either i) links were added back to those pages or ii) the content from those pages is moved/edited to more appropriate/relevant pages or iii) those pages are marked as "redundant info, please delete" or something ?
[[User:AndrewS|AndrewS]] 01:45, 30 October 2012 (UTC)
:Thank you for the info. w.r.t. orphaned pages. I'm still finding my way around here myself, but, being retired, I have more time to deal with such issues than, maybe, Jeff has. (That is, when I'm not trying things out etc. with my raspbery pi boxes). I'll take a look at them as soon as I get the chance. --[[User:TrevorGowen|TrevorGowen]] 14:40, 30 October 2012 (UTC)

I am really bothered by the nonsense at the top of the hub page. The "model wizard" and following pages are quite absurd, and even if they weren't, they don't belong there. Is anybody opposed to removing this content or at least moving it?
[[User:HBrydon|HBrydon]] 22:40 23 Feb 2013 (UTC)
: You have my support, but I suspect "Jeff" will object :-/ I personally think this whole "wiki council" (and it's claim of authority, coupled with lack of action) is absurd too. I added some (personal) comments to [[User_talk:Zootboy]] which in hindsight I should probably have added here. [[User:AndrewS|AndrewS]] ([[User talk:AndrewS|talk]]) 13:00, 24 February 2013 (UTC)

RPi schematic errata

2013-02-22T05:17:51Z

AndrewS: /* Unverified typos */ updated information re: the components fitted to ModelA boards

[[Category: RaspberryPi]]

Back to [[RPi_Hardware#Components]]

= Raspberry Pi schematic errata =

The schematic 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]

It has a couple of typos. Some more serious than others.

Let's gather those schematic typos and errors here.

The quality of the schematic is high. It looks like it contains the information that designers need.

==Schematic v1.0==

===Unverified typos===

* On sheet 3, area C9, should that not be a (B) instead of (A) under the “IC3?”
* Also D10 close by
* R22,23,24,25 & C28 all missing (B) designation
* Also on sheet 3: R38 (area B8), R28 (area H5), C49 (area A1) and C29 (area A2) also appear to be missing (B) designation
* [[RPi_Hardware#Components]] says that D5 is yellow, but the schematic says D5 is green. Could somebody who actually has a production board check? -> The OK led is definitively GREEN. -- REW.
* Sheet 4 D6: DSI0 should be DSI1

* there is an extra line drawn across R22-R25. ''(I think this might just be a display artefact in some PDF readers)''

===Verified typos===

* 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 "10M" rather than "100M" ? -> YES it is marked 10M due to space constraints. 100M wouldn't have fit. -- REW <ref>http://www.raspberrypi.org/forum/troubleshooting/ethernet-10m-only</ref>
As of revision 2 boards the marking has changed to simply read "100".

==Schematic v2.0==

===Unverified typos===

The [http://www.raspberrypi.org/wp-content/uploads/2012/10/Raspberry-Pi-R2.0-Schematics-Issue2.2_027.pdf schematic] for [http://www.raspberrypi.org/archives/2233 revision 2.0] Raspberry Pi boards seems to fix all of the unverified typos listed above, with one exception:
* C49 (area A1) appears to be missing (B) designation

''Update 22nd-Feb-2013:'' I've just checked on a production Revision2.0 Model A board, and the C49 capacitor '''is''' still present, so it looks like there ''isn't'' a mistake in the Rev2.0 schematics after all (unless this mistake got accidentally carried all the way through into production!?)

=References=
<references/>

RaspberryPi Boards

2013-02-22T04:42:42Z

AndrewS: Added my Revision2.0 ModelB board (Made in the UK)

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following table tries to help you identify your board for better troubleshooting.
These differences are being debated on raspberrypi.org on this thread [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9524&start=25]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

Note: For '''Board ver.''' we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")
Look for the date of manufacturing printed with the year and week (back side, board edge near LAN connector). In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

'''Model A:'''
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! C6
! F1 / F2
Ref. & Ohm
! RG2
! Reported issues / Feedback
! Front
! Back
! Distributor
! Owner
|-
| AS1245
| Samsung <pre>225
K4P2G324ED-AGC1
GAC0288J</pre>
| N/A
| <pre>220
CFP
20N</pre>
| N/A
| <pre>17-33G
RQB44</pre>
|
* None
|
|
| RS
| [[User:AndrewS|AndrewS]]
|}

'''Model B:'''
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! C6
! F1 / F2
Ref. & Ohm
! RG2
! Reported issues / Feedback
! Front
! Back
! Distributor
! Owner
|-
| BS1215
| Samsung
| SMSC
| <pre>220
16V
EEZ</pre>
| ?
? / ?
|
|
* None
|
|
| Farnell
| SN
|-
| BS1215
| Samsung
| SMSC
| <pre>n2
220
UD</pre>
| ?
? / ?
|
|
* None
|
|
| Farnell
| SN
|-
| BS1215
| Samsung <pre>216
K4P2G324ED-AGC1
GA30419V</pre>
| SMSC <pre>LAN9512-JZX
B1211-A1B17
BR149884A
CTI-TW</pre>
| <pre>n2
220C
UD</pre>
| 14
? / ?
| <pre>SE8117733
943-1F</pre>
|
* None
|
|
| Farnell
| [[User:AndrewS|AndrewS]]
|-
| BS1301
| Samsung <pre>301
K4P4G32F4EB-AGC1
GKL438GHU
(512MB version)</pre>
| SMSC <pre>
LAN9512-JZX
81244-A1817
BR1525858
CTI-TW</pre>
| <pre>220
CFP
28D</pre>
| N/A
| <pre>17-33G
RQB44</pre>
|
* None
|
|
| Farnell
| [[User:AndrewS|AndrewS]]
|-
| BS1218
| Samsung<pre>216
K4P2G324ED-AGC1
GAL0839V</pre>
| SMSC<pre>
LAN9512-JZX
B1212-A1B17
BR149884S</pre>
| <pre>220
16V
EE5</pre>
| T014
3.8 / 4.4
| <pre>SE8117T33
1213-LF</pre>
|
* None
| [[File:RaspberryPi-Board_A-Front.JPG|100px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|100px|thumb|center]]
| Farnell
| marcoalexcampos
|-
| BS1218
| Samsung<pre>216
K4P2G324ED-AGC1
GAJ0419C</pre>
| SMSC<pre>
LAN9512-JZX
B1212-A1B17
BR149884S</pre>
| <pre>220
16V
EE5</pre>
| T014
5.8 / 3.9
| <pre>SE8117T33
1213-LF</pre>
|
* None
| [[File:Antijn_raspi_farnell_top.jpg|100px|thumb|center]]
| [[File:Antijn_raspi_farnell_bot.jpg|100px|thumb|center]]
| Farnell
| antijn
|-
| BS1218
| Samsung
| ?
| <pre></pre>
| ?
? / ?
|
|
* None
| [[File:RaspberryPi-BS1218-Front-JakeBlues.jpg|100px|thumb|center]]
| [[File:RaspberryPi-BS1218-Back-JakeBlues.jpg|100px|thumb|center]]
| Farnell
| JakeBlues
|-

| BH1208
| Hynix <pre>
H9TKNNN2GDMP
LANDM 149A
</pre>
| SMSC<pre>
LAN9512-JZX
B1134-A1B17
8R147769B
STA-SG
</pre>
| <pre>220
16V
EE2</pre>
| 14
| <pre>
SE8117T33
1001-LF</pre>
|
* No issues after getting a good power supply
* Note the SMSC is 8R149482C which I suspect is the same for the others.
* Ethernet: LU1S041ALF 1018M
| [[File:RaspberryPi-BS1208-Front-MarkBeckett.JPG|100px|thumb|center]]
| [[File:RaspberryPi-BS1208-Back-MarkBeckett.JPG|100px|thumb|center]]
| Farnell
| MarkBeckett
|-

| BH1219
| Hynix <pre>
H9TKNNN2GDMP
LANDM 218A
</pre>
| SMSC<pre>
LAN9512-JZX
B1206-A1B17
8R149471A
CTI-TW
</pre>
| <pre>220
16V
2E2</pre>
| T014
| <pre>
SE8117T33
1217-LF</pre>
|
* No issues
* Ethernet: HanRun HR901110A 1220
| [[File:RaspberryPI_1219_RS_Pi_1_MCB1.JPG|100px|thumb|center]]
| [[File:RaspberryPI_1219_RS_Pi_2_MCB1.JPG|100px|thumb|center]]
| RS
| MarkBeckett
|-
| BH1218
| Hynix <pre>H9TKNNN2GDMP
LRNOM 217A</pre>
| SMSC<pre>
LAN9512-JZX
B1215-A1B17
BR1501888</pre>
| <pre>2E
220
16H</pre>
| 14
6.4 / 5.0
| <pre>SE8117T33
1213-LF</pre>
|
* USB/Keyboard/LAN issues
| [[File:Antijn_raspi_RS_top.jpg|100px|thumb|center]]
| [[File:Antijn_raspi_RS_bot.jpg|100px|thumb|center]]
| RS
| antijn
|-
| BH1218
| Hynix <pre>
H9TKNNN2GDMP
LRNDM 217A</pre>
| SMSC<pre>
LAN9512-JZX
B1215-A1817
BR1494828</pre>
| <pre>2E
220
16H</pre>
| 14
6.1 / 5.6
| <pre>
SE8117T33
1213-LF</pre>
|
* "I haven't had any issues"[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9524&start=50]
* Ethernet HR901110A 1211
* E2112RSV1.0B1.1
|
|
| RS
| dukla2000
|-
| BS1219
| Samsung
| SMSC
| <pre>2E
220
16H
</pre>
| T014
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* None
| [[File:RaspberryPi-A1219-Front.jpg|100px|thumb|center]]
| [[File:RaspberryPi-A1219-Back.jpg|100px|thumb|center]]
| Farnell
| Troublesome
|-
| BH1208
| Hynix
| SMSC
| <pre>220
16V
EE2</pre>
| 14
? / ?
| ?
|
* None
| [[File:Raspberry-pi-top.jpg|100px|thumb|center]]
| [[File:Raspberry-pi-bottom.jpg|100px|thumb|center]]
| Farnell
| selsinork
|-
| BH1213
| Hynix
| SMSC
| <pre>n2
220c
UD</pre>
| 14
? / ?
| <blank>
|
* None
| [[File:RaspberryPi-Board_C-Front.jpg|100px|thumb|center]]
| [[File:RaspberryPi-Board_C-Back.jpg|100px|thumb|center]]
| RS
|
|-
| BH1213
| Hynix
<pre>h9tknnn2c0mp
landm 1494</pre>
| SMSC
<pre>lan9512-jzx
b1134 a1b17 8r14
77698
sta-sg</pre>
| <pre>n2
220c
UD</pre>
| 14
? / ?
| <blank>
|
* "pretty stable"
| [[File:RaspberryPi-B1213-Front-RaTTuS.jpg|100px|thumb|center]]
| [[File:RaspberryPi-B1213-Back-RaTTuS.jpg|100px|thumb|center]]
| Farnell
| RaTTuS
|-
| BS12xx
| Samsung
<pre>216 k4p
26324ED
agc1</pre>
| SMSC
<pre>lan9512-jzx
b1212 a1b17
br149884b
cti-tw</pre>
| <pre>220
16V
EE5</pre>
| ?
? / ?
|
|
* OK "has not been stress tested yet"
|
|
| Farnell
| RaTTuS
|-
| BH1218
| Hynix
<pre>h9trnnn2g0mp
lrndm 217a</pre>
| SMSC
<pre>lan9512-jzy
b1215-a1b17
ase-tw</pre>
| <pre>2e
220
16h</pre>
| 14
? / ?
| <pre>Se8117t33
12-13 cf</pre>
|
* "stable good runner overclocked to 900mhz"
| [[File:RaspberryPi-B1218-Front-RaTTuS.jpg|100px|thumb|center]]
| [[File:RaspberryPi-B1218-Back-RaTTuS.jpg|100px|thumb|center]]
| RS
| RaTTuS
|-
| BH1218
| Hynix
| SMSC<pre>
LAN9512-JZX
B1215-A1B17
BR150188A
ASE-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 14
8.2 / 5.9
| <pre>SE8117T33
1213-LF</pre>
|
* USB/Keyboard/LAN power down[http://www.raspberrypi.org/phpBB3/viewtopic.php?p=109984#p109984]
*
| [[File:RaspberryPi-Board_B-Front.JPG|100px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|100px|thumb|center]]
| RS
| marcoalexcampos
|-
| BH1218
| Hynix
| SMSC
| <pre>2B
220
16H</pre>
| ?
6-7 / 6-7
|
|
* None
|
|
| RS
| SN
|-
| BH1218
| Hynix
| SMSC
| <pre>2B
220
16H</pre>
| ?
? / ?
|
|
* None
|
|
| RS
|
|-
| BH1218
| Hynix
| SMSC
| <pre>2E
220
16H</pre>
| F014
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* None
| [[File:RaspberryPi-B1218-Front.jpg|100px|thumb|center]]
| [[File:RaspberryPi-B1218-Back.jpg|100px|thumb|center]]
| RS
| Troublesome
|-
| BH1218
| Hynix <pre>H9TKNNN2GDMP
LANDM 217A</pre>
| SMSC
<pre>LAN9512-JZX
B1215-A1B17
BR150188B
ASE-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 14
6.9 / 5.9
| <pre>SE8117T33
1213-LF</pre>
|
* None
|[[File:RPi1T.jpg|100px|thumb|center]]
|[[File:RPi1B.jpg|100px|thumb|center]]
| RS
| Mortimer
|-
| BH1218
| Hynix <pre>H9TKNNN2GDMP
LANDM 218A</pre>
| SMSC
<pre>LAN9512-JZX
B1215-A1B17
BR150188A
ASE-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 14
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* None
|[[File:RPi2T.jpg|100px|thumb|center]]
|[[File:RPi2B.jpg|100px|thumb|center]]
| RS
| Mortimer
|-
| BH1218
| Hynix
<pre>
H9TKNNN2GDMP
LRNOM 217A
</pre>
| SMSC
<pre>
LAN9512-JZX
B1215-A1B17
8R150188B
ASE-TW (e3)
</pre>
| <pre>2E
22-
16H</pre>
| 14
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* D1 shorted when attaching a Neewer HDMI to VGA adapter. The adapter has had no other tests and the raspberry pi's HDMI output has not been connected to any other devices before or since.
| [[File:RaspberryPi-BH1218-Front-Tom1989.jpg|100px|thumb|center]]
| [[File:RaspberryPi-BH1218-Back-Tom1989.jpg|100px|thumb|center]]
| RS
| Tom1989
|-
| BH1208
| Hynix <pre>H9TKNNN2GDMP
LANDM 149A</pre>
| SMSC
<pre>LAN9512-JZX
B1134-A1B17
BR147769B
STA-SG</pre>
| <pre>220
16V
EE2</pre>
| ?
? / ?
| <pre>SE8117T33
1001-LF</pre>
|
* Stable, powers up off any charger. Powers off laptop USB without any issues
* Ethernet: LU1S041ALF 1018M
|
|
| Farnell
| Tass
|-
| BH1213
| Hynix <pre>H9TKNNN2GDMP
LANDM 149A</pre>
| SMSC
<pre>LAN9512-JZX
B1134-A1B17
BR147769B
STA-SG</pre>
| <pre>n2
220C
UD</pre>
| ?
? / ?
| <pre>SE8117T33
943-LF</pre>
|
* Stable, no power issues (not thouroughly tested)
* Ethernet: HR901110A 1211|
|
|
| RS
| Tass
|-
| BH1218
| Hynix <pre>H9TKNNN2GDMP
LANDM 217A</pre>
| SMSC
<pre>LAN9512-JZX
B1216-A1B17
8R149482C
ASE-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 14
14 / 5.1
| <pre>SE8117T33
1213-LF</pre>
|
* Up headless with Squeeze and Wheezy for ~six weeks, light duty, no problems
* Ethernet: HR901110A 1211
|[[File:Rpi001F.jpg|100px|thumb|center]]
|[[File:Rpi001R.jpg|100px|thumb|center]]
| RS
| Davidm870
|-
| BS1218
| Samsung <pre>216
K42P2G324ED-AGG1
GAL0839T</pre>
| SMSC
<pre>LAN9512-JZX
B1212-A1B17
8R149885A
ASE-TW (e3)</pre>
| <pre>220
16V
EE5</pre>
| T014
T014 / ?
| <pre>SE8117T33
1213-LF</pre>
|
* Comes upp headless with Wheezy, not tested extensively
* Ethernet: HR901110A 1218
|[[File:Rpi002F.jpg|100px|thumb|center]]
|[[File:Rpi002R.jpg|100px|thumb|center]]
| Farnell
| Davidm870
|-
| BS1219
| Samsung <pre>216
K4P2G324ED-AGC1
GAL0859V</pre>
| SMSC
<pre>LAN9512-JZX
B1216-A1B17
8R149482C
ASE-TW (e3)</pre>
| <pre>2E
220
16H
</pre>
| T014
2.9ohm / 3.0ohm
| <pre>SE8117T33
0941-LF</pre>
|
* First had problems (freezing, no LAN, etc.) due to low quality power supply - cheap ebay adaptor. Solved with own [[RPi_5V_PSU_construction| PSU construction]] with 7805 stabiliser adjusted to 5.25V. Now works OK with Raspbian “wheezy”, but not yet tested extensively.
* Ethernet: HR901110A 1220
* F3 0.3ohm
| [[File:RPi-BS1219-Front_Pinoccio.jpg|100px|thumb|center]]
| [[File:RPi-BS1219-Back_Pinoccio.jpg|100px|thumb|center]]
| Farnell
| [[User:Pinoccio|Pinoccio]]
|-
| BS1219
| Samsung <pre>216
K4P2G324ED-AGC1
GAL0859D</pre>
| SMSC
<pre>LAN9512-JZX
B1216-A1B17
8R149482C
ASE-TW (e3)</pre>
| <pre>2E
220
16H
</pre>
| T014 / T014
? / ?
| <pre>SE8117T33
0941-LF</pre>
|
* No issues
* Ethernet: HanRun HR901110A 1220
* FN120659744
| [[File:RPi-BS1219-Front_slabua.jpg|100px|thumb|center]]
| [[File:RPi-BS1219-Back_slabua.jpg|100px|thumb|center]]
| Farnell
| [SLB] [http://twitter.com/slabua @slabua]
|-
| BH1222
| Hynix <pre>H9TKNNN2GDMP
LANDM 214A</pre>
| SMSC
<pre>LAN9512-JZX
B1215-A1B17
8R148168E
ASE-TW (e3)</pre>
| <pre>2E
220
16H
</pre>
| T014 / T014
? / ?
| <pre>SE8117T33
1217-LF</pre>
|
* No issues
* Ethernet: HanRun HR901110A 1225
* E2712RSV1.0B1.1
| [[File:RPi-BH1222-Front_slabua.jpg|100px|thumb|center]]
| [[File:RPi-BH1222-Back_slabua.jpg|100px|thumb|center]]
| RS
| [SLB] [http://twitter.com/slabua @slabua]
|-
| BS1224
| Samsung <pre>222
K4P2G324ED-AGC1
GAA0419T</pre>
| SMSC
<pre>LAN9512-JZX
B1222-A1B17
8R150543C
CTI-TW (e3)</pre>
| <pre>2F
220
16H
</pre>
| T014 / T014
? / ?
| <pre>SE8117T33
1217-LF</pre>
|
* Ethernet: HanRun HR901110A 1225
|
|
| Farnell
| accumulator
|-
| BS1224
| Samsung <pre>222
K4P2G324ED-AGC1
GAA0519H</pre>
| SMSC
<pre>LAN9512-JZX
B1223-A1B17
8R15D81DA
CTI-TW (e3)</pre>
| <pre>2F
220
16H
</pre>
| 0000 / 0000
0 / 0
| <pre>SE8117T33
1220-LF</pre>
|
* Ethernet: HanRun HR901110A 1225
* No Issues
* Note: F1 and F2 are black 0 ohm resistors instead of green polyfuses
| [[File:RPi-BS1224-Front_Shuckle.jpg|100px|thumb|center]]
|
| Farnell
| shuckle
|-
| BS1218
| Samsung<pre>216
K4P2G324ED-AGC1
GAL0839R</pre>
| SMSC<pre>
LAN9512-JZX
B1215-A1B17
8R150188B
ASE-TW
(e3)</pre>
| <pre>2E
220
16H
</pre>
| F014
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* None
|
|
| Farnell
| d4lamar
|-
| BS1222
| Samsung <pre>225
K4P2G324ED-AGC1
GAC0289E</pre>
| SMSC
<pre>LAN9512-JZX
B1227-A1B17
8R1511968
CTI-TW (e3)</pre>
| <pre>2F
220
16H
</pre>
| 0000 / 0000
0 / 0
| <pre>SE8117T33
1217-LF</pre>
|
* Ethernet: HanRun HR901110A 1228
* Both boards by wcfields ordered at the same time/date.
* Note: F1 and F2 are black 0 ohm resistors instead of green polyfuses
|
|
| MCM
| wcfields
|-
| BS1232
| Samsung <pre>225
K4P2G324ED-AGC1
GAC0289H</pre>
| SMSC
<pre>LAN9512-JZX
B1227-A1B17
8R151261A
CTI-TW (e3)</pre>
| <pre>2F
220
16H
</pre>
| 0000 / 0000
0 / 0
| <pre>SE8117T33
1225-LF</pre>
|
* Ethernet: HanRun HR901110A 1228
* Both boards by wcfields ordered at the same time/date.
* Note: F1 and F2 are black 0 ohm resistors instead of green polyfuses
|
|
| MCM
| wcfields
|-
| BS1228
| Samsung <pre>234
K4P2G324ED-AGC1
GAK1229X</pre>
| SMSC
<pre>LAN9512-JZX
B1228-A1B17
8R151303B
CTI-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 0000 / 0000
? / ?
| <pre>SE8117T33
1220-LF</pre>
|
* Serious problems with the 4GB SDHC-Card ordered with the board on initial testing with Gentoo (corrupted FS)
* Same issues using rasbian and two different supported SD cards
* Using RS original power adapter
|
|
| RC
| FKlama
|-
| BS1233
| Samsung <pre>231
K4P4G324EB-AGC1
GKG0609V
(512MB version)</pre>
| SMSC
<pre>LAN9512-JZX
B1227-A1B17
8R151261A
CTI-TW (e3)</pre>
| <pre>2E
220
CFP
2G6</pre>
| None / None
? / ?
| <pre>17-33G
RRB32 (ON)</pre>
|
-Ethernet Jack: No visible branding
-PS: 500mA Mobile phone charger & USB Port on Laptop and Desktop (These are all I had). Works with blackberry 8520 550mA charger.
-Fuse(s): ONLY seems to have green polyswitch (F3) on bottom side of board F1 and F2 don't exist
-In the position of the (other fuses) there is a mounting hole, likewise there is also a mounting hole under the Raspberry Pi Logo.

-There is also an extra header (P5) defined on the bottom side of the PCB near P1 (which is on the top side)
-Won't boot with a known working (This same card will boot on BS1215 ) Kingston 4GB Class 4 SD Card, Raspbian "wheezy" 2012-09-18.
-When using raspbmc powered with 550ma blackberry 8520 charger, keyboard and mouse disconnects frequently also external hard drive unmounts frequently.
-When using torrents and connected with usb wireless adapter (tested with Netgear WNA1000M), when torrent picks up speed, raspbian becomes unstable. Same works well over Ethernet.
-The unit WILL boot from the SD card bought from Element 14.
-Will add more when I know more.
|
|
| Farnell/Element14 (AU)
| TheSteveB
|-
| BS1236
| Samsung <pre>225
K4P46324EB-AGC1
GKEM509X
(512MB version)</pre>
| SMSC
<pre>LAN9512-JZX
B1232-A1B17
8R151680A
CTI-TW (e3)</pre>
| <pre>2F
220
16H</pre>
| None / None
? / ?
| <pre>SE8117T33
1225-LF</pre>
|
*Ethernet Jack: HanRun HT901110A 1228
*Seems to randomly power off on 3 different PS's (650mA, 900mA and 1A) (http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=22353)
*Extra header, F1, F2 and F3 and mounting holes just like BS1233
|
|
|RS
|Yaron
|-
| BS1238
| Samsung <pre>225
K4P4G324EB-AGC1
GKFX1390
(512MB version)</pre>
| SMSC
<pre>LAN9512-JZX
B1232-A1B17
8R151549A
CTI-TW (e3)</pre>
| <pre>2H
220
16H</pre>
| None / None
? / ?
| <pre>SE8117T33
1225-LF</pre>
|
*Ethernet Jack: HanRun HR901110A 1230
*With extra header P5, missing fuses F1 and F2, and with mounting holes just like BS1233
*Weird stability problems. Can build Quake3, and can play it for a little while, but eventually locks up (black screen, loses ethernet link). Putting it in the Adafruit case seems to exacerbate the problem.
*Highest temp measured by <code>vcgencmd measure_temp</code> is 53.5C. Last measured temp before lockup was 53.0C
*Problem occurs with both the Adafruit power supply as well as my Nexus 7 2A supply.
*Tested with at least 3 different Micro-USB cables.
*Tested with the 4GB Dane-Elec Class 4 MicroSD card from Adafruit, as well as an 8GB Class 10 SanDisk full-size SD card.
*Voltages:
**Idle, with HDMI only
***5.06V (polyfuse in)
***4.82V (polyfuse out)
**Idle, with HDMI, keyboard and mouse
***5.04V (polyfuse in)
***4.77V (polyfuse out)
**Running Quake (with HDMI, keyboard, mouse, and network)
***4.98V (polyfuse in)
***4.55V (polyfuse out)
|
|
|Adafruit (US)
|Balefrost
|-}

RaspberryPi Boards

2013-02-22T04:24:48Z

AndrewS: /* Hardware versions/revisions */ Added details of my ModelA board (the first on the page!)

==Hardware versions/revisions==
Several different boards have been found probably from different assembly lines, and the following table tries to help you identify your board for better troubleshooting.
These differences are being debated on raspberrypi.org on this thread [http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9524&start=25]

For what we can see for model B boards there are mainly two versions that differ on the type RAM used, Samsung (S) and Hynix (H).

Note: For '''Board ver.''' we used: <model><RAM Maker><production date> (ex.: BS1218 is "Model B, Samsung RAM, 18th week of 2012")
Look for the date of manufacturing printed with the year and week (back side, board edge near LAN connector). In this example year (2012) and week (18th):[[File:Date_of_manufacturing.jpg|200px|thumb|right]]

'''Model A:'''
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! C6
! F1 / F2
Ref. & Ohm
! RG2
! Reported issues / Feedback
! Front
! Back
! Distributor
! Owner
|-
| AS1245
| Samsung <pre>225
K4P2G324ED-AGC1
GAC0288J</pre>
| N/A
| <pre>220
CFP
20N</pre>
| N/A
| <pre>17-33G
RQB44</pre>
| * None
|
|
| RS
| [[User:AndrewS|AndrewS]]
|}

'''Model B:'''
{| border="1" class="wikitable"
|-
! Board
ver.
! RAM
Chip
! USB
Chip
! C6
! F1 / F2
Ref. & Ohm
! RG2
! Reported issues / Feedback
! Front
! Back
! Distributor
! Owner
|-
| BS1215
| Samsung
| SMSC
| <pre>220
16V
EEZ</pre>
| ?
? / ?
|
|
* None
|
|
| Farnell
| SN
|-
| BS1215
| Samsung
| SMSC
| <pre>n2
220
UD</pre>
| ?
? / ?
|
|
* None
|
|
| Farnell
| SN
|-
| BS1215
| Samsung <pre>216
K4P2G324ED-AGC1
GA30419V</pre>
| SMSC <pre>LAN9512-JZX
B1211-A1B17
BR149884A
CTI-TW</pre>
| <pre>n2
220C
UD</pre>
| 14
? / ?
| <pre>SE8117733
943-1F</pre>
|
* None
|
|
| Farnell
| AndrewS
|-
| BS1218
| Samsung<pre>216
K4P2G324ED-AGC1
GAL0839V</pre>
| SMSC<pre>
LAN9512-JZX
B1212-A1B17
BR149884S</pre>
| <pre>220
16V
EE5</pre>
| T014
3.8 / 4.4
| <pre>SE8117T33
1213-LF</pre>
|
* None
| [[File:RaspberryPi-Board_A-Front.JPG|100px|thumb|center]]
| [[File:RaspberryPi-Board_A-Back.JPG|100px|thumb|center]]
| Farnell
| marcoalexcampos
|-
| BS1218
| Samsung<pre>216
K4P2G324ED-AGC1
GAJ0419C</pre>
| SMSC<pre>
LAN9512-JZX
B1212-A1B17
BR149884S</pre>
| <pre>220
16V
EE5</pre>
| T014
5.8 / 3.9
| <pre>SE8117T33
1213-LF</pre>
|
* None
| [[File:Antijn_raspi_farnell_top.jpg|100px|thumb|center]]
| [[File:Antijn_raspi_farnell_bot.jpg|100px|thumb|center]]
| Farnell
| antijn
|-
| BS1218
| Samsung
| ?
| <pre></pre>
| ?
? / ?
|
|
* None
| [[File:RaspberryPi-BS1218-Front-JakeBlues.jpg|100px|thumb|center]]
| [[File:RaspberryPi-BS1218-Back-JakeBlues.jpg|100px|thumb|center]]
| Farnell
| JakeBlues
|-

| BH1208
| Hynix <pre>
H9TKNNN2GDMP
LANDM 149A
</pre>
| SMSC<pre>
LAN9512-JZX
B1134-A1B17
8R147769B
STA-SG
</pre>
| <pre>220
16V
EE2</pre>
| 14
| <pre>
SE8117T33
1001-LF</pre>
|
* No issues after getting a good power supply
* Note the SMSC is 8R149482C which I suspect is the same for the others.
* Ethernet: LU1S041ALF 1018M
| [[File:RaspberryPi-BS1208-Front-MarkBeckett.JPG|100px|thumb|center]]
| [[File:RaspberryPi-BS1208-Back-MarkBeckett.JPG|100px|thumb|center]]
| Farnell
| MarkBeckett
|-

| BH1219
| Hynix <pre>
H9TKNNN2GDMP
LANDM 218A
</pre>
| SMSC<pre>
LAN9512-JZX
B1206-A1B17
8R149471A
CTI-TW
</pre>
| <pre>220
16V
2E2</pre>
| T014
| <pre>
SE8117T33
1217-LF</pre>
|
* No issues
* Ethernet: HanRun HR901110A 1220
| [[File:RaspberryPI_1219_RS_Pi_1_MCB1.JPG|100px|thumb|center]]
| [[File:RaspberryPI_1219_RS_Pi_2_MCB1.JPG|100px|thumb|center]]
| RS
| MarkBeckett
|-
| BH1218
| Hynix <pre>H9TKNNN2GDMP
LRNOM 217A</pre>
| SMSC<pre>
LAN9512-JZX
B1215-A1B17
BR1501888</pre>
| <pre>2E
220
16H</pre>
| 14
6.4 / 5.0
| <pre>SE8117T33
1213-LF</pre>
|
* USB/Keyboard/LAN issues
| [[File:Antijn_raspi_RS_top.jpg|100px|thumb|center]]
| [[File:Antijn_raspi_RS_bot.jpg|100px|thumb|center]]
| RS
| antijn
|-
| BH1218
| Hynix <pre>
H9TKNNN2GDMP
LRNDM 217A</pre>
| SMSC<pre>
LAN9512-JZX
B1215-A1817
BR1494828</pre>
| <pre>2E
220
16H</pre>
| 14
6.1 / 5.6
| <pre>
SE8117T33
1213-LF</pre>
|
* "I haven't had any issues"[http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=9524&start=50]
* Ethernet HR901110A 1211
* E2112RSV1.0B1.1
|
|
| RS
| dukla2000
|-
| BS1219
| Samsung
| SMSC
| <pre>2E
220
16H
</pre>
| T014
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* None
| [[File:RaspberryPi-A1219-Front.jpg|100px|thumb|center]]
| [[File:RaspberryPi-A1219-Back.jpg|100px|thumb|center]]
| Farnell
| Troublesome
|-
| BH1208
| Hynix
| SMSC
| <pre>220
16V
EE2</pre>
| 14
? / ?
| ?
|
* None
| [[File:Raspberry-pi-top.jpg|100px|thumb|center]]
| [[File:Raspberry-pi-bottom.jpg|100px|thumb|center]]
| Farnell
| selsinork
|-
| BH1213
| Hynix
| SMSC
| <pre>n2
220c
UD</pre>
| 14
? / ?
| <blank>
|
* None
| [[File:RaspberryPi-Board_C-Front.jpg|100px|thumb|center]]
| [[File:RaspberryPi-Board_C-Back.jpg|100px|thumb|center]]
| RS
|
|-
| BH1213
| Hynix
<pre>h9tknnn2c0mp
landm 1494</pre>
| SMSC
<pre>lan9512-jzx
b1134 a1b17 8r14
77698
sta-sg</pre>
| <pre>n2
220c
UD</pre>
| 14
? / ?
| <blank>
|
* "pretty stable"
| [[File:RaspberryPi-B1213-Front-RaTTuS.jpg|100px|thumb|center]]
| [[File:RaspberryPi-B1213-Back-RaTTuS.jpg|100px|thumb|center]]
| Farnell
| RaTTuS
|-
| BS12xx
| Samsung
<pre>216 k4p
26324ED
agc1</pre>
| SMSC
<pre>lan9512-jzx
b1212 a1b17
br149884b
cti-tw</pre>
| <pre>220
16V
EE5</pre>
| ?
? / ?
|
|
* OK "has not been stress tested yet"
|
|
| Farnell
| RaTTuS
|-
| BH1218
| Hynix
<pre>h9trnnn2g0mp
lrndm 217a</pre>
| SMSC
<pre>lan9512-jzy
b1215-a1b17
ase-tw</pre>
| <pre>2e
220
16h</pre>
| 14
? / ?
| <pre>Se8117t33
12-13 cf</pre>
|
* "stable good runner overclocked to 900mhz"
| [[File:RaspberryPi-B1218-Front-RaTTuS.jpg|100px|thumb|center]]
| [[File:RaspberryPi-B1218-Back-RaTTuS.jpg|100px|thumb|center]]
| RS
| RaTTuS
|-
| BH1218
| Hynix
| SMSC<pre>
LAN9512-JZX
B1215-A1B17
BR150188A
ASE-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 14
8.2 / 5.9
| <pre>SE8117T33
1213-LF</pre>
|
* USB/Keyboard/LAN power down[http://www.raspberrypi.org/phpBB3/viewtopic.php?p=109984#p109984]
*
| [[File:RaspberryPi-Board_B-Front.JPG|100px|thumb|center]]
| [[File:RaspberryPi-Board_B-Back.JPG|100px|thumb|center]]
| RS
| marcoalexcampos
|-
| BH1218
| Hynix
| SMSC
| <pre>2B
220
16H</pre>
| ?
6-7 / 6-7
|
|
* None
|
|
| RS
| SN
|-
| BH1218
| Hynix
| SMSC
| <pre>2B
220
16H</pre>
| ?
? / ?
|
|
* None
|
|
| RS
|
|-
| BH1218
| Hynix
| SMSC
| <pre>2E
220
16H</pre>
| F014
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* None
| [[File:RaspberryPi-B1218-Front.jpg|100px|thumb|center]]
| [[File:RaspberryPi-B1218-Back.jpg|100px|thumb|center]]
| RS
| Troublesome
|-
| BH1218
| Hynix <pre>H9TKNNN2GDMP
LANDM 217A</pre>
| SMSC
<pre>LAN9512-JZX
B1215-A1B17
BR150188B
ASE-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 14
6.9 / 5.9
| <pre>SE8117T33
1213-LF</pre>
|
* None
|[[File:RPi1T.jpg|100px|thumb|center]]
|[[File:RPi1B.jpg|100px|thumb|center]]
| RS
| Mortimer
|-
| BH1218
| Hynix <pre>H9TKNNN2GDMP
LANDM 218A</pre>
| SMSC
<pre>LAN9512-JZX
B1215-A1B17
BR150188A
ASE-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 14
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* None
|[[File:RPi2T.jpg|100px|thumb|center]]
|[[File:RPi2B.jpg|100px|thumb|center]]
| RS
| Mortimer
|-
| BH1218
| Hynix
<pre>
H9TKNNN2GDMP
LRNOM 217A
</pre>
| SMSC
<pre>
LAN9512-JZX
B1215-A1B17
8R150188B
ASE-TW (e3)
</pre>
| <pre>2E
22-
16H</pre>
| 14
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* D1 shorted when attaching a Neewer HDMI to VGA adapter. The adapter has had no other tests and the raspberry pi's HDMI output has not been connected to any other devices before or since.
| [[File:RaspberryPi-BH1218-Front-Tom1989.jpg|100px|thumb|center]]
| [[File:RaspberryPi-BH1218-Back-Tom1989.jpg|100px|thumb|center]]
| RS
| Tom1989
|-
| BH1208
| Hynix <pre>H9TKNNN2GDMP
LANDM 149A</pre>
| SMSC
<pre>LAN9512-JZX
B1134-A1B17
BR147769B
STA-SG</pre>
| <pre>220
16V
EE2</pre>
| ?
? / ?
| <pre>SE8117T33
1001-LF</pre>
|
* Stable, powers up off any charger. Powers off laptop USB without any issues
* Ethernet: LU1S041ALF 1018M
|
|
| Farnell
| Tass
|-
| BH1213
| Hynix <pre>H9TKNNN2GDMP
LANDM 149A</pre>
| SMSC
<pre>LAN9512-JZX
B1134-A1B17
BR147769B
STA-SG</pre>
| <pre>n2
220C
UD</pre>
| ?
? / ?
| <pre>SE8117T33
943-LF</pre>
|
* Stable, no power issues (not thouroughly tested)
* Ethernet: HR901110A 1211|
|
|
| RS
| Tass
|-
| BH1218
| Hynix <pre>H9TKNNN2GDMP
LANDM 217A</pre>
| SMSC
<pre>LAN9512-JZX
B1216-A1B17
8R149482C
ASE-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 14
14 / 5.1
| <pre>SE8117T33
1213-LF</pre>
|
* Up headless with Squeeze and Wheezy for ~six weeks, light duty, no problems
* Ethernet: HR901110A 1211
|[[File:Rpi001F.jpg|100px|thumb|center]]
|[[File:Rpi001R.jpg|100px|thumb|center]]
| RS
| Davidm870
|-
| BS1218
| Samsung <pre>216
K42P2G324ED-AGG1
GAL0839T</pre>
| SMSC
<pre>LAN9512-JZX
B1212-A1B17
8R149885A
ASE-TW (e3)</pre>
| <pre>220
16V
EE5</pre>
| T014
T014 / ?
| <pre>SE8117T33
1213-LF</pre>
|
* Comes upp headless with Wheezy, not tested extensively
* Ethernet: HR901110A 1218
|[[File:Rpi002F.jpg|100px|thumb|center]]
|[[File:Rpi002R.jpg|100px|thumb|center]]
| Farnell
| Davidm870
|-
| BS1219
| Samsung <pre>216
K4P2G324ED-AGC1
GAL0859V</pre>
| SMSC
<pre>LAN9512-JZX
B1216-A1B17
8R149482C
ASE-TW (e3)</pre>
| <pre>2E
220
16H
</pre>
| T014
2.9ohm / 3.0ohm
| <pre>SE8117T33
0941-LF</pre>
|
* First had problems (freezing, no LAN, etc.) due to low quality power supply - cheap ebay adaptor. Solved with own [[RPi_5V_PSU_construction| PSU construction]] with 7805 stabiliser adjusted to 5.25V. Now works OK with Raspbian “wheezy”, but not yet tested extensively.
* Ethernet: HR901110A 1220
* F3 0.3ohm
| [[File:RPi-BS1219-Front_Pinoccio.jpg|100px|thumb|center]]
| [[File:RPi-BS1219-Back_Pinoccio.jpg|100px|thumb|center]]
| Farnell
| [[User:Pinoccio|Pinoccio]]
|-
| BS1219
| Samsung <pre>216
K4P2G324ED-AGC1
GAL0859D</pre>
| SMSC
<pre>LAN9512-JZX
B1216-A1B17
8R149482C
ASE-TW (e3)</pre>
| <pre>2E
220
16H
</pre>
| T014 / T014
? / ?
| <pre>SE8117T33
0941-LF</pre>
|
* No issues
* Ethernet: HanRun HR901110A 1220
* FN120659744
| [[File:RPi-BS1219-Front_slabua.jpg|100px|thumb|center]]
| [[File:RPi-BS1219-Back_slabua.jpg|100px|thumb|center]]
| Farnell
| [SLB] [http://twitter.com/slabua @slabua]
|-
| BH1222
| Hynix <pre>H9TKNNN2GDMP
LANDM 214A</pre>
| SMSC
<pre>LAN9512-JZX
B1215-A1B17
8R148168E
ASE-TW (e3)</pre>
| <pre>2E
220
16H
</pre>
| T014 / T014
? / ?
| <pre>SE8117T33
1217-LF</pre>
|
* No issues
* Ethernet: HanRun HR901110A 1225
* E2712RSV1.0B1.1
| [[File:RPi-BH1222-Front_slabua.jpg|100px|thumb|center]]
| [[File:RPi-BH1222-Back_slabua.jpg|100px|thumb|center]]
| RS
| [SLB] [http://twitter.com/slabua @slabua]
|-
| BS1224
| Samsung <pre>222
K4P2G324ED-AGC1
GAA0419T</pre>
| SMSC
<pre>LAN9512-JZX
B1222-A1B17
8R150543C
CTI-TW (e3)</pre>
| <pre>2F
220
16H
</pre>
| T014 / T014
? / ?
| <pre>SE8117T33
1217-LF</pre>
|
* Ethernet: HanRun HR901110A 1225
|
|
| Farnell
| accumulator
|-
| BS1224
| Samsung <pre>222
K4P2G324ED-AGC1
GAA0519H</pre>
| SMSC
<pre>LAN9512-JZX
B1223-A1B17
8R15D81DA
CTI-TW (e3)</pre>
| <pre>2F
220
16H
</pre>
| 0000 / 0000
0 / 0
| <pre>SE8117T33
1220-LF</pre>
|
* Ethernet: HanRun HR901110A 1225
* No Issues
* Note: F1 and F2 are black 0 ohm resistors instead of green polyfuses
| [[File:RPi-BS1224-Front_Shuckle.jpg|100px|thumb|center]]
|
| Farnell
| shuckle
|-
| BS1218
| Samsung<pre>216
K4P2G324ED-AGC1
GAL0839R</pre>
| SMSC<pre>
LAN9512-JZX
B1215-A1B17
8R150188B
ASE-TW
(e3)</pre>
| <pre>2E
220
16H
</pre>
| F014
? / ?
| <pre>SE8117T33
1213-LF</pre>
|
* None
|
|
| Farnell
| d4lamar
|-
| BS1222
| Samsung <pre>225
K4P2G324ED-AGC1
GAC0289E</pre>
| SMSC
<pre>LAN9512-JZX
B1227-A1B17
8R1511968
CTI-TW (e3)</pre>
| <pre>2F
220
16H
</pre>
| 0000 / 0000
0 / 0
| <pre>SE8117T33
1217-LF</pre>
|
* Ethernet: HanRun HR901110A 1228
* Both boards by wcfields ordered at the same time/date.
* Note: F1 and F2 are black 0 ohm resistors instead of green polyfuses
|
|
| MCM
| wcfields
|-
| BS1232
| Samsung <pre>225
K4P2G324ED-AGC1
GAC0289H</pre>
| SMSC
<pre>LAN9512-JZX
B1227-A1B17
8R151261A
CTI-TW (e3)</pre>
| <pre>2F
220
16H
</pre>
| 0000 / 0000
0 / 0
| <pre>SE8117T33
1225-LF</pre>
|
* Ethernet: HanRun HR901110A 1228
* Both boards by wcfields ordered at the same time/date.
* Note: F1 and F2 are black 0 ohm resistors instead of green polyfuses
|
|
| MCM
| wcfields
|-
| BS1228
| Samsung <pre>234
K4P2G324ED-AGC1
GAK1229X</pre>
| SMSC
<pre>LAN9512-JZX
B1228-A1B17
8R151303B
CTI-TW (e3)</pre>
| <pre>2E
220
16H</pre>
| 0000 / 0000
? / ?
| <pre>SE8117T33
1220-LF</pre>
|
* Serious problems with the 4GB SDHC-Card ordered with the board on initial testing with Gentoo (corrupted FS)
* Same issues using rasbian and two different supported SD cards
* Using RS original power adapter
|
|
| RC
| FKlama
|-
| BS1233
| Samsung <pre>231
K4P4G324EB-AGC1
GKG0609V
(512MB version)</pre>
| SMSC
<pre>LAN9512-JZX
B1227-A1B17
8R151261A
CTI-TW (e3)</pre>
| <pre>2E
220
CFP
2G6</pre>
| None / None
? / ?
| <pre>17-33G
RRB32 (ON)</pre>
|
-Ethernet Jack: No visible branding
-PS: 500mA Mobile phone charger & USB Port on Laptop and Desktop (These are all I had). Works with blackberry 8520 550mA charger.
-Fuse(s): ONLY seems to have green polyswitch (F3) on bottom side of board F1 and F2 don't exist
-In the position of the (other fuses) there is a mounting hole, likewise there is also a mounting hole under the Raspberry Pi Logo.

-There is also an extra header (P5) defined on the bottom side of the PCB near P1 (which is on the top side)
-Won't boot with a known working (This same card will boot on BS1215 ) Kingston 4GB Class 4 SD Card, Raspbian "wheezy" 2012-09-18.
-When using raspbmc powered with 550ma blackberry 8520 charger, keyboard and mouse disconnects frequently also external hard drive unmounts frequently.
-When using torrents and connected with usb wireless adapter (tested with Netgear WNA1000M), when torrent picks up speed, raspbian becomes unstable. Same works well over Ethernet.
-The unit WILL boot from the SD card bought from Element 14.
-Will add more when I know more.
|
|
| Farnell/Element14 (AU)
| TheSteveB
|-
| BS1236
| Samsung <pre>225
K4P46324EB-AGC1
GKEM509X
(512MB version)</pre>
| SMSC
<pre>LAN9512-JZX
B1232-A1B17
8R151680A
CTI-TW (e3)</pre>
| <pre>2F
220
16H</pre>
| None / None
? / ?
| <pre>SE8117T33
1225-LF</pre>
|
*Ethernet Jack: HanRun HT901110A 1228
*Seems to randomly power off on 3 different PS's (650mA, 900mA and 1A) (http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=22353)
*Extra header, F1, F2 and F3 and mounting holes just like BS1233
|
|
|RS
|Yaron
|-
| BS1238
| Samsung <pre>225
K4P4G324EB-AGC1
GKFX1390
(512MB version)</pre>
| SMSC
<pre>LAN9512-JZX
B1232-A1B17
8R151549A
CTI-TW (e3)</pre>
| <pre>2H
220
16H</pre>
| None / None
? / ?
| <pre>SE8117T33
1225-LF</pre>
|
*Ethernet Jack: HanRun HR901110A 1230
*With extra header P5, missing fuses F1 and F2, and with mounting holes just like BS1233
*Weird stability problems. Can build Quake3, and can play it for a little while, but eventually locks up (black screen, loses ethernet link). Putting it in the Adafruit case seems to exacerbate the problem.
*Highest temp measured by <code>vcgencmd measure_temp</code> is 53.5C. Last measured temp before lockup was 53.0C
*Problem occurs with both the Adafruit power supply as well as my Nexus 7 2A supply.
*Tested with at least 3 different Micro-USB cables.
*Tested with the 4GB Dane-Elec Class 4 MicroSD card from Adafruit, as well as an 8GB Class 10 SanDisk full-size SD card.
*Voltages:
**Idle, with HDMI only
***5.06V (polyfuse in)
***4.82V (polyfuse out)
**Idle, with HDMI, keyboard and mouse
***5.04V (polyfuse in)
***4.77V (polyfuse out)
**Running Quake (with HDMI, keyboard, mouse, and network)
***4.98V (polyfuse in)
***4.55V (polyfuse out)
|
|
|Adafruit (US)
|Balefrost
|-}

User:AndrewS

2013-02-22T04:06:37Z

AndrewS:

'''Freelance Software Developer'''

Visit my website to get in touch with me:<BR>
http://www.andrewscheller.co.uk

User talk:Zootboy

2013-02-22T03:54:29Z

AndrewS:

== Your error ==
Do not EVER make a correction of the model wizard on the actual WIZARD, there's a talk page for that. You are wrong (even though it may seem like common sense), so do not ever edit the model.

:Hello, Jeff. Thank you for alerting me to my supposed error, I appreciate the chance to defend myself. I'm a bit surprised by your tone, however. You seem to be very controlling, almost possessive over the model wizard. It seems strange to me, considering that this is an open wiki that is supposed to be contributed to by everybody.

:I will quote your message here: "Do not EVER make a correction of the model wizard on the actual WIZARD, there's a talk page for that. You are wrong (even though it may seem like common sense), so do not ever edit the model."

:As I understand it, the talk page is meant to discuss changes or revisions that may be under question. My edit, however, did not fall under that category, and I can back my edit up with facts. To refresh our memories, the line under question is this: " It is impossible to connect to the internet, even with a wireless adapter."

:This line is factually incorrect, so I edited the page to correct this. The Model A and Model B have these differences: one verses two USB ports, 256MB verses 256/512MB, no built-in ethernet verses on-board ethernet adapter. On a deeper level, the Model A connects the single USB port directly to the chipset, while the Model B has a USB hub within the ethernet chipset to supply the two ports.

:So, from this, we know that both models of RPi have fully functioning USB ports. Since they also share the same EXACT Broadcom chipset and run the same EXACT Linux images, there is no reason from a hardware or software standpoint that one can network while the other one can't. (The power issue for running a USB WiFi chipset is present on both models, and must be mitigated in both by using a powered USB hub.)

:I would also point out that the ethernet chipset is not required to run a USB wireless chipset. The two operate totally independently, with different kernel modules and everything.

:I see from your userpage that you are the President of the RPWC. I take that to mean that you are heavily involved in the RPi wiki project. Please understand that I mean no disrespect when I assert my claims, but I find it uncharacteristic of a heavy wiki user to revert a perfectly reasonable assertion without any sort of explanation and going on to leave a heavy-handed and somewhat belittling message on their talk page. I hope this is uncharacteristic of you, Jeff.

:: FWIW, [[User:Jeff]] does not represent the elinux.org wiki or any content found therein. I'm still unsure what the RPWC is, or how it thinks it has any bearing on any content on elinux.org, be it RPi content or not, but I assure you that elinux.org will remain as open as possible! Edit what you want, review counter edits, etc. etc. Please contact [[User:wmat]] if you have any questions regarding this. --[[User:Wmat|Wmat]] ([[User talk:Wmat|talk]]) 02:45, 29 November 2012 (UTC)

::: Thanks for the info. I wasn't sure exactly how this wiki operated, so I was treading carefully. Glad to know the wiki supports open wiki principles! --[[User:Zootboy|Zootboy]] ([[User talk:Zootboy|talk]]) 02:57, 29 November 2012 (UTC)

:::: I also agree that "Jeff" and "RPWC" seem to be very heavy-handed and over the top. AFAICT Jeff (view his [[Special:Contributions/Jeff|edits]]) took it upon himself to create the "Wiki Council" and elect himself "President" :-/ <BR> [[R-Pi_Hub]] says "As the RPi wiki is currently a wreck, the council's current goal is to clean up the RPi Wiki" so I made some suggestions at the bottom of [[eLinux.org:RPi_Council]] but that page hasn't even been touched since October last year, which IMHO speaks volumes... I personally think it's doing more harm than good, especially with the "Note: This is official and is ok with the administration of eLinux." line at the top. [[User:AndrewS|AndrewS]] ([[User talk:AndrewS|talk]]) 03:54, 22 February 2013 (UTC)

Talk:RPi ADC I2C Python

2013-02-22T03:22:01Z

AndrewS: /* Updated PYTHONPATH step */

==Updated PYTHONPATH step==
It seems the quick2wire people reorganized the quick2wire-python-api so there is no longer a src directory. The README says to add the path to the root directory of the package to the PYTHONPATH variable. I found in my own use that was required as well. There is no longer a src/ directory and the test script fails saying it can not find the module. Putting in the root directory path for the package fixed the problem, so I updated these directions to reflect the current correct installation procedure. --[[User:Bgirardot|Bgirardot]] ([[User talk:Bgirardot|talk]]) 00:49, 15 January 2013 (UTC)

Thanks! :) [[User:AndrewS|AndrewS]] ([[User talk:AndrewS|talk]]) 03:22, 22 February 2013 (UTC)

RPi Hardware

2013-02-22T03:14:06Z

AndrewS: /* Schematic / Layout */

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

==Introduction==
[[File:Rpi unpopulated pcb.jpg|thumb|right|The unpopulated Rpi bèta board]]
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]].

Those who are looking to set up a Raspberry Pi for the first time, see [[RPi Hardware Basic Setup]].

Several different Hardware versions/revisions [[RaspberryPi Boards]] have been found probably from different assembly lines. Try to identify your board for better troubleshooting and update it if you have one which is not mentioned.

==Specifications==
{| class="wikitable"
!
! Model A
! Model B
|-
| Target price:<ref name="faq" >http://www.raspberrypi.org/faqs</ref>
| US$25 Ext tax (GBP £16 Exc VAT)
| US$35 Ext tax (GBP £22 Exc VAT)
|-
| System-on-a-chip (SoC):<ref name="faq" />
| colspan="2" | Broadcom BCM2835 (CPU + GPU. SDRAM is a separate chip stacked on top)
|-
| CPU:
| colspan="2" | 700 MHz ARM11 ARM1176JZF-S core
|-
| GPU:
| colspan="2" | Broadcom VideoCore IV,OpenGL ES 2.0,OpenVG 1080p30 H.264 high-profile encode/decode
|-
| Memory (SDRAM)iB
| 256 MiB (planned with 128 MiB, upgraded to 256 MiB on 29 Feb 2012)
| 256 MiB (until 15 Oct 2012); 512 MiB (since 15 Oct 2012)
|-
| USB 2.0 ports:
| 1 (provided by the BCM2835)
| 2 (via integrated USB hub)
|-
| Video outputs:<ref name="faq" />
| colspan="2" | Composite video | Composite RCA, HDMI (not at the same time)
|-
| Audio outputs:<ref name="faq" />
| colspan="2" | TRS connector | 3.5 mm jack, HDMI
|-
| Audio inputs:
| colspan="2" | none, but a USB mic or sound-card could be added
|-
| Onboard Storage:
| colspan="2" | Secure Digital|SD / MMC / SDIO card slot
|-
| Onboard Network:<ref name="faq" />
| None
| 10/100 wired Ethernet RJ45
|-
| Low-level peripherals:
| colspan="2" | General Purpose Input/Output (GPIO) pins, Serial Peripheral Interface Bus (SPI), I²C, I²S<ref name="i2s">[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?]</ref>, Universal asynchronous receiver/transmitter (UART)
|-
| Real-time clock:<ref name="faq" />
| colspan="2" | None
|-
| Power ratings (provisional, from alpha board):
| 500 mA, (2.5 W) <ref name="faq" />
| 700 mA, (3.5 W)
|-
| Power source:<ref name="faq" />
| colspan="2" | 5 V (DC) via Micro USB type B or GPIO header
|-
| Size:
| colspan="2" | 85.0 x 56.0 mm (two different boards, measured with callipers)
|}

==Components==
[[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
Beech, edited to show 256MB ram for both boards]]
(Provisional - some of the expansion interfaces won't be available on production boards)
(PCB IDs are those of the Model B Beta board)

* 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:
** 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].
** 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
** 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)
** 256MiB of ([http://www.hynix.com/products/mobile/view.jsp?info.ramKind=28&info.serialNo=H9TKNNN2GDMPLR&posMap=MobileDDR2 Hynix MobileDDR2] or [http://www.samsung.com/global/business/semiconductor/product/mobile-dram/detail?productId=7611&iaId=747 Samsung Mobile DRAM]) SDRAM (or 512MB [http://www.samsung.com/global/business/semiconductor/product/mobile-dram/detail?iaId=747&productId=7609 Mobile DRAM] on later boards). The RAM is physically stacked on top of the Broadcom media processor ([http://en.wikipedia.org/wiki/Package_on_package package-on-package technology]). Here is a photo of the [http://www.raspberrypi.org/wp-content/uploads/2012/01/brcm2835plusmemory.jpg SDRAM (left) and BCM2835 (right)] ball grid arrays on JamesH's finger. You are looking at the bottom side. The BCM2835 top side has a land grid array which matches the SDRAM ball grid array. Here is a highly magnified side view of the SDRAM stacked on top of the BCM2835 stacked on top of the PCB [http://www.raspberrypi.org/wp-content/uploads/2012/09/2012-09-21-10.58.22.jpg PoP stack] (you can see why it's job that can only be done by robots!).
* 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:
** 10/100Mb Ethernet (Auto-MDIX)<ref name=autoMDIX>[http://en.wikipedia.org/wiki/Medium_dependent_interface#Auto-MDIX Wikipedia:Auto-MDIX]</ref>
** 2x USB 2.0
* S1: Micro USB power jack (5v - Power Only)
* 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.
* S3: HDMI connector providing type A HDMI 1.3a out
* S4: Composite Video connector: RCA
* S5: MIPI [http://www.mipi.org/specifications/camera-interface CSI-2] interface. 15-pin surface mounted flat flex connector.
* S6: Audio connector: 3.5mm stereo jack (output only)
* S8: SD/MMC/SDIO memory card slot (underside)
* S7: Either 1x USB 2.0 '''(Model A)''' 2x USB 2.0 '''(Model B)'''
* P1: 26-pin 2.54 mm header expansion, providing: see [[Rpi_Low-level_peripherals | Low-level peripherals]]
** 8 [[Rpi_Low-level_peripherals#General_Purpose_Input.2FOutput_.28GPIO.29|GPIO]]s at 3v3
** 2-pin UART serial console, 3v3 TTL (debug); or 2 GPIOs at 3v3
** I²C interface (3v3); or 2 GPIOs at 3v3
** SPI interface (3v3); or 5 GPIOs at 3v3
** 3v3, 5v and GND supply pins
** ARM JTAG (if pins are reconfigured in software and one signal is taken from S5)
** Second I²C interface (3v3) (if pins are reconfigured in software)
** I²S interface (if pins are reconfigured in software, hardware hack may be required<ref name="i2s"/>)
** 6 pins reserved for future use
* P2: 8-pin 2.54 mm header expansion providing GPU JTAG (ARM11 pinout, pin 7 is nofit for locating)
* P3: 7-pin 2.54 mm header expansion (header not fitted), providing LAN9512 JTAG (pin 6 is nofit for locating)
* P4: 10/100Mb RJ45 Ethernet jack '''(Model B)'''
* TP1 and TP2: Test Points giving access to +5V and GND respectively
* 5 Status LEDs<ref name="PCBs">[http://www.raspberrypi.org/archives/402 RPiBlog Post: High-res pics of the PCBs]</ref><ref name="LEDs">[http://twitpic.com/8edlsf TwitPic:Photo of Board Powered]</ref><ref name="LEDsGPIO">[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?]</ref><ref name="OKGreen">[[RPi_schematic_errata]]</ref><ref name="Revision2.0">[http://www.raspberrypi.org/archives/1959 RPiBlog Post: A nice shiny photo of the rev2 board – and User Guide news]</ref>:
** D5(Green) - SDCard Access (via GPIO16) - labelled as "OK" on Rev1.0 boards and "ACT" on Rev2.0 boards
** D6(Red) - 3.3 V Power - labelled as "PWR" on both Rev1.0 and Rev2.0 boards
** D7(Green) - Full Duplex (LAN) '''(Model B)''' - labelled as "FDX" on both Rev1.0 and Rev2.0 boards
** D8(Green) - Link/Activity (LAN) '''(Model B)''' - labelled as "LNK" on both Rev1.0 and Rev2.0 boards
** D9(Yellow) - 10/100Mbit (LAN) '''(Model B)''' - labelled (incorrectly) as "10M" on Rev1.0 boards and "100" on Rev2.0 boards

* Board size: 85.60 mm x 53.98 mm. Overall height expected to be less than 25 mm. <ref name="artwork">http://www.raspberrypi.org/archives/344</ref>
** A model B between highest points (USB connector to card slot) measured 21 mm.
* Weight: under 40 g?
** Alpha board weighs approx. 55 g.<ref>http://www.raspberrypi.org/?page_id=43&mingleforumaction=viewtopic&t=285.0</ref>
** A sample model B weighed 39.45 g.
* 6 layer PCB <ref name="artwork" />

==Schematic / Layout==

* [http://www.raspberrypi.org/wp-content/uploads/2011/07/raspberry1.png PCB screenshot, Alpha board]
* [http://www.raspberrypi.org/wp-content/uploads/2011/11/gerbers2.png PCB screenshot rev 1.0]
* [http://lh3.googleusercontent.com/-uO4l8pwSLvU/TsQGbth6x6I/AAAAAAAAAkk/5zQMH3uKPiE/s829/Boardlayout.png PCB screenshot rev 1.0, labelled version]
* [http://www.raspberrypi.org/wp-content/uploads/2011/12/psu.png Preliminary power supply schematic, Beta board]
* [http://elinux.org/File:RPi-Front-JPB.jpg High-resolution Model B PCB front photo, production board rev 1.0]
* [http://elinux.org/File:RPi-back-JPB.jpg High-resolution Model B PCB back photo, production board rev 1.0]
* [http://www.raspberrypi.org/wp-content/uploads/2012/09/sony-rasp-pi.jpg High-resolution Model B PCB front photo, production board rev 2.0]
* [http://www.raspberrypi.org/wp-content/uploads/2012/11/2012-11-29-14.48.47-HDR.jpg High-resolution Model A PCB front photo, production board rev 2.0]
* [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 (117MB)]
* [[Media:RPi beta xray.jpg|"Xray style" image of the beta board, created from the above GIMP project]] | [[RPi_xray_wallpapers|desktop wallpapers]]
* [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf Official Rev 1.0 schematics PDF] | [http://www.raspberrypi.org/wp-content/uploads/2012/10/Raspberry-Pi-R2.0-Schematics-Issue2.2_027.pdf Official Rev 2.0 schematics PDF] | [[RPi_schematic_differences|differences]] | [[RPi_schematic_errata|errata]] | [[RPi_schematics_breakdown|breakdown]] | [[RPi_Partial_BOM_Rev2.0_ModelB|partial BOM]]
* [http://www.andrewscheller.co.uk/rpi_pcb_modules.html 'Module groups' of the PCB photos]

==Power==

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).
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.

Premier Farnell recommend the following power supplies:
* Model A: 5V dc, 500-700mA
* Model B: 5V dc, 700-1200mA

Power consumption of the Raspberry Pi device is

* Board A: 5V, 500 mA (2.5W) '''without any devices connected''' (e.g. USB, Ethernet, HDMI)
* 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 "using networking and high-current USB peripherals" [http://www.raspberrypi.org/archives/260].)

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.

*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.
* 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.
* POE ([[wikipedia: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 - mind though that the Ethernet jack on the board is a 'magjack' - http://www.sparkfun.com/datasheets/Prototyping/MagJack.pdf - which means that the usual 'dumb or passive PoE' power pins 47 and 78 are *not* wired through to the board. So this is not an entirely trivial exercise).
* Back-Powering; (powering the Raspberry Pi from a USB hub through the uplink/data port, single cable) Back powering is possible on the Raspberry Pi. Revision 1.0 boards have to be modified to back power, this is due to the 140ma "polyfuses" that are installed in the USB port circuit. Revision 1.1 boards do not need modifications to back-power, they have replaced the polyfuses with 0ohm resistors in their place. Revision 2.0 boards do not need modification, they have neither resistors nor polyfuses. It is advised that short (12" (.3 meter) or less) USB cables be used for back-powering a Raspberry Pi. Cable resistance plus connector resistance can quickly reduce operating voltages below the proper range(5.25V to 4.75V).

===Power Supply Problems===

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.

The power required by the Pi will vary depending on how busy it is and what peripherals are connected.
* Running a GUI will take more power.
* The USB devices and Ethernet connection will take power.
* Running the GPU will take extra power.

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.
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 of the two USB ports on the Pi has a polyfuse rated at 140 mA, so any connected USB devices should draw less than this amount of current. In addition the polyfuse will cause a significant voltage drop, so that USB devices get less voltage than is available on the RPI itself, sometimes up to half a volt less (maybe more if the fuse has recently been hot). For regular "low power" USB devices this doesn't cause a problem as they are designed to work with voltages as low as 4.4 Volt. This isn't the case however with some USB devices such as WiFi dongles which may need 4.75 Volt, and are also known to draw more than 150 mA when configured and active. Because of the problems these polyfuses caused Raspberry PI's produced after August 25, 2012 have the USB polyfuses F1 & F2 removed (replaced with shorts).

The microUSB input port also has a 1.1 A polyfuse (700mA "hold current") which may also have enough resistance (although much smaller than the 140mA fuses) to cause a significant voltage drop on the board, even below its 1.1 A total current.

A extended explanation of the consequences of the use of these polyfuses can be found here [[Polyfuses explained]]

There are several reasons why the power to the board may be inadequate:
* 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 its full power without the voltage dropping.
* The PSU is not regulated.
* 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.
* If the PSU is unregulated it can also output too high a voltage, which may trigger the overvoltage device in the PI, which will temporarily short the 5V to ground, this will then "blow" polyfuse F3, which will take several days to recover from. Meanwhile (possibly with another PSU) the PI might not get enough power because the (partly) blown polyfuse is consuming some of the power. The solution is when this happens to ways a few days to give the polyfuse time to recover before attempting to use the better PSU. If you suspect a blow polyfuse, measure the voltage across F3, which should be less than 0.05 Volt.

====How Can I tell if the power supply is inadequate?====

Common symptoms of an inadequate power supply are
* Unreliable Ethernet or keyboard operation, especially if it's OK at first but not when the GUI is started.
* SD card errors at start up seems to be another symptom of poor power.

If you think you have a problem with your power supply, it is a good idea to check the actual voltage
on the Raspberry Pi circuit board. Two test points labelled TP1 and TP2 are provided on the circuit board
to facilitate voltage measurements.

Use a multimeter which is set to the range 20 volts DC (or 20v =). You should see a voltage between 4.75 and 5.25 volts. Anything outside this range indicates that you have a problem with your power supply or your power cable, or the input polyfuse F3. Anything inside, but close to the limits, of this range ''may'' indicate a problem.

[[File:RPI_Test_Points.JPG|400px]] [[File:Voltmeter.JPG|250px]]

====Things that can cause problems====
* 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.
* 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.
* A power supply that is rated for less than 700mA may work some of the time.
* 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.
* 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.

====Summary====

* If you are having unreliable operation the first thing to do is check your power supply.
* Start with a good quality regulated power supply that is rated to provide 5V and at least 1A (1000mA).
* Use a good quality micro USB cable. Cables are notorious for giving trouble so be prepared to swap for another one.
* Not all power supplies will deliver what they claim.

===Capacitor C6===
Behind the microUSB power connector on the Model B is a metallic grey component called a capacitor, marked as C6. This capacitor helps stabilise the DC power on the board, but for some it has also become a place for their thumb when removing the RPI's power lead; unfortunately, this can result in the capacitor breaking off! It has been stated in the forums that the type of capacitor used for C6 will be changed on later RPi models for one with sturdier leads. If you do break off your C6 capacitor, it's highly likely that your RPi will still work properly, unless you have a particularly unstable power supply, but the general advice is to not use C6 as a leverage point when removing the power connector and also take care when storing or transporting your RPi if it's not fitted in a case - try not to stow the board where C6 could be knocked by other items - for example in a laptop carry case or in amongst some books.
[[File:Rpic6.jpg|300px|thumb|center|Capacitor C6 (ringed)]]

It's unlikely that replacing a broken off C6 capacitor will be covered under warranty, but fortunately they are easy to replace if you have average [http://www.raspberrypi.org/archives/1494 soldering skills], but remember that reworking your RPi will void its warranty too. C6 is a surface mount electrolytic capacitor with a capacitance of 220 microfarad (μF) and a voltage rating of 16 volt (V). The capacitor is polarised and so must be fitted the right way round - notice the black marking on one side in the picture above. A replacement capacitor can be purchased from numerous sources - for example:

[http://uk.farnell.com/jsp/search/browse.jsp?N=202457+110114112+110119850+110141127+110200576&No=0&getResults=true&appliedparametrics=true&locale=en_UK&divisionLocale=en_UK&catalogId=&skipManufacturer=false&skipParametricAttributeId=&prevNValues=202457+110114112+110119850+110141127&mm=1000002|110114112|110114112,1001880|110119850|110119850,1002520||,1002063||,1002999||,&filtersHidden=false&appliedHidden=false&autoApply=true&originalQueryURL=%2Fjsp%2Fsearch%2Fbrowse.jsp%3FN%3D202457%26No%3D0%26getResults%3Dtrue%26appliedparametrics%3Dtrue%26locale%3Den_UK%26divisionLocale%3Den_UK%26catalogId%3D%26skipManufacturer%3Dfalse%26skipParametricAttributeId%3D%26prevNValues%3D202457 Farnell]

[http://www.rapidonline.com/Electronic-Components/220uf-16v-85deg-Smd-Electro-Capacitor-11-2264 Rapid Electronics]

[http://uk.rs-online.com/web/c/passives/capacitors/aluminium/?sort-by=default&sort-order=default&applied-dimensions=4294884868,%204294884170,%204294672278,4294885140&lastAttributeSelectedBlock=4294955811 RS Components]

If you prefer to make your own PSU - see: [[RPi_5V_PSU_construction| Power Supply construction - HowTo]]

==References==
<references/>

{{Template:Raspberry Pi}}

Talk:RPi ADC I2C Python

2013-02-22T03:07:55Z

AndrewS: /* Updated PYTHONPATH step */

RPi BCM2835 GPIOs

2013-02-22T03:00:59Z

AndrewS: /* BCM2835 GPIO functions */ Crossed out outdated info

[[Category: RaspberryPi]]
[[Category: BCM2835]]

Back to [[RPi_Low-level_peripherals]]

= BCM2835 GPIO functions =

This is a wiki-fied copy of Table 6-31 from the BCM2835 [http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf datasheet] including any relevant [[BCM2835_datasheet_errata|errata]], with a couple of extra columns, all nicely hyperlinked together and cross-referenced so that clicking on a function name will automatically take you to the description of that function.
Any GPIOs that aren't [[RPi_BCM2835_Pinout|connected]] on the RaspberryPi Model B revision 1.0 circuit board are <del>crossed out</del>, and the GPIOs available on the [[Rpi_Low-level_peripherals|GPIO Connector (P1)]] are in '''bold''', with their default function (according to the [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf schematics]) in '''''bold italics'''''.<br>
(If you want to see how GPIO-pins map back to ''actual'' pins, see [[RPi_BCM2835_Pinout|this page]])

GPIO Pins Alternative Function Assignment
{| border="1"
! style="background-color:yellow;" | !! style="background-color:yellow;" | Pull !! style="background-color:yellow;" | ALT0 !! style="background-color:yellow;" | ALT1 !! style="background-color:yellow;" | ALT2 !! style="background-color:yellow;" | ALT3 !! style="background-color:yellow;" | ALT4 !! style="background-color:yellow;" | ALT5 !! style="background-color:yellow;" | RPi [[RPi_BCM2835_Signals_Rev1.0|Rev1.0 signal name]] !! style="background-color:yellow;" | RPi [[RPi_BCM2835_Signals_Rev2.0|Rev2.0 signal name]] !! style="background-color:yellow;" | RPi Rev1.0 [[Rpi_Low-level_peripherals|connection]] !! style="background-color:yellow;" | RPi Rev2.0 [[Rpi_Low-level_peripherals|connection]]
|-
| <div id="GPIO0">'''GPIO0'''</div> || High || style="background-color:orange;" | '''''[[#SDA0|SDA0]]''''' || style="background-color:royalblue;" | [[#SAx|SA5]] || style="background-color:darkolivegreen" | <reserved> || || || || SDA0 || SDA0 || style="background-color:cyan;" | P1-03 || S5-14
|-
| <div id="GPIO1">'''GPIO1'''</div> || High || style="background-color:orange;" | '''''[[#SCL0|SCL0]]''''' || style="background-color:royalblue;" | [[#SAx|SA4]] || style="background-color:darkolivegreen" | <reserved> || || || || SCL0 || SCL0 || style="background-color:cyan;" | P1-05 || S5-13
|-
| <div id="GPIO2">GPIO2</div> || High || style="background-color:magenta;" | [[#SDA1|SDA1]] || style="background-color:royalblue;" | [[#SAx|SA3]] || style="background-color:darkolivegreen" | <reserved> || || || || SDA1 || SDA1 || S5-14 || style="background-color:cyan;" | P1-03
|-
| <div id="GPIO3">GPIO3</div> || High || style="background-color:magenta;" | [[#SCL1|SCL1]] || style="background-color:royalblue;" | [[#SAx|SA2]] || style="background-color:darkolivegreen" | <reserved> || || || || SCL1 || SCL1 || S5-13 || style="background-color:cyan;" | P1-05
|-
| <div id="GPIO4">'''GPIO4'''</div> || High || style="background-color:turquoise;" | '''''[[#GPCLK0|GPCLK0]]''''' || style="background-color:royalblue;" | [[#SAx|SA1]] || style="background-color:darkolivegreen" | <reserved> || || || style="background-color:silver" | [[#ARM_TDI|ARM_TDI]] || GPIO_GCLK || GPIO_GCLK || style="background-color:lime;" | P1-07 || style="background-color:lime;" | P1-07
|-
| <div id="GPIO5">GPIO5</div> || High || style="background-color:turquoise;" | [[#GPCLK1|GPCLK1]] || style="background-color:royalblue;" | [[#SAx|SA0]] || style="background-color:darkolivegreen" | <reserved> || || || style="background-color:silver" | [[#ARM_TDO|ARM_TDO]] || CAM_CLK || CAM_CLK || S5-12 || S5-12
|-
| <div id="GPIO6">GPIO6</div> || High || style="background-color:turquoise;" | [[#GPCLK2|GPCLK2]] || style="background-color:royalblue;" | [[#SOE_N|SOE_N / SE]] || style="background-color:darkolivegreen" | <reserved> || || || style="background-color:silver" | [[#ARM_RTCK|ARM_RTCK]] || LAN_RUN || LAN_RUN || IC3-12 || IC3-12
|-
| <div id="GPIO7">'''GPIO7'''</div> || High || style="background-color:plum;" | '''''[[#SPI0_CE1_N|SPI0_CE1_N]]''''' || style="background-color:royalblue;" | [[#SWE_N|SWE_N / SRW_N]] || style="background-color:darkolivegreen" | <reserved> || || || || SPI_CE1_N || SPI_CE1_N || style="background-color:purple;color:white;" | P1-26 || style="background-color:purple;color:white;" | P1-26
|-
| <div id="GPIO8">'''GPIO8'''</div> || High || style="background-color:plum;" | '''''[[#SPI0_CE0_N|SPI0_CE0_N]]''''' || style="background-color:royalblue;" | [[#SDx|SD0]] || style="background-color:darkolivegreen" | <reserved> || || || || SPI_CE0_N || SPI_CE0_N || style="background-color:purple;color:white;" | P1-24 || style="background-color:purple;color:white;" | P1-24
|-
| <div id="GPIO9">'''GPIO9'''</div> || Low || style="background-color:plum;" | '''''[[#SPI0_MISO|SPI0_MISO]]''''' || style="background-color:royalblue;" | [[#SDx|SD1]] || style="background-color:darkolivegreen" | <reserved> || || || || SPI_MISO || SPI_MISO || style="background-color:purple;color:white;" | P1-21 || style="background-color:purple;color:white;" | P1-21
|-
| <div id="GPIO10">'''GPIO10'''</div> || Low || style="background-color:plum;" | '''''[[#SPI0_MOSI|SPI0_MOSI]]''''' || style="background-color:royalblue;" | [[#SDx|SD2]] || style="background-color:darkolivegreen" | <reserved> || || || || SPI_MOSI || SPI_MOSI || style="background-color:purple;color:white;" | P1-19 || style="background-color:purple;color:white;" | P1-19
|-
| <div id="GPIO11">'''GPIO11'''</div> || Low || style="background-color:plum;" | '''''[[#SPI0_SCLK|SPI0_SCLK]]''''' || style="background-color:royalblue;" | [[#SDx|SD3]] || style="background-color:darkolivegreen" | <reserved> || || || || SPI_SCLK || SPI_SCLK || style="background-color:purple;color:white;" | P1-23 || style="background-color:purple;color:white;" | P1-23
|-
| <div id="GPIO12"><del>GPIO12</del></div> || Low || style="background-color:lightblue;" | [[#PWMx|PWM0]] || style="background-color:royalblue;" | [[#SDx|SD4]] || style="background-color:darkolivegreen" | <reserved> || || || style="background-color:silver" | [[#ARM_TMS|ARM_TMS]] || nc || nc || ||
|-
| <div id="GPIO13"><del>GPIO13</del></div> || Low || style="background-color:lightblue;" | [[#PWMx|PWM1]] || style="background-color:royalblue;" | [[#SDx|SD5]] || style="background-color:darkolivegreen" | <reserved> || || || style="background-color:silver" | [[#ARM_TCK|ARM_TCK]] || nc || nc || ||
|-
| <div id="GPIO14">'''GPIO14'''</div> || Low || style="background-color:red;" | '''''[[#TXD0|TXD0]]''''' || style="background-color:royalblue;" | [[#SDx|SD6]] || style="background-color:darkolivegreen;" | <reserved> || || || style="background-color:red;" | [[#TXD1|TXD1]] || TXD0 || TXD0 || style="background-color:yellow;" | P1-08 || style="background-color:yellow;" | P1-08
|-
| <div id="GPIO15">'''GPIO15'''</div> || Low || style="background-color:red;" | '''''[[#RXD0|RXD0]]''''' || style="background-color:royalblue;" | [[#SDx|SD7]] || style="background-color:darkolivegreen;" | <reserved> || || || style="background-color:red;" | [[#RXD1|RXD1]] || RXD0 || RXD0 || style="background-color:yellow;" | P1-10 || style="background-color:yellow;" | P1-10
|-
| <div id="GPIO16">GPIO16</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SDx|SD8]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:red;" | [[#CTS0|CTS0]] || style="background-color:plum;" | [[#SPI1_CEx_N|SPI1_CE2_N]] || style="background-color:red;" | [[#CTS1|CTS1]] || STATUS_LED_N || STATUS_LED_N || D5 (OK LED) || D5 (ACT LED)
|-
| <div id="GPIO17">'''''GPIO17'''''</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SDx|SD9]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:red;" | [[#RTS0|RTS0]] || style="background-color:plum;" | [[#SPI1_CEx_N|SPI1_CE1_N]] || style="background-color:red;" | [[#RTS1|RTS1]] || GPIO_GEN0 || GPIO_GEN0 || style="background-color:lime;" | P1-11 || style="background-color:lime;" | P1-11
|-
| <div id="GPIO18">'''''GPIO18'''''</div> || Low || style="background-color:lawngreen;" | [[#PCM_CLK|PCM_CLK]] || style="background-color:royalblue;" | [[#SDx|SD10]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:maroon;color:white;" | [[#MOSI|BSCSL SDA / MOSI]] || style="background-color:plum;" | [[#SPI1_CEx_N|SPI1_CE0_N]] || style="background-color:lightblue;" | [[#PWMx|PWM0]] || GPIO_GEN1 || GPIO_GEN1 || style="background-color:lime;" | P1-12 || style="background-color:lime;" | P1-12
|-
| <div id="GPIO19"><del>GPIO19</del></div> || Low || style="background-color:lawngreen;" | [[#PCM_FS|PCM_FS]] || style="background-color:royalblue;" | [[#SDx|SD11]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:maroon;color:white;" | [[#SCLK|BSCSL SCL / SCLK]] || style="background-color:plum;" | [[#SPI1_MISO|SPI1_MISO]] || style="background-color:lightblue;" | [[#PWMx|PWM1]] || nc || nc || ||
|-
| <div id="GPIO20"><del>GPIO20</del></div> || Low || style="background-color:lawngreen;" | [[#PCM_DIN|PCM_DIN]] || style="background-color:royalblue;" | [[#SDx|SD12]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:maroon;color:white;" | [[#MISO|BSCSL / MISO]] || style="background-color:plum;" | [[#SPI1_MOSI|SPI1_MOSI]] || style="background-color:turquoise;" | [[#GPCLK0|GPCLK0]] || nc || nc || ||
|-
| <div id="GPIO21">'''''GPIO21'''''</div> || Low || style="background-color:lawngreen;" | [[#PCM_DOUT|PCM_DOUT]] || style="background-color:royalblue;" | [[#SDx|SD13]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:maroon;color:white;" | [[#CE_N|BSCSL / CE_N]] || style="background-color:plum;" | [[#SPI1_SCLK|SPI1_SCLK]] || style="background-color:turquoise;" | [[#GPCLK1|GPCLK1]] || GPIO_GEN2 || CAM_GPIO || style="background-color:lime;" | P1-13 || S5-11
|-
| <div id="GPIO22">'''''GPIO22'''''</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SDx|SD14]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:turquoise;" | SD1_CLK || style="background-color:silver;" | [[#ARM_TRST|ARM_TRST]] || || GPIO_GEN3 || GPIO_GEN3 || style="background-color:lime;" | P1-15 || style="background-color:lime;" | P1-15
|-
| <div id="GPIO23">'''''GPIO23'''''</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SDx|SD15]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:turquoise;" | SD1_CMD || style="background-color:silver;" | [[#ARM_RTCK|ARM_RTCK]] || || GPIO_GEN4 || GPIO_GEN4 || style="background-color:lime;" | P1-16 || style="background-color:lime;" | P1-16
|-
| <div id="GPIO24">'''''GPIO24'''''</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SDx|SD16]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:turquoise;" | SD1_DAT0 || style="background-color:silver;" | [[#ARM_TDO|ARM_TDO]] || || GPIO_GEN5 || GPIO_GEN5 || style="background-color:lime;" | P1-18 || style="background-color:lime;" | P1-18
|-
| <div id="GPIO25">'''''GPIO25'''''</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SDx|SD17]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:turquoise;" | SD1_DAT1 || style="background-color:silver;" | [[#ARM_TCK|ARM_TCK]] || || GPIO_GEN6 || GPIO_GEN6 || style="background-color:lime;" | P1-22 || style="background-color:lime;" | P1-22
|-
| <div id="GPIO26"><del>GPIO26</del></div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:darkolivegreen;" | <reserved> || style="background-color:darkolivegreen;" | <reserved> || style="background-color:turquoise;" | SD1_DAT2 || style="background-color:silver;" | [[#ARM_TDI|ARM_TDI]] || || nc || nc || ||
|-
| <div id="GPIO27">GPIO27</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:darkolivegreen;" | <reserved> || style="background-color:darkolivegreen;" | <reserved> || style="background-color:turquoise;" | SD1_DAT3 || style="background-color:silver;" | [[#ARM_TMS|ARM_TMS]] || || CAM_GPIO || GPIO_GEN2 || S5-11 || style="background-color:lime;" | P1-13
|-
| <div id="GPIO28">GPIO28</div> || - || style="background-color:orange;" | [[#SDA0|SDA0]] || style="background-color:royalblue;" | [[#SAx|SA5]] || style="background-color:lawngreen;" | [[#PCM_CLK|PCM_CLK]] || style="background-color:darkolivegreen;" | <reserved> || || || CONFIG0 || GPIO_GEN7 || R10 / R8 || P5-3
|-
| <div id="GPIO29">GPIO29</div> || - || style="background-color:orange;" | [[#SCL0|SCL0]] || style="background-color:royalblue;" | [[#SAx|SA4]] || style="background-color:lawngreen;" | [[#PCM_FS|PCM_FS]] || style="background-color:darkolivegreen;" | <reserved> || || || CONFIG1 || GPIO_GEN8 || R9 / R7 || P5-4
|-
| <div id="GPIO30">GPIO30</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SAx|SA3]] || style="background-color:lawngreen;" | [[#PCM_DIN|PCM_DIN]] || style="background-color:red;" | [[#CTS0|CTS0]] || || style="background-color:red;" | [[#CTS1|CTS1]] || CONFIG2 || GPIO_GEN9 || R6 / R4 || P5-5
|-
| <div id="GPIO31">GPIO31</div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SAx|SA2]] || style="background-color:lawngreen;" | [[#PCM_DOUT|PCM_DOUT]] || style="background-color:red;" | [[#RTS0|RTS0]] || || style="background-color:red;" | [[#RTS1|RTS1]] || CONFIG3 || GPIO_GEN10 || R5 / R3 || P5-6
|-
| <div id="GPIO32"><del>GPIO32</del></div> || Low || style="background-color:turquoise;" | [[#GPCLK0|GPCLK0]] || style="background-color:royalblue;" | [[#SAx|SA1]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:red;" | [[#TXD0|TXD0]] || || style="background-color:red;" | [[#TXD1|TXD1]] || nc || nc || ||
|-
| <div id="GPIO33"><del>GPIO33</del></div> || Low || style="background-color:darkolivegreen;" | <reserved> || style="background-color:royalblue;" | [[#SAx|SA0]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:red;" | [[#RXD0|RXD0]] || || style="background-color:red;" | [[#RXD1|RXD1]] || nc || nc || ||
|-
| <div id="GPIO34"><del>GPIO34</del></div> || High || style="background-color:turquoise;" | [[#GPCLK0|GPCLK0]] || style="background-color:royalblue;" | [[#SOE_N|SOE_N / SE]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:darkolivegreen;" | <reserved> || || || nc || nc || ||
|-
| <div id="GPIO35"><del>GPIO35</del></div> || High || style="background-color:plum;" | [[#SPI0_CE1_N|SPI0_CE1_N]] || style="background-color:royalblue;" | [[#SWE_N|SWE_N / SRW_N]] || || style="background-color:darkolivegreen;" | <reserved> || || || nc || nc || ||
|-
| <div id="GPIO36"><del>GPIO36</del></div> || High || style="background-color:plum;" | [[#SPI0_CE0_N|SPI0_CE0_N]] || style="background-color:royalblue;" | [[#SDx|SD0]] || style="background-color:red;" | [[#TXD0|TXD0]] || style="background-color:darkolivegreen;" | <reserved> || || || nc || nc || ||
|-
| <div id="GPIO37"><del>GPIO37</del></div> || Low || style="background-color:plum;" | [[#SPI0_MISO|SPI0_MISO]] || style="background-color:royalblue;" | [[#SDx|SD1]] || style="background-color:red;" | [[#RXD0|RXD0]] || style="background-color:darkolivegreen;" | <reserved> || || || nc || nc || ||
|-
| <div id="GPIO38"><del>GPIO38</del></div> || Low || style="background-color:plum;" | [[#SPI0_MOSI|SPI0_MOSI]] || style="background-color:royalblue;" | [[#SDx|SD2]] || style="background-color:red;" | [[#RTS0|RTS0]] || style="background-color:darkolivegreen;" | <reserved> || || || nc || nc || ||
|-
| <div id="GPIO39"><del>GPIO39</del></div> || Low || style="background-color:plum;" | [[#SPI0_SCLK|SPI0_SCLK]] || style="background-color:royalblue;" | [[#SDx|SD3]] || style="background-color:red;" | [[#CTS0|CTS0]] || style="background-color:darkolivegreen;" | <reserved> || || || nc || nc || ||
|-
| <div id="GPIO40">GPIO40</div> || Low || style="background-color:lightblue;" | [[#PWMx|PWM0]] || style="background-color:royalblue;" | [[#SDx|SD4]] || || style="background-color:darkolivegreen;" | <reserved> || style="background-color:plum;" | [[#SPI2_MISO|SPI2_MISO]] || style="background-color:red;" | [[#TXD1|TXD1]] || PWM0_OUT || PWM0_OUT || R21 || R21
|-
| <div id="GPIO41"><del>GPIO41</del></div> || Low || style="background-color:lightblue;" | [[#PWMx|PWM1]] || style="background-color:royalblue;" | [[#SDx|SD5]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:darkolivegreen;" | <reserved> || style="background-color:plum;" | [[#SPI2_MOSI|SPI2_MOSI]] || style="background-color:red;" | [[#RXD1|RXD1]] || nc || nc || ||
|-
| <div id="GPIO42"><del>GPIO42</del></div> || Low || style="background-color:turquoise;" | [[#GPCLK1|GPCLK1]] || style="background-color:royalblue;" | [[#SDx|SD6]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:darkolivegreen;" | <reserved> || style="background-color:plum;" | [[#SPI2_SCLK|SPI2_SCLK]] || style="background-color:red;" | [[#RTS1|RTS1]] || nc || nc || ||
|-
| <div id="GPIO43"><del>GPIO43</del></div> || Low || style="background-color:turquoise;" | [[#GPCLK2|GPCLK2]] || style="background-color:royalblue;" | [[#SDx|SD7]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:darkolivegreen;" | <reserved> || style="background-color:plum;" | [[#SPI2_CEx_N|SPI2_CE0_N]] || style="background-color:red;" | [[#CTS1|CTS1]] || nc || nc || ||
|-
| <div id="GPIO44"><del>GPIO44</del></div> || - || style="background-color:turquoise;" | [[#GPCLK1|GPCLK1]] || style="background-color:orange;" | [[#SDA0|SDA0]] || style="background-color:magenta;" | [[#SDA1|SDA1]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:plum;" | [[#SPI2_CEx_N|SPI2_CE1_N]] || || nc || nc || ||
|-
| <div id="GPIO45">GPIO45</div> || - || style="background-color:lightblue;" | [[#PWMx|PWM1]] || style="background-color:orange;" | [[#SCL0|SCL0]] || style="background-color:magenta;" | [[#SCL1|SCL1]] || style="background-color:darkolivegreen;" | <reserved> || style="background-color:plum;" | [[#SPI2_CEx_N|SPI2_CE2_N]] || || PWM1_OUT || PWM1_OUT || R27 || R27
|-
| <div id="GPIO46">GPIO46</div> || High || || || || style="background-color:darkolivegreen;" | <internal> || || || HDMI_HPD_P || HDMI_HPD_P || IC1-6 || IC1-6
|-
| <div id="GPIO47">GPIO47</div> || High || || || || style="background-color:darkolivegreen;" | <internal> || || || SD_CARD_DET || SD_CARD_DET || S8-10 || S8-10
|-
| <div id="GPIO48">GPIO48</div> || High || || || || style="background-color:darkolivegreen;" | <internal> || || || SD_CLK_R || SD_CLK_R || R48 || R48
|-
| <div id="GPIO49">GPIO49</div> || High || || || || style="background-color:darkolivegreen;" | <internal> || || || SD_CMD_R || SD_CMD_R || R47 || R47
|-
| <div id="GPIO50">GPIO50</div> || High || || || || style="background-color:darkolivegreen;" | <internal> || || || SD_DATA0_R || SD_DATA0_R || R49 || R49
|-
| <div id="GPIO51">GPIO51</div> || High || || || || style="background-color:darkolivegreen;" | <internal> || || || SD_DATA1_R || SD_DATA1_R || R50 || R50
|-
| <div id="GPIO52">GPIO52</div> || High || || || || style="background-color:darkolivegreen;" | <internal> || || || SD_DATA2_R || SD_DATA2_R || R45 || R45
|-
| <div id="GPIO53">GPIO53</div> || High || || || || style="background-color:darkolivegreen;" | <internal> || || || SD_DATA3_R || SD_DATA3_R || R46 || R46
|-
! style="background-color:yellow;" | !! style="background-color:yellow;" | Pull !! style="background-color:yellow;" | ALT0 !! style="background-color:yellow;" | ALT1 !! style="background-color:yellow;" | ALT2 !! style="background-color:yellow;" | ALT3 !! style="background-color:yellow;" | ALT4 !! style="background-color:yellow;" | ALT5 !! style="background-color:yellow;" | RPi [[RPi_BCM2835_Signals_Rev1.0|Rev1.0 signal name]] !! style="background-color:yellow;" | RPi [[RPi_BCM2835_Signals_Rev2.0|Rev2.0 signal name]] !! style="background-color:yellow;" | RPi Rev1.0 [[Rpi_Low-level_peripherals|connection]] !! style="background-color:yellow;" | RPi Rev2.0 [[Rpi_Low-level_peripherals|connection]]
|}

This next paragraph (which I've crossed out) only applies to Rev.1 boards, and even then these GPIOs were apparently never ''actually'' used for board identification!<BR>
<del>'''Board revision coding'''<BR>
GPIO 28-31 are brought out, with each pin attached to a voltage divider. These four GPIO's are used to auto detect the revision version, as is indicated in the schematic (sheet to, location 7D). With 10K resistors either mounted or unmounted the pins are either pulled low or high, giving a four bit condition that can be read, with currently only two of the sixteen possible combinations used, one (code '0') for the model A and the other (code '1') for the model B, with codes '2' to 'F' reserved for future use.</del>

As in the table above, the GPIOs available on the [[Rpi_Low-level_peripherals|GPIO Connector (P1)]] are in '''bold''', with their default function (according to the [http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf schematics]) in '''''bold italics'''''.

Special function legend:
{| border="1"
! style="background-color:powderblue;" | Name !! style="background-color:powderblue;" | Function !! style="background-color:powderblue;" | Datasheet section !! style="background-color:powderblue;" | GPIOs
|-
| style="background-color:orange;" | <div id="SDA0">SDA0</div> || BSC master 0 data line || BSC || '''''[[#GPIO0|GPIO0]]''''' [[#GPIO28|GPIO28]] <del>[[#GPIO44|GPIO44]]</del>
|-
| style="background-color:orange;" | <div id="SCL0">SCL0</div> || BSC master 0 clock line || BSC || '''''[[#GPIO1|GPIO1]]''''' [[#GPIO29|GPIO29]] [[#GPIO45|GPIO45]]
|-
| style="background-color:magenta;" | <div id="SDA1">SDA1</div> || BSC master 1 data line || BSC || [[#GPIO2|GPIO2]] <del>[[#GPIO44|GPIO44]]</del>
|-
| style="background-color:magenta;" | <div id="SCL1">SCL1</div> || BSC master 1 clock line || BSC || [[#GPIO3|GPIO3]] [[#GPIO45|GPIO45]]
|-
| style="background-color:turquoise;" | <div id="GPCLK0">GPCLK0</div> || General purpose Clock 0 || '''<TBD>''' || '''''[[#GPIO4|GPIO4]]''''' <del>[[#GPIO20|GPIO20]]</del> <del>[[#GPIO32|GPIO32]]</del> <del>[[#GPIO34|GPIO34]]</del>
|-
| style="background-color:turquoise;" | <div id="GPCLK1">GPCLK1</div> || General purpose Clock 1 || '''<TBD>''' || [[#GPIO5|GPIO5]] '''[[#GPIO21|GPIO21]]''' <del>[[#GPIO42|GPIO42]]</del> <del>[[#GPIO44|GPIO44]]</del>
|-
| style="background-color:turquoise;" | <div id="GPCLK2">GPCLK2</div> || General purpose Clock 2 || '''<TBD>''' || [[#GPIO6|GPIO6]] <del>[[#GPIO43|GPIO43]]</del>
|-
| style="background-color:plum;" | <div id="SPI0_CE1_N">SPI0_CE1_N</div> || SPI0 Chip select 1 || SPI || '''''[[#GPIO7|GPIO7]]''''' <del>[[#GPIO35|GPIO35]]</del>
|-
| style="background-color:plum;" | <div id="SPI0_CE0_N">SPI0_CE0_N</div> || SPI0 Chip select 0 || SPI || '''''[[#GPIO8|GPIO8]]''''' <del>[[#GPIO36|GPIO36]]</del>
|-
| style="background-color:plum;" | <div id="SPI0_MISO">SPI0_MISO</div> || SPI0 MISO || SPI || '''''[[#GPIO9|GPIO9]]''''' <del>[[#GPIO37|GPIO37]]</del>
|-
| style="background-color:plum;" | <div id="SPI0_MOSI">SPI0_MOSI</div> || SPI0 MOSI || SPI || '''''[[#GPIO10|GPIO10]]''''' <del>[[#GPIO38|GPIO38]]</del>
|-
| style="background-color:plum;" | <div id="SPI0_SCLK">SPI0_SCLK</div> || SPI0 Serial clock || SPI || '''''[[#GPIO11|GPIO11]]''''' <del>[[#GPIO39|GPIO39]]</del>
|-
| style="background-color:lightblue;" | <div id="PWMx">PWMx</div> || Pulse Width Modulator 0..1 || Pulse Width Modulator || PWM0: <del>[[#GPIO12|GPIO12]]</del> '''[[#GPIO18|GPIO18]]''' [[#GPIO40|GPIO40]]<br> PWM1: <del>[[#GPIO13|GPIO13]]</del> <del>[[#GPIO19|GPIO19]]</del> <del>[[#GPIO41|GPIO41]]</del> [[#GPIO45|GPIO45]]
|-
| style="background-color:red;" | <div id="TXD0">TXD0</div> || UART 0 Transmit Data || UART || '''''[[#GPIO14|GPIO14]]''''' <del>[[#GPIO32|GPIO32]]</del> <del>[[#GPIO36|GPIO36]]</del>
|-
| style="background-color:red;" | <div id="RXD0">RXD0</div> || UART 0 Receive Data || UART || '''''[[#GPIO15|GPIO15]]''''' <del>[[#GPIO33|GPIO33]]</del> <del>[[#GPIO37|GPIO37]]</del>
|-
| style="background-color:red;" | <div id="CTS0">CTS0</div> || UART 0 Clear To Send || UART || [[#GPIO16|GPIO16]] [[#GPIO30|GPIO30]] <del>[[#GPIO39|GPIO39]]</del>
|-
| style="background-color:red;" | <div id="RTS0">RTS0</div> || UART 0 Request To Send || UART || '''[[#GPIO17|GPIO17]]''' [[#GPIO31|GPIO31]] <del>[[#GPIO38|GPIO38]]</del>
|-
| style="background-color:lawngreen;" | <div id="PCM_CLK">PCM_CLK</div> || PCM clock || PCM Audio || '''[[#GPIO18|GPIO18]]''' [[#GPIO28|GPIO28]]
|-
| style="background-color:lawngreen;" | <div id="PCM_FS">PCM_FS</div> || PCM Frame Sync || PCM Audio || <del>[[#GPIO19|GPIO19]]</del> [[#GPIO29|GPIO29]]
|-
| style="background-color:lawngreen;" | <div id="PCM_DIN">PCM_DIN</div> || PCM Data in || PCM Audio || <del>[[#GPIO20|GPIO20]]</del> [[#GPIO30|GPIO30]]
|-
| style="background-color:lawngreen;" | <div id="PCM_DOUT">PCM_DOUT</div> || PCM data out || PCM Audio || '''[[#GPIO21|GPIO21]]''' [[#GPIO31|GPIO31]]
|-
| style="background-color:royalblue;color:white;" | <div id="SAx">SAx</div> || Secondary mem Address bus || Secondary Memory Interface || many
|-
| style="background-color:royalblue;color:white;" | <div id="SOE_N">SOE_N / SE</div> || Secondary mem. Controls || Secondary Memory Interface || [[#GPIO6|GPIO6]] <del>[[#GPIO34|GPIO34]]</del>
|-
| style="background-color:royalblue;color:white;" | <div id="SWE_N">SWE_N / SRW_N</div> || Secondary mem. Controls || Secondary Memory Interface || '''[[#GPIO7|GPIO7]]''' <del>[[#GPIO35|GPIO35]]</del>
|-
| style="background-color:royalblue;color:white;" | <div id="SDx">SDx</div> || Secondary mem. data bus || Secondary Memory Interface || many
|-
| style="background-color:maroon;color:white;" | <div id="MOSI">BSCSL SDA / MOSI</div> || BSC slave Data, SPI slave MOSI || BSC/SPI slave || '''[[#GPIO18|GPIO18]]'''
|-
| style="background-color:maroon;color:white;" | <div id="SCLK">BSCSL SCL / SCLK</div> || BSC slave Clock, SPI slave clock || BSC/SPI slave || <del>[[#GPIO19|GPIO19]]</del>
|-
| style="background-color:maroon;color:white;" | <div id="MISO">BSCSL - / MISO</div> || BSC <not used>, SPI MISO || BSC/SPI slave || <del>[[#GPIO20|GPIO20]]</del>
|-
| style="background-color:maroon;color:white;" | <div id="CE_N">BSCSL - / CE_N</div> || BSC <not used>, SPI CSn || BSC/SPI slave || '''[[#GPIO21|GPIO21]]'''
|-
| style="background-color:plum;" | <div id="SPI1_CEx_N">SPI1_CEx_N</div> || SPI1 Chip select 0-2 || Auxiliary I/O || SPI1_CE0_N: '''[[#GPIO18|GPIO18]]'''<br> SPI1_CE1_N: '''[[#GPIO17|GPIO17]]'''<br> SPI1_CE2_N: [[#GPIO16|GPIO16]]
|-
| style="background-color:plum;" | <div id="SPI1_MISO">SPI1_MISO</div> || SPI1 MISO || Auxiliary I/O || <del>[[#GPIO19|GPIO19]]</del>
|-
| style="background-color:plum;" | <div id="SPI1_MOSI">SPI1_MOSI</div> || SPI1 MOSI || Auxiliary I/O || <del>[[#GPIO20|GPIO20]]</del>
|-
| style="background-color:plum;" | <div id="SPI1_SCLK">SPI1_SCLK</div> || SPI1 Serial clock || Auxiliary I/O || '''[[#GPIO21|GPIO21]]'''
|-
| style="background-color:red;" | <div id="TXD1">TXD1</div> || UART 1 Transmit Data || Auxiliary I/O || '''[[#GPIO14|GPIO14]]''' <del>[[#GPIO32|GPIO32]]</del> [[#GPIO40|GPIO40]]
|-
| style="background-color:red;" | <div id="RXD1">RXD1</div> || UART 1 Receive Data || Auxiliary I/O || '''[[#GPIO15|GPIO15]]''' <del>[[#GPIO33|GPIO33]]</del> <del>[[#GPIO41|GPIO41]]</del>
|-
| style="background-color:red;" | <div id="CTS1">CTS1</div> || UART 1 Clear To Send || Auxiliary I/O || [[#GPIO16|GPIO16]] [[#GPIO30|GPIO30]] <del>[[#GPIO43|GPIO43]]</del>
|-
| style="background-color:red;" | <div id="RTS1">RTS1</div> || UART 1 Request To Send || Auxiliary I/O || '''[[#GPIO17|GPIO17]]''' [[#GPIO31|GPIO31]] <del>[[#GPIO42|GPIO42]]</del>
|-
| style="background-color:plum;" | <div id="SPI2_CEx_N">SPI2_CEx_N</div> || SPI2 Chip select 0-2 || Auxiliary I/O || SPI2_CE0_N: <del>[[#GPIO43|GPIO43]]</del><br> SPI2_CE1_N: <del>[[#GPIO44|GPIO44]]</del><br> SPI2_CE2_N: [[#GPIO45|GPIO45]]
|-
| style="background-color:plum;" | <div id="SPI2_MISO">SPI2_MISO</div> || SPI2 MISO || Auxiliary I/O || [[#GPIO40|GPIO40]]
|-
| style="background-color:plum;" | <div id="SPI2_MOSI">SPI2_MOSI</div> || SPI2 MOSI || Auxiliary I/O || <del>[[#GPIO41|GPIO41]]</del>
|-
| style="background-color:plum;" | <div id="SPI2_SCLK">SPI2_SCLK</div> || SPI2 Serial clock || Auxiliary I/O || <del>[[#GPIO42|GPIO42]]</del>
|-
| style="background-color:silver;" | <div id="ARM_TRST">ARM_TRST</div> || ARM JTAG reset || '''<TBD>''' || '''[[#GPIO22|GPIO22]]'''
|-
| style="background-color:silver;" | <div id="ARM_RTCK">ARM_RTCK</div> || ARM JTAG return clock || '''<TBD>''' || [[#GPIO6|GPIO6]] '''[[#GPIO23|GPIO23]]'''
|-
| style="background-color:silver;" | <div id="ARM_TDO">ARM_TDO</div> || ARM JTAG Data out || '''<TBD>''' || '''[[#GPIO4|GPIO4]]''' '''[[#GPIO24|GPIO24]]'''
|-
| style="background-color:silver;" | <div id="ARM_TCK">ARM_TCK</div> || ARM JTAG Clock || '''<TBD>''' || <del>[[#GPIO13|GPIO13]]</del> '''[[#GPIO25|GPIO25]]'''
|-
| style="background-color:silver;" | <div id="ARM_TDI">ARM_TDI</div> || ARM JTAG Data in || '''<TBD>''' || '''[[#GPIO4|GPIO4]]''' <del>[[#GPIO26|GPIO26]]</del>
|-
| style="background-color:silver;" | <div id="ARM_TMS">ARM_TMS</div> || ARM JTAG Mode select || '''<TBD>''' || <del>[[#GPIO12|GPIO12]]</del> [[#GPIO27|GPIO27]]
|-
! style="background-color:powderblue;" | Name !! style="background-color:powderblue;" | Function !! style="background-color:powderblue;" | Datasheet section !! style="background-color:powderblue;" | GPIOs
|}

RPi Low-level peripherals

2013-02-22T02:12:47Z

AndrewS: /* GPIO hardware hacking */

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

==Introduction==
In addition to the familiar USB, Ethernet and HDMI ports, the R-Pi offers lower-level interfaces intended to connect more directly with chips and subsystem modules. These GPIO (general purpose I/O) signals on the 2x13 header pins include SPI, I2C, serial UART, 3V3 and 5V power. These interfaces are not "plug and play" and require care to avoid miswiring. The pins use a 3V3 logic level and are not tolerant of 5V levels, such as you might find on a 5V powered Arduino. Not yet software-enabled are the flex cable connectors with CSI (camera serial interface) and DSI (display serial interface), and a serial link inside the HDMI connector called CEC. (consumer electronics control)

==General Purpose Input/Output (GPIO)==
[[File:GPIOs.png|thumb|254px|right|The layout of the Raspberry Pi Revision 1 P1 pin-header seen from the top, containing pins useable for general purpose I/O. Colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs2.gif Source] ]]

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.

The Raspberry Pi allows peripherals and expansion boards (such as the [[Rpi Gertboard]]) to access the CPU by exposing the inputs and outputs.

For further general information about GPIOs, see: [http://en.wikipedia.org/wiki/GPIO the wikipedia article].<BR>
For further specific information about the Raspberry Pi's BCM2835 GPIOs, see: [[RPi_BCM2835_GPIOs|this wiki article]].

The production Raspberry Pi board has a 26-pin 2.54 mm (100 mil)<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907</ref> expansion header, marked as P1, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I²C, SPI, UART), as well as +3.3 V, +5 V and GND supply lines. Pin one is the pin in the first column and on the bottom row. <ref>http://www.raspberrypi.org/archives/384</ref>

'''GPIO voltage levels are 3.3 V and are not 5 V 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.

All the GPIO pins can be reconfigured to provide alternate functions, SPI, [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM], I²C and so. At reset only pins GPIO 14 & 15 are assigned to the alternate function UART, these two can be switched back to GPIO to provide a total of 17 GPIO pins<ref>http://www.raspberrypi.org/archives/384</ref>. Each of their functions and full details of how to access are detailed in the chipset datasheet <ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref>.

Each GPIO can interrupt, high/low/rise/fall/change.<ref>http://www.raspberrypi.org/archives/384#comment-5217</ref><ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref> There is currently no support for GPIO interrupts in the official kernel, howewer a patch exists, requiring compilation of modified source tree.<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=44&t=7509</ref> The 'Raspbian "wheezy"' <ref>http://www.raspberrypi.org/downloads</ref> version that is currently recommended for starters already includes GPIO interrupts.

GPIO input hysteresis (Schmitt trigger) can be on or off, output slew rate can be fast or limited, and source and sink current is configurable from 2 mA up to 16 mA. Note that chipset GPIO pins 0-27 are in the same block and these properties are set per block, not per pin. See [http://www.scribd.com/doc/101830961/GPIO-Pads-Control2 GPIO Datasheet Addendum - GPIO Pads Control]. Particular attention should be applied to the note regarding SSO (Simultaneous Switching Outputs): to avoid interference, driving currents should be kept as low as possible.

The available [[RPi_BCM2835_GPIOs|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.

There is also some information on the [[RPi Tutorial Easy GPIO Hardware & Software|Tutorial on Easy GPIO Hardware & Software]].

Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200 bit/s.

'''R-Pi PCB Revision 2 UPDATE:''' According to Eben at [http://www.raspberrypi.org/archives/1929#comment-31646] the R-Pi Rev.2 board being rolled out starting in September 2012 adds 4 more GPIO on a new connector called P5, and changes some of the existing P1 GPIO pinouts. On Rev2, GPIO_GEN2 [BCM2835/GPIO27] is routed to P1 pin 13, and changes what was SCL0/SDA0 to SCL1/SDA1: SCL1 [BCM2835/GPIO3] is routed to P1 pin 5, SDA1 [BCM2835/GPIO2] is routed to P1 pin 3. Also the power and ground connections previously marked "Do Not Connect" on P1 will remain as connected, specifically: P1-04:+5V0, P1-09:GND, P1-14:GND, P1-17:+3V3, P1-20:GND, P1-25:GND. According to this comment [http://www.raspberrypi.org/archives/2081#comment-33577] (and confirmed in this post [http://www.raspberrypi.org/archives/2233]) the P1 pinout is not expected to change in future beyond the current Rev.2 layout.

'''Header Pinout, top row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-02 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-04 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-06 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
|-
| P1-08 || bgcolor="lime" | GPIO 14 || bgcolor="lime" | GPIO 14 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_TXD || ALT5 = UART1_TXD
|-
| P1-10 || bgcolor="lime" | GPIO 15 || bgcolor="lime" | GPIO 15 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_RXD || ALT5 = UART1_RXD
|-
| P1-12 || bgcolor="lime" | GPIO 18 || bgcolor="lime" | GPIO 18 || || PCM_CLK || ALT4 = SPI1_CE0_N ALT5 = PWM0
|-
| P1-14 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-16 || bgcolor="lime" | GPIO23 || bgcolor="lime" | GPIO23 || || || ALT3 = SD1_CMD ALT4 = ARM_RTCK
|-
| P1-18 || bgcolor="lime" | GPIO24 || bgcolor="lime" | GPIO24 || || || ALT3 = SD1_DAT0 ALT4 = ARM_TDO
|-
| P1-20 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-22 || bgcolor="lime" | GPIO25 || bgcolor="lime" | GPIO25 || || || ALT3 = SD1_DAT1 ALT4 = ARM_TCK
|-
| P1-24 || bgcolor="lime" | GPIO08 || bgcolor="lime" | GPIO08 || || bgcolor="purple" | <span style="color:white">SPI0_CE0_N</span> ||
|-
| P1-26 || bgcolor="lime" | GPIO07 || bgcolor="lime" | GPIO07 || || bgcolor="purple" | <span style="color:white">SPI0_CE1_N</span> ||
|}

'''Header Pinout, bottom row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-01 || bgcolor="orange" | 3.3 V ||bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-03 || bgcolor="lime" | GPIO 0 || bgcolor="lime" | '''GPIO 2'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SDA / '''I2C1_SDA''' ||
|-
| P1-05 || bgcolor="lime" | GPIO 1 || bgcolor="lime" | '''GPIO 3'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SCL / '''I2C1_SCL''' ||
|-
| P1-07 || bgcolor="lime" | GPIO 4 || bgcolor="lime" | GPIO 4 || || GPCLK0 || ALT5 = ARM_TDI
|-
| P1-09 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-11 || bgcolor="lime" | GPIO17 || bgcolor="lime" | GPIO17 || || ||| ALT3 = UART0_RTS ALT4 = SPI1_CE1_N ALT5 = UART1_RTS
|-
| P1-13 || bgcolor="lime" | GPIO21 || bgcolor="lime" | '''GPIO27''' || || PCM_DOUT / '''reserved''' || ALT4 = SPI1_SCLK ALT5 = GPCLK1 / '''ALT3 = SD1_DAT3 ALT4 = ARM_TMS'''
|-
| P1-15 || bgcolor="lime" | GPIO22 || bgcolor="lime" | GPIO22 || || || ALT3 = SD1_CLK ALT4 = ARM_TRST
|-
| P1-17 || bgcolor="orange" | 3.3 V || bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-19 || bgcolor="lime" | GPIO10 || bgcolor="lime" | GPIO10 || || bgcolor="purple" | <span style="color:white">SPI0_MOSI</span> ||
|-
| P1-21 || bgcolor="lime" | GPIO9 || bgcolor="lime" | GPIO9 || || bgcolor="purple" | <span style="color:white">SPI0_MISO</span> ||
|-
| P1-23 || bgcolor="lime" | GPIO11 || bgcolor="lime" | GPIO11 || || bgcolor="purple" | <span style="color:white">SPI0_SCLK</span> ||
|-
| P1-25 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|}

{| border="1"
! Colour legend
|-
| bgcolor="red" | <span style="color:white">+5 V</span>
|-
| bgcolor="orange" | +3.3 V
|-
| bgcolor="black" | <span style="color:white">Ground, 0V</span>
|-
| bgcolor="yellow" | UART
|-
| bgcolor="lime" | GPIO
|-
| bgcolor="purple" | <span style="color:white">SPI</span>
|-
| bgcolor="cyan" | I²C
|}

KiCad symbol: [[File:Conn-raspberry.lib]]

<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2</ref>

Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as an I²C interface. So there are 1.8 kilohm pulls up resistors on the board for these pins.<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480</ref>

Pin 12 supports [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM] .

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.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.1</ref> 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.

It is also possible to reconfigure GPIO connector pins P1-12 and 13 (chipset GPIO 18 and 21) to provide an I2S (a hardware modification may be required<ref name="I2S">[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?]</ref>) or PCM interface.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.2</ref> However, PCM_FS and PCM_DIN (chipset pins 19 and 20) are needed for I2S or PCM.

A second I²C 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.

===Referring to pins on the Expansion header===

The header is referred to as "The GPIO Connector (P1)". To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended.

* The expansion header is referred to as "Expansion Header" or "GPIO Connector (P1)"
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.
* Names GPIO0, GPIO1, GPIOx-ALTy, etc. refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where "x" matches BCM2835 number (without leading zero) and "y" 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 "GPIO7" to refer to a row of the table, and "GPIO7-ALT0" would refer to a specific cell of the table.
* 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 "SPI0_*" and "SPI1_*", but they didn't do the same on the I²C and UART pins. Instead of using "SDA0" and "SCL0", you should use "I2C0_SDA" and "I2C0_SCL"; and instead of "TX" or "TXD" and "RX" or "RXD", you should use "UART0_TXD" and "UART0_RXD".

===Power pins===
The maximum permitted current draw from the 3.3 V pins is 50 mA.

Maximum permitted current draw from the 5 V pin is the USB input current (usually 1 A) minus any current draw from the rest of the board.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1536#postid-21841</ref>
*Model A: 1000 mA - 500 mA -> max current draw: 500 mA
*Model B: 1000 mA - 700 mA -> max current draw: 300 mA
Be very careful with the 5 V pins P1-02 and P1-04, because if you short 5 V to any other P1 pin you may permanently damage your RasPi. Before probing P1, it's a good idea to strip short pieces of insulation off a wire and push them over the 5 V pins so you don't accidentally short them with a probe.

=== GPIO hardware hacking ===

The complete list of [[RPi_BCM2835_GPIOs|chipset GPIO pins]] which are available on the GPIO connector is: <blockquote>[[RPi_BCM2835_GPIOs#GPIO0|0]], [[RPi_BCM2835_GPIOs#GPIO1|1]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO21|21]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]]</blockquote>

(on the Revision2.0 RaspberryPis, this list changes to: [[RPi_BCM2835_GPIOs#GPIO2|2]], [[RPi_BCM2835_GPIOs#GPIO3|3]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]], [[RPi_BCM2835_GPIOs#GPIO27|27]], with [[RPi_BCM2835_GPIOs#GPIO28|28]], [[RPi_BCM2835_GPIOs#GPIO29|29]], [[RPi_BCM2835_GPIOs#GPIO30|30]], [[RPi_BCM2835_GPIOs#GPIO31|31]] additionally available on the [[#P5_header|P5 header]])

As noted above, P1-03 and P1-05 (SDA0 and SCL0 / SDA1 and SCL1) have 1.8 kilohm pull-up resistors to 3.3 V.

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:

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 3.3 V.

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.

There are a few other chipset GPIO pins accessible on the PCB but are in use:

* GPIO16 drives status LED D5 (usually SD card access indicator)
* GPIO28-31 are used by the board ID and are connected to resistors R3 to R10 (only on Rev1.0 boards).
* GPIO40 and 45 are used by analogue audio and support [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM]. They connect to the analogue audio circuitry via R21 and R27 respectively.
* GPIO46 is HDMI hotplug detect (goes to pin 6 of IC1).
* 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.

=== P2 header ===

The P2 header is the VideoCore JTAG and used only during the production of the board. It cannot be used as the ARM JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>. This connector is unpopulated in Rev 2.0 boards.

Useful P2 pins:

* Pin 1 - 3.3V (same as P1-01, 50 mA max current draw across both of them)
* Pin 7 - GND
* Pin 8 - GND

=== P3 header ===

The P3 header, unpopulated, is the LAN9512 JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>.

=== P5 header ===

The P5 header was added with the release of the Revision 2.0 PCB design.

'''P5 Pinout, seen from the bottom of the board:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P5-01 || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P5-02 || bgcolor="orange" | 3.3 V || 50 mA max (combined with P1)
|-
| P5-03 || bgcolor="lime" | GPIO28 || || bgcolor="cyan" | I2C0_SDA || ALT2 = PCM_CLK
|-
| P5-04 || bgcolor="lime" | GPIO29 || || bgcolor="cyan" | I2C0_SCL || ALT2 = PCM_FS
|-
| P5-05 || bgcolor="lime" | GPIO30 || || || ALT2 = PCM_DIN ALT3 = UART0_CTS ALT5 = UART1_CTS
|-
| P5-06 || bgcolor="lime" | GPIO31 || || || ALT2 = PCM_DOUT ALT3 = UART0_RTS ALT5 = UART1_RTS
|-
| P5-07 || bgcolor="black" | <span style="color:white">GND</span>
|-
| P5-08 || bgcolor="black" | <span style="color:white">GND</span>
|}

Note that the connector is intended to be mounted on the '''bottom''' of the PCB, so that for those who put the connector on the top side, the pin numbers are swapped. Pin 1 and pin 2 are swapped, pin 3 and 4, etc.

The new header can provide a second I2C channel (SDA + SCL) and handshake lines for the existing UART (TxD and RxD), or it can be used for an I2S (audio codec chip) interface using the PCM signals CLK, FS (Frame Sync), Din and Dout.

Note that the connector is placed JUST off-grid with respect to the P1 connector.

=== P6 header ===

The P6 header was added with the release of the Revision 2.0 PCB design.

[http://raspi.tv/2012/making-a-reset-switch-for-your-rev-2-raspberry-pi A reset button can be attached to the P6 header], with which the Pi can be reset.
Momentarily shorting the two pins of P6 together will cause a soft reset of the CPU.

===Driver support===

The Foundation will not include a GPIO driver in the initial release, standard Linux GPIO drivers should work with minimal modification.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1278.0</ref>

The community implemented SPI and I²C drivers <ref>http://www.bootc.net/projects/raspberry-pi-kernel/</ref>, which will be integrated with the new Linux pinctrl concept in a later version of the kernel. (On Oct. 14 2012, it was already included in the latest raspbian image.) A first compiled version as Linux modules is available to install on the 19/04/2012 Debian image, including 1-wire support<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=86172#p86172</ref>. The I²C and SPI driver uses the hardware modules of the microcontroller and interrupts for low CPU usage, the 1-wire support uses bitbanging on the GPIO ports, which results in higher CPU usage.

GordonH<ref>http://www.raspberrypi.org/forum/general-discussion/wiring-for-the-raspberry-pis-gpio</ref> wrote a (mostly) Arduino compatible/style [https://projects.drogon.net/raspberry-pi/wiringpi/ WiringPi library] in C for controlling the GPIO pins.

A useful tutorial on setting up I²C driver support can be found at [http://www.robot-electronics.co.uk/htm/raspberry_pi_examples.htm Robot Electronics] - look for the downloadable document rpi_i2c_setup.doc

===Graphical User Interfaces===
====WebIOPi====
[http://code.google.com/p/webiopi/ WebIOPi] allows you to control each GPIO with a simple web interface that you can use with any browser. Available in PHP and Python, they both require root access, but Python version serves HTTP itself. You can setup each GPIO as input or output and change their states (LOW/HIGH). WebIOPi is fully customizable, so you can use it for home remote control. It also work over Internet. UART/SPI/I2C support will be added later. If you need some computing for your GPIO go to code examples below.

==GPIO Code examples==
====GPIO Driving Example (C)====
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo & Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)
Example GPIO code:

<pre>
//
// How to access GPIO registers from C-code on the Raspberry-Pi
// Example program
// 15-January-2012
// Dom and Gert
// Revised: 15-Feb-2013

// Access from ARM Running Linux

#define BCM2708_PERI_BASE 0x20000000
#define GPIO_BASE (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/mman.h>
#include <unistd.h>

#define PAGE_SIZE (4*1024)
#define BLOCK_SIZE (4*1024)

int mem_fd;
void *gpio_map;

// I/O access
volatile unsigned *gpio;

// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)
#define INP_GPIO(g) *(gpio+((g)/10)) &= ~(7<<(((g)%10)*3))
#define OUT_GPIO(g) *(gpio+((g)/10)) |= (1<<(((g)%10)*3))
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)<=3?(a)+4:(a)==4?3:2)<<(((g)%10)*3))

#define GPIO_SET *(gpio+7) // sets bits which are 1 ignores bits which are 0
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0

void setup_io();

int main(int argc, char **argv)
{
int g,rep;

// Set up gpi pointer for direct register access
setup_io();

// Switch GPIO 7..11 to output mode

/************************************************************************\
* You are about to change the GPIO settings of your computer. *
* Mess this up and it will stop working! *
* It might be a good idea to 'sync' before running this program *
* so at least you still have your code changes written to the SD-card! *
\************************************************************************/

// Set GPIO pins 7-11 to output
for (g=7; g<=11; g++)
{
INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO
OUT_GPIO(g);
}

for (rep=0; rep<10; rep++)
{
for (g=7; g<=11; g++)
{
GPIO_SET = 1<<g;
sleep(1);
}
for (g=7; g<=11; g++)
{
GPIO_CLR = 1<<g;
sleep(1);
}
}

return 0;

} // main

//
// Set up a memory regions to access GPIO
//
void setup_io()
{
/* open /dev/mem */
if ((mem_fd = open("/dev/mem", O_RDWR|O_SYNC) ) < 0) {
printf("can't open /dev/mem \n");
exit(-1);
}

/* mmap GPIO */
gpio_map = mmap(
NULL, //Any adddress in our space will do
BLOCK_SIZE, //Map length
PROT_READ|PROT_WRITE,// Enable reading & writting to mapped memory
MAP_SHARED, //Shared with other processes
mem_fd, //File to map
GPIO_BASE //Offset to GPIO peripheral
);

close(mem_fd); //No need to keep mem_fd open after mmap

if (gpio_map == MAP_FAILED) {
printf("mmap error %d\n", (int)gpio_map);//errno also set!
exit(-1);
}

// Always use volatile pointer!
gpio = (volatile unsigned *)gpio_map;

} // setup_io

</pre>

====GPIO Pull Up/Pull Down Register Example====
<pre>
// enable pull-up on GPIO24&25
GPIO_PULL = 2;
short_wait();
// clock on GPIO 24 & 25 (bit 24 & 25 set)
GPIO_PULLCLK0 = 0x03000000;
short_wait();
GPIO_PULL = 0;
GPIO_PULLCLK0 = 0;
</pre>

====GPIO Driving Example (Python)====
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO
Any Python script that controls GPIO must be run as root.
<pre>import RPi.GPIO as GPIO

# Set up the GPIO channels - one input and one output
GPIO.setup(11, GPIO.IN)
GPIO.setup(12, GPIO.OUT)

# Input from pin 11
input_value = GPIO.input(11)

# Output to pin 12
GPIO.output(12, True)

# The same script as above but using BCM GPIO 00..nn numbers
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.IN)
GPIO.setup(18, GPIO.OUT)
input_value = GPIO.input(17)
GPIO.output(18, True)</pre>

====GPIO Driving Example (Java using the Pi4J Library)====
This uses the Java library available at http://www.pi4j.com/.
(Any Java application that controls GPIO must be run as root.)

Please note that the Pi4J library uses the WiringPi GPIO pin numbering scheme <ref>http://pi4j.com/usage.html#Pin_Numbering</ref> <ref>https://projects.drogon.net/raspberry-pi/wiringpi/pins/</ref>. Please see the usage documentation for more details: http://pi4j.com/usage.html

<pre>

public static void main(String[] args) {

// create gpio controller
GpioController gpio = GpioFactory.getInstance();

// provision gpio pin #01 as an output pin and turn off
GpioPinDigitalOutput outputPin = gpio.provisionDigitalOutputPin(RaspiPin.GPIO_01, "MyLED", PinState.LOW);

// turn output to LOW/OFF state
outputPin.low();

// turn output to HIGH/ON state
outputPin.high();

// provision gpio pin #02 as an input pin with its internal pull down resistor enabled
GpioPinDigitalInput inputPin = gpio.provisionDigitalInputPin(RaspiPin.GPIO_02, "MyButton", PinPullResistance.PULL_DOWN);

// get input state from pin 2
boolean input_value = inputPin.isHigh();
}
</pre>

More complete and detailed examples are included on the Pi4J website at http://www.pi4j.com/.

The Pi4J library includes support for:
* GPIO Control
* GPIO Listeners
* Serial Communication
* I2C Communication
* SPI Communication

====GPIO Driving Example (Java)====
This uses the Java library available at https://github.com/jkransen/framboos. It does not depend on (or use) the wiringPi driver, but uses the same numbering scheme. Instead it uses the default driver under /sys/class/gpio that ships with the distro, so it works out of the box. Any Java application that controls GPIO must be run as root.
<pre>
public static void main(String[] args) {
// reading from an in pin
InPin button = new InPin(8);
boolean isButtonPressed = button.getValue();
button.close();

// writing to an out pin
OutPin led = new Outpin(0);
led.setValue(true);
led.setValue(false);
led.close();
}
</pre>

====GPIO Driving Example (Java Webapp GPIO web control via http)====
This uses the Java Webapp available at https://bitbucket.org/sbub/raspberry-pi-gpio-web-control/overview. You can control your GPIO over the internet. Any Java application that controls GPIO must be run as root.
<pre>

host:~ sb$ curl 'http://raspberrypi:8080/handle?g0=1&g1=0'
{"g1":0,"g0":1}

</pre>

====GPIO Driving Example (Bash shell script, using sysfs, part of the raspbian operating system)====
The export and unexport of pins must be done as root.
To change to the root user see below: To change back, the word exit must be entered.
<pre>sudo -i</pre>
Export creates a new folder for the exported pin, and creates files for each of its control functions (i.e. active_low, direction, edge, power, subsystem, uevent, and value). Upon creation, the control files can be read by all users (not just root), but can only be written to by user root, the file's owner. Nevertheless, once created, it is possible to allow users other than root, to also write inputs to the control files, by changing the ownership or permissions of these files. Changes to the file's ownership or permissions must initially be done as root, as their owner and group is set to root upon creation. Typically you might change the owner to be the (non root) user controlling the GPIO, or you might add write permission, and change the group ownership to one of which the user controlling the GPIO is a member. By such means, using only packages provided in the recommended rasbian distribution, it is possible for Python CGI scripts, which are typically run as user nobody, to be used for control of the GPIO over the internet from a browser at a remote location.
<pre>
#!/bin/sh

# GPIO numbers should be from this list
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25

# Note that the GPIO numbers that you program here refer to the pins
# of the BCM2835 and *not* the numbers on the pin header.
# So, if you want to activate GPIO7 on the header you should be
# using GPIO4 in this script. Likewise if you want to activate GPIO0
# on the header you should be using GPIO17 here.

# Set up GPIO 4 and set to output
echo "4" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio4/direction

# Set up GPIO 7 and set to input
echo "7" > /sys/class/gpio/export
echo "in" > /sys/class/gpio/gpio7/direction

# Write output
echo "1" > /sys/class/gpio/gpio4/value

# Read from input
cat /sys/class/gpio/gpio7/value

# Clean up
echo "4" > /sys/class/gpio/unexport
echo "7" > /sys/class/gpio/unexport
</pre>

====GPIO Driving Example (Shell script - take 2)====
You need the wiringPi library from
https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/. Once installed, there is a new command '''gpio''' which can be used
as a '''non-root''' user to control the GPIO pins.

The man page <pre>man gpio</pre> has full details, but briefly:

<pre>
gpio -g mode 17 out
gpio -g mode 18 pwm

gpio -g write 17 1
gpio -g pwm 18 512
</pre>

The '''-g''' flag tells the '''gpio''' program to use the BCM GPIO pin numbering
scheme (otherwise it will use the wiringPi numbering scheme by default).

The gpio command can also control the internal pull-up and pull-down
resistors:

<pre>
gpio -g mode 17 up
</pre>

This sets the pull-up resistor - however any change of mode, even
setting a pin that's already set as an input to an input will remove
the pull-up/pull-down resistors, so they may need to be reset.

Additionally, it can export/un-export the GPIO devices for use by
other non-root programms - e.g. Python scripts. (Although you
may need to drop the calls to GPIO.Setup() in the Python scripts, and
do the setup separately in a little shell script, or call the '''gpio''' program
from inside Python).

<pre>
gpio export 17 out
gpio export 18 in
</pre>

These exports GPIO-17 and sets it to output, and exports GPIO-18
and sets it to input.

And when done:

<pre>
gpio unexport 17
</pre>

The export/unexport commands always use the BCM GPIO pin numbers regardless of the
presence of the '''-g''' flag or not.

If you want to use the internal pull-up/down's with the /sys/class/gpio mechanisms,
then you can set them after exporting them. So:

<pre>
gpio -g export 4 in
gpio -g mode 4 up
</pre>

You can then use GPIO-4 as an input in your Python, Shell, Java, etc. programs without the use
of an external resistor to pull the pin high. (If that's what you were after - for example, a simple push
button switch taking the pin to ground.)

A fully working example of a shell script using the GPIO pins
can be found at http://project-downloads.drogon.net/files/gpioExamples/tuxx.sh.

====GPIO Driving Example (Lazarus / Free Pascal)====
[[File:RPI GPIO testprogram with lazarus.png|thumb|254px|right|A simple app for controlling GPIO pin 17 with Lazarus]]

The GPIO pins are accessible from [[Lazarus on RPi|Lazarus]] without any third-party software. This is performed by means of invoking Unix shell commands with '''fpsystem'''. The following example uses GPIO pin 17 as output port. It is assumed that you created a form with a TToggleBox named GPIO17ToggleBox and for logging purposes a TMemo with name LogMemo (optional). The program has to be executed with root privileges.

''Unit for controlling the GPIO port:''
<pre>
unit Unit1;

{Demo application for GPIO on Raspberry Pi}
{Inspired by the Python input/output demo application by Gareth Halfacree}
{written for the Raspberry Pi User Guide, ISBN 978-1-118-46446-5}

{$mode objfpc}{$H+}

interface

uses
Classes, SysUtils, FileUtil, Forms, Controls, Graphics, Dialogs, StdCtrls, Unix;

type

{ TForm1 }

TForm1 = class(TForm)
LogMemo: TMemo;
GPIO17ToggleBox: TToggleBox;
procedure FormActivate(Sender: TObject);
procedure FormClose(Sender: TObject; var CloseAction: TCloseAction);
procedure GPIO17ToggleBoxChange(Sender: TObject);
private
{ private declarations }
public
{ public declarations }
end;

var
Form1: TForm1;
gReturnCode: longint; {stores the result of the IO operation}

implementation

{$R *.lfm}

{ TForm1 }

procedure TForm1.FormActivate(Sender: TObject);
begin
{ Prepare SoC pin 17 (pin 11 on GPIO port) for access: }
gReturnCode := fpsystem('echo "17" > /sys/class/gpio/export');
LogMemo.Lines.Add(IntToStr(gReturnCode));
{ Set SoC pin 17 as output: }
gReturnCode := fpsystem('echo "out" > /sys/class/gpio/gpio17/direction');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;

procedure TForm1.FormClose(Sender: TObject; var CloseAction: TCloseAction);
begin
{ Free SoC pin 17: }
gReturnCode := fpsystem('echo "17" > /sys/class/gpio/unexport');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;

procedure TForm1.GPIO17ToggleBoxChange(Sender: TObject);
begin
if GPIO17ToggleBox.Checked then
begin
{ Swith SoC pin 17 on: }
gReturnCode := fpsystem('echo "1" > /sys/class/gpio/gpio17/value');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end
else
begin
{ Switch SoC pin 17 off: }
gReturnCode := fpsystem('echo "0" > /sys/class/gpio/gpio17/value');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;

end.
</pre>

''Main program:''
<pre>
program io_test;

{$mode objfpc}{$H+}

uses
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Interfaces, // this includes the LCL widgetset
Forms, Unit1
{ you can add units after this };

{$R *.res}

begin
Application.Initialize;
Application.CreateForm(TForm1, Form1);
Application.Run;
end.
</pre>

An alternative way to access the GPIO port with Lazarus / Free Pascal is by using [http://www.lazarus.freepascal.org/index.php/topic,17404.0.html Lazarus wrapper unit for Gordon Henderson's wiringPi C library].

====GPIO Driving Example (C + wiringPi)====
Get and install wiringPi: https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/

Save this, and compile with:
<pre>
gcc -o blink blink.c -lwiringPi
</pre>
and run with:
<pre>
sudo ./blink
</pre>

<pre>
/*
* blink.c:
* blinks the first LED
* Gordon Henderson, projects@drogon.net
*/

#include <stdio.h>
#include <wiringPi.h>

int main (void)
{
printf ("Raspberry Pi blink\n") ;

if (wiringPiSetup () == -1)
return 1 ;

pinMode (0, OUTPUT) ; // aka BCM_GPIO pin 17

for (;;)
{
digitalWrite (0, 1) ; // On
delay (500) ; // mS
digitalWrite (0, 0) ; // Off
delay (500) ;
}
return 0 ;
}
</pre>

====GPIO Driving Example (C)====
This must be done as root. To change to the root user:
<pre>sudo -i</pre>
You must also get and install the bcm2835 library, which supports
GPIO and SPI interfaces. Details and downloads
from http://www.open.com.au/mikem/bcm2835

<pre>

// blink.c
//
// Example program for bcm2835 library
// Blinks a pin on an off every 0.5 secs
//
// After installing bcm2835, you can build this
// with something like:
// gcc -o blink -l rt blink.c -l bcm2835
// sudo ./blink
//
// Or you can test it before installing with:
// gcc -o blink -l rt -I ../../src ../../src/bcm2835.c blink.c
// sudo ./blink
//
// Author: Mike McCauley (mikem@open.com.au)
// Copyright (C) 2011 Mike McCauley
// $Id: RF22.h,v 1.21 2012/05/30 01:51:25 mikem Exp $

#include <bcm2835.h>

// Blinks on RPi pin GPIO 11
#define PIN RPI_GPIO_P1_11

int main(int argc, char **argv)
{
// If you call this, it will not actually access the GPIO
// Use for testing
// bcm2835_set_debug(1);

if (!bcm2835_init())
return 1;

// Set the pin to be an output
bcm2835_gpio_fsel(PIN, BCM2835_GPIO_FSEL_OUTP);

// Blink
while (1)
{
// Turn it on
bcm2835_gpio_write(PIN, HIGH);

// wait a bit
delay(500);

// turn it off
bcm2835_gpio_write(PIN, LOW);

// wait a bit
delay(500);
}

return 0;
}
</pre>

====GPIO Driving Example (Perl)====
This must be done as root. To change to the root user:
<pre>sudo su -</pre>
Supports GPIO and SPI interfaces.
You must also get and install the bcm2835 library. Details and downloads
from http://www.open.com.au/mikem/bcm2835
You must then get and install the Device::BCM2835 perl library from CPAN
http://search.cpan.org/~mikem/Device-BCM2835-1.0/lib/Device/BCM2835.pm
<pre>
use Device::BCM2835;
use strict;

# call set_debug(1) to do a non-destructive test on non-RPi hardware
#Device::BCM2835::set_debug(1);
Device::BCM2835::init()
|| die "Could not init library";

# Blink pin 11:
# Set RPi pin 11 to be an output
Device::BCM2835::gpio_fsel(&Device::BCM2835::RPI_GPIO_P1_11,
&Device::BCM2835::BCM2835_GPIO_FSEL_OUTP);

while (1)
{
# Turn it on
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 1);
Device::BCM2835::delay(500); # Milliseconds
# Turn it off
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 0);
Device::BCM2835::delay(500); # Milliseconds
}

</pre>

==== GPIO Driving Example (C#) ====
RaspberryPiDotNet library is available at https://github.com/cypherkey/RaspberryPi.Net/.
The library includes a GPIOFile and GPIOMem class. The GPIOMem requires compiling Mike McCauley's bcm2835 library above in to a shared object.

<pre>
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using RaspberryPiDotNet;
using System.Threading;

namespace RaspPi
{
class Program
{
static void Main(string[] args)
{
// Access the GPIO pin using a static method
GPIOFile.Write(GPIO.GPIOPins.GPIO00, true);

// Create a new GPIO object
GPIOMem gpio = new GPIOMem(GPIO.GPIOPins.GPIO01);
gpio.Write(false);
}
}
}
</pre>

====GPIO Driving Example (Ruby)====

This example uses the WiringPi Ruby Gem: http://pi.gadgetoid.co.uk/post/015-wiringpi-now-with-serial which you can install on your Pi with "gem install wiringpi"

<pre>
MY_PIN = 1

require 'wiringpi'
io = WiringPi::GPIO.new
io.mode(MY_PIN,OUTPUT)
io.write(MY_PIN,HIGH)
io.read(MY_PIN)
</pre>

Alternatively the Pi Piper Gem (https://github.com/jwhitehorn/pi_piper) allows for event driven programming:

<pre>
require 'pi_piper'
include PiPiper

watch :pin => 23 do
puts "Pin changed from #{last_value} to #{value}"
end

PiPiper.wait
</pre>

====GPIO Driving Example (BASIC - Return to BASIC)====

'''RTB''' or Return to Basic can be found here: https://projects.drogon.net/return-to-basic/

It's a new BASIC featuring modern looping constructs, switch statements, named procedures and functions as well as graphics (caresian and turtle), file handling and more. It also supports the Pi's on-board GPIO without needing to be run as root. (You don't need any special setup routines either)

Sample blink program:

<pre>
// blink.rtb:
// Blink program in Return to Basic
// Gordon Henderson, projects@drogon.net
//
PinMode (0, 1) // Output
CYCLE
DigitalWrite (0, 1) // Pin 0 ON
WAIT (0.5) // 0.5 seconds
DigitalWrite (0, 0)
WAIT (0.5)
REPEAT
END
</pre>

====GPIO Driving Example (BASIC)====

'''Bywater BASIC Interpreter'''

The Bywater BASIC Interpreter (bwBASIC) implements a large superset of the ANSI Standard for Minimal BASIC (X3.60-1978) and a significant subset of the ANSI Standard for Full BASIC (X3.113-1987) in C. It also offers shell programming facilities as an extension of BASIC. bwBASIC seeks to be as portable as possible.
You can download it at.
http://packages.debian.org/stable/interpreters/bwbasic

'''BASIC programming of the I/O'''

'''Setting up a GPIO pin to be used for inputs or for outputs.'''

We cannot load the control words directly into the 32 bit ARM registers with 32 bit addresses, as bwBASIC has no POKE and PEEK commands and other versions of BASIC (as far as I know) only handle 8 bit registers with 16 bit addresses with these commands. So we need to export the GPIO pins, so that they exist in a file structure which we can access from basic with the OPEN command.(ref 2)

We need to do this in Linux root.
We need to run BASIC in the root too. First we go to the root, then we load bwbasic into root.
<pre>
sudo -1
sudo bwbasic
</pre>

REM Now to export the no4 GPIO pin for example, using a Shell command.

<pre>echo “4” > /sys/class/gpio/export</pre>

Whilst bwbasic can accommodate shell commands, and we can store a set of these commands (eg. to export a number of GPIO pins at the outset) as numbered statements in a file that can be loaded with the basic command LOAD “filename” and RUN (ref 2), the shell commands have to run as a separate file, as they cannot be run from within, as part of a basic programme.

'''Now we can access the file containing the pin direction setting from BASIC'''

We can set GPIO pin 4 to input or to output by OPENing its pin direction file for output and writing “in” or “out” with a PRINT# command. (ref 2 )
<syntaxhighlight lang="basic4gl">
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 PRINT #1,”out”
30 CLOSE #1
</syntaxhighlight>

REM closes the open direction file, whereupon the system performs the action of setting the direction to “out”. NB the system only carries out the action as the file is closed.(ref 3)

'''We are now able to control the output of the gpio 4 pin from BASIC'''

We can set the GPIO 4 pin to 1 or to 0 by OPENing its pin value file for output and writing “1” or “0” with a PRINT# command.
<syntaxhighlight lang="basic4gl">
40 OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
50 PRINT #4,”1”
60 CLOSE #4
</syntaxhighlight>

REM turns on the output of GPIO pin 4.

REM similarly we can turn off the output of GPIO pin 4.
OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
PRINT #4,”0”
CLOSE #4.

'''Example of an (unstructured) BASIC programme'''

To read the state of a switch and control the power to two LEDs connected to GPIO pins 8,7 and 4 respectively.

Programme to set 2 pins as outputs and 1 pin as input and to read the input turning on two different combinations of the two outputs (ie output 0,1 or 1,0) depending on the state of the input (1 or 0).
<syntaxhighlight lang="basic4gl">
sudo –i
sudo bwbasic
LOAD “export.bas”
LIST
REM a set of Shell statements to export the three GPIO pins.
10 echo “4” > /sys/class/gpio/export
20 echo “7” > /sys/class/gpio/export
30 echo “8” > /sys/class/gpio/export
RUN
</syntaxhighlight>

NEW REM clears the export.bas programme from memory
<syntaxhighlight lang="basic4gl">
.
LOAD “demo1.bas”
LIST
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 OPEN ”O”,#2, “/sys/devices/virtual/gpio/gpio7/direction”,2
30 OPEN ”O”,#3, “/sys/devices/virtual/gpio/gpio8/direction”,2
REM opens the three pin direction files
40 PRINT #1, “out”
50 PRINT #2, “out”
60 PRINT #3, “in”
REM sets GPIO pins 4 and 7 as outputs and GPIO pin 8 as input.
70 CLOSE #1
80 CLOSE #2
90 CLOSE #3
REM closes all open files, allowing the system to perform the direction settings.
100 OPEN ”I”,#8, “/sys/devices/virtual/gpio/gpio8/value”,1
REM opens the GPIO pin 8 value file
110 INPUT #8,x
REM reads the value of the input pin and stores the value in numerical variable x
120 CLOSE #8
REM closes the open file, allowing the system to read the value of the input pin and store the value in numerical variable x.
130 OPEN “O”,#1, “/sys/devices/virtual/gpio/gpio4/value”,1
140 OPEN “O”,#2, “/sys/devices/virtual/gpio/gpio7/value”,1
REM opens the GPIO pins 4 and value files ready for outputting 1s and 0s.
150 IF x<1 THEN GOTO 160 ELSE GOTO 190
REM tests the state of the switch (1 or0) and directs the program to generate the appropriate outputs
160 PRINT #1,”1”
170 PRINT #2,”0”
180 GOTO 210
190 PRINT#1,"0"
200 PRINT #2,"1"
210 CLOSE #1
220 CLOSE #2
REM Closes the files and allows the outputs to light the LED
230 END.
</syntaxhighlight>

When all is done, we should unexport the GPIO pins, to leave the R-Pi as we found it.(Ref 1.)
<syntaxhighlight lang="basic4gl">
NEW
LOAD “unexport.bas”
LIST
REM a set of Shell statements to unexport the three GPIO pins.
10 echo “4” > /sys/class/gpio/unexport
20 echo “7” > /sys/class/gpio/unexport
30 echo “8” > /sys/class/gpio/unexport
RUN
</syntaxhighlight>
A simple circuit to provide the switched input and the two LED outputs.

Ancient Mariner. Dec. 2012

References.

1. This paper RPi Low-level peripherals.

2. Ed Beynon. [http://www.ybw.com/forums/showthread.php?t=331320&page=5 http://www.ybw.com/forums/showthread.php?t=331320&page=5]

3. Arthur Kaletzky. Private communication. 25/10/2012

4. bwbasic manual.<br/>

For the two original documents this example has been copied from see:<br/>
[[Media:GPIO_Driving_Example_(BASIC)_.doc | GPIO_Driving_Example_(BASIC)_.doc]]

[[Media:Raspberry_Pi_I-O_viii.doc | Raspberry_Pi_I-O_viii.doc]]

==MIPI CSI-2==

On the production board<ref>http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf</ref>, the Raspberry Pi Foundation design brings out the MIPI CSI-2 (Camera Serial Interface<ref>http://www.mipi.org/specifications/camera-interface</ref>) to a 15-way flat flex connector S5, between the Ethernet and HDMI connectors. A compatible camera has been discussed as working in tests and is planned for release at a later date.<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/complex-camera-peripherials#p72602</ref>.


==DSI==

On the production board, the Raspberry Pi Foundation design brings out the DSI (Display Serial Interface<ref>http://www.mipi.org/specifications/display-interface</ref>) to a 15-way flat flex connector labelled S2, next to Raspberry Pi logo. It has two data lanes and a clock lane, to drive a possible future LCD screen device. Some smart phone screens use DSI<ref>http://en.wikipedia.org/wiki/Display_Serial_Interface</ref>.

==CEC==

[[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.
Eben notes that he has seen CEC demos on the Broadcom SoC they are using.

libCEC with Raspberry Pi support has been included in OpenELEC and will be included in Raspbmc RC4.<ref>http://blog.pulse-eight.com/2012/08/01/libcec-1-8-0-a-firmware-upgrade-and-raspberry-pi-support/</ref>

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.

== References ==
<references/>

{{Template:Raspberry Pi}}

RPi Low-level peripherals

2013-02-22T02:05:35Z

AndrewS: /* General Purpose Input/Output (GPIO) */ Table-ified the P5 header pinout

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

==Introduction==
In addition to the familiar USB, Ethernet and HDMI ports, the R-Pi offers lower-level interfaces intended to connect more directly with chips and subsystem modules. These GPIO (general purpose I/O) signals on the 2x13 header pins include SPI, I2C, serial UART, 3V3 and 5V power. These interfaces are not "plug and play" and require care to avoid miswiring. The pins use a 3V3 logic level and are not tolerant of 5V levels, such as you might find on a 5V powered Arduino. Not yet software-enabled are the flex cable connectors with CSI (camera serial interface) and DSI (display serial interface), and a serial link inside the HDMI connector called CEC. (consumer electronics control)

==General Purpose Input/Output (GPIO)==
[[File:GPIOs.png|thumb|254px|right|The layout of the Raspberry Pi Revision 1 P1 pin-header seen from the top, containing pins useable for general purpose I/O. Colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs2.gif Source] ]]

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.

The Raspberry Pi allows peripherals and expansion boards (such as the [[Rpi Gertboard]]) to access the CPU by exposing the inputs and outputs.

For further general information about GPIOs, see: [http://en.wikipedia.org/wiki/GPIO the wikipedia article].<BR>
For further specific information about the Raspberry Pi's BCM2835 GPIOs, see: [[RPi_BCM2835_GPIOs|this wiki article]].

The production Raspberry Pi board has a 26-pin 2.54 mm (100 mil)<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907</ref> expansion header, marked as P1, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I²C, SPI, UART), as well as +3.3 V, +5 V and GND supply lines. Pin one is the pin in the first column and on the bottom row. <ref>http://www.raspberrypi.org/archives/384</ref>

'''GPIO voltage levels are 3.3 V and are not 5 V 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.

All the GPIO pins can be reconfigured to provide alternate functions, SPI, [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM], I²C and so. At reset only pins GPIO 14 & 15 are assigned to the alternate function UART, these two can be switched back to GPIO to provide a total of 17 GPIO pins<ref>http://www.raspberrypi.org/archives/384</ref>. Each of their functions and full details of how to access are detailed in the chipset datasheet <ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref>.

Each GPIO can interrupt, high/low/rise/fall/change.<ref>http://www.raspberrypi.org/archives/384#comment-5217</ref><ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref> There is currently no support for GPIO interrupts in the official kernel, howewer a patch exists, requiring compilation of modified source tree.<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=44&t=7509</ref> The 'Raspbian "wheezy"' <ref>http://www.raspberrypi.org/downloads</ref> version that is currently recommended for starters already includes GPIO interrupts.

GPIO input hysteresis (Schmitt trigger) can be on or off, output slew rate can be fast or limited, and source and sink current is configurable from 2 mA up to 16 mA. Note that chipset GPIO pins 0-27 are in the same block and these properties are set per block, not per pin. See [http://www.scribd.com/doc/101830961/GPIO-Pads-Control2 GPIO Datasheet Addendum - GPIO Pads Control]. Particular attention should be applied to the note regarding SSO (Simultaneous Switching Outputs): to avoid interference, driving currents should be kept as low as possible.

The available [[RPi_BCM2835_GPIOs|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.

There is also some information on the [[RPi Tutorial Easy GPIO Hardware & Software|Tutorial on Easy GPIO Hardware & Software]].

Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200 bit/s.

'''R-Pi PCB Revision 2 UPDATE:''' According to Eben at [http://www.raspberrypi.org/archives/1929#comment-31646] the R-Pi Rev.2 board being rolled out starting in September 2012 adds 4 more GPIO on a new connector called P5, and changes some of the existing P1 GPIO pinouts. On Rev2, GPIO_GEN2 [BCM2835/GPIO27] is routed to P1 pin 13, and changes what was SCL0/SDA0 to SCL1/SDA1: SCL1 [BCM2835/GPIO3] is routed to P1 pin 5, SDA1 [BCM2835/GPIO2] is routed to P1 pin 3. Also the power and ground connections previously marked "Do Not Connect" on P1 will remain as connected, specifically: P1-04:+5V0, P1-09:GND, P1-14:GND, P1-17:+3V3, P1-20:GND, P1-25:GND. According to this comment [http://www.raspberrypi.org/archives/2081#comment-33577] (and confirmed in this post [http://www.raspberrypi.org/archives/2233]) the P1 pinout is not expected to change in future beyond the current Rev.2 layout.

'''Header Pinout, top row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-02 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-04 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-06 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
|-
| P1-08 || bgcolor="lime" | GPIO 14 || bgcolor="lime" | GPIO 14 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_TXD || ALT5 = UART1_TXD
|-
| P1-10 || bgcolor="lime" | GPIO 15 || bgcolor="lime" | GPIO 15 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_RXD || ALT5 = UART1_RXD
|-
| P1-12 || bgcolor="lime" | GPIO 18 || bgcolor="lime" | GPIO 18 || || PCM_CLK || ALT4 = SPI1_CE0_N ALT5 = PWM0
|-
| P1-14 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-16 || bgcolor="lime" | GPIO23 || bgcolor="lime" | GPIO23 || || || ALT3 = SD1_CMD ALT4 = ARM_RTCK
|-
| P1-18 || bgcolor="lime" | GPIO24 || bgcolor="lime" | GPIO24 || || || ALT3 = SD1_DAT0 ALT4 = ARM_TDO
|-
| P1-20 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-22 || bgcolor="lime" | GPIO25 || bgcolor="lime" | GPIO25 || || || ALT3 = SD1_DAT1 ALT4 = ARM_TCK
|-
| P1-24 || bgcolor="lime" | GPIO08 || bgcolor="lime" | GPIO08 || || bgcolor="purple" | <span style="color:white">SPI0_CE0_N</span> ||
|-
| P1-26 || bgcolor="lime" | GPIO07 || bgcolor="lime" | GPIO07 || || bgcolor="purple" | <span style="color:white">SPI0_CE1_N</span> ||
|}

'''Header Pinout, bottom row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-01 || bgcolor="orange" | 3.3 V ||bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-03 || bgcolor="lime" | GPIO 0 || bgcolor="lime" | '''GPIO 2'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SDA / '''I2C1_SDA''' ||
|-
| P1-05 || bgcolor="lime" | GPIO 1 || bgcolor="lime" | '''GPIO 3'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SCL / '''I2C1_SCL''' ||
|-
| P1-07 || bgcolor="lime" | GPIO 4 || bgcolor="lime" | GPIO 4 || || GPCLK0 || ALT5 = ARM_TDI
|-
| P1-09 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-11 || bgcolor="lime" | GPIO17 || bgcolor="lime" | GPIO17 || || ||| ALT3 = UART0_RTS ALT4 = SPI1_CE1_N ALT5 = UART1_RTS
|-
| P1-13 || bgcolor="lime" | GPIO21 || bgcolor="lime" | '''GPIO27''' || || PCM_DOUT / '''reserved''' || ALT4 = SPI1_SCLK ALT5 = GPCLK1 / '''ALT3 = SD1_DAT3 ALT4 = ARM_TMS'''
|-
| P1-15 || bgcolor="lime" | GPIO22 || bgcolor="lime" | GPIO22 || || || ALT3 = SD1_CLK ALT4 = ARM_TRST
|-
| P1-17 || bgcolor="orange" | 3.3 V || bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-19 || bgcolor="lime" | GPIO10 || bgcolor="lime" | GPIO10 || || bgcolor="purple" | <span style="color:white">SPI0_MOSI</span> ||
|-
| P1-21 || bgcolor="lime" | GPIO9 || bgcolor="lime" | GPIO9 || || bgcolor="purple" | <span style="color:white">SPI0_MISO</span> ||
|-
| P1-23 || bgcolor="lime" | GPIO11 || bgcolor="lime" | GPIO11 || || bgcolor="purple" | <span style="color:white">SPI0_SCLK</span> ||
|-
| P1-25 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|}

{| border="1"
! Colour legend
|-
| bgcolor="red" | <span style="color:white">+5 V</span>
|-
| bgcolor="orange" | +3.3 V
|-
| bgcolor="black" | <span style="color:white">Ground, 0V</span>
|-
| bgcolor="yellow" | UART
|-
| bgcolor="lime" | GPIO
|-
| bgcolor="purple" | <span style="color:white">SPI</span>
|-
| bgcolor="cyan" | I²C
|}

KiCad symbol: [[File:Conn-raspberry.lib]]

<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2</ref>

Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as an I²C interface. So there are 1.8 kilohm pulls up resistors on the board for these pins.<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480</ref>

Pin 12 supports [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM] .

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.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.1</ref> 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.

It is also possible to reconfigure GPIO connector pins P1-12 and 13 (chipset GPIO 18 and 21) to provide an I2S (a hardware modification may be required<ref name="I2S">[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?]</ref>) or PCM interface.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.2</ref> However, PCM_FS and PCM_DIN (chipset pins 19 and 20) are needed for I2S or PCM.

A second I²C 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.

===Referring to pins on the Expansion header===

The header is referred to as "The GPIO Connector (P1)". To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended.

* The expansion header is referred to as "Expansion Header" or "GPIO Connector (P1)"
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.
* Names GPIO0, GPIO1, GPIOx-ALTy, etc. refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where "x" matches BCM2835 number (without leading zero) and "y" 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 "GPIO7" to refer to a row of the table, and "GPIO7-ALT0" would refer to a specific cell of the table.
* 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 "SPI0_*" and "SPI1_*", but they didn't do the same on the I²C and UART pins. Instead of using "SDA0" and "SCL0", you should use "I2C0_SDA" and "I2C0_SCL"; and instead of "TX" or "TXD" and "RX" or "RXD", you should use "UART0_TXD" and "UART0_RXD".

===Power pins===
The maximum permitted current draw from the 3.3 V pins is 50 mA.

Maximum permitted current draw from the 5 V pin is the USB input current (usually 1 A) minus any current draw from the rest of the board.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1536#postid-21841</ref>
*Model A: 1000 mA - 500 mA -> max current draw: 500 mA
*Model B: 1000 mA - 700 mA -> max current draw: 300 mA
Be very careful with the 5 V pins P1-02 and P1-04, because if you short 5 V to any other P1 pin you may permanently damage your RasPi. Before probing P1, it's a good idea to strip short pieces of insulation off a wire and push them over the 5 V pins so you don't accidentally short them with a probe.

=== GPIO hardware hacking ===

The complete list of [[RPi_BCM2835_GPIOs|chipset GPIO pins]] which are available on the GPIO connector is: <blockquote>[[RPi_BCM2835_GPIOs#GPIO0|0]], [[RPi_BCM2835_GPIOs#GPIO1|1]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO21|21]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]]</blockquote>

(on the Revision2.0 RaspberryPis, this list changes to: [[RPi_BCM2835_GPIOs#GPIO2|2]], [[RPi_BCM2835_GPIOs#GPIO3|3]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]], [[RPi_BCM2835_GPIOs#GPIO27|27]], with [[RPi_BCM2835_GPIOs#GPIO28|28]], [[RPi_BCM2835_GPIOs#GPIO29|29]], [[RPi_BCM2835_GPIOs#GPIO30|30]], [[RPi_BCM2835_GPIOs#GPIO31|31]] additionally available on the [[#P5_header|P5 header]])

As noted above, GPIO00 and 01 (SDA0 and SCL0) have 1.8 kilohm pull-up resistors to 3.3 V.

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:

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 3.3 V.

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.

There are a few other chipset GPIO pins accessible on the PCB but are in use:

* GPIO16 drives status LED D5 (usually SD card access indicator)
* GPIO28-31 are used by the board ID and are connected to resistors R3 to R10 (only on Rev1.0 boards).
* GPIO40 and 45 are used by analogue audio and support [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM]. They connect to the analogue audio circuitry via R21 and R27 respectively.
* GPIO46 is HDMI hotplug detect (goes to pin 6 of IC1).
* 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.

=== P2 header ===

The P2 header is the VideoCore JTAG and used only during the production of the board. It cannot be used as the ARM JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>. This connector is unpopulated in Rev 2.0 boards.

Useful P2 pins:

* Pin 1 - 3.3V (same as P1-01, 50 mA max current draw across both of them)
* Pin 7 - GND
* Pin 8 - GND

=== P3 header ===

The P3 header, unpopulated, is the LAN9512 JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>.

=== P5 header ===

The P5 header was added with the release of the Revision 2.0 PCB design.

'''P5 Pinout, seen from the bottom of the board:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P5-01 || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P5-02 || bgcolor="orange" | 3.3 V || 50 mA max (combined with P1)
|-
| P5-03 || bgcolor="lime" | GPIO28 || || bgcolor="cyan" | I2C0_SDA || ALT2 = PCM_CLK
|-
| P5-04 || bgcolor="lime" | GPIO29 || || bgcolor="cyan" | I2C0_SCL || ALT2 = PCM_FS
|-
| P5-05 || bgcolor="lime" | GPIO30 || || || ALT2 = PCM_DIN ALT3 = UART0_CTS ALT5 = UART1_CTS
|-
| P5-06 || bgcolor="lime" | GPIO31 || || || ALT2 = PCM_DOUT ALT3 = UART0_RTS ALT5 = UART1_RTS
|-
| P5-07 || bgcolor="black" | <span style="color:white">GND</span>
|-
| P5-08 || bgcolor="black" | <span style="color:white">GND</span>
|}

Note that the connector is intended to be mounted on the '''bottom''' of the PCB, so that for those who put the connector on the top side, the pin numbers are swapped. Pin 1 and pin 2 are swapped, pin 3 and 4, etc.

The new header can provide a second I2C channel (SDA + SCL) and handshake lines for the existing UART (TxD and RxD), or it can be used for an I2S (audio codec chip) interface using the PCM signals CLK, FS (Frame Sync), Din and Dout.

Note that the connector is placed JUST off-grid with respect to the P1 connector.

=== P6 header ===

The P6 header was added with the release of the Revision 2.0 PCB design.

[http://raspi.tv/2012/making-a-reset-switch-for-your-rev-2-raspberry-pi A reset button can be attached to the P6 header], with which the Pi can be reset.
Momentarily shorting the two pins of P6 together will cause a soft reset of the CPU.

===Driver support===

The Foundation will not include a GPIO driver in the initial release, standard Linux GPIO drivers should work with minimal modification.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1278.0</ref>

The community implemented SPI and I²C drivers <ref>http://www.bootc.net/projects/raspberry-pi-kernel/</ref>, which will be integrated with the new Linux pinctrl concept in a later version of the kernel. (On Oct. 14 2012, it was already included in the latest raspbian image.) A first compiled version as Linux modules is available to install on the 19/04/2012 Debian image, including 1-wire support<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=86172#p86172</ref>. The I²C and SPI driver uses the hardware modules of the microcontroller and interrupts for low CPU usage, the 1-wire support uses bitbanging on the GPIO ports, which results in higher CPU usage.

GordonH<ref>http://www.raspberrypi.org/forum/general-discussion/wiring-for-the-raspberry-pis-gpio</ref> wrote a (mostly) Arduino compatible/style [https://projects.drogon.net/raspberry-pi/wiringpi/ WiringPi library] in C for controlling the GPIO pins.

A useful tutorial on setting up I²C driver support can be found at [http://www.robot-electronics.co.uk/htm/raspberry_pi_examples.htm Robot Electronics] - look for the downloadable document rpi_i2c_setup.doc

===Graphical User Interfaces===
====WebIOPi====
[http://code.google.com/p/webiopi/ WebIOPi] allows you to control each GPIO with a simple web interface that you can use with any browser. Available in PHP and Python, they both require root access, but Python version serves HTTP itself. You can setup each GPIO as input or output and change their states (LOW/HIGH). WebIOPi is fully customizable, so you can use it for home remote control. It also work over Internet. UART/SPI/I2C support will be added later. If you need some computing for your GPIO go to code examples below.

==GPIO Code examples==
====GPIO Driving Example (C)====
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo & Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)
Example GPIO code:

<pre>
//
// How to access GPIO registers from C-code on the Raspberry-Pi
// Example program
// 15-January-2012
// Dom and Gert
// Revised: 15-Feb-2013

// Access from ARM Running Linux

#define BCM2708_PERI_BASE 0x20000000
#define GPIO_BASE (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/mman.h>
#include <unistd.h>

#define PAGE_SIZE (4*1024)
#define BLOCK_SIZE (4*1024)

int mem_fd;
void *gpio_map;

// I/O access
volatile unsigned *gpio;

// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)
#define INP_GPIO(g) *(gpio+((g)/10)) &= ~(7<<(((g)%10)*3))
#define OUT_GPIO(g) *(gpio+((g)/10)) |= (1<<(((g)%10)*3))
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)<=3?(a)+4:(a)==4?3:2)<<(((g)%10)*3))

#define GPIO_SET *(gpio+7) // sets bits which are 1 ignores bits which are 0
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0

void setup_io();

int main(int argc, char **argv)
{
int g,rep;

// Set up gpi pointer for direct register access
setup_io();

// Switch GPIO 7..11 to output mode

/************************************************************************\
* You are about to change the GPIO settings of your computer. *
* Mess this up and it will stop working! *
* It might be a good idea to 'sync' before running this program *
* so at least you still have your code changes written to the SD-card! *
\************************************************************************/

// Set GPIO pins 7-11 to output
for (g=7; g<=11; g++)
{
INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO
OUT_GPIO(g);
}

for (rep=0; rep<10; rep++)
{
for (g=7; g<=11; g++)
{
GPIO_SET = 1<<g;
sleep(1);
}
for (g=7; g<=11; g++)
{
GPIO_CLR = 1<<g;
sleep(1);
}
}

return 0;

} // main

//
// Set up a memory regions to access GPIO
//
void setup_io()
{
/* open /dev/mem */
if ((mem_fd = open("/dev/mem", O_RDWR|O_SYNC) ) < 0) {
printf("can't open /dev/mem \n");
exit(-1);
}

/* mmap GPIO */
gpio_map = mmap(
NULL, //Any adddress in our space will do
BLOCK_SIZE, //Map length
PROT_READ|PROT_WRITE,// Enable reading & writting to mapped memory
MAP_SHARED, //Shared with other processes
mem_fd, //File to map
GPIO_BASE //Offset to GPIO peripheral
);

close(mem_fd); //No need to keep mem_fd open after mmap

if (gpio_map == MAP_FAILED) {
printf("mmap error %d\n", (int)gpio_map);//errno also set!
exit(-1);
}

// Always use volatile pointer!
gpio = (volatile unsigned *)gpio_map;

} // setup_io

</pre>

====GPIO Pull Up/Pull Down Register Example====
<pre>
// enable pull-up on GPIO24&25
GPIO_PULL = 2;
short_wait();
// clock on GPIO 24 & 25 (bit 24 & 25 set)
GPIO_PULLCLK0 = 0x03000000;
short_wait();
GPIO_PULL = 0;
GPIO_PULLCLK0 = 0;
</pre>

====GPIO Driving Example (Python)====
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO
Any Python script that controls GPIO must be run as root.
<pre>import RPi.GPIO as GPIO

# Set up the GPIO channels - one input and one output
GPIO.setup(11, GPIO.IN)
GPIO.setup(12, GPIO.OUT)

# Input from pin 11
input_value = GPIO.input(11)

# Output to pin 12
GPIO.output(12, True)

# The same script as above but using BCM GPIO 00..nn numbers
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.IN)
GPIO.setup(18, GPIO.OUT)
input_value = GPIO.input(17)
GPIO.output(18, True)</pre>

====GPIO Driving Example (Java using the Pi4J Library)====
This uses the Java library available at http://www.pi4j.com/.
(Any Java application that controls GPIO must be run as root.)

Please note that the Pi4J library uses the WiringPi GPIO pin numbering scheme <ref>http://pi4j.com/usage.html#Pin_Numbering</ref> <ref>https://projects.drogon.net/raspberry-pi/wiringpi/pins/</ref>. Please see the usage documentation for more details: http://pi4j.com/usage.html

<pre>

public static void main(String[] args) {

// create gpio controller
GpioController gpio = GpioFactory.getInstance();

// provision gpio pin #01 as an output pin and turn off
GpioPinDigitalOutput outputPin = gpio.provisionDigitalOutputPin(RaspiPin.GPIO_01, "MyLED", PinState.LOW);

// turn output to LOW/OFF state
outputPin.low();

// turn output to HIGH/ON state
outputPin.high();

// provision gpio pin #02 as an input pin with its internal pull down resistor enabled
GpioPinDigitalInput inputPin = gpio.provisionDigitalInputPin(RaspiPin.GPIO_02, "MyButton", PinPullResistance.PULL_DOWN);

// get input state from pin 2
boolean input_value = inputPin.isHigh();
}
</pre>

More complete and detailed examples are included on the Pi4J website at http://www.pi4j.com/.

The Pi4J library includes support for:
* GPIO Control
* GPIO Listeners
* Serial Communication
* I2C Communication
* SPI Communication

====GPIO Driving Example (Java)====
This uses the Java library available at https://github.com/jkransen/framboos. It does not depend on (or use) the wiringPi driver, but uses the same numbering scheme. Instead it uses the default driver under /sys/class/gpio that ships with the distro, so it works out of the box. Any Java application that controls GPIO must be run as root.
<pre>
public static void main(String[] args) {
// reading from an in pin
InPin button = new InPin(8);
boolean isButtonPressed = button.getValue();
button.close();

// writing to an out pin
OutPin led = new Outpin(0);
led.setValue(true);
led.setValue(false);
led.close();
}
</pre>

====GPIO Driving Example (Java Webapp GPIO web control via http)====
This uses the Java Webapp available at https://bitbucket.org/sbub/raspberry-pi-gpio-web-control/overview. You can control your GPIO over the internet. Any Java application that controls GPIO must be run as root.
<pre>

host:~ sb$ curl 'http://raspberrypi:8080/handle?g0=1&g1=0'
{"g1":0,"g0":1}

</pre>

====GPIO Driving Example (Bash shell script, using sysfs, part of the raspbian operating system)====
The export and unexport of pins must be done as root.
To change to the root user see below: To change back, the word exit must be entered.
<pre>sudo -i</pre>
Export creates a new folder for the exported pin, and creates files for each of its control functions (i.e. active_low, direction, edge, power, subsystem, uevent, and value). Upon creation, the control files can be read by all users (not just root), but can only be written to by user root, the file's owner. Nevertheless, once created, it is possible to allow users other than root, to also write inputs to the control files, by changing the ownership or permissions of these files. Changes to the file's ownership or permissions must initially be done as root, as their owner and group is set to root upon creation. Typically you might change the owner to be the (non root) user controlling the GPIO, or you might add write permission, and change the group ownership to one of which the user controlling the GPIO is a member. By such means, using only packages provided in the recommended rasbian distribution, it is possible for Python CGI scripts, which are typically run as user nobody, to be used for control of the GPIO over the internet from a browser at a remote location.
<pre>
#!/bin/sh

# GPIO numbers should be from this list
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25

# Note that the GPIO numbers that you program here refer to the pins
# of the BCM2835 and *not* the numbers on the pin header.
# So, if you want to activate GPIO7 on the header you should be
# using GPIO4 in this script. Likewise if you want to activate GPIO0
# on the header you should be using GPIO17 here.

# Set up GPIO 4 and set to output
echo "4" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio4/direction

# Set up GPIO 7 and set to input
echo "7" > /sys/class/gpio/export
echo "in" > /sys/class/gpio/gpio7/direction

# Write output
echo "1" > /sys/class/gpio/gpio4/value

# Read from input
cat /sys/class/gpio/gpio7/value

# Clean up
echo "4" > /sys/class/gpio/unexport
echo "7" > /sys/class/gpio/unexport
</pre>

====GPIO Driving Example (Shell script - take 2)====
You need the wiringPi library from
https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/. Once installed, there is a new command '''gpio''' which can be used
as a '''non-root''' user to control the GPIO pins.

The man page <pre>man gpio</pre> has full details, but briefly:

<pre>
gpio -g mode 17 out
gpio -g mode 18 pwm

gpio -g write 17 1
gpio -g pwm 18 512
</pre>

The '''-g''' flag tells the '''gpio''' program to use the BCM GPIO pin numbering
scheme (otherwise it will use the wiringPi numbering scheme by default).

The gpio command can also control the internal pull-up and pull-down
resistors:

<pre>
gpio -g mode 17 up
</pre>

This sets the pull-up resistor - however any change of mode, even
setting a pin that's already set as an input to an input will remove
the pull-up/pull-down resistors, so they may need to be reset.

Additionally, it can export/un-export the GPIO devices for use by
other non-root programms - e.g. Python scripts. (Although you
may need to drop the calls to GPIO.Setup() in the Python scripts, and
do the setup separately in a little shell script, or call the '''gpio''' program
from inside Python).

<pre>
gpio export 17 out
gpio export 18 in
</pre>

These exports GPIO-17 and sets it to output, and exports GPIO-18
and sets it to input.

And when done:

<pre>
gpio unexport 17
</pre>

The export/unexport commands always use the BCM GPIO pin numbers regardless of the
presence of the '''-g''' flag or not.

If you want to use the internal pull-up/down's with the /sys/class/gpio mechanisms,
then you can set them after exporting them. So:

<pre>
gpio -g export 4 in
gpio -g mode 4 up
</pre>

You can then use GPIO-4 as an input in your Python, Shell, Java, etc. programs without the use
of an external resistor to pull the pin high. (If that's what you were after - for example, a simple push
button switch taking the pin to ground.)

A fully working example of a shell script using the GPIO pins
can be found at http://project-downloads.drogon.net/files/gpioExamples/tuxx.sh.

====GPIO Driving Example (Lazarus / Free Pascal)====
[[File:RPI GPIO testprogram with lazarus.png|thumb|254px|right|A simple app for controlling GPIO pin 17 with Lazarus]]

The GPIO pins are accessible from [[Lazarus on RPi|Lazarus]] without any third-party software. This is performed by means of invoking Unix shell commands with '''fpsystem'''. The following example uses GPIO pin 17 as output port. It is assumed that you created a form with a TToggleBox named GPIO17ToggleBox and for logging purposes a TMemo with name LogMemo (optional). The program has to be executed with root privileges.

''Unit for controlling the GPIO port:''
<pre>
unit Unit1;

{Demo application for GPIO on Raspberry Pi}
{Inspired by the Python input/output demo application by Gareth Halfacree}
{written for the Raspberry Pi User Guide, ISBN 978-1-118-46446-5}

{$mode objfpc}{$H+}

interface

uses
Classes, SysUtils, FileUtil, Forms, Controls, Graphics, Dialogs, StdCtrls, Unix;

type

{ TForm1 }

TForm1 = class(TForm)
LogMemo: TMemo;
GPIO17ToggleBox: TToggleBox;
procedure FormActivate(Sender: TObject);
procedure FormClose(Sender: TObject; var CloseAction: TCloseAction);
procedure GPIO17ToggleBoxChange(Sender: TObject);
private
{ private declarations }
public
{ public declarations }
end;

var
Form1: TForm1;
gReturnCode: longint; {stores the result of the IO operation}

implementation

{$R *.lfm}

{ TForm1 }

procedure TForm1.FormActivate(Sender: TObject);
begin
{ Prepare SoC pin 17 (pin 11 on GPIO port) for access: }
gReturnCode := fpsystem('echo "17" > /sys/class/gpio/export');
LogMemo.Lines.Add(IntToStr(gReturnCode));
{ Set SoC pin 17 as output: }
gReturnCode := fpsystem('echo "out" > /sys/class/gpio/gpio17/direction');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;

procedure TForm1.FormClose(Sender: TObject; var CloseAction: TCloseAction);
begin
{ Free SoC pin 17: }
gReturnCode := fpsystem('echo "17" > /sys/class/gpio/unexport');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;

procedure TForm1.GPIO17ToggleBoxChange(Sender: TObject);
begin
if GPIO17ToggleBox.Checked then
begin
{ Swith SoC pin 17 on: }
gReturnCode := fpsystem('echo "1" > /sys/class/gpio/gpio17/value');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end
else
begin
{ Switch SoC pin 17 off: }
gReturnCode := fpsystem('echo "0" > /sys/class/gpio/gpio17/value');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;

end.
</pre>

''Main program:''
<pre>
program io_test;

{$mode objfpc}{$H+}

uses
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Interfaces, // this includes the LCL widgetset
Forms, Unit1
{ you can add units after this };

{$R *.res}

begin
Application.Initialize;
Application.CreateForm(TForm1, Form1);
Application.Run;
end.
</pre>

An alternative way to access the GPIO port with Lazarus / Free Pascal is by using [http://www.lazarus.freepascal.org/index.php/topic,17404.0.html Lazarus wrapper unit for Gordon Henderson's wiringPi C library].

====GPIO Driving Example (C + wiringPi)====
Get and install wiringPi: https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/

Save this, and compile with:
<pre>
gcc -o blink blink.c -lwiringPi
</pre>
and run with:
<pre>
sudo ./blink
</pre>

<pre>
/*
* blink.c:
* blinks the first LED
* Gordon Henderson, projects@drogon.net
*/

#include <stdio.h>
#include <wiringPi.h>

int main (void)
{
printf ("Raspberry Pi blink\n") ;

if (wiringPiSetup () == -1)
return 1 ;

pinMode (0, OUTPUT) ; // aka BCM_GPIO pin 17

for (;;)
{
digitalWrite (0, 1) ; // On
delay (500) ; // mS
digitalWrite (0, 0) ; // Off
delay (500) ;
}
return 0 ;
}
</pre>

====GPIO Driving Example (C)====
This must be done as root. To change to the root user:
<pre>sudo -i</pre>
You must also get and install the bcm2835 library, which supports
GPIO and SPI interfaces. Details and downloads
from http://www.open.com.au/mikem/bcm2835

<pre>

// blink.c
//
// Example program for bcm2835 library
// Blinks a pin on an off every 0.5 secs
//
// After installing bcm2835, you can build this
// with something like:
// gcc -o blink -l rt blink.c -l bcm2835
// sudo ./blink
//
// Or you can test it before installing with:
// gcc -o blink -l rt -I ../../src ../../src/bcm2835.c blink.c
// sudo ./blink
//
// Author: Mike McCauley (mikem@open.com.au)
// Copyright (C) 2011 Mike McCauley
// $Id: RF22.h,v 1.21 2012/05/30 01:51:25 mikem Exp $

#include <bcm2835.h>

// Blinks on RPi pin GPIO 11
#define PIN RPI_GPIO_P1_11

int main(int argc, char **argv)
{
// If you call this, it will not actually access the GPIO
// Use for testing
// bcm2835_set_debug(1);

if (!bcm2835_init())
return 1;

// Set the pin to be an output
bcm2835_gpio_fsel(PIN, BCM2835_GPIO_FSEL_OUTP);

// Blink
while (1)
{
// Turn it on
bcm2835_gpio_write(PIN, HIGH);

// wait a bit
delay(500);

// turn it off
bcm2835_gpio_write(PIN, LOW);

// wait a bit
delay(500);
}

return 0;
}
</pre>

====GPIO Driving Example (Perl)====
This must be done as root. To change to the root user:
<pre>sudo su -</pre>
Supports GPIO and SPI interfaces.
You must also get and install the bcm2835 library. Details and downloads
from http://www.open.com.au/mikem/bcm2835
You must then get and install the Device::BCM2835 perl library from CPAN
http://search.cpan.org/~mikem/Device-BCM2835-1.0/lib/Device/BCM2835.pm
<pre>
use Device::BCM2835;
use strict;

# call set_debug(1) to do a non-destructive test on non-RPi hardware
#Device::BCM2835::set_debug(1);
Device::BCM2835::init()
|| die "Could not init library";

# Blink pin 11:
# Set RPi pin 11 to be an output
Device::BCM2835::gpio_fsel(&Device::BCM2835::RPI_GPIO_P1_11,
&Device::BCM2835::BCM2835_GPIO_FSEL_OUTP);

while (1)
{
# Turn it on
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 1);
Device::BCM2835::delay(500); # Milliseconds
# Turn it off
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 0);
Device::BCM2835::delay(500); # Milliseconds
}

</pre>

==== GPIO Driving Example (C#) ====
RaspberryPiDotNet library is available at https://github.com/cypherkey/RaspberryPi.Net/.
The library includes a GPIOFile and GPIOMem class. The GPIOMem requires compiling Mike McCauley's bcm2835 library above in to a shared object.

<pre>
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using RaspberryPiDotNet;
using System.Threading;

namespace RaspPi
{
class Program
{
static void Main(string[] args)
{
// Access the GPIO pin using a static method
GPIOFile.Write(GPIO.GPIOPins.GPIO00, true);

// Create a new GPIO object
GPIOMem gpio = new GPIOMem(GPIO.GPIOPins.GPIO01);
gpio.Write(false);
}
}
}
</pre>

====GPIO Driving Example (Ruby)====

This example uses the WiringPi Ruby Gem: http://pi.gadgetoid.co.uk/post/015-wiringpi-now-with-serial which you can install on your Pi with "gem install wiringpi"

<pre>
MY_PIN = 1

require 'wiringpi'
io = WiringPi::GPIO.new
io.mode(MY_PIN,OUTPUT)
io.write(MY_PIN,HIGH)
io.read(MY_PIN)
</pre>

Alternatively the Pi Piper Gem (https://github.com/jwhitehorn/pi_piper) allows for event driven programming:

<pre>
require 'pi_piper'
include PiPiper

watch :pin => 23 do
puts "Pin changed from #{last_value} to #{value}"
end

PiPiper.wait
</pre>

====GPIO Driving Example (BASIC - Return to BASIC)====

'''RTB''' or Return to Basic can be found here: https://projects.drogon.net/return-to-basic/

It's a new BASIC featuring modern looping constructs, switch statements, named procedures and functions as well as graphics (caresian and turtle), file handling and more. It also supports the Pi's on-board GPIO without needing to be run as root. (You don't need any special setup routines either)

Sample blink program:

<pre>
// blink.rtb:
// Blink program in Return to Basic
// Gordon Henderson, projects@drogon.net
//
PinMode (0, 1) // Output
CYCLE
DigitalWrite (0, 1) // Pin 0 ON
WAIT (0.5) // 0.5 seconds
DigitalWrite (0, 0)
WAIT (0.5)
REPEAT
END
</pre>

====GPIO Driving Example (BASIC)====

'''Bywater BASIC Interpreter'''

The Bywater BASIC Interpreter (bwBASIC) implements a large superset of the ANSI Standard for Minimal BASIC (X3.60-1978) and a significant subset of the ANSI Standard for Full BASIC (X3.113-1987) in C. It also offers shell programming facilities as an extension of BASIC. bwBASIC seeks to be as portable as possible.
You can download it at.
http://packages.debian.org/stable/interpreters/bwbasic

'''BASIC programming of the I/O'''

'''Setting up a GPIO pin to be used for inputs or for outputs.'''

We cannot load the control words directly into the 32 bit ARM registers with 32 bit addresses, as bwBASIC has no POKE and PEEK commands and other versions of BASIC (as far as I know) only handle 8 bit registers with 16 bit addresses with these commands. So we need to export the GPIO pins, so that they exist in a file structure which we can access from basic with the OPEN command.(ref 2)

We need to do this in Linux root.
We need to run BASIC in the root too. First we go to the root, then we load bwbasic into root.
<pre>
sudo -1
sudo bwbasic
</pre>

REM Now to export the no4 GPIO pin for example, using a Shell command.

<pre>echo “4” > /sys/class/gpio/export</pre>

Whilst bwbasic can accommodate shell commands, and we can store a set of these commands (eg. to export a number of GPIO pins at the outset) as numbered statements in a file that can be loaded with the basic command LOAD “filename” and RUN (ref 2), the shell commands have to run as a separate file, as they cannot be run from within, as part of a basic programme.

'''Now we can access the file containing the pin direction setting from BASIC'''

We can set GPIO pin 4 to input or to output by OPENing its pin direction file for output and writing “in” or “out” with a PRINT# command. (ref 2 )
<syntaxhighlight lang="basic4gl">
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 PRINT #1,”out”
30 CLOSE #1
</syntaxhighlight>

REM closes the open direction file, whereupon the system performs the action of setting the direction to “out”. NB the system only carries out the action as the file is closed.(ref 3)

'''We are now able to control the output of the gpio 4 pin from BASIC'''

We can set the GPIO 4 pin to 1 or to 0 by OPENing its pin value file for output and writing “1” or “0” with a PRINT# command.
<syntaxhighlight lang="basic4gl">
40 OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
50 PRINT #4,”1”
60 CLOSE #4
</syntaxhighlight>

REM turns on the output of GPIO pin 4.

REM similarly we can turn off the output of GPIO pin 4.
OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
PRINT #4,”0”
CLOSE #4.

'''Example of an (unstructured) BASIC programme'''

To read the state of a switch and control the power to two LEDs connected to GPIO pins 8,7 and 4 respectively.

Programme to set 2 pins as outputs and 1 pin as input and to read the input turning on two different combinations of the two outputs (ie output 0,1 or 1,0) depending on the state of the input (1 or 0).
<syntaxhighlight lang="basic4gl">
sudo –i
sudo bwbasic
LOAD “export.bas”
LIST
REM a set of Shell statements to export the three GPIO pins.
10 echo “4” > /sys/class/gpio/export
20 echo “7” > /sys/class/gpio/export
30 echo “8” > /sys/class/gpio/export
RUN
</syntaxhighlight>

NEW REM clears the export.bas programme from memory
<syntaxhighlight lang="basic4gl">
.
LOAD “demo1.bas”
LIST
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 OPEN ”O”,#2, “/sys/devices/virtual/gpio/gpio7/direction”,2
30 OPEN ”O”,#3, “/sys/devices/virtual/gpio/gpio8/direction”,2
REM opens the three pin direction files
40 PRINT #1, “out”
50 PRINT #2, “out”
60 PRINT #3, “in”
REM sets GPIO pins 4 and 7 as outputs and GPIO pin 8 as input.
70 CLOSE #1
80 CLOSE #2
90 CLOSE #3
REM closes all open files, allowing the system to perform the direction settings.
100 OPEN ”I”,#8, “/sys/devices/virtual/gpio/gpio8/value”,1
REM opens the GPIO pin 8 value file
110 INPUT #8,x
REM reads the value of the input pin and stores the value in numerical variable x
120 CLOSE #8
REM closes the open file, allowing the system to read the value of the input pin and store the value in numerical variable x.
130 OPEN “O”,#1, “/sys/devices/virtual/gpio/gpio4/value”,1
140 OPEN “O”,#2, “/sys/devices/virtual/gpio/gpio7/value”,1
REM opens the GPIO pins 4 and value files ready for outputting 1s and 0s.
150 IF x<1 THEN GOTO 160 ELSE GOTO 190
REM tests the state of the switch (1 or0) and directs the program to generate the appropriate outputs
160 PRINT #1,”1”
170 PRINT #2,”0”
180 GOTO 210
190 PRINT#1,"0"
200 PRINT #2,"1"
210 CLOSE #1
220 CLOSE #2
REM Closes the files and allows the outputs to light the LED
230 END.
</syntaxhighlight>

When all is done, we should unexport the GPIO pins, to leave the R-Pi as we found it.(Ref 1.)
<syntaxhighlight lang="basic4gl">
NEW
LOAD “unexport.bas”
LIST
REM a set of Shell statements to unexport the three GPIO pins.
10 echo “4” > /sys/class/gpio/unexport
20 echo “7” > /sys/class/gpio/unexport
30 echo “8” > /sys/class/gpio/unexport
RUN
</syntaxhighlight>
A simple circuit to provide the switched input and the two LED outputs.

Ancient Mariner. Dec. 2012

References.

1. This paper RPi Low-level peripherals.

2. Ed Beynon. [http://www.ybw.com/forums/showthread.php?t=331320&page=5 http://www.ybw.com/forums/showthread.php?t=331320&page=5]

3. Arthur Kaletzky. Private communication. 25/10/2012

4. bwbasic manual.<br/>

For the two original documents this example has been copied from see:<br/>
[[Media:GPIO_Driving_Example_(BASIC)_.doc | GPIO_Driving_Example_(BASIC)_.doc]]

[[Media:Raspberry_Pi_I-O_viii.doc | Raspberry_Pi_I-O_viii.doc]]

==MIPI CSI-2==

On the production board<ref>http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf</ref>, the Raspberry Pi Foundation design brings out the MIPI CSI-2 (Camera Serial Interface<ref>http://www.mipi.org/specifications/camera-interface</ref>) to a 15-way flat flex connector S5, between the Ethernet and HDMI connectors. A compatible camera has been discussed as working in tests and is planned for release at a later date.<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/complex-camera-peripherials#p72602</ref>.


==DSI==

On the production board, the Raspberry Pi Foundation design brings out the DSI (Display Serial Interface<ref>http://www.mipi.org/specifications/display-interface</ref>) to a 15-way flat flex connector labelled S2, next to Raspberry Pi logo. It has two data lanes and a clock lane, to drive a possible future LCD screen device. Some smart phone screens use DSI<ref>http://en.wikipedia.org/wiki/Display_Serial_Interface</ref>.

==CEC==

[[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.
Eben notes that he has seen CEC demos on the Broadcom SoC they are using.

libCEC with Raspberry Pi support has been included in OpenELEC and will be included in Raspbmc RC4.<ref>http://blog.pulse-eight.com/2012/08/01/libcec-1-8-0-a-firmware-upgrade-and-raspberry-pi-support/</ref>

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.

== References ==
<references/>

{{Template:Raspberry Pi}}

RPi Low-level peripherals

2013-02-22T01:08:46Z

AndrewS: /* General Purpose Input/Output (GPIO) */ Corrections to the P1 GPIO ALT functions

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

==Introduction==
In addition to the familiar USB, Ethernet and HDMI ports, the R-Pi offers lower-level interfaces intended to connect more directly with chips and subsystem modules. These GPIO (general purpose I/O) signals on the 2x13 header pins include SPI, I2C, serial UART, 3V3 and 5V power. These interfaces are not "plug and play" and require care to avoid miswiring. The pins use a 3V3 logic level and are not tolerant of 5V levels, such as you might find on a 5V powered Arduino. Not yet software-enabled are the flex cable connectors with CSI (camera serial interface) and DSI (display serial interface), and a serial link inside the HDMI connector called CEC. (consumer electronics control)

==General Purpose Input/Output (GPIO)==
[[File:GPIOs.png|thumb|254px|right|The layout of the Raspberry Pi Revision 1 P1 pin-header seen from the top, containing pins useable for general purpose I/O. Colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs2.gif Source] ]]

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.

The Raspberry Pi allows peripherals and expansion boards (such as the [[Rpi Gertboard]]) to access the CPU by exposing the inputs and outputs.

For further general information about GPIOs, see: [http://en.wikipedia.org/wiki/GPIO the wikipedia article].<BR>
For further specific information about the Raspberry Pi's BCM2835 GPIOs, see: [[RPi_BCM2835_GPIOs|this wiki article]].

The production Raspberry Pi board has a 26-pin 2.54 mm (100 mil)<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907</ref> expansion header, marked as P1, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I²C, SPI, UART), as well as +3.3 V, +5 V and GND supply lines. Pin one is the pin in the first column and on the bottom row. <ref>http://www.raspberrypi.org/archives/384</ref>

'''GPIO voltage levels are 3.3 V and are not 5 V 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.

All the GPIO pins can be reconfigured to provide alternate functions, SPI, [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM], I²C and so. At reset only pins GPIO 14 & 15 are assigned to the alternate function UART, these two can be switched back to GPIO to provide a total of 17 GPIO pins<ref>http://www.raspberrypi.org/archives/384</ref>. Each of their functions and full details of how to access are detailed in the chipset datasheet <ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref>.

Each GPIO can interrupt, high/low/rise/fall/change.<ref>http://www.raspberrypi.org/archives/384#comment-5217</ref><ref>http://www.raspberrypi.org/wp-content/uploads/2012/02/BCM2835-ARM-Peripherals.pdf</ref> There is currently no support for GPIO interrupts in the official kernel, howewer a patch exists, requiring compilation of modified source tree.<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=44&t=7509</ref> The 'Raspbian "wheezy"' <ref>http://www.raspberrypi.org/downloads</ref> version that is currently recommended for starters already includes GPIO interrupts.

GPIO input hysteresis (Schmitt trigger) can be on or off, output slew rate can be fast or limited, and source and sink current is configurable from 2 mA up to 16 mA. Note that chipset GPIO pins 0-27 are in the same block and these properties are set per block, not per pin. See [http://www.scribd.com/doc/101830961/GPIO-Pads-Control2 GPIO Datasheet Addendum - GPIO Pads Control]. Particular attention should be applied to the note regarding SSO (Simultaneous Switching Outputs): to avoid interference, driving currents should be kept as low as possible.

The available [[RPi_BCM2835_GPIOs|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.

There is also some information on the [[RPi Tutorial Easy GPIO Hardware & Software|Tutorial on Easy GPIO Hardware & Software]].

Kernel boot messages go to the [[RPi_Serial_Connection|UART]] at 115200 bit/s.

'''R-Pi PCB Revision 2 UPDATE:''' According to Eben at [http://www.raspberrypi.org/archives/1929#comment-31646] the R-Pi Rev.2 board being rolled out starting in September 2012 adds 4 more GPIO on a new connector called P5, and changes some of the existing P1 GPIO pinouts. On Rev2, GPIO_GEN2 [BCM2835/GPIO27] is routed to P1 pin 13, and changes what was SCL0/SDA0 to SCL1/SDA1: SCL1 [BCM2835/GPIO3] is routed to P1 pin 5, SDA1 [BCM2835/GPIO2] is routed to P1 pin 3. Also the power and ground connections previously marked "Do Not Connect" on P1 will remain as connected, specifically: P1-04:+5V0, P1-09:GND, P1-14:GND, P1-17:+3V3, P1-20:GND, P1-25:GND. According to this comment [http://www.raspberrypi.org/archives/2081#comment-33577] (and confirmed in this post [http://www.raspberrypi.org/archives/2233]) the P1 pinout is not expected to change in future beyond the current Rev.2 layout.

'''Header Pinout, top row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-02 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-04 || bgcolor="red" | <span style="color:white">5V0</span> || bgcolor="red" | <span style="color:white">5V0</span> || Supply through input poly fuse
|-
| P1-06 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
|-
| P1-08 || bgcolor="lime" | GPIO 14 || bgcolor="lime" | GPIO 14 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_TXD || ALT5 = UART1_TXD
|-
| P1-10 || bgcolor="lime" | GPIO 15 || bgcolor="lime" | GPIO 15 || Boot to Alt 0 -> || bgcolor="yellow" | UART0_RXD || ALT5 = UART1_RXD
|-
| P1-12 || bgcolor="lime" | GPIO 18 || bgcolor="lime" | GPIO 18 || || PCM_CLK || ALT4 = SPI1_CE0_N ALT5 = PWM0
|-
| P1-14 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-16 || bgcolor="lime" | GPIO23 || bgcolor="lime" | GPIO23 || || || ALT3 = SD1_CMD ALT4 = ARM_RTCK
|-
| P1-18 || bgcolor="lime" | GPIO24 || bgcolor="lime" | GPIO24 || || || ALT3 = SD1_DAT0 ALT4 = ARM_TDO
|-
| P1-20 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-22 || bgcolor="lime" | GPIO25 || bgcolor="lime" | GPIO25 || || || ALT3 = SD1_DAT1 ALT4 = ARM_TCK
|-
| P1-24 || bgcolor="lime" | GPIO08 || bgcolor="lime" | GPIO08 || || bgcolor="purple" | <span style="color:white">SPI0_CE0_N</span> ||
|-
| P1-26 || bgcolor="lime" | GPIO07 || bgcolor="lime" | GPIO07 || || bgcolor="purple" | <span style="color:white">SPI0_CE1_N</span> ||
|}

'''Header Pinout, bottom row:'''
{| border="1" style="text-align:center;"
| '''Pin Number''' || '''Pin Name Rev1''' || '''Pin Name Rev2''' || '''Hardware Notes''' || '''Alt 0 Function''' || '''Other Alternative Functions'''
|-
| P1-01 || bgcolor="orange" | 3.3 V ||bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-03 || bgcolor="lime" | GPIO 0 || bgcolor="lime" | '''GPIO 2'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SDA / '''I2C1_SDA''' ||
|-
| P1-05 || bgcolor="lime" | GPIO 1 || bgcolor="lime" | '''GPIO 3'''|| 1K8 pull up resistor || bgcolor="cyan" | I2C0_SCL / '''I2C1_SCL''' ||
|-
| P1-07 || bgcolor="lime" | GPIO 4 || bgcolor="lime" | GPIO 4 || || GPCLK0 || ALT5 = ARM_TDI
|-
| P1-09 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|-
| P1-11 || bgcolor="lime" | GPIO17 || bgcolor="lime" | GPIO17 || || ||| ALT3 = UART0_RTS ALT4 = SPI1_CE1_N ALT5 = UART1_RTS
|-
| P1-13 || bgcolor="lime" | GPIO21 || bgcolor="lime" | '''GPIO27''' || || PCM_DOUT / '''reserved''' || ALT4 = SPI1_SCLK ALT5 = GPCLK1 / '''ALT3 = SD1_DAT3 ALT4 = ARM_TMS'''
|-
| P1-15 || bgcolor="lime" | GPIO22 || bgcolor="lime" | GPIO22 || || || ALT3 = SD1_CLK ALT4 = ARM_TRST
|-
| P1-17 || bgcolor="orange" | 3.3 V || bgcolor="orange" | 3.3 V || 50 mA max (01 & 17)
|-
| P1-19 || bgcolor="lime" | GPIO10 || bgcolor="lime" | GPIO10 || || bgcolor="purple" | <span style="color:white">SPI0_MOSI</span> ||
|-
| P1-21 || bgcolor="lime" | GPIO9 || bgcolor="lime" | GPIO9 || || bgcolor="purple" | <span style="color:white">SPI0_MISO</span> ||
|-
| P1-23 || bgcolor="lime" | GPIO11 || bgcolor="lime" | GPIO11 || || bgcolor="purple" | <span style="color:white">SPI0_SCLK</span> ||
|-
| P1-25 || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="black" | <span style="color:white">GND</span>
|}

{| border="1"
! Colour legend
|-
| bgcolor="red" | <span style="color:white">+5 V</span>
|-
| bgcolor="orange" | +3.3 V
|-
| bgcolor="black" | <span style="color:white">Ground, 0V</span>
|-
| bgcolor="yellow" | UART
|-
| bgcolor="lime" | GPIO
|-
| bgcolor="purple" | <span style="color:white">SPI</span>
|-
| bgcolor="cyan" | I²C
|}

KiCad symbol: [[File:Conn-raspberry.lib]]

<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/gpio-header-pinout-clarification/page-2</ref>

Pin 3 (SDA0) and Pin 5 (SCL0) are preset to be used as an I²C interface. So there are 1.8 kilohm pulls up resistors on the board for these pins.<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-6/#p56480</ref>

Pin 12 supports [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM] .

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.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.1</ref> 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.

It is also possible to reconfigure GPIO connector pins P1-12 and 13 (chipset GPIO 18 and 21) to provide an I2S (a hardware modification may be required<ref name="I2S">[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?]</ref>) or PCM interface.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1288.2</ref> However, PCM_FS and PCM_DIN (chipset pins 19 and 20) are needed for I2S or PCM.

A second I²C 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.

===Referring to pins on the Expansion header===

The header is referred to as "The GPIO Connector (P1)". To avoid nomenclature confusion between Broadcom signal names on the SoC and pin names on the expansion header, the following naming is highly recommended.

* The expansion header is referred to as "Expansion Header" or "GPIO Connector (P1)"
* Pins on the GPIO connector (P1) are referred to as P1-01, etc.
* Names GPIO0, GPIO1, GPIOx-ALTy, etc. refer to the signal names on the SoC as enumerated in the Broadcom datasheet, where "x" matches BCM2835 number (without leading zero) and "y" 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 "GPIO7" to refer to a row of the table, and "GPIO7-ALT0" would refer to a specific cell of the table.
* 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 "SPI0_*" and "SPI1_*", but they didn't do the same on the I²C and UART pins. Instead of using "SDA0" and "SCL0", you should use "I2C0_SDA" and "I2C0_SCL"; and instead of "TX" or "TXD" and "RX" or "RXD", you should use "UART0_TXD" and "UART0_RXD".

===Power pins===
The maximum permitted current draw from the 3.3 V pins is 50 mA.

Maximum permitted current draw from the 5 V pin is the USB input current (usually 1 A) minus any current draw from the rest of the board.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1536#postid-21841</ref>
*Model A: 1000 mA - 500 mA -> max current draw: 500 mA
*Model B: 1000 mA - 700 mA -> max current draw: 300 mA
Be very careful with the 5 V pins P1-02 and P1-04, because if you short 5 V to any other P1 pin you may permanently damage your RasPi. Before probing P1, it's a good idea to strip short pieces of insulation off a wire and push them over the 5 V pins so you don't accidentally short them with a probe.

=== GPIO hardware hacking ===

The complete list of [[RPi_BCM2835_GPIOs|chipset GPIO pins]] which are available on the GPIO connector is: <blockquote>[[RPi_BCM2835_GPIOs#GPIO0|0]], [[RPi_BCM2835_GPIOs#GPIO1|1]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO21|21]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]]</blockquote>

(on the Revision2.0 RaspberryPis, this list changes to: [[RPi_BCM2835_GPIOs#GPIO2|2]], [[RPi_BCM2835_GPIOs#GPIO3|3]], [[RPi_BCM2835_GPIOs#GPIO4|4]], [[RPi_BCM2835_GPIOs#GPIO7|7]], [[RPi_BCM2835_GPIOs#GPIO8|8]], [[RPi_BCM2835_GPIOs#GPIO9|9]], [[RPi_BCM2835_GPIOs#GPIO10|10]], [[RPi_BCM2835_GPIOs#GPIO11|11]], [[RPi_BCM2835_GPIOs#GPIO14|14]], [[RPi_BCM2835_GPIOs#GPIO15|15]], [[RPi_BCM2835_GPIOs#GPIO17|17]], [[RPi_BCM2835_GPIOs#GPIO18|18]], [[RPi_BCM2835_GPIOs#GPIO22|22]], [[RPi_BCM2835_GPIOs#GPIO23|23]], [[RPi_BCM2835_GPIOs#GPIO24|24]], [[RPi_BCM2835_GPIOs#GPIO25|25]], [[RPi_BCM2835_GPIOs#GPIO27|27]], with [[RPi_BCM2835_GPIOs#GPIO28|28]], [[RPi_BCM2835_GPIOs#GPIO29|29]], [[RPi_BCM2835_GPIOs#GPIO30|30]], [[RPi_BCM2835_GPIOs#GPIO31|31]] additionally available on the [[#P5_header|P5 header]])

As noted above, GPIO00 and 01 (SDA0 and SCL0) have 1.8 kilohm pull-up resistors to 3.3 V.

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:

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 3.3 V.

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.

There are a few other chipset GPIO pins accessible on the PCB but are in use:

* GPIO16 drives status LED D5 (usually SD card access indicator)
* GPIO28-31 are used by the board ID and are connected to resistors R3 to R10 (only on Rev1.0 boards).
* GPIO40 and 45 are used by analogue audio and support [http://en.wikipedia.org/wiki/Pulse-width_modulation PWM]. They connect to the analogue audio circuitry via R21 and R27 respectively.
* GPIO46 is HDMI hotplug detect (goes to pin 6 of IC1).
* 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.

=== P2 header ===

The P2 header is the VideoCore JTAG and used only during the production of the board. It cannot be used as the ARM JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>. This connector is unpopulated in Rev 2.0 boards.

Useful P2 pins:

* Pin 1 - 3.3V (same as P1-01, 50 mA max current draw across both of them)
* Pin 7 - GND
* Pin 8 - GND

=== P3 header ===

The P3 header, unpopulated, is the LAN9512 JTAG <ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?f=24&t=5894</ref>.

=== P5 header ===

The P5 header was added with the release of the Revision 2.0 PCB design.
<pre>
* Pin 1 - 5V
* Pin 2 - 3V3
* Pin 3 - GPIO28	ALT0 = SDA0 	ALT2 = PCM_CLK
* Pin 4 - GPIO29	ALT0 = SCL0 	ALT2 = PCM_FS
* Pin 5 - GPIO30	ALT2 = CTS0 	ALT2 = PCM_DIN
* Pin 6 - GPIO31	ALT2 = RTS0 	ALT2 = PCM_DOUT
* Pin 7 - GND
* Pin 8 - GND
</pre>
Note that the connector is intended to be mounted on the '''bottom''' of the PCB, so that for those who put the connector on the top side, the pin numbers are swapped. Pin 1 and pin 2 are swapped, pin 3 and 4, etc.

The new header can provide a second I2C channel (SDA + SCL) and handshake lines for the existing UART (TxD and RxD), or it can be used for an I2S (audio codec chip) interface using the PCM signals CLK, FS (Frame Sync), Din and Dout.

Note that the connector is placed JUST off-grid with respect to the P1 connector.

=== P6 header ===

The P6 header was added with the release of the Revision 2.0 PCB design.

[http://raspi.tv/2012/making-a-reset-switch-for-your-rev-2-raspberry-pi A reset button can be attached to the P6 header], with which the Pi can be reset.
Momentarily shorting the two pins of P6 together will cause a soft reset of the CPU.

===Driver support===

The Foundation will not include a GPIO driver in the initial release, standard Linux GPIO drivers should work with minimal modification.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1278.0</ref>

The community implemented SPI and I²C drivers <ref>http://www.bootc.net/projects/raspberry-pi-kernel/</ref>, which will be integrated with the new Linux pinctrl concept in a later version of the kernel. (On Oct. 14 2012, it was already included in the latest raspbian image.) A first compiled version as Linux modules is available to install on the 19/04/2012 Debian image, including 1-wire support<ref>http://www.raspberrypi.org/phpBB3/viewtopic.php?p=86172#p86172</ref>. The I²C and SPI driver uses the hardware modules of the microcontroller and interrupts for low CPU usage, the 1-wire support uses bitbanging on the GPIO ports, which results in higher CPU usage.

GordonH<ref>http://www.raspberrypi.org/forum/general-discussion/wiring-for-the-raspberry-pis-gpio</ref> wrote a (mostly) Arduino compatible/style [https://projects.drogon.net/raspberry-pi/wiringpi/ WiringPi library] in C for controlling the GPIO pins.

A useful tutorial on setting up I²C driver support can be found at [http://www.robot-electronics.co.uk/htm/raspberry_pi_examples.htm Robot Electronics] - look for the downloadable document rpi_i2c_setup.doc

===Graphical User Interfaces===
====WebIOPi====
[http://code.google.com/p/webiopi/ WebIOPi] allows you to control each GPIO with a simple web interface that you can use with any browser. Available in PHP and Python, they both require root access, but Python version serves HTTP itself. You can setup each GPIO as input or output and change their states (LOW/HIGH). WebIOPi is fully customizable, so you can use it for home remote control. It also work over Internet. UART/SPI/I2C support will be added later. If you need some computing for your GPIO go to code examples below.

==GPIO Code examples==
====GPIO Driving Example (C)====
[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 Gert van Loo & Dom, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.
(Thanks to Dom for doing the difficult work of finding and testing the mapping.)
Example GPIO code:

<pre>
//
// How to access GPIO registers from C-code on the Raspberry-Pi
// Example program
// 15-January-2012
// Dom and Gert
// Revised: 15-Feb-2013

// Access from ARM Running Linux

#define BCM2708_PERI_BASE 0x20000000
#define GPIO_BASE (BCM2708_PERI_BASE + 0x200000) /* GPIO controller */

#include <stdio.h>
#include <stdlib.h>
#include <fcntl.h>
#include <sys/mman.h>
#include <unistd.h>

#define PAGE_SIZE (4*1024)
#define BLOCK_SIZE (4*1024)

int mem_fd;
void *gpio_map;

// I/O access
volatile unsigned *gpio;

// GPIO setup macros. Always use INP_GPIO(x) before using OUT_GPIO(x) or SET_GPIO_ALT(x,y)
#define INP_GPIO(g) *(gpio+((g)/10)) &= ~(7<<(((g)%10)*3))
#define OUT_GPIO(g) *(gpio+((g)/10)) |= (1<<(((g)%10)*3))
#define SET_GPIO_ALT(g,a) *(gpio+(((g)/10))) |= (((a)<=3?(a)+4:(a)==4?3:2)<<(((g)%10)*3))

#define GPIO_SET *(gpio+7) // sets bits which are 1 ignores bits which are 0
#define GPIO_CLR *(gpio+10) // clears bits which are 1 ignores bits which are 0

void setup_io();

int main(int argc, char **argv)
{
int g,rep;

// Set up gpi pointer for direct register access
setup_io();

// Switch GPIO 7..11 to output mode

/************************************************************************\
* You are about to change the GPIO settings of your computer. *
* Mess this up and it will stop working! *
* It might be a good idea to 'sync' before running this program *
* so at least you still have your code changes written to the SD-card! *
\************************************************************************/

// Set GPIO pins 7-11 to output
for (g=7; g<=11; g++)
{
INP_GPIO(g); // must use INP_GPIO before we can use OUT_GPIO
OUT_GPIO(g);
}

for (rep=0; rep<10; rep++)
{
for (g=7; g<=11; g++)
{
GPIO_SET = 1<<g;
sleep(1);
}
for (g=7; g<=11; g++)
{
GPIO_CLR = 1<<g;
sleep(1);
}
}

return 0;

} // main

//
// Set up a memory regions to access GPIO
//
void setup_io()
{
/* open /dev/mem */
if ((mem_fd = open("/dev/mem", O_RDWR|O_SYNC) ) < 0) {
printf("can't open /dev/mem \n");
exit(-1);
}

/* mmap GPIO */
gpio_map = mmap(
NULL, //Any adddress in our space will do
BLOCK_SIZE, //Map length
PROT_READ|PROT_WRITE,// Enable reading & writting to mapped memory
MAP_SHARED, //Shared with other processes
mem_fd, //File to map
GPIO_BASE //Offset to GPIO peripheral
);

close(mem_fd); //No need to keep mem_fd open after mmap

if (gpio_map == MAP_FAILED) {
printf("mmap error %d\n", (int)gpio_map);//errno also set!
exit(-1);
}

// Always use volatile pointer!
gpio = (volatile unsigned *)gpio_map;

} // setup_io

</pre>

====GPIO Pull Up/Pull Down Register Example====
<pre>
// enable pull-up on GPIO24&25
GPIO_PULL = 2;
short_wait();
// clock on GPIO 24 & 25 (bit 24 & 25 set)
GPIO_PULLCLK0 = 0x03000000;
short_wait();
GPIO_PULL = 0;
GPIO_PULLCLK0 = 0;
</pre>

====GPIO Driving Example (Python)====
This uses the Python module available at http://pypi.python.org/pypi/RPi.GPIO
Any Python script that controls GPIO must be run as root.
<pre>import RPi.GPIO as GPIO

# Set up the GPIO channels - one input and one output
GPIO.setup(11, GPIO.IN)
GPIO.setup(12, GPIO.OUT)

# Input from pin 11
input_value = GPIO.input(11)

# Output to pin 12
GPIO.output(12, True)

# The same script as above but using BCM GPIO 00..nn numbers
GPIO.setmode(GPIO.BCM)
GPIO.setup(17, GPIO.IN)
GPIO.setup(18, GPIO.OUT)
input_value = GPIO.input(17)
GPIO.output(18, True)</pre>

====GPIO Driving Example (Java using the Pi4J Library)====
This uses the Java library available at http://www.pi4j.com/.
(Any Java application that controls GPIO must be run as root.)

Please note that the Pi4J library uses the WiringPi GPIO pin numbering scheme <ref>http://pi4j.com/usage.html#Pin_Numbering</ref> <ref>https://projects.drogon.net/raspberry-pi/wiringpi/pins/</ref>. Please see the usage documentation for more details: http://pi4j.com/usage.html

<pre>

public static void main(String[] args) {

// create gpio controller
GpioController gpio = GpioFactory.getInstance();

// provision gpio pin #01 as an output pin and turn off
GpioPinDigitalOutput outputPin = gpio.provisionDigitalOutputPin(RaspiPin.GPIO_01, "MyLED", PinState.LOW);

// turn output to LOW/OFF state
outputPin.low();

// turn output to HIGH/ON state
outputPin.high();

// provision gpio pin #02 as an input pin with its internal pull down resistor enabled
GpioPinDigitalInput inputPin = gpio.provisionDigitalInputPin(RaspiPin.GPIO_02, "MyButton", PinPullResistance.PULL_DOWN);

// get input state from pin 2
boolean input_value = inputPin.isHigh();
}
</pre>

More complete and detailed examples are included on the Pi4J website at http://www.pi4j.com/.

The Pi4J library includes support for:
* GPIO Control
* GPIO Listeners
* Serial Communication
* I2C Communication
* SPI Communication

====GPIO Driving Example (Java)====
This uses the Java library available at https://github.com/jkransen/framboos. It does not depend on (or use) the wiringPi driver, but uses the same numbering scheme. Instead it uses the default driver under /sys/class/gpio that ships with the distro, so it works out of the box. Any Java application that controls GPIO must be run as root.
<pre>
public static void main(String[] args) {
// reading from an in pin
InPin button = new InPin(8);
boolean isButtonPressed = button.getValue();
button.close();

// writing to an out pin
OutPin led = new Outpin(0);
led.setValue(true);
led.setValue(false);
led.close();
}
</pre>

====GPIO Driving Example (Java Webapp GPIO web control via http)====
This uses the Java Webapp available at https://bitbucket.org/sbub/raspberry-pi-gpio-web-control/overview. You can control your GPIO over the internet. Any Java application that controls GPIO must be run as root.
<pre>

host:~ sb$ curl 'http://raspberrypi:8080/handle?g0=1&g1=0'
{"g1":0,"g0":1}

</pre>

====GPIO Driving Example (Bash shell script, using sysfs, part of the raspbian operating system)====
The export and unexport of pins must be done as root.
To change to the root user see below: To change back, the word exit must be entered.
<pre>sudo -i</pre>
Export creates a new folder for the exported pin, and creates files for each of its control functions (i.e. active_low, direction, edge, power, subsystem, uevent, and value). Upon creation, the control files can be read by all users (not just root), but can only be written to by user root, the file's owner. Nevertheless, once created, it is possible to allow users other than root, to also write inputs to the control files, by changing the ownership or permissions of these files. Changes to the file's ownership or permissions must initially be done as root, as their owner and group is set to root upon creation. Typically you might change the owner to be the (non root) user controlling the GPIO, or you might add write permission, and change the group ownership to one of which the user controlling the GPIO is a member. By such means, using only packages provided in the recommended rasbian distribution, it is possible for Python CGI scripts, which are typically run as user nobody, to be used for control of the GPIO over the internet from a browser at a remote location.
<pre>
#!/bin/sh

# GPIO numbers should be from this list
# 0, 1, 4, 7, 8, 9, 10, 11, 14, 15, 17, 18, 21, 22, 23, 24, 25

# Note that the GPIO numbers that you program here refer to the pins
# of the BCM2835 and *not* the numbers on the pin header.
# So, if you want to activate GPIO7 on the header you should be
# using GPIO4 in this script. Likewise if you want to activate GPIO0
# on the header you should be using GPIO17 here.

# Set up GPIO 4 and set to output
echo "4" > /sys/class/gpio/export
echo "out" > /sys/class/gpio/gpio4/direction

# Set up GPIO 7 and set to input
echo "7" > /sys/class/gpio/export
echo "in" > /sys/class/gpio/gpio7/direction

# Write output
echo "1" > /sys/class/gpio/gpio4/value

# Read from input
cat /sys/class/gpio/gpio7/value

# Clean up
echo "4" > /sys/class/gpio/unexport
echo "7" > /sys/class/gpio/unexport
</pre>

====GPIO Driving Example (Shell script - take 2)====
You need the wiringPi library from
https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/. Once installed, there is a new command '''gpio''' which can be used
as a '''non-root''' user to control the GPIO pins.

The man page <pre>man gpio</pre> has full details, but briefly:

<pre>
gpio -g mode 17 out
gpio -g mode 18 pwm

gpio -g write 17 1
gpio -g pwm 18 512
</pre>

The '''-g''' flag tells the '''gpio''' program to use the BCM GPIO pin numbering
scheme (otherwise it will use the wiringPi numbering scheme by default).

The gpio command can also control the internal pull-up and pull-down
resistors:

<pre>
gpio -g mode 17 up
</pre>

This sets the pull-up resistor - however any change of mode, even
setting a pin that's already set as an input to an input will remove
the pull-up/pull-down resistors, so they may need to be reset.

Additionally, it can export/un-export the GPIO devices for use by
other non-root programms - e.g. Python scripts. (Although you
may need to drop the calls to GPIO.Setup() in the Python scripts, and
do the setup separately in a little shell script, or call the '''gpio''' program
from inside Python).

<pre>
gpio export 17 out
gpio export 18 in
</pre>

These exports GPIO-17 and sets it to output, and exports GPIO-18
and sets it to input.

And when done:

<pre>
gpio unexport 17
</pre>

The export/unexport commands always use the BCM GPIO pin numbers regardless of the
presence of the '''-g''' flag or not.

If you want to use the internal pull-up/down's with the /sys/class/gpio mechanisms,
then you can set them after exporting them. So:

<pre>
gpio -g export 4 in
gpio -g mode 4 up
</pre>

You can then use GPIO-4 as an input in your Python, Shell, Java, etc. programs without the use
of an external resistor to pull the pin high. (If that's what you were after - for example, a simple push
button switch taking the pin to ground.)

A fully working example of a shell script using the GPIO pins
can be found at http://project-downloads.drogon.net/files/gpioExamples/tuxx.sh.

====GPIO Driving Example (Lazarus / Free Pascal)====
[[File:RPI GPIO testprogram with lazarus.png|thumb|254px|right|A simple app for controlling GPIO pin 17 with Lazarus]]

The GPIO pins are accessible from [[Lazarus on RPi|Lazarus]] without any third-party software. This is performed by means of invoking Unix shell commands with '''fpsystem'''. The following example uses GPIO pin 17 as output port. It is assumed that you created a form with a TToggleBox named GPIO17ToggleBox and for logging purposes a TMemo with name LogMemo (optional). The program has to be executed with root privileges.

''Unit for controlling the GPIO port:''
<pre>
unit Unit1;

{Demo application for GPIO on Raspberry Pi}
{Inspired by the Python input/output demo application by Gareth Halfacree}
{written for the Raspberry Pi User Guide, ISBN 978-1-118-46446-5}

{$mode objfpc}{$H+}

interface

uses
Classes, SysUtils, FileUtil, Forms, Controls, Graphics, Dialogs, StdCtrls, Unix;

type

{ TForm1 }

TForm1 = class(TForm)
LogMemo: TMemo;
GPIO17ToggleBox: TToggleBox;
procedure FormActivate(Sender: TObject);
procedure FormClose(Sender: TObject; var CloseAction: TCloseAction);
procedure GPIO17ToggleBoxChange(Sender: TObject);
private
{ private declarations }
public
{ public declarations }
end;

var
Form1: TForm1;
gReturnCode: longint; {stores the result of the IO operation}

implementation

{$R *.lfm}

{ TForm1 }

procedure TForm1.FormActivate(Sender: TObject);
begin
{ Prepare SoC pin 17 (pin 11 on GPIO port) for access: }
gReturnCode := fpsystem('echo "17" > /sys/class/gpio/export');
LogMemo.Lines.Add(IntToStr(gReturnCode));
{ Set SoC pin 17 as output: }
gReturnCode := fpsystem('echo "out" > /sys/class/gpio/gpio17/direction');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;

procedure TForm1.FormClose(Sender: TObject; var CloseAction: TCloseAction);
begin
{ Free SoC pin 17: }
gReturnCode := fpsystem('echo "17" > /sys/class/gpio/unexport');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;

procedure TForm1.GPIO17ToggleBoxChange(Sender: TObject);
begin
if GPIO17ToggleBox.Checked then
begin
{ Swith SoC pin 17 on: }
gReturnCode := fpsystem('echo "1" > /sys/class/gpio/gpio17/value');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end
else
begin
{ Switch SoC pin 17 off: }
gReturnCode := fpsystem('echo "0" > /sys/class/gpio/gpio17/value');
LogMemo.Lines.Add(IntToStr(gReturnCode));
end;
end;

end.
</pre>

''Main program:''
<pre>
program io_test;

{$mode objfpc}{$H+}

uses
{$IFDEF UNIX}{$IFDEF UseCThreads}
cthreads,
{$ENDIF}{$ENDIF}
Interfaces, // this includes the LCL widgetset
Forms, Unit1
{ you can add units after this };

{$R *.res}

begin
Application.Initialize;
Application.CreateForm(TForm1, Form1);
Application.Run;
end.
</pre>

An alternative way to access the GPIO port with Lazarus / Free Pascal is by using [http://www.lazarus.freepascal.org/index.php/topic,17404.0.html Lazarus wrapper unit for Gordon Henderson's wiringPi C library].

====GPIO Driving Example (C + wiringPi)====
Get and install wiringPi: https://projects.drogon.net/raspberry-pi/wiringpi/download-and-install/

Save this, and compile with:
<pre>
gcc -o blink blink.c -lwiringPi
</pre>
and run with:
<pre>
sudo ./blink
</pre>

<pre>
/*
* blink.c:
* blinks the first LED
* Gordon Henderson, projects@drogon.net
*/

#include <stdio.h>
#include <wiringPi.h>

int main (void)
{
printf ("Raspberry Pi blink\n") ;

if (wiringPiSetup () == -1)
return 1 ;

pinMode (0, OUTPUT) ; // aka BCM_GPIO pin 17

for (;;)
{
digitalWrite (0, 1) ; // On
delay (500) ; // mS
digitalWrite (0, 0) ; // Off
delay (500) ;
}
return 0 ;
}
</pre>

====GPIO Driving Example (C)====
This must be done as root. To change to the root user:
<pre>sudo -i</pre>
You must also get and install the bcm2835 library, which supports
GPIO and SPI interfaces. Details and downloads
from http://www.open.com.au/mikem/bcm2835

<pre>

// blink.c
//
// Example program for bcm2835 library
// Blinks a pin on an off every 0.5 secs
//
// After installing bcm2835, you can build this
// with something like:
// gcc -o blink -l rt blink.c -l bcm2835
// sudo ./blink
//
// Or you can test it before installing with:
// gcc -o blink -l rt -I ../../src ../../src/bcm2835.c blink.c
// sudo ./blink
//
// Author: Mike McCauley (mikem@open.com.au)
// Copyright (C) 2011 Mike McCauley
// $Id: RF22.h,v 1.21 2012/05/30 01:51:25 mikem Exp $

#include <bcm2835.h>

// Blinks on RPi pin GPIO 11
#define PIN RPI_GPIO_P1_11

int main(int argc, char **argv)
{
// If you call this, it will not actually access the GPIO
// Use for testing
// bcm2835_set_debug(1);

if (!bcm2835_init())
return 1;

// Set the pin to be an output
bcm2835_gpio_fsel(PIN, BCM2835_GPIO_FSEL_OUTP);

// Blink
while (1)
{
// Turn it on
bcm2835_gpio_write(PIN, HIGH);

// wait a bit
delay(500);

// turn it off
bcm2835_gpio_write(PIN, LOW);

// wait a bit
delay(500);
}

return 0;
}
</pre>

====GPIO Driving Example (Perl)====
This must be done as root. To change to the root user:
<pre>sudo su -</pre>
Supports GPIO and SPI interfaces.
You must also get and install the bcm2835 library. Details and downloads
from http://www.open.com.au/mikem/bcm2835
You must then get and install the Device::BCM2835 perl library from CPAN
http://search.cpan.org/~mikem/Device-BCM2835-1.0/lib/Device/BCM2835.pm
<pre>
use Device::BCM2835;
use strict;

# call set_debug(1) to do a non-destructive test on non-RPi hardware
#Device::BCM2835::set_debug(1);
Device::BCM2835::init()
|| die "Could not init library";

# Blink pin 11:
# Set RPi pin 11 to be an output
Device::BCM2835::gpio_fsel(&Device::BCM2835::RPI_GPIO_P1_11,
&Device::BCM2835::BCM2835_GPIO_FSEL_OUTP);

while (1)
{
# Turn it on
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 1);
Device::BCM2835::delay(500); # Milliseconds
# Turn it off
Device::BCM2835::gpio_write(&Device::BCM2835::RPI_GPIO_P1_11, 0);
Device::BCM2835::delay(500); # Milliseconds
}

</pre>

==== GPIO Driving Example (C#) ====
RaspberryPiDotNet library is available at https://github.com/cypherkey/RaspberryPi.Net/.
The library includes a GPIOFile and GPIOMem class. The GPIOMem requires compiling Mike McCauley's bcm2835 library above in to a shared object.

<pre>
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using RaspberryPiDotNet;
using System.Threading;

namespace RaspPi
{
class Program
{
static void Main(string[] args)
{
// Access the GPIO pin using a static method
GPIOFile.Write(GPIO.GPIOPins.GPIO00, true);

// Create a new GPIO object
GPIOMem gpio = new GPIOMem(GPIO.GPIOPins.GPIO01);
gpio.Write(false);
}
}
}
</pre>

====GPIO Driving Example (Ruby)====

This example uses the WiringPi Ruby Gem: http://pi.gadgetoid.co.uk/post/015-wiringpi-now-with-serial which you can install on your Pi with "gem install wiringpi"

<pre>
MY_PIN = 1

require 'wiringpi'
io = WiringPi::GPIO.new
io.mode(MY_PIN,OUTPUT)
io.write(MY_PIN,HIGH)
io.read(MY_PIN)
</pre>

Alternatively the Pi Piper Gem (https://github.com/jwhitehorn/pi_piper) allows for event driven programming:

<pre>
require 'pi_piper'
include PiPiper

watch :pin => 23 do
puts "Pin changed from #{last_value} to #{value}"
end

PiPiper.wait
</pre>

====GPIO Driving Example (BASIC - Return to BASIC)====

'''RTB''' or Return to Basic can be found here: https://projects.drogon.net/return-to-basic/

It's a new BASIC featuring modern looping constructs, switch statements, named procedures and functions as well as graphics (caresian and turtle), file handling and more. It also supports the Pi's on-board GPIO without needing to be run as root. (You don't need any special setup routines either)

Sample blink program:

<pre>
// blink.rtb:
// Blink program in Return to Basic
// Gordon Henderson, projects@drogon.net
//
PinMode (0, 1) // Output
CYCLE
DigitalWrite (0, 1) // Pin 0 ON
WAIT (0.5) // 0.5 seconds
DigitalWrite (0, 0)
WAIT (0.5)
REPEAT
END
</pre>

====GPIO Driving Example (BASIC)====

'''Bywater BASIC Interpreter'''

The Bywater BASIC Interpreter (bwBASIC) implements a large superset of the ANSI Standard for Minimal BASIC (X3.60-1978) and a significant subset of the ANSI Standard for Full BASIC (X3.113-1987) in C. It also offers shell programming facilities as an extension of BASIC. bwBASIC seeks to be as portable as possible.
You can download it at.
http://packages.debian.org/stable/interpreters/bwbasic

'''BASIC programming of the I/O'''

'''Setting up a GPIO pin to be used for inputs or for outputs.'''

We cannot load the control words directly into the 32 bit ARM registers with 32 bit addresses, as bwBASIC has no POKE and PEEK commands and other versions of BASIC (as far as I know) only handle 8 bit registers with 16 bit addresses with these commands. So we need to export the GPIO pins, so that they exist in a file structure which we can access from basic with the OPEN command.(ref 2)

We need to do this in Linux root.
We need to run BASIC in the root too. First we go to the root, then we load bwbasic into root.
<pre>
sudo -1
sudo bwbasic
</pre>

REM Now to export the no4 GPIO pin for example, using a Shell command.

<pre>echo “4” > /sys/class/gpio/export</pre>

Whilst bwbasic can accommodate shell commands, and we can store a set of these commands (eg. to export a number of GPIO pins at the outset) as numbered statements in a file that can be loaded with the basic command LOAD “filename” and RUN (ref 2), the shell commands have to run as a separate file, as they cannot be run from within, as part of a basic programme.

'''Now we can access the file containing the pin direction setting from BASIC'''

We can set GPIO pin 4 to input or to output by OPENing its pin direction file for output and writing “in” or “out” with a PRINT# command. (ref 2 )
<syntaxhighlight lang="basic4gl">
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 PRINT #1,”out”
30 CLOSE #1
</syntaxhighlight>

REM closes the open direction file, whereupon the system performs the action of setting the direction to “out”. NB the system only carries out the action as the file is closed.(ref 3)

'''We are now able to control the output of the gpio 4 pin from BASIC'''

We can set the GPIO 4 pin to 1 or to 0 by OPENing its pin value file for output and writing “1” or “0” with a PRINT# command.
<syntaxhighlight lang="basic4gl">
40 OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
50 PRINT #4,”1”
60 CLOSE #4
</syntaxhighlight>

REM turns on the output of GPIO pin 4.

REM similarly we can turn off the output of GPIO pin 4.
OPEN ”O”,#4, “/sys/devices/virtual/gpio/gpio4/value”,1
PRINT #4,”0”
CLOSE #4.

'''Example of an (unstructured) BASIC programme'''

To read the state of a switch and control the power to two LEDs connected to GPIO pins 8,7 and 4 respectively.

Programme to set 2 pins as outputs and 1 pin as input and to read the input turning on two different combinations of the two outputs (ie output 0,1 or 1,0) depending on the state of the input (1 or 0).
<syntaxhighlight lang="basic4gl">
sudo –i
sudo bwbasic
LOAD “export.bas”
LIST
REM a set of Shell statements to export the three GPIO pins.
10 echo “4” > /sys/class/gpio/export
20 echo “7” > /sys/class/gpio/export
30 echo “8” > /sys/class/gpio/export
RUN
</syntaxhighlight>

NEW REM clears the export.bas programme from memory
<syntaxhighlight lang="basic4gl">
.
LOAD “demo1.bas”
LIST
10 OPEN ”O”,#1, “/sys/devices/virtual/gpio/gpio4/direction”,2
20 OPEN ”O”,#2, “/sys/devices/virtual/gpio/gpio7/direction”,2
30 OPEN ”O”,#3, “/sys/devices/virtual/gpio/gpio8/direction”,2
REM opens the three pin direction files
40 PRINT #1, “out”
50 PRINT #2, “out”
60 PRINT #3, “in”
REM sets GPIO pins 4 and 7 as outputs and GPIO pin 8 as input.
70 CLOSE #1
80 CLOSE #2
90 CLOSE #3
REM closes all open files, allowing the system to perform the direction settings.
100 OPEN ”I”,#8, “/sys/devices/virtual/gpio/gpio8/value”,1
REM opens the GPIO pin 8 value file
110 INPUT #8,x
REM reads the value of the input pin and stores the value in numerical variable x
120 CLOSE #8
REM closes the open file, allowing the system to read the value of the input pin and store the value in numerical variable x.
130 OPEN “O”,#1, “/sys/devices/virtual/gpio/gpio4/value”,1
140 OPEN “O”,#2, “/sys/devices/virtual/gpio/gpio7/value”,1
REM opens the GPIO pins 4 and value files ready for outputting 1s and 0s.
150 IF x<1 THEN GOTO 160 ELSE GOTO 190
REM tests the state of the switch (1 or0) and directs the program to generate the appropriate outputs
160 PRINT #1,”1”
170 PRINT #2,”0”
180 GOTO 210
190 PRINT#1,"0"
200 PRINT #2,"1"
210 CLOSE #1
220 CLOSE #2
REM Closes the files and allows the outputs to light the LED
230 END.
</syntaxhighlight>

When all is done, we should unexport the GPIO pins, to leave the R-Pi as we found it.(Ref 1.)
<syntaxhighlight lang="basic4gl">
NEW
LOAD “unexport.bas”
LIST
REM a set of Shell statements to unexport the three GPIO pins.
10 echo “4” > /sys/class/gpio/unexport
20 echo “7” > /sys/class/gpio/unexport
30 echo “8” > /sys/class/gpio/unexport
RUN
</syntaxhighlight>
A simple circuit to provide the switched input and the two LED outputs.

Ancient Mariner. Dec. 2012

References.

1. This paper RPi Low-level peripherals.

2. Ed Beynon. [http://www.ybw.com/forums/showthread.php?t=331320&page=5 http://www.ybw.com/forums/showthread.php?t=331320&page=5]

3. Arthur Kaletzky. Private communication. 25/10/2012

4. bwbasic manual.<br/>

For the two original documents this example has been copied from see:<br/>
[[Media:GPIO_Driving_Example_(BASIC)_.doc | GPIO_Driving_Example_(BASIC)_.doc]]

[[Media:Raspberry_Pi_I-O_viii.doc | Raspberry_Pi_I-O_viii.doc]]

==MIPI CSI-2==

On the production board<ref>http://www.raspberrypi.org/wp-content/uploads/2012/04/Raspberry-Pi-Schematics-R1.0.pdf</ref>, the Raspberry Pi Foundation design brings out the MIPI CSI-2 (Camera Serial Interface<ref>http://www.mipi.org/specifications/camera-interface</ref>) to a 15-way flat flex connector S5, between the Ethernet and HDMI connectors. A compatible camera has been discussed as working in tests and is planned for release at a later date.<ref>http://www.raspberrypi.org/forum/projects-and-collaboration-general/complex-camera-peripherials#p72602</ref>.


==DSI==

On the production board, the Raspberry Pi Foundation design brings out the DSI (Display Serial Interface<ref>http://www.mipi.org/specifications/display-interface</ref>) to a 15-way flat flex connector labelled S2, next to Raspberry Pi logo. It has two data lanes and a clock lane, to drive a possible future LCD screen device. Some smart phone screens use DSI<ref>http://en.wikipedia.org/wiki/Display_Serial_Interface</ref>.

==CEC==

[[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.
Eben notes that he has seen CEC demos on the Broadcom SoC they are using.

libCEC with Raspberry Pi support has been included in OpenELEC and will be included in Raspbmc RC4.<ref>http://blog.pulse-eight.com/2012/08/01/libcec-1-8-0-a-firmware-upgrade-and-raspberry-pi-support/</ref>

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.

== References ==
<references/>

{{Template:Raspberry Pi}}