70 March 2014
(Model B) on the bench. As you can see in Photo 2, the
Pi is radically different as far as physical design is
concerned. There are some logical differences too. The Pi
boots from a microSD card only. No big deal because
loading the latest version of Raspbian onto the Pi’s
microSD card is procedurally similar to that of the Bone.
SDFormatter is used to “clean” an 8 MB microSD card
and Win32 Disk Imager puts down the Raspbian image.
The microSD card is then physically mounted on the Pi
and power is applied.
Getting at the Pi the first time around without a
monitor and keyboard is not very straightforward. We
must first determine the Pi’s IP address. Since the Pi
defaults to DHCP operation, the easy way to obtain the
Pi’s IP address is to check the router’s DHCP table.
Our Pi was assigned 192.168.0.141 as evidenced in
Screenshot 7. Recall that we were able to get at our Bone
without specifying the IP address using beaglebone.local.
Well, guess what? Linux is Linux is Linux. We can do the
same with the Pi. Before I put raspberrypi.local into place,
I’ll perform the operation that has been “suggested” in
Screenshot 8. For now, I will only select the Expand
Filesystem option to resize the root partition.
In my Linux travels, I learned that it is good to
bring a new installation up to snuff using the
update and upgrade methods. For the Pi, that
equates to sudo apt-get update and sudo apt-get
upgrade, respectively. Once that was done, I
issued sudo apt-get install avahi-daemon.
In a nutshell, Avahi is a system based on the
mDNS/DNS-SD protocol suite that enables service
discovery on a LAN. This allows us to simply
attach the Pi to our LAN and find it using the
Screenshot 9 verifies that the Pi is ready to go
to work. By the way, sudo or “su do” is a program
that allows users to issue certain root (super user)
commands without having full root privileges.
Living On the LAN
Our Bone and Pi need a common launch pad.
In our case, that launch pad — or Integrated
■ Screenshot 7. This is a singular capture of the EDTP
workshop router's DHCP table. The EDTP workshop
router has assigned 192.168.0.141 to our Raspberry Pi.
■ Screenshot 8. We're up with the Raspberry Pi! Before
we can go any further, we'll finish up the suggested
configuration operation and do some updating.
■ Screenshot 9. Pretty cool stuff, this Linux. By issuing a
simple command that ran an Internet errand for us
automagically, we can now remotely log in to our
Raspberry Pi in the same way we remotely log in
to our BeagleBone Black.
■ Screenshot 10. Installing Eclipse and RSE was painless as the
Eclipse IDE and RSE installation procedures are very well
documented in a number of locations on the Internet.