Raspberry Pi User Guide - Eben Upton - E-Book

Raspberry Pi User Guide E-Book

Eben Upton

4,8
14,99 €

-100%
Sammeln Sie Punkte in unserem Gutscheinprogramm und kaufen Sie E-Books und Hörbücher mit bis zu 100% Rabatt.

Mehr erfahren.
Beschreibung

The “unofficial official” guide to the Raspberry Pi, complete with creator insight

Raspberry Pi User Guide, 3rdEdition contains everything you need to know to get up and running with Raspberry Pi. This book is the go-to guide for Noobs who want to dive right in. This updated third edition covers the model B+ Raspberry Pi and its software, additional USB ports, and changes to the GPIO, including new information on Arduino and Minecraft on the Pi. You’ll find clear, step-by-step instruction for everything from software installation and configuration to customizing your Raspberry Pi with capability-expanding add-ons. Learn the basic Linux SysAdmin and flexible programming languages that allow you to make your Pi into whatever you want it to be.

The Raspberry Pi was created by the UK Non-profit Raspberry Pi Foundation to help get kids interested in programming. Affordable, portable, and utterly adorable, the Pi exceeded all expectations, introducing millions of people to programming since its creation. The Raspberry Pi User Guide, 3rd Edition helps you and your Pi get acquainted, with clear instruction in easy to understand language.

  • Install software, configure, and connect your Raspberry Pi to other devices
  • Master basic Linux System Admin to better understand nomenclature and conventions
  • Write basic productivity and multimedia programs in Scratch and Python
  • Extend capabilities with add-ons like Gertboard, Arduino, and more

The Raspberry Pi has become a full-fledged phenomenon, popular with tinkerers, hackers, experimenters, and inventors. If you want to get started but aren’t sure where to begin, Raspberry Pi User Guide, 3rd Edition contains everything you need. 

Sie lesen das E-Book in den Legimi-Apps auf:

Android
iOS
von Legimi
zertifizierten E-Readern

Seitenzahl: 400

Veröffentlichungsjahr: 2014

Bewertungen
4,8 (18 Bewertungen)
14
4
0
0
0
Mehr Informationen
Mehr Informationen
Legimi prüft nicht, ob Rezensionen von Nutzern stammen, die den betreffenden Titel tatsächlich gekauft oder gelesen/gehört haben. Wir entfernen aber gefälschte Rezensionen.



Eben Upton and Gareth Halfacree

This edition first published 2014

© 2014 Eben Upton and Gareth Halfacree

Registered office

John Wiley & Sons Ltd., The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ, United Kingdom

For details of our global editorial offices, for customer services and for information about how to apply for permission to reuse the copyright material in this book please see our website at www.wiley.com.

The right of the authors to be identified as the authors of this work has been asserted in accordance with the Copyright, Designs and Patents Act 1988.

All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, except as permitted by the UK Copyright, Designs and Patents Act 1988, without the prior permission of the publisher.

Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.

Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners. The publisher is not associated with any product or vendor mentioned in this book. This publication is designed to provide accurate and authoritative information in regard to the subject matter covered. It is sold on the understanding that the publisher is not engaged in rendering professional services. If professional advice or other expert assistance is required, the services of a competent professional should be sought.

Trademarks: Wiley and the Wiley logo are trademarks or registered trademarks of John Wiley & Sons, Inc. and/or its affiliates in the United States and/or other countries, and may not be used without written permission. Raspberry Pi and the Raspberry Pi logo are registered trademarks of the Raspberry Pi Foundation. All other trademarks are the property of their respective owners. John Wiley & Sons, Ltd. is not associated with any product or vendor mentioned in the book.

Google Drive™ is a registered trademark of Google™.

A catalogue record for this book is available from the British Library.

ISBN 978-1-118-92166-1 (Pbk); ISBN 978-1-118-92168-5 (ePDF); ISBN 978-1-118-92167-8 (ePub)

Set in 10 pt. Chaparral Pro by TCS/SPS

Printed simultaneously in Great Britain and the United States

Publisher’s Acknowledgements

Some of the people who helped bring this book to market include the following:

Editorial and Production

VP Consumer and Technology Publishing Director: Michelle Leete

Associate Director–Book Content Management: Martin Tribe

Associate Publisher: Chris Webb

Executive Commissioning Editor: Craig Smith

Project Editor: John Sleeva

Copy Editor: Melba Hopper

Technical Editor: Andrew Scheller

Senior Project Editor: Sara Shlaer

Editorial Manager: Rev Mengle

Editorial Assistant: Claire Johnson

Marketing

Marketing Manager: Lorna Mein

Associate Marketing Manager: Carrie Sherrill

Assistant Marketing Manager: Dave Allen

About the Authors

