Difference between revisions of "TCF/Raspberry Pi"
|Line 23:||Line 23:|
cp –R machine/arm machine/armv6l
cp –R machine/arm machine/armv6l
''# In case you don't have libcrypt / libssl, you can also <b>make
''# In case you don't have libcrypt / libssl, you can also <b>make ==</b>''
Revision as of 02:53, 14 November 2013
Getting TCF to run on the Raspberry Pi
The Raspberry Pi is a tiny, cheap single-board computer that is powerful enough to play HD video. It runs Linux on its ARMv6 chip, connects a monitor and a keyboard for stand-alone work, and provides all the necessary tools to get started quickly. TCF needs a network, so the instructions here are for a "Type B" Raspberry Pi which should cost around 25 $. Getting it up and running is quick and easy:
Building the TCF Agent
Getting TCF up and running is really easy if your Pi has a network - this shouldn't take more than 15 minutes depending on your network connection for the downloads:
- Prepare an SD Card (4 GB recommended) with the Raspbian Image to boot your device. We used "wheezy" for this.
- Connect native monitor and keyboard. Finish setup wizard, type “ifconfig”. Read IP address from eth0.
- If you can't get a monitor and a keyboard, you can use a tool like the advanced IP scanner
Now you're ready to rock and roll on the keyboard
# (Replace n.n.n.n by the actual IP address that you read) ssh firstname.lastname@example.org / password : raspberry sudo apt-get update # (Need to update the Raspbian update caches to get git) sudo apt-get install git uuid uuid-dev libssl-dev git clone git://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.agent.git cd org.eclipse.tcf.agent/agent cp –R machine/arm machine/armv6l make # In case you don't have libcrypt / libssl, you can also make NO_SSL=1 NO_UUID=1 obj/GNU/Linux/armv6l/Debug/agent –S
The last command actually launches the agent, for testing.
Installing the Agent for auto-start
One benefit of running TCF on the device is the TCF auto-discovery: It allows to connect to a headless device (without keyboard and monitor) quickly even without knowing its IP address. For that to work right after powering on the device, you'll need to register the TCF agent for auto-start:
cd org.eclipse.tcf.agent/agent make install # (Review the files being installed into /tmp) sudo make install INSTALLROOT= sudo update-rc.d tcf-agent defaults sudo update-rc.d tcf-agent enable 2
The last command is necessary, because the Pi uses runlevel 2 by default even if networking is enabled (ie sshd is up); so we'll want TCF to come up on runlevel 2 as well, and not only on runlevel 3 as in most standard Linux distributions. The good thing is that this change is persistent.
Connecting the TCF Debugger to the Pi
- Get Eclipse, we've used the Eclipse IDE for C/C++ Developers, Juno SR2 package
- Launch it, choose Help > Install New Software and go to the TCF milestone repository:
- You can safely install all of TCF (will also get you the sources)
- Allow to restart, then switch to the Target Explorer Perspective
- Your Pi should show up under "Neighborhood"
You can install a VNC server on the Pi - the TCF source repository on git://git.eclipse.org/gitroot/tcf/org.eclipse.tcf.git has an experimental VNC integration:
sudo apt-get install tightvncserver
There's more details on this Blog on setting up VNC on the Pi.
You can install an NFS server on the Pi - provides access to source code and debug objects that you compile right on the Pi:
# purge rpcbind and nfs-common to avoid [warn] Not starting: portmapper is not running ... (warning). sudo apt-get purge rpcbind sudo apt-get purge nfs-common sudo apt-get install rpcbind sudo apt-get install nfs-kernel-server nfs-common sudo nano /etc/exports # add the following line : # / *(rw,sync,no_subtree_check,insecure) #restart your nfs deamon /etc/init.d/nfs-kernel-server restart