Difference between revisions of "Talk:RPi Low-level peripherals"
| Line 1: | Line 1: | ||
| + | Save old header pinout table | ||
| + | |||
| + | '''Header Pinout:''' | ||
| + | {| border="1" style="text-align:center;" | ||
| + | | '''Top Row''' || bgcolor="red" | <span style="color:white">5V0</span> || DNC || bgcolor="black" | <span style="color:white">GND</span> || bgcolor="yellow" | UART0_TXD || bgcolor="yellow" | UART0_RXD || bgcolor="lime" | GPIO1_PWM || DNC || bgcolor="lime" | GPIO4 || bgcolor="lime" | GPIO5 || DNC || bgcolor="lime" | GPIO6 || bgcolor="purple" | <span style="color:white">SPI_CE0_N</span> || bgcolor="purple" | <span style="color:white">SPI_CE1_N</span> | ||
| + | |- | ||
| + | | '''Bottom Row''' || bgcolor="orange" | 3V3 || bgcolor="cyan" | I2C0_SDA || bgcolor="cyan" | I2C0_SCL || bgcolor="lime" | GPIO7 || DNC || bgcolor="lime" | GPIO0 || bgcolor="lime" | GPIO2 || bgcolor="lime" | GPIO3 || DNC || bgcolor="purple" | <span style="color:white">SPI_MOSI</span> || bgcolor="purple" | <span style="color:white">SPI_MISO</span> || bgcolor="purple" | <span style="color:white">SPI_SCLK</span> || DNC | ||
| + | |} | ||
| + | |||
| + | |||
| + | {| border="1" | ||
| + | ! Colour legend | ||
| + | |- | ||
| + | | bgcolor="red" | <span style="color:white">+5V</span> | ||
| + | |- | ||
| + | | bgcolor="orange" | +3.3V | ||
| + | |- | ||
| + | | Do not connect | ||
| + | |- | ||
| + | | bgcolor="yellow" | UART | ||
| + | |- | ||
| + | | bgcolor="lime" | GPIO | ||
| + | |- | ||
| + | | bgcolor="purple" | <span style="color:white">SPI</span> | ||
| + | |- | ||
| + | | bgcolor="cyan" | I2C | ||
| + | |} | ||
| + | |||
| + | ---- | ||
| + | |||
Donster2k: "Kernel boot messages go to the UART at 115200bps." - This should be configurable as a kernel parameter. It is the bootloader that will always output to the uart on the header, correct? | Donster2k: "Kernel boot messages go to the UART at 115200bps." - This should be configurable as a kernel parameter. It is the bootloader that will always output to the uart on the header, correct? | ||
Revision as of 18:11, 26 March 2012
Save old header pinout table
Header Pinout:
| Top Row | 5V0 | DNC | GND | UART0_TXD | UART0_RXD | GPIO1_PWM | DNC | GPIO4 | GPIO5 | DNC | GPIO6 | SPI_CE0_N | SPI_CE1_N |
| Bottom Row | 3V3 | I2C0_SDA | I2C0_SCL | GPIO7 | DNC | GPIO0 | GPIO2 | GPIO3 | DNC | SPI_MOSI | SPI_MISO | SPI_SCLK | DNC |
| Colour legend |
|---|
| +5V |
| +3.3V |
| Do not connect |
| UART |
| GPIO |
| SPI |
| I2C |
Donster2k: "Kernel boot messages go to the UART at 115200bps." - This should be configurable as a kernel parameter. It is the bootloader that will always output to the uart on the header, correct?
Donster2k: What will be the power-on states of the GPIO pins?
Donster2k: USB2 spec states that the max current draw from a port (either powered hub or PC's usb) is 500mA. Does this mean that the revB module will need to be powered via a usb charger?
Donster2k: Most of the reference links to the forum are broken. Probably happened when they moved the forum.
naicheben: The color legend is fine for the table "Header Pinout" but it does not correspond to the GPIOs.gif as stated below the GIF. Shouldn't we better use same color "coding"?