EBEN UPTON is a founder of the Raspberry Pi Foundation and serves as the CEO of Raspberry Pi (Trading), its commercial arm. He is a Technical Director with Broadcom, a Fortune 500 semiconductor company. In an earlier life, he founded two successful mobile games and middleware companies, Ideaworks 3d (now Marmalade) and Podfun, held the post of Director of Studies for Computer Science at St John's College, Cambridge, and wrote the Oxford Rhyming Dictionary with his father, Professor Clive Upton. He holds a BA, a PhD and an MBA from the University of Cambridge.

GARETH HALFACREE is a freelance technology journalist and the co-author of the Raspberry Pi User Guide alongside project co-founder Eben Upton. Formerly a system administrator working in the education sector, Gareth's passion for open source projects has followed him from one career to another, and he can often be seen reviewing, documenting or even contributing to projects such as GNU/Linux, LibreOffice, Fritzing and Arduino. He is also the creator of the Sleepduino and Burnduino open hardware projects, which extend the capabilities of the Arduino electronics prototyping system. A summary of his current work can be found at http://freelance.halfacree.co.uk.

For Liz, who made it all possible.

—Eben

For my father, the enthusiastic past, and my daughter, the exciting future.

—Gareth

Raspberry Pi User Guide

Table of Contents

Introduction

Programming Is Fun!

A Bit of History

So What Can You Do with the Raspberry Pi?

Part I

Chapter 1: Meet the Raspberry Pi

A Trip Around the Board

Model A

Model B

Model B+

A History of Model B PCB Revisions

Revision 1

Revision 2

Model B+

A Bit of Background

ARM versus x86

Windows versus Linux

Chapter 2: Getting Started with the Raspberry Pi

Connecting a Display

Composite Video

HDMI Video

DSI Video

Connecting Audio

Connecting a Keyboard and Mouse

Installing NOOBS on an SD Card

Connecting External Storage

Connecting the Network

Wired Networking

Wireless Networking

Connecting Power

Installing the Operating System

Installing Using NOOBS

Installing Manually

Chapter 3: Linux System Administration

Linux: An Overview

Linux Basics

Introducing Raspbian

About Raspbian’s Parent, Debian

Alternatives to Raspbian

Using External Storage Devices

Creating a New User Account

File System Layout

Logical Layout

Physical Layout

Installing and Uninstalling Software

Obtaining Software from the Pi Store

Obtaining Software from Elsewhere

Finding the Software You Want

Installing Software

Uninstalling Software

Upgrading Software

Shutting the Pi Down Safely

Chapter 4: Troubleshooting

Keyboard and Mouse Diagnostics

Power Diagnostics

Display Diagnostics

Boot Diagnostics

Network Diagnostics

The Emergency Kernel

Chapter 5: Network Configuration

Wired Networking

Wireless Networking

Installing Firmware

Connecting to a Wireless Network via wpa_gui

Connecting to a Wireless Network via the Terminal

Chapter 6: The Raspberry Pi Software Configuration Tool

Running the Tool

The Setup Options Screen

1 Expand Filesystem

2 Change User Password

3 Enable Boot to Desktop/Scratch

4 Internationalisation Options

5 Enable Camera

6 Add to Rastrack

7 Overclock

8 Advanced Options

9 About raspi-config

Chapter 7: Advanced Raspberry Pi Configuration

Editing Configuration Files via NOOBS

Hardware Settings—config.txt

Modifying the Display

Boot Options

Overclocking the Raspberry Pi

Disabling L2 Cache

Enabling Test Mode

Memory Partitioning

Software Settings—cmdline.txt

Part II

Chapter 8: The Pi as a Home Theatre PC

Playing Music at the Console

Dedicated HTPC with Raspbmc

Streaming Internet Media

Streaming Local Network Media

Configuring Raspbmc

Chapter 9: The Pi as a Productivity Machine

Using Cloud-Based Apps

Using LibreOffice

Image Editing with the Gimp

Chapter 10: The Pi as a Web Server

Installing a LAMP Stack

Installing WordPress

Part III

Chapter 11: An Introduction to Scratch

Introducing Scratch

Example 1: Hello World

Example 2: Animation and Sound

Example 3: A Simple Game

Robotics and Sensors

Sensing with the PicoBoard

Robotics with LEGO

Further Reading

Chapter 12: An Introduction to Python

Introducing Python

Example 1: Hello World

Example 2: Comments, Inputs, Variables and Loops

Example 3: Gaming with pygame

Example 4: Python and Networking

Further Reading

Chapter 13: Minecraft Pi Edition

Introducing Minecraft Pi Edition

Installing Minecraft

Running Minecraft

Exploration

Hacking Minecraft

Part IV

Chapter 14: Learning to Hack Hardware

Electronic Equipment

Reading Resistor Colour Codes

Sourcing Components

Online Sources

Offline Sources

Hobby Specialists

Moving Up from the Breadboard

A Brief Guide to Soldering

Chapter 15: The GPIO Port

Identifying Your Board Revision

GPIO Pinout Diagrams

GPIO Features

UART Serial Bus

I²C Bus

SPI Bus

Using the GPIO Port in Python

GPIO Output: Flashing an LED

