I downloaded the OpenOCD source via “git”.

git clone git://openocd.git.sourceforge.net/gitroot/openocd/openocd

Run the bootstrap to generate the configure scripts.

./bootstrap

Install the libftdi libraries.

sudo apt-get install libftdi1 libftdi-dev

Be sure to install the Doxygen libraries if you want to build the Doxygen generated documents.

Run the configure script. I chose to install in the default directory. Use the prefix directive to specify an alternative directory if you prefer. I found that I had to specify the –enable-maintainer-mode switch to get OpenOCD to compile correctly.

./configure --enable-maintainer-mode --enable-ft2232_libftdi

Build the code using make.

make

Build the PDF and HTML documentation if desired.

make pdf
make html

Install and verify the installation.

sudo make install
which openocd

Finally, install the documentation.

sudo make install-pdf
sudo make install-html

Here is a simple example of a recent install.

I downloaded the Sourcery G++ Lite 2010q1-188 for ARM EABI binary installer for Linux. This link may be dated when you read this, so be sure to check for the latest version for your system. I am programming bare ARM systems without an operating system, e.g., I am building my own custom OS, so I installed the ARM EABI variant.

The binary installer and the tools were built for 32-bit systems, so I had to make sure the ia32 bit library was installed on my 64-bit Ubuntu system. You will not need this if your system is 32-bit. I once tried to install the CodeSourcery tools on a fresh installation of Ubuntu, and the GUI Java based installer failed to run. I wrongly assumed there was something wrong with my Java configuration, so I switched to the non-GUI version of the CodeSourcery installer, which if I remember correctly is disabled via a command line switch on the installer. The non-GUI installer failed too, and it turned out that I was missing the IA32 libraries on my Ubuntu system, which I installed by something like this.

sudo apt-get install ia32-libs

I chose to install the the tool chain in the default directory “/usr/local/share/CodeSourcery” instead of in my home directory. Simply follow the GUI instructions and watch it happen.

sudo ./arm-2010q1-188-arm-none-eabi.bin

If you need or prefer the non-GUI installer, then invoke with the console switch.

sudo ./arm-2010q1-188-arm-none-eabi.bin -i console

I updated my path in “/etc/environment” by appending “/usr/local/share/CodeSourcery/bin”, the location of the new CodeSourcery executables, to the existing path.

sudo gedit /etc/environment

I verified my new environment settings by testing the existence an arbitrary CodeSourcery executable in the new path.

which arm-none-eabi-ar

If you chose to install the documentation as prompted by the GUI installer as I did, you can find PDF, HTML, info, and man documents here.

/usr/local/share/CodeSourcery/share/doc/arm-arm-none-eabi

That’s pretty much it.

Installing and configuring VNC on Ubuntu.

Install vnc4server and xinetd.

sudo apt-get install vnc4server xinetd

Start the vnc4server. You will be prompted for a new password.

vnc4server

The VNC server responds with something like this.

New 'your-computer-name:3 (your-computer-name)' desktop is your-computer-name:your-session-number
Remember your new password. Remember the session number following the colon (:).
A .vnc directory will be create in your home directory.

Stop the vnc4server.

vnc4server -kill :your-session-number

Edit your .vnc/xstartup file to look like this:

#!/bin/sh
# Uncomment the following two lines for normal desktop:unset SESSION_MANAGER
exec /etc/X11/xinit/xinitrc
[ -x /etc/vnc/xstartup ] && exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
#xsetroot -solid grey
#vncconfig -iconic &
#xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
#twm &

Change the permissions on the /etc/X11/xinit/xinitrc file to make it executable:

sudo chmod 755 /etc/X11/xinit/xinitrc

Start the vnc4server again. Remember your session number.

vnc4server

Install the vncviewer.

sudo apt-get install xvnc4viewer

Test your new virtual desktop. Log in using your new password and session number.

vncviewer your-computer-name:your-session-number

If you want to share a computer with multiple users, it can be useful for each user to have permanent session number. Simply agree on a set of unique session numbers, and start a separate VNC server session for each user with their unique session number on the command line.

vnc4server :unique-session-number