Rpi Low-level peripherals - Revision history

Tufty: Transferred to RPi Low-level peripherals, intentionally blanking and redirecting

2012-01-28T20:17:52Z

Transferred to RPi Low-level peripherals, intentionally blanking and redirecting

Show changes

Tufty: Adding template

2012-01-28T14:05:21Z

Adding template

Tufty at 18:00, 27 January 2012

2012-01-27T18:00:19Z

Harley: /* CEC */

2012-01-26T15:27:27Z

‎CEC

Gimliflea: /* Driver support */

2012-01-24T17:31:25Z

‎Driver support

Meltwater: /* Code examples */

2012-01-19T21:20:08Z

‎Code examples

Meltwater: /* Code examples */ - link to Gert for the GPIO code ex

2012-01-19T21:15:28Z

‎Code examples: - link to Gert for the GPIO code ex

Meltwater: pin spacing

2012-01-19T17:25:42Z

pin spacing

Alpaca: /* Power pins */

2012-01-16T21:48:29Z

‎Power pins

Alpaca: /* Power pins */

2012-01-16T21:47:03Z

‎Power pins

← Older revision		Revision as of 14:05, 28 January 2012
Line 227:		Line 227:
	== References ==		== References ==
	<references/>		<references/>
		+
		+
		+	{{Template:Raspberry Pi}}

@@ Line 1: / Line 1: @@
 [[Category: RaspberryPi]]
 [[File:GPIOs.gif|thumb|254px|right|the layout of the Rpi GPIO's, not colour coded to the table. [https://sites.google.com/site/burngatehouse/home/drawings/GPIOs.gif Source] ]]
-The Rpi allows peripherals and expansion boards to access the CPU by exposing the in and outputs. The production board has a 26-pin 2.54mm (100mil)<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907</ref> expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is column 0 on the bottom row. <ref>http://www.raspberrypi.org/archives/384</ref>
+The Rpi allows peripherals and expansion boards (such as the upcoming [[Rpi Gertboard]]) to access the CPU by exposing the in and outputs. The production board has a 26-pin 2.54mm (100mil)<ref>http://www.raspberrypi.org/forum/features-and-requests/easy-gpio-hardware-software/page-3/#p31907</ref> expansion header, arranged in a 2x13 strip. They provide 8 GPIO pins plus access to I2C, SPI, UART), as well as +3V3, +5V and GND supply lines.  Pin one is column 0 on the bottom row. <ref>http://www.raspberrypi.org/archives/384</ref>
 Voltage levels are 3v3.  There is no over-voltage protection on the board - the intention is that people interested in serious interfacing will use an external board with buffers, level conversion and analog I/O rather than soldering directly onto the main board.

@@ Line 220: / Line 220: @@
 ==CEC==
-HDMI-CEC is supported by hardware but some driver work will be needed and currently isn't exposed into Linux userland.
+[[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.
 == References ==
 <references/>

@@ Line 62: / Line 62: @@
 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 Foundation will not include a SPI driver in the initial release, we hope the community might write one.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1278.0</ref>
+The Foundation will not include an SPI driver in the initial release, we hope the community might write one.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1278.0</ref>
 The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1202</ref>
 ===Code examples===
 [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.

@@ Line 65: / Line 65: @@
 The Foundation will not include an I2C driver in the initial release, we hope the community might provide one, standard linux I2C drivers should work with minimal modification.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1202</ref>
 ===Code examples===
-[http://www.raspberrypi.org/forum/educational-applications/gertboard/page-4/#p31555 | Gert van Loo, has provided] some tested code which accesses the GPIO pins through direct GPIO register manipulation in C-code.
+[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:

@@ Line 40: / Line 40: @@
 Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board.<ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1536#postid-21841</ref>
-*Model A: 1000mA - 500mA = 500mA
+*Model A: 1000mA - 500mA -> max power draw: 500mA
-*Model B: 1000mA - 700mA = 300mA
+*Model B: 1000mA - 700mA -> max power draw: 300mA
 ==General Purpose Input/Output (GPIO)==

@@ Line 38: / Line 38: @@
 ==Power pins==
 Maximum permitted current draw from the 3v3 pin is 50mA.
-Maximum permitted current draw from the 5v pin is the USB input current (usually 1A) minus any current draw from the rest of the board, or about 500mA for model A, or 700mA for B. <ref>http://www.raspberrypi.org/forum?mingleforumaction=viewtopic&t=1536#postid-21841</ref>
 ==General Purpose Input/Output (GPIO)==