GPIO Input: Reading a Button

Chapter 16: The Raspberry Pi Camera Module

Why Use the Camera Module?

Installing the Camera Module

Enabling Camera Mode

Capturing Stills

Recording Video

Command-Line Time-Lapse Photography

Chapter 17: Add-On Boards

Ciseco Slice of Pi

Adafruit Prototyping Pi Plate

Fen Logic Gertboard

Part V

Appendix A: Python Recipes

Raspberry Snake (Chapter 12, Example 3)

IRC User List (Chapter 12, Example 4)

GPIO Input and Output (Chapter 15)

Appendix B: Raspberry Pi Camera Module Quick Reference

Shared Options

Raspistill Options

Raspivid Options

Raspiyuv Options

Appendix C: HDMI Display Modes

Guide

Table of Contents

Begin Reading

Pages

1

2

3

4

5

6

7

8

9

11

13

14

15

16

17

18

19

20

21

23

24

25

26

27

28

29

30

31

32

33

34

35

36

40

37

38

39

41

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

63

64

65

66

67

68

69

70

71

72

73

75

76

77

78

79

80

81

82

83

84

85

86

87

88

89

90

91

93

94

95

96

97

98

99

100

101

102

103

104

105

106

107

108

109

110

111

112

113

114

115

116

117

118

119

121

123

124

125

126

127

128

129

130

131

132

133

134

135

136

137

138

139

140

141

142

143

144

145

146

147

148

149

151

153

154

155

156

157

158

159

160

161

162

163

164

165

166

167

168

169

170

171

172

173

174

175

176

177

178

179

180

181

182

183

184

185

186

187

188

189

190

191

192

193

194

195

196

197

198

199

200

201

202

203

204

205

207

208

209

210

211

212

213

214

215

216

217

218

219

220

221

223

224

225

226

227

228

229

230

231

232

233

234

235

236

237

238

239

240

241

242

243

244

245

246

247

248

249

250

251

252

253

255

256

257

258

259

260

261

262

263

264

265

266

267

269

270

271

272

273

274

275

276

277

278

279

280

281

282

283

284

285

Introduction

“CHILDREN TODAY ARE digital natives”, said a man I got talking to at a fireworks party. “I don’t understand why you’re making this thing. My kids know more about setting up our PC than I do.”

I asked him if they could program, to which he replied: “Why would they want to? The computers do all the stuff they need for them already, don’t they? Isn’t that the point?”

As it happens, plenty of kids today aren’t digital natives. We have yet to meet any of these imagined wild digital children, swinging from ropes of twisted-pair cable and chanting war songs in nicely parsed Python. In the Raspberry Pi Foundation’s educational outreach work, we do meet a lot of kids whose entire interaction with technology is limited to closed platforms with graphical user interfaces (GUIs) that they use to play movies, do a spot of word-processed homework and play games. They can browse the web, upload pictures and video, and even design web pages. (They’re often better at setting the satellite TV box than Mum or Dad, too.) It’s a useful toolset, but it’s shockingly incomplete, and in a country where 20 percent of households still don’t have a computer in the home, even this toolset is not available to all children.

Despite the most fervent wishes of my new acquaintance at the fireworks party, computers don’t program themselves. We need an industry full of skilled engineers to keep technology moving forward, and we need young people to be taking those jobs to fill the pipeline as older engineers retire and leave the industry. But there’s much more to teaching a skill like programmatic thinking than breeding a new generation of coders and hardware hackers. Being able to structure your creative thoughts and tasks in complex, non-linear ways is a learned talent, and one that has huge benefits for everyone who acquires it, from historians to designers, lawyers and chemists.

Programming Is Fun!

It’s enormous, rewarding, creative fun. You can create gorgeous intricacies, as well as (much more gorgeous, in my opinion) clever, devastatingly quick and deceptively simple-looking routes through, under and over obstacles. You can make stuff that’ll have other people looking on jealously, and that’ll make you feel wonderfully smug all afternoon. In my day job, where I design the sort of silicon chips that we use in the Raspberry Pi as a processor and work on the low-level software that runs on them, I basically get paid to sit around all day playing. What could be better than equipping people to be able to spend a lifetime doing that?

It’s not even as if we’re coming from a position where children don’t want to get involved in the computer industry. A big kick up the backside came a few years ago, when we were moving quite slowly on the Raspberry Pi project. All the development work on Raspberry Pi was done in the spare evenings and weekends of the Foundation’s trustees and volunteers—we’re a charity, so the trustees aren’t paid by the Foundation, and we all have full-time jobs to pay the bills. This meant that, occasionally, motivation was hard to come by when all I wanted to do in the evening was slump in front of the Arrested Development boxed set with a glass of wine. One evening, when not slumping, I was talking to a neighbour’s nephew about the subjects he was taking for his General Certificate of Secondary Education (GCSE, the British system of public examinations taken in various subjects from the age of about 16), and I asked him what he wanted to do for a living later on.

“I want to write computer games”, he said.

