Development Environment — is called Eclipse.
Eclipse is an open source IDE that runs under
Windows and Linux. To install Eclipse on the
Linux laptop, I opened a terminal window and
issued apt-get install eclipse. Once Eclipse
installed, the next step was to install the Eclipse
C++ Development Tools.
This is done by clicking on Help and
choosing the Install New Software in the
dropdown menu. I then chose Work with: Indigo
Update Site in the Install window. All of the
available software was listed, and I selected C++
Development Tools and C/C++ Library API
Documentation Hover Help from the list.
Following the install process, the Eclipse IDE was
primed to do some C/C++ development. Since I
wanted to work with the Pi and Bone at the end
of a wire, I also installed the Remote System
Explorer plugin. RSE allows us to look at the Pi
and Bone file systems, transfer files between hosts
on the LAN, and generally command and control
hosts that we can connect to.
Once everything was installed, I was left
with the Eclipse IDE interface you see in
Screenshot 10. Note that the Eclipse IDE
interface includes a Project Explorer tab and a
Let’s see if we can contact and connect the
Pi to the Eclipse IDE. A right click anywhere
inside the Eclipse Remote tab area brings up the
New Connection menu item. We will use simple
logic to make our choices as we work our way
through the various configuration windows. We know that
we are working with a Linux system. We also know that
we have established .local domains for the Pi and Bone.
So, we will address the Pi as raspberrypi.local and call the
new connection RaspberryPI. We are basically interested
in communicating with the Pi via SSH access. With that,
we will focus on configuring only the SSH terminals and
In Screenshot 11, you can see that I have successfully
configured an Eclipse remote connection to the Pi called
RaspberryPI. I also launched an SSH terminal session that
logged in as pi. I applied the same procedures I used to
form the Pi connection to the Bone. I was able to launch a
root SSH terminal session for the Bone, which is coexisting
with the Pi pi terminal session in Screenshot 12.
We are ready to start writing Bone and Pi applications
using our Eclipse-based cross-compiler environment. So,
be sure to get your Linux host computer in touch with
your Bone and/or Pi before we talk again. In the next
installment of Design Cycle, we are going to jump into Pi
and Bone application development. NV
March 2014 71
■ Screenshot 11. Success! The Raspberry Pi is connected to the
Eclipse IDE, and now falls under the control of the C/C++
development environment we have established. The terminal was
kicked off with the SSH Terminal's Launch Terminal menu selection.
■ Screenshot 12. The same process used to connect to the
Raspberry Pi was applied for the BeagleBone Black. Take note
of the Pi terminal session that is coexisting with
the new BeagleBone terminal session. We can now
move files between the Bone, Pi,
and Linux PC.
The Raspberry and BeagleBone can be had
from a number of distributors. You can source
them from your preferences of distributors.
Here’s a few I know of: