Arduino用户转战Raspberry Pi：构建物联网与网络应用指南

需积分: 10 140 浏览量更新于2024-07-18 收藏 5.58MB PDF 举报

《Raspberry Pi for Arduino Users: Building IoT and Network Applications and Devices》是一本专为熟悉Arduino编程但希望扩展网络功能的用户撰写的指南。作者James R. Strickland旨在帮助读者在Raspberry Pi世界中利用已有的Arduino技能，将两者的优势结合，创建更为复杂的物联网（IoT）和网络应用设备。书中的主要内容涵盖了以下几个关键知识点： 1. **Arduino与Raspberry Pi的融合**：书中指出，尽管Arduino通过各种网络“屏蔽”可以增加网络功能，但这往往会增加系统的成本和复杂性。相比之下，Raspberry Pi以其内置的Linux系统，尤其是最新的Raspberry Pi Zero W版本，具备Wi-Fi和蓝牙连接能力，且价格低廉。因此，该书提倡转向Raspberry Pi平台，以简化网络设备的开发。 2. **Linux系统基础与安全**：学习者将掌握一些基本的Linux系统管理知识，了解如何设置Raspberry Pi并确保其安全，例如安装必要的软件、配置防火墙和基本权限管理。 3. **IDE工具的迁移**：书中介绍了如何在Raspberry Pi上设置Geany IDE，这个环境类似于Arduino IDE，便于移植Arduino项目到Pi上。 4. **GPIO系统的比较**：重点讲解了WiringPi系统，这是Arduino中用于控制GPIO引脚的方法，与Arduino的Wiring类似。同时，会对比Raspberry Pi和Arduino的GPIO差异，以及Raspberry Pi在某些功能上的限制。 5. **扩展硬件与通信**：作为最终项目，作者指导读者将Atmega 328P与Raspberry Pi相连，将Arduino IDE运行在Pi上，实现两个平台之间的通信，这样既能利用Raspberry Pi的网络能力，又保留了Arduino的灵活性。 6. **实用技能**：读者将学会如何设置Apache web服务器，编写CGI程序以供其他计算机访问，以及如何利用C/C++编写适用于Raspberry Pi的程序。这本书适合那些已经掌握了Arduino基础知识，想要探索物联网和网络应用的开发，希望利用Raspberry Pi平台进行更多可能性的工程师和爱好者。通过阅读本书，他们可以跨越平台限制，提升自己的技能，并且在物联网领域有所建树。

xvii

About the Technical

Reviewers

MassimoNardone has more than 22 years

of experience in security, web/mobile

development, and cloud and IT architecture.

His true IT passions are security and Android.

He has been programming and teaching

people how to program with Android, Perl,

PHP, Java, VB, Python, C/C++, and MySQL

for more than 20 years. He has worked as a

project manager, software engineer, research

engineer, chief security architect, information

security manager, PCI/SCADA auditor, and senior lead IT security/cloud/

SCADA architect for many years.

His technical skills include security, android, cloud, Java, MySQL,

Drupal, Cobol, Perl, web and mobile development, MongoDB, D3, Joomla,

Couchbase, C/C++, WebGL, Python, Pro Rails, Django CMS, Jekyll,

Scratch, etc. He currently works as a Chief Information Security Officer

(CISO) for Cargotec Oyj. He worked as visiting lecturer and supervisor

for exercises at the Networking Laboratory of the Helsinki University of

Technology (Aalto University). He holds four international patents (PKI,

SIP, SAML, and Proxy areas). He holds a Master of Science degree in

computing science from the University of Salerno, Italy.

By late 1982, microcomputers had become a fad. You could go to Kmart

and buy a Vic 20 or Commodore 64, or to Radio Shack for any of the vast

TRS-80 family of computers. One thing was common to all of them, though.

Software was expensive. Sooner or later, unless you were only using the

machine as a glorified Atari (as in the Atari 2600, a video game console of

the day), you were going to have to write some code. For a lot of us, this was

the real attraction. The computer did what we wanted, even though some

of us were kids. The more electronically astute added circuitry, just as their

IMSAI forbearers had. You explored this machine all the way through to

see what it was capable of, what you could make it do. Our IMSAI forebears

and exceptional Apple II/TRS-80/Commodore 64 tinkerers developed

deep understandings of their machines, pushed their limits, and learned

computing all the way down to the logic gate level and beyond.

Microcontrollers

Back in the mid-to-late 1970s, it became obvious that computerizing

traffic lights, your car, your toaster, and so on was still too expensive. A

microcomputer had to have the CPU, the clock, the RAM, logic to control

the RAM, and ROM to boot from. You had to build a complete computer

to do simple tasks, and then it was too big, took too much power, and cost

too much for volume production. Engineers at Texas Instruments and

Intel addressed this problem first, with the TMS 1000 and the Intel 8048

and 8051 microcontrollers, respectively. These contained RAM and ROM

on the IC, and in the case of the TMS 1000, also included the system clock.

You programmed them like ROMs or EPROMs—placed the IC in a specially

designed programmer and burned the program into the device, connected

power and whatever peripheral circuitry they needed to do their jobs, and

away they went. Today, when you compare desktop microcomputers to

microcontrollers, like the bacteria in your digestive system verses the number

of your cells in your body, they outnumber desktop computers by thousands

to one. Um. You did know about the intestinal bacteria thing, right? Sorry.

inTRoduCTioninTRoduCTion

xxi

The Decline

By the 2000s, thanks to the explosion of the Internet and computers that

access it, home computers had become like the family car, packaged as

consumer devices with no user serviceable parts inside, like my Mac Mini or

my iPhone today. Sealed up, opening the case voids the warrantee, and I can’t

even load my own software on my iPhone. Just like today, microcontroller

devices weren’t user modifiable at all, and if you bought new, blank

microcontrollers, you had to make a substantial investment in equipment,

software, and licenses. The result was that fewer people had the kind of deep

understanding of computers that built the industry in the first place, at a time

when literally everything was—and is—becoming computerized. Could the

Internet, which had produced the Linux operating system, not produce tools

to allow new generations of tinkerers that same access? It could.

The New Beginning

There were always hobbyists. The 8051, and later the MicroChip PIC

and Parallax BASIC Stamp platforms, have and still retain a hard core

of enthusiasts, but these platforms required complex, often expensive,

software tools and a great deal of study of individual ICs to learn how

to control their specific peripherals. As his master’s thesis project,

Hernando Barragán set out to simplify the learning and programming of

microcontrollers and to make the tools free and open source. His project

gave each pin a standard name and a standard set of functions to control

it, and to call its special functions, if any. He called it Wiring. He soon

retargeted it to Atmel’s less expensive AVR microcontrollers.

Wiring evolved to include an IDE and incorporated Brian

Dean’s AVRDUDE, which allowed users to upload programs to their

microcontroller board easily. It was open source from the start. If all of this

sounds familiar, it should. Wiring boards ran about $50 US each. According

to Barragán, Massimo Banzi, originally his advisor on the Wiring project,

inTRoduCTioninTRoduCTion

剩余443页未读，继续阅读

sinat_41581062

粉丝: 21
资源: 174

Arduino用户转战Raspberry Pi：构建物联网与网络应用指南

Beginning Robotics with Raspberry Pi and Arduino_Using Python and OpenCV

Raspberry.Pi.Home.Automation.with.Arduino.2nd.Edition.178439

(源码)基于Raspberry Pi和Arduino的实时追踪车辆系统.zip

the difference between Raspberry pi and Raspberry pi pico

raspberry pi pico python

raspberry pi hardware reference

raspberry pi cam kit

codesys control for raspberry pi 4.0.1.0.package

raspberry pi 4 jupyter

Raspberry Pi是什么

最新资源