“Awesome. What sort of computer do you have at home? I’ve got some programming books you might be interested in.”

“A Wii and an Xbox.”

On talking with him a bit more, it became clear that this perfectly smart kid had never done any real programming at all; that there wasn’t any machine that he could program in the house; and that his information and communication technology (ICT) classes—where he shared a computer and was taught about web page design, using spreadsheets and word processing—hadn’t really equipped him to use a computer even in the barest sense. But computer games were a passion for him (and there’s nothing peculiar about wanting to work on something you’re passionate about). So that was what he was hoping the GCSE subjects he’d chosen would enable him to do. He certainly had the artistic skills that the games industry looks for, and his maths and science marks weren’t bad. But his schooling had skirted around any programming—there were no Computing options on his syllabus, just more of the same ICT classes, with its emphasis on end users rather than programming. And his home interactions with computing meant that he stood a vanishingly small chance of acquiring the skills he needed in order to do what he really wanted to do with his life.

This is the sort of situation I want to see the back of, where potential and enthusiasm is squandered to no purpose. Now, obviously, I’m not monomaniacal enough to imagine that simply making the Raspberry Pi is enough to effect all the changes that are needed. But I do believe that it can act as a catalyst. We’re already seeing big changes in the UK schools’ curriculum, where Computing is arriving on the syllabus this year and ICT is being entirely reshaped, and we’ve seen a massive change in awareness of a gap in our educational and cultural provision for kids just in the short time since the Raspberry Pi was launched.

Too many of the computing devices a child will interact with daily are so locked down that they can’t be used creatively as a tool—even though computing is a creative subject. Try using your iPhone to act as the brains of a robot, or getting your PS3 to play a game you’ve written. Sure, you can program the home PC, but there are significant barriers in doing that which a lot of children don’t overcome: the need to download special software, and having the sort of parents who aren’t worried about you breaking something that they don’t know how to fix. And plenty of kids aren’t even aware that doing such a thing as programming the home PC is possible. They think of the PC as a machine with nice clicky icons that give you an easy way to do the things you need to do so you don’t need to think much. It comes in a sealed box, which Mum and Dad use to do the banking and which will cost lots of money to replace if something goes wrong!

The Raspberry Pi is cheap enough to buy with a few weeks’ pocket money, and you probably have all the equipment you need to make it work: a TV, an SD card that can come from an old camera, a mobile phone charger, a keyboard and a mouse. It’s not shared with the family; it belongs to the kid; and it’s small enough to put in a pocket and take to a friend’s house. If something goes wrong, it’s no big deal—you just swap out a new SD card and your Raspberry Pi is factory-new again. And all the tools, environments and learning materials that you need to get started on the long, smooth curve to learning how to program your Raspberry Pi are right there, waiting for you as soon as you turn it on.

A Bit of History

I started work on a tiny, affordable, bare-bones computer in 2006, when I was a Director of Studies in Computer Science at Cambridge University. I’d received a degree at the University Computer Lab as well as studying for a PhD while teaching there, and over that period, I’d noticed a distinct decline in the skillset of the young people who were applying to read Computer Science at the Lab. From a position in the mid-1990s, when 17-year-olds wanting to read Computer Science had come to the University with a grounding in several computer languages, knew a bit about hardware hacking, and often even worked in assembly language, we gradually found ourselves in a position where, by 2005, those kids were arriving having done some HTML—with a bit of PHP and Cascading Style Sheets if you were lucky. They were still fearsomely clever kids with lots of potential, but their experience with computers was entirely different from what we’d been seeing before.

The Computer Science course at Cambridge includes about 60 weeks of lecture and seminar time over three years. If you’re using the whole first year to bring students up to speed, it’s harder to get them to a position where they can start a PhD or go into industry over the next two years. The best undergraduates—the ones who performed the best at the end of their three-year course—were the ones who weren’t just programming when they’d been told to for their weekly assignment or for a class project. They were the ones who were programming in their spare time. So the initial idea behind the Raspberry Pi was a very parochial one with a very tight (and pretty unambitious) focus: I wanted to make a tool to get the small number of applicants to this small university course a kick start. My colleagues and I imagined we’d hand out these devices to schoolkids at open days, and if they came to Cambridge for an interview a few months later, we’d ask what they’d done with the free computer we’d given them. Those who had done something interesting would be the ones that we’d be interested in having in the program. We thought maybe we’d make a few hundred of these devices, or best case, a lifetime production run of a few thousand.

Of course, once work was seriously underway on the project, it became obvious that there was a lot more we could address with a cheap little computer like this. What we started with is a long way indeed from the Raspberry Pi you see today. I began by soldering up the longest piece of breadboard you can buy at Maplin with an Atmel chip at our kitchen table, and the first crude prototypes used cheap microcontroller chips to drive a standard-definition TV set directly. With only 512 K of RAM, and a few MIPS of processing power, these prototypes were very similar in performance to the original 8-bit microcomputers. It was hard to imagine these machines capturing the imaginations of kids used to modern games consoles and iPads.

