Raspberrypi Odt
Raspberrypi Odt
Raspberrypi Odt
Hardware
Initial sales were of the Model B, with Model A following in early 2013. Model A has one USB
port and no Ethernet controller, and costs less than the Model B with two USB ports and a 10/100
Ethernet controller.
Though the Model A does not have an 8P8C (RJ45) Ethernet port, it can connect to a network
by using an external user-supplied USB Ethernet or Wi-Fi adapter. On the model B the Ethernet port is
provided by a built-in USB Ethernet adapter. As is typical of modern computers, generic USB
keyboards and mice are compatible with the Raspberry Pi.
The Raspberry Pi does not come with a real-time clock, so an OS must use a network time
server, or ask the user for time information at boot time to get access to time and date for file time and
date stamping. However, a real-time clock (such as the DS1307) with battery backup can be added via
the I²C interface.
On 20 April 2012 the schematics for the Model-A and Model-B were released by the Raspberry
Pi Foundation.
Hardware accelerated video (H.264) encoding became available on 24 August 2012 when it
became known that the existing license also covered encoding. Previously it was thought that encoding
would be added with the release of the announced camera module. However, no stable software support
exists for hardware H.264 encoding.
At the same time the Raspberry Pi Foundation released two additional codecs that can be
bought separately, MPEG-2 and Microsoft's VC-1. Also it was announced that the Pi will support CEC,
enabling it to be controlled with the television's remote control.
On 5 September 2012, a revision 2.0 board was announced, with a number of minor corrections
and improvements.
On 15 October 2012, the Raspberry Pi foundation announced that new Raspberry Pi model B's
would be fitted with 512 MB instead of 256 MB RAM.
Specifications
Model A Model B
Target price: US$ 25 US$ 35
SoC: Broadcom BCM2835 (CPU, GPU, DSP, SDRAM, and single USB port)
CPU: 700 MHz ARM1176JZF-S core (ARM11 family, ARMv6 instruction set)
GPU: Broadcom VideoCore IV @ 250 MHz
OpenGL ES 2.0 (24 GFLOPS)
MPEG-2 and VC-1 (with license), 1080p30 h.264/MPEG-4 AVC high-profile
decoder and encoder
Memory 256 MB (shared with GPU) 512 MB (shared with GPU) as of 15 October
(SDRAM): 2012
USB 2.0 ports: 1 (direct from BCM2835 chip) 2 (via the built in integrated 3-port USB
hub)
Video input: A CSI input connector allows for the connection of a RPF designed camera
module
Video outputs: Composite RCA (PAL and NTSC), HDMI (rev 1.3 & 1.4),[87] raw LCD Panels
via DSI
14 HDMI resolutions from 640×350 to 1920×1200 plus various PAL and NTSC
standards.
Audio outputs: 3.5 mm jack, HDMI, and, as of revision 2 boards, I²S audio (also potentially for
audio input)
Onboard storage: SD / MMC / SDIO card slot (3.3 V card power support only)
Onboard network: None 10/100 Mbit/s Ethernet (8P8C) USB adapter
on the third port of the USB hub
Low-level 8 × GPIO,[92] UART, I²C bus, SPI bus with two chip selects, I²S audio +3.3 V,
peripherals: +5 V, ground
Power ratings: 300 mA (1.5 W) 700 mA (3.5 W)
Power source: 5 V via MicroUSB or GPIO header
Size: 85.60 mm × 56 mm (3.370 in × 2.205 in)
Weight: 45 g (1.6 oz)
Operating systems: Arch Linux ARM,[2] Debian GNU/Linux, Gentoo, Fedora, FreeBSD, NetBSD,
Plan 9, Raspbian OS, RISC OS, Slackware Linux
Notes
1. Model A and Model B are cultural references to the original models of the British educational
BBC Micro computer, developed by Acorn Computers, who originally developed the ARM
processors (the architecture of the Raspberry Pi) and operating system RISC OS, which will
also be able to be run on the Raspberry Pi (version 5.17).
2. On the older beta model B boards, 128 MB was allocated by default to the GPU, leaving 128
MB for the CPU. On the first 256 MB release model B (and Model A), three different splits
were possible. The default split was 192 MB (CPU RAM), which should be sufficient for
standalone 1080p video decoding, or for simple 3D, but probably not for both together. 224 MB
was for Linux only, with just a 1080p frame buffer, and was likely to fail for any video or 3D.
128 MB was for heavy 3D, possibly also with video decoding (e.g. XBMC). Comparatively the
Nokia 701 uses 128 MB for the Broadcom Video Core IV. For the new model B with 512 MB
RAM initially there were new standard memory split files released( arm256_start.elf,
arm384_start.elf, arm496_start.elf) for 256 MB, 384 MB and 496 MB CPU RAM (and 256 MB,
128 MB and 16 MB video RAM). But a week or so later the RPF released a new version of
start.elf that could read a new entry in config.txt (gpu_mem=xx) and could dynamically assign
an amount of RAM (from 16 to 256 MB in 8 MB steps) to the GPU, so the older method of
memory splits became obsolete, and a single start.elf worked the same for 256 and 512 MB Pis.
3. Level 2 cache is 128 KB, used primarily by the GPU, not the CPU.
4. The ARM11 is based on version 6 of the ARM architecture (ARMv6k), which due to its age is
no longer supported by several popular versions of Linux, including Ubuntu which dropped
support for processors below ARMv7 in 2009.
5. The Raspberry Pi also contains a 15-pin MIPI camera interface (CSI) connector, which is used
with the Raspberry Pi Camera Addon.
6. Support for raw LCD panels is available in hardware through the available DSI connector from
the Mobile Industry Processor Interface (MIPI) Alliance.[88] Software support is being planned.
7. Supported digital video resolutions are: 640 × 350 EGA; 640 × 480 VGA; 800 × 600 SVGA;
1024 × 768 XGA; 1280×720 720p HDTV; 1280 × 768 WXGA Variant; 1280 × 800 WXGA
Variant; 1280 × 1024 SXGA; 1366 × 768 WXGA Variant; 1400 × 1050 SXGA+; 1600 × 1200
UXGA; 1680 × 1050 WXGA+; 1920 × 1080 1080p HDTV; 1920 × 1200 WUXGA.[90] Also to
be supported are the generation of 576i and 480i composite video signals for PAL-BGHID,
PAL-M, PAL-N, NTSC and NTSC-J
8. Size dimensions do not include overhanging components such as the USB and RCA connectors.
9. Newer versions of the firmware contain the option to choose between five overclock ("turbo")
presets that when turned on try to get the most performance out of the SoC without impairing
the lifetime of the Pi. This is done by monitoring the core temperature of the chip, and the CPU
load, and dynamically adjusting clock speeds and the core voltage. When the demand is low on
the CPU, or it is running too hot, the performance is throttled, but if the CPU has much to do,
and the chip's temperature is acceptable, performance is temporarily increased, with clock
speeds of up to 1 GHz, depending on the individual board, and on which of the turbo settings is
used. The five settings are:
1. None; 700 MHz ARM, 250 MHz core, 400 MHz SDRAM, 0 overvolt,
2. Modest; 800 MHz ARM, 250 MHz core, 400 MHz SDRAM, 0 overvolt,
3. Medium 900 MHz ARM, 250 MHz core, 450 MHz SDRAM, 2 overvolt,
4. High; 950 MHz ARM, 250 MHz core, 450 MHz SDRAM, 6 overvolt,
5. Turbo; 1000 MHz ARM, 500 MHz core, 600 MHz SDRAM, 6 overvolt
In the highest (turbo) preset the SDRAM clock was originally 500 MHz, but this was later
changed to 600 MHz because 500 MHz sometimes causes SD card corruption. Simultaneously in high
mode the core clock speed was lowered from 450 to 250 MHz, and in medium mode from 333 to 250
MHz.
Accessories
The Foundation reported on its blog in May 2012 about a prototype camera module they had
tested. The prototype used a 14 megapixel module, while the released version will be 5 megapixels.
On 14 May 2013 the foundation and the distributors RS Components & Premier
Farnell/Element 14 launched the Raspberry Pi camera board with a firmware update to support it. The
camera board is shipped with a flexible flat cable that plugs into the CSI connector located between the
Ethernet and HDMI ports. In Raspbian support can be enabled by the installing or upgrading to the
latest version of the OS and then running Raspi-config and selecting the camera option. The cost of the
camera module is 20 EUR in Europe (9 September 2013). and supports 1080p, 720p, 640x480p video.
The footprint dimensions are 25 mm x 20 mm x 9 mm.
A number of Raspberry Pi specific peripheral devices and cases are available from third-
party suppliers. These include the Raspberry Pi Foundation sanctioned Gertboard, which is designed
for educational purposes, and expands the Raspberry Pi's GPIO pins to allow interface with and control
of LEDs, switches, analog signals, sensors and other devices. It also includes an optional Arduino
compatible controller to interface with the Pi.
Software
Driver API
The Raspberry Pi primarily uses Linux kernel-based operating systems.
The GPU hardware is accessed via a firmware image which is loaded into the GPU at boot time
from the SD-card. The firmware image is known as the binary blob, while the associated ARM coded
Linux drivers were initially closed source. This part of the driver code was later released, however
much of the actual driver work is done using the closed source GPU code. Application software uses
calls to closed source run-time libraries (Open Max, OpenGL ES or open VG) which in turn calls an
open source driver inside the Linux kernel, which then calls the closed source Videocore IV GPU
driver code. The API of the kernel driver is specific for these closed libraries. Video applications use
OpenMAX, 3D applications use OpenGL ES and 2D applications use OpenVG which both in turn use
EGL. OpenMAX and EGL use the open source kernel driver in turn.
Raspbian
After cycling through several recommendations since just before the hardware was first made
available, the Raspberry Pi Foundation created the New Out Of Box System (NOOBS) installer, and as
of July 2013 suggests using it to install the Debian-derived Raspbian. The Foundation intends to create
an application store website for people to exchange programs.
Raspbian is a Debian-based free operating system optimized for the Raspberry Pi hardware. It is
the current recommended system, and was officially released in July 2012, although it is still in
development. It is free software and maintained independently of the Raspberry Pi Foundation. It is
based on ARM hard-float (armhf)-Debian 7 'Wheezy' architecture port with the LXDE desktop
environment, but optimized for the ARMv6 instruction set of the Raspberry Pi, which lacks Jazelle
RCT/ThumbEE, VFPv3 and the NEON SIMD extension.[clarification needed] It provides some
available deb software packages, pre-compiled software bundles. A minimum size of 2 GB SD card is
required for Raspbian, but a 4 GB SD card or above is recommended. The downloaded Raspbian
Wheezy image file has to be unzipped and then written to a suitable SD card, formatting it for use.
History
On 19 February 2012, the Raspberry Pi Foundation released its first proof of concept SD card
image that could be loaded onto an SD card to produce a preliminary operating system. The image was
based on Debian 6.0 (Squeeze), with the LXDE desktop and the Midori browser, plus various
programming tools. The image also runs on QEMU allowing the Raspberry Pi to be emulated on
various other platforms.
On 8 March 2012 The Raspberry Pi Foundation released Raspberry Pi Fedora Remix, at the
time its recommended Linux distribution, which was developed at Seneca College in Canada.
The Debian port was initiated by Mike Thompson, former CTO of Atomz, in March 2012, a
week after the Raspberry Pi's launch. The effort was largely carried out by Thompson and Peter Green,
a volunteer Debian developer, with some support from the Raspberry Pi Foundation, who tested the
resulting binaries that the two produced during the early stages (neither Thompson nor Green had
physical access to the hardware, as boards were not widely accessible at the time due to demand.)
While the preliminary proof of concept image distributed by the Foundation before launch was also
Debian-based, it differed from Thompson and Green's Raspbian effort in a couple of ways.
The POC image was based on then-stable Debian Squeeze, while Raspbian aimed to
track then-upcoming Debian Wheezy packages. Aside from the updated packages that would come
with the new release, Wheezy was also set to introduce the armhf architecture, which became the raison
d'être for the Raspbian effort.
The Squeeze-based POC image was limited to the armel architecture, which was, at the time of
Squeeze's release, the latest attempt by the Debian project to support the newest ARM EABI. The
armhf architecture in Wheezy intended to support the ARM VFP hardware floating-point unit, while
armel was limited to emulating floating point operations in software. Since the Raspberry Pi included a
VFP, being able to make use of the hardware unit would result in performance gains and reduced power
usage for floating point operations.The armhf effort in mainline Debian, however, was orthogonal to
the work surrounding the Pi and only intended to support ARMv7 at a minimum, which would mean
the Pi, an ARMv6k device, would not benefit.As a result, Thompson and Green set out to build the
19,000 Debian packages for the device using a custom build cluster.On 3 June 2013 the Raspberry Pi
foundation introduced a new tool called New Out Of Box Software or NOOBS which makes the
Raspberry Pi easier to use by simplifying the installation of an operating system. Instead of using
specific software to prepare an SD card, a file is unzipped and the contents copied over to a FAT
formatted (4 GB or bigger) SD card. That card can then be booted on the Raspberry Pi and a choice of
six operating systems is presented for installation on the card. The system also contains a recovery
partition that allows for the quick restoration of the installed OS, tools to modify the config.txt and an
online help button and web browser which directs to the Raspberry Pi Forums.
The operating systems the NOOBS installer is tailored for are:
• Archlinux ARM
• OpenELEC
• Pidora (Fedora Remix)
• Raspbmc
• Raspbian (recommended)
• RISC OS