There had been discussions at the University Computer Lab about the general state of computer education, and when I left the Lab for a non-academic job in the industry, I noticed that I was seeing the same issues in young job applicants as I’d been seeing at the University. So I got together with my colleagues Dr Rob Mullins and Professor Alan Mycroft (two colleagues from the Computer Lab), Jack Lang (who lectures in entrepreneurship at the University), Pete Lomas (a hardware guru) and David Braben (a Cambridge games industry leading light with an invaluable address book), and over beers (and, in Jack’s case, cheese and wine), we set up the Raspberry Pi Foundation—a little charity with big ideas.

Why “Raspberry Pi”?

We get asked a lot where the name “Raspberry Pi” came from. Bits of the name came from different trustees. It’s one of the very few successful bits of design by committee I’ve seen, and to be honest, I hated it at first. (I have since come to love the name, because it works really well—but it took a bit of getting used to since I’d been calling the project the “ABC Micro” in my head for years.) It’s “Raspberry” because there’s a long tradition of fruit names in computer companies (besides the obvious, there are the old Tangerine and Apricot computers—and we like to think of the Acorn as a fruit as well). “Pi” is a mangling of “Python”, which we thought early on in development would be the only programming language available on a much less powerful platform than the Raspberry Pi we ended up with. As it happens, we still recommend Python as our favourite language for learning and development, but there is a world of other language options you can explore on the Raspberry Pi too.

In my new role as a chip architect at Broadcom, a big semiconductor company, I had access to inexpensive but high-performing hardware produced by the company with the intention of being used in very high-end mobile phones—the sort with the HD video and the 14-megapixel cameras. I was amazed by the difference between the chips you could buy for $10 as a small developer, and what you could buy as a cell-phone manufacturer for roughly the same amount of money: general purpose processing, 3D graphics, video and memory bundled into a single BGA package the size of a fingernail. These microchips consume very little power, and have big capabilities. They are especially good at multimedia, and were already being used by set-top box companies to play high-definition video. A chip like this seemed the obvious next step for the shape the Raspberry Pi was taking, so I worked on taping out a low-cost variant that had an ARM microprocessor on board and could handle the processing grunt we needed.

We felt it was important to have a way to get kids enthusiastic about using a Raspberry Pi even if they didn’t feel very enthusiastic about programming. In the 1980s, if you wanted to play a computer game, you had to boot up a box that went “bing” and fed you a command prompt. It required typing a little bit of code just to get started, and most users didn’t ever go beyond that—but some did, and got beguiled into learning how to program by that little bit of interaction. We realised that the Raspberry Pi could work as a very capable, very tiny, very cheap modern media centre, so we emphasised that capability to suck in the unwary—with the hope that they’d pick up some programming while they’re at it.

After about five years’ hard grind, we had created a very cute prototype board, about the size of a thumb drive. We included a permanent camera module on top of the board to demonstrate the sort of peripherals that can easily be added (there was no camera when we launched because it brought the price up too much, but we’ve now made a separate, cheap camera module available for photography projects), and brought it along to a number of meetings with the BBC’s R&D department. Those of us who grew up in the UK in the 1980s had learned a lot about 8-bit computing from the BBC Microcomputer and the ecosystem that had grown up around it—with BBC-produced books, magazines and TV programmes—so I’d hoped that they might be interested in developing the Raspberry Pi further. But as it turned out, something has changed since we were kids: various competition laws in the UK and the EU meant that “the Beeb” couldn’t become involved in the way we’d hoped. In a last-ditch attempt to get something organised with them, we ditched the R&D department idea and David (he of the giant address book) organised a meeting with Rory Cellan-Jones, a senior tech journalist, in May 2011. Rory didn’t hold out much hope for partnership with the BBC, but he did ask if he could take a video of the little prototype board with his phone, to put on his blog.

The next morning, Rory’s video had gone viral, and I realised that we had accidentally promised the world that we’d make everybody a $25 computer.

While Rory went off to write another blog post on exactly what it is that makes a video go viral, we went off to put our thinking caps on. That original, thumb-drive-sized prototype didn’t fit the bill: with the camera included as standard, it was way too expensive to meet the cost model we’d suggested (the $25 figure came from my statement to the BBC that the Raspberry Pi should cost around the same as a text book, and is a splendid demonstration of the fact that I had no idea how much text books cost these days), and the tiny prototype model didn’t have enough room around its periphery for all the ports we needed to make it as useable as we wanted it to be. So we spent a year working on engineering the board to lower cost as much as possible while retaining all the features we wanted (engineering cost down is a harder job than you might think), and to get the Raspberry Pi as useable as possible for people who might not be able to afford much in the way of peripherals.

We knew we wanted the Raspberry Pi to be used with TVs at home, just like the ZX Spectrum in the 1980s, saving the user the cost of a monitor. But not everybody has access to an HDMI television, so we added a composite port to make the Raspberry Pi work with an old cathode-ray television instead since SD cards are cheap and easy to find. We decided against microSD as the storage medium, because the little fingernail-sized cards are so flimsy in the hands of children and so easy to lose. And we went through several iterations of power supply, ending up with a micro USB cable. Recently, micro USB became the standard charger cable for mobile telephones across the EU (and it’s becoming the standard everywhere), which means the cables are becoming more and more ubiquitous, and in many cases, people already have them at home.

By the end of 2011, with a projected February release date, it was becoming obvious to us that things were moving faster, and demand was higher, than we were ever going to be able to cope with. The initial launch was always aimed at developers, with the educational launch planned for later in 2012. We had a small number of very dedicated volunteers, but we needed the wider Linux community to help us prepare a software stack and iron out any early-life niggles with the board before releasing into the educational market. We had enough capital in the Foundation to buy the parts for and build 10,000 Raspberry Pis over a period of a month or so, and we thought that the people in the community who would be interested in an early board would come to around that number. Fortunately and unfortunately, we’d been really successful in building a big online community around the device, and interest wasn’t limited to the UK, or to the educational market. Ten thousand was looking less and less realistic.

Our Community

The Raspberry Pi community is one of the things we’re proudest of. We started with a very bare-bones blog at www.raspberrypi.org just after Rory’s May 2011 video, and put up a forum on the same website shortly after that. That forum now has more than 60,000 members—between them they’ve contributed more than half a million posts of wit and wisdom about the Raspberry Pi. If there’s any question, no matter how abstruse, that you want to ask about the Raspberry Pi or about programming in general, someone there will have the answer (if it’s not in this book, you’ll find it in the forums).

Part of my job at Raspberry Pi involves giving talks to hacker groups, computing conferences, teachers, programming collectives and the like, and there’s always someone in the audience who has talked to me or to my wife Liz (who runs the community) on the Raspberry Pi website—and some of these people have become good friends of ours. The Raspberry Pi website gets more than one request every single second of the day.

There are now hundreds of fan sites out there. There’s also a fan magazine called The MagPi (a free download from www.themagpi.com), which is produced monthly by community members, with type-in listings, lots of articles, project guides, tutorials and more. Type-in games in magazines and books provided an easy route into programming for me—my earliest programming experience with the BBC Micro was of modifying a type-in helicopter game to add enemies and pick-ups.

We blog something interesting about the device at www.raspberrypi.org at least once every day. Come and join in the conversation!

There were 100,000 people on our mailing list wanting a Raspberry Pi—and they all put an order in on day one! Not surprisingly, this brought up a few issues.

First off, there are the inevitable paper cuts you’re going to get boxing up 100,000 little computers and mailing them out—and the fact was that we had absolutely no money to hire people to do this for us. We didn’t have a warehouse—we had Jack’s garage. There was no way we could raise the money to build 100,000 units at once—we’d envisaged making them in batches of 2,000 every couple of weeks, which, with this level of interest, was going to take so long that the thing would be obsolete before we managed to fulfil all the orders. Clearly, manufacturing and distribution were something we were going to have to give up on and hand over to somebody else who already had the infrastructure and capital to do that, so we got in touch with element14 and RS Components, both UK microelectronics suppliers with worldwide businesses, and contracted with them to do the actual manufacture and distribution side of things worldwide so we could concentrate on development and the Raspberry Pi Foundation’s charitable goals.

Demand on the first day was still so large that RS and element14’s websites both crashed for most of the day—at one point in the day, element14 were getting seven orders a second, and for a couple of hours on February 29, Google showed more searches were made worldwide for “Raspberry Pi” than were made for “Lady Gaga”. We made and sold more than a million Raspberry Pis in the first year of business, making Raspberry Pi the fastest-growing computer company in the world, ever. Things aren’t slowing down: we make more than 100,000 Pis every month and have sold more than 3 million in well under three years, with no hint of a slowdown. If we’d stuck with our original plans, we’d have made 100 or so of these devices for University open days, and that would have been it.

Note

The first production Pis were made in Chinese factories, but in 2012 we managed to repatriate all of the production to the UK. Your Raspberry Pi is now made in South Wales, in an area of the country with a proud manufacturing heritage, but few remaining factories. Amazingly, it costs us the same to manufacture in Wales as it did in China, and we’re able to do that manufacture without a language or cultural barrier, and with the ability to jump in the car and be on the factory floor in a few hours if necessary.

There is nothing that affects the blood pressure quite like accidentally ending up running a large computer company!

So What Can You Do with the Raspberry Pi?

This book explores a number of things you can do with your Raspberry Pi, from controlling hardware with Python, to using it as a media centre, setting up camera projects, or building games in Scratch. The beauty of the Raspberry Pi is that it’s just a very tiny general-purpose computer (which may be a little slower than you’re used to for some desktop applications, but much better at some other stuff than a regular PC), so you can do anything you could do on a regular computer with it. In addition, the Raspberry Pi has powerful multimedia and 3D graphics capabilities, so it has the potential to be used as a games platform, and we very much hope to see more people starting to write games for it.

We think physical computing—building systems using sensors, motors, lights and microcontrollers—is something that gets overlooked in favour of pure software projects in a lot of instances, and it’s a shame, because physical computing is massive fun. To the extent that there was any children’s computing movement when we began this project, it was a physical computing movement. The LOGO turtles that represented physical computing when we were kids are now fighting robots, quadcopters or parent-sensing bedroom doors, and we love it. However, the lack of General Purpose Input/Output (GPIO) on home PCs is a real handicap for many people getting started with robotics projects. The Raspberry Pi exposes GPIO so you can get to work straight away.

I keep being surprised by ideas the community comes up with which wouldn’t have crossed my mind in a thousand years: the Australian school meteor-tracking project; the Boreatton Scouts in the UK and their robot, which is controlled via an electroencephalography headset (the world’s first robot controlled by Scouting brain waves); the family who are building a robot vacuum cleaner; Manuel, the talking Christmas moose. And I’m a real space cadet, so reading about the people sending Raspberry Pis into near-earth orbit on rockets and balloons gives me goosebumps.

In the first edition of this book, I said that success for us would be another 1,000 people every year taking up Computer Science at the university level in the UK. That would not only be beneficial for the country, the software and hardware industries, and the economy; but it would be even more beneficial for every one of those 1,000 people, who, I hope, will discover that there’s a whole world of possibilities and a great deal of fun to be had out there. We’ve gotten greedy now: I’d like to see that sort of statistic replicated in many more countries across the developed world, and to see something similar starting to happen in the developing world. We’ve been immensely proud to see Raspberry Pi labs spring up in the most unlikely places, like a village lab in a part of Cameroon with no electricity network where the Pis run off solar power, generators and batteries, or a school high in the mountains in Bhutan.

Building a robot when you’re a kid can take you to places you never imagined—I know because it happened to me!

—Eben Upton

Part I

The Board

Chapter 1 Meet the Raspberry Pi

Chapter 2 Getting Started with Raspberry Pi

Chapter 3 Linux System Administration

Chapter 4 Troubleshooting

Chapter 5 Network Configuration

Chapter 6 The Raspberry Pi Software Configuration Tool

Chapter 7 Advanced Raspberry Pi Configuration

Chapter 1

Meet the Raspberry Pi

YOUR RASPBERRY PI board is a miniature marvel, packing considerable computing power into a footprint no larger than a credit card. It’s capable of some amazing feats, but you need to know a few things before you plunge head-first into the bramble patch.

Tip

If you’re eager to get started, skip to the next chapter to find out how to connect your Raspberry Pi to a display, keyboard and mouse; install an operating system; and jump straight into using the Pi.

A Trip Around the Board

The Raspberry Pi is currently available as two different models, known as the Model A and the Model B. While there are differences, with the Model A sacrificing some functionality in order to reduce its cost and power requirements, both share plenty of similarities that you find out about in this chapter. Figure 1-1 shows a Raspberry Pi Model B Revision 2, the most common board type. Its layout is shared between the original Model B Revision 1 and the cheaper Model A; the latest Model B+ uses an altered layout discussed later in this chapter.

In the rough centre of all Raspberry Pi boards is a square semiconductor, more commonly known as an integrated circuit or chip. This is the Broadcom BCM2835 system-on-chip (SoC) module, which provides the Pi with its general-purpose processing, graphics rendering and input/output capabilities. Stacked on top of that chip is another semiconductor, which provides the Pi with memory for temporary storage of data while it’s running programs. This type of memory is known as random access memory (RAM), because the computer can read from or write to any part of the memory at any time. RAM is volatile, meaning that anything stored in the memory is lost when the Pi loses power or is switched off.

Figure 1-1: The Raspberry Pi Model B Revision 2 board

Above and below the SoC are the Pi’s video outputs. The silver (bottom) connector is a High Definition Multimedia Interface (HDMI) port, the same type of connector found on media players and many satellite and cable set-top boxes. When connected to a modern TV or monitor, the HDMI port provides high-resolution video and digital audio. The yellow (top) connector is a composite video port, which is designed for connection to older TVs that don’t have an HDMI socket. The video quality is lower than is available via HDMI, and there’s no audio; instead, audio is provided as an analogue signal on the 3.5mm audio jack to the right of the composite video socket.

The pins to the top-left of the Pi compose the general-purpose input-output (GPIO) header, which can be used to connect the Pi to other hardware. The most common use for this port is to connect an add-on board. A selection of these boards is described in Chapter 17, “Add-On Boards”. The GPIO port is extremely powerful, but it’s fragile. When handling the Pi, always avoid touching these pins and never connect anything to them while the Pi is switched on.

The plastic and metal connector below the GPIO port is the Display Serial Interface (DSI) port, which is used to connect digitally driven flat-panel display systems. These are rarely used except by professional embedded developers because the HDMI port is more flexible. A second plastic and metal connector, found to the right of the HDMI port, is the Camera Serial Interface (CSI) port, which provides a high-speed connection to the Raspberry Pi Camera Module or other Pi-compatible CSI-connected camera system. For more details on the CSI port, see Chapter 16, “The Raspberry Pi Camera Module”.

At the very bottom-left of the board is the Pi’s power socket. This is a micro-USB socket, the same type found on most modern smartphones and tablets. Connecting a micro-USB cable to a suitable power adapter, detailed in Chapter 2, “Getting Started with the Raspberry Pi”, switches the Raspberry Pi on. Unlike a desktop or laptop computer, the Pi doesn’t have a power switch and will start immediately when power is connected.

On the underside of the Raspberry Pi board on the left-hand side is an SD card slot. A Secure Digital (SD) memory card provides storage for the operating system, programs, data and other files, and is non-volatile. Unlike the volatile RAM, it will retain its information even when power is lost. In Chapter 2, you’ll learn how to prepare an SD card for use with the Pi, including installing an operating system in a process known as flashing.

The right-hand edge of the Pi will have different connectors depending on which model of Raspberry Pi you have, the Model A or the Model B. Above these is a series of Light Emitting Diodes (LEDs), the left-most two of which—marked ACT and PWR and providing SD card activity notification and power notification, respectively—are present on all boards.

Model A

The least expensive Raspberry Pi, the Model A shown in Figure 1-2, is designed to be affordable yet flexible. As well as costing less than the Model B, the Model A draws less power and is a good choice for projects that use solar, wind or battery power. Although the Model A’s BCM2835 SoC is just as powerful as the one found on the Model B, it comes with half the memory, at 256MB. This is an important consideration when deciding which model to buy, because it can make more complex applications run slowly—in particular, those applications that turn the Pi into a server, as described in Chapter 10, “The Pi as a Web Server”.

The Model A has only a single port on its right-hand edge, a Universal Serial Bus (USB) port. This is the same type of port found on desktop and laptop computers, and allows the Pi to be connected to almost any USB-compatible peripheral. Most commonly, the USB port is used to connect a keyboard for interacting with the Pi. If you also want to use a mouse at the same time, you’ll need to buy a USB hub to add more ports to the Model A, or alternatively, a keyboard with built-in mouse functionality.

Figure 1-2: The Raspberry Pi Model A board

Model B

The Raspberry Pi Model B shown in Figure 1-3 is more expensive than the Model A, but it comes with considerable advantages. Internally, it includes twice the memory, at 512MB, while externally there are additional ports not available on the lower-cost model. For many users, the Model B is a worthwhile investment. Only those with particular requirements of low weight, space or power draw should consider the Model A for general-purpose use.

The Model B has either two or four USB ports on the right-hand edge of the board, primarily to provide connectivity for a keyboard and mouse along with other USB peripherals. Additionally, the Model B includes an Ethernet port for connecting the Pi to a wired network, which allows the Pi to access the Internet and allows other devices on the network to access the Pi—providing, that is, that they know the username and password or that the Pi has been set up as a server, as described in Chapter 10.

Model B+

The Raspberry Pi Model B+, shown in Figure 1-4, is the latest version of the board developed by the Raspberry Pi Foundation. It was created to address issues with the existing Model B Revision 2 design and has a dramatically different layout than any of the previously released Raspberry Pi models.

Figure 1-3: The Raspberry Pi Model B Revision 2 board

Figure 1-4: The Raspberry Pi Model B+ board

The Raspberry Pi Model B+ includes the same BCM2835 processor and 512MB memory as its predecessor, the Model B Revision 2, but on a newly designed circuit board with four—rather than two—mounting holes. The biggest changes are the elongated GPIO connector, with 40 pins to the other models’ 26 pins; four USB ports instead of two; a shifted power connector and 3.5mm jack; and the removal of the composite video connector on the top of the board. The Model B+ also uses a micro-SD card, in place of the full-size SD card of other models, and the power and activity lights have been moved to the top-left.

The Model B+ is a good choice if you are interested in getting the most out of the Pi. Its extended GPIO header, described in Chapter 15, “The GPIO Port”, offers additional pins for more complex electronics projects; its extra USB ports mean a keyboard and mouse can be connected while still leaving two ports free for other devices; and its power circuitry has been revised to dramatically reduce power draw and improve reliability when used with cheaper power supplies.

A History of Model B PCB Revisions

Although the latest model of Raspberry Pi Model B+ currently has 512MB of memory and four USB ports, this wasn’t always the case. As well as the Model B+, there are two variants of standard Model B; if you bought a second-hand Rasbperry Pi Model B or purchased one some time ago, you may have the earliest Revision 1 model.

Revision 1

The original Raspberry Pi Model B, the Revision 1 board, has only 256MB of RAM. It also has a slightly different GPIO header. That is, while the number and locations of the pins look identical to those of later revisions, it assigns certain features to different pins. (See Chapter 15