rone Setup Instructions - New Spring 2014

The old instructions can be found here.

These instructions assume that you are running Windows on your computer.

Make sure to have Git installed. If you do not, you can follow the instructions here.

Install these things

  1. Eclipse IDE
    1. It is recommended to download the 32-bit version of Eclipse, as it allows for greater compatibility with older software and drivers.
  2. Eclipse CDT (install from within Eclipse)
    1. You should install the Eclipse CDT through the Eclipse install wizard. Click Help > Install New Software... on the top menubar to pull up the wizard.
    2. Inside the wizard, put the URL http://download.eclipse.org/releases/kepler inside the Work With: dialog box and press enter. It should be saved under the name of Kepler on the drop-down menu. This will populate the table below.
    3. Expand the Programming Languages option and select C/C++ Development Tools. Then, click next until finished. After restart, Eclipse should have the Eclipse CDT installed.
  3. ARM-Eclipse integration (also install from within Eclipse)
    1. Follow steps from above to launch the install wizard, but instead of the previous URL, use the URL listed under the Quicklinks heading from here. This will populate the table with the ARM-Eclipse tools.
    2. Select all options excluding GNU ARM C/C++ Freescale Project Templates and GNU ARM C/C++ STM32Fx Project Templates. Then, click next until finished and restart Eclipse.
  4. Code Sourcery Lite Cross-complier, ARM EABI
    1. You can download the Windows executable that will extract and install the binaries here.
    2. Otherwise, you can download it from the provided site. Click on the link under the ARM Processor heading that says Download the EABI Release.

Checkout the repository

If you have not already, use Git to checkout the rone repository at GitHub.

After installing those things

Copy these following files

from

<repository location>/rone/software/setup

to

<CodeSourcery location>/Sourcery_CodeBench_Lite_for_ARM_EABI/arm-none-eabi/lib/thumb2

Also, grab OpenOCD from here.

Extract the to some local directory you can easily remember, as you will need to reference it again soon.

Correcting JTAG adaptor drivers

Connect the JTAG adaptor to your computer using a USB cable.

The drivers installed automatically by Windows for the JTAG adaptor are incorrect for our purposes, so they must be overwritten.

Grab the Zadig USB driver installer and unzip it to a local directory.

Run Zadig, and from the top menu bar select Options > List All Devices. This will now show, among other things, two entries entitled Dual RS232-HS. These drivers both need to be replaced by libusb-win32.

For each interface, make sure the box next to the right of the green arrow has libusb-win32 listed. If not, tab through the options until it is found. Then, reinstall the driver.

Make sure this is done for both Interface 0 and Interface 1.

Note that this has to be done each time you plug the JTAG adaptor into a different USB port on your computer.

Configuring Eclipse for debugging

As a test, start Eclipse and set your workspace to /rone/software.

Then, make sure your perspective in Eclipse is set to C/C++

In the Project Explorer tab, right click and select Import..., and from that dialog select General > Existing Projects into Workspace. Select the robotcode directory as the root directory (which should be the default selected), and watch the list of projects populate. From this list, select driverlib, FreeRTOS, roneLib, roneos, and SuperDemo. This will pull these projects into the workspace.

Next, right click on the SuperDemo project under the Project Explorer and select Properties. Then, pull up C/C++ Build > Settings and go to the Toolchains tab. Then put the absolute path to 

<CodeSourcery location>/Sourcery_CodeBench_Lite_for_ARM_EABI/bin

in Global Path. Apply this new setting.

Finally, right click on the SuperDemo project and select Debug As > Debug Configurations.... Then, go to GDB OpenOCD Debugging > SuperDemo bin_rone_v12 > Debugger and go to the Debugger tab. Click Variables..., then Edit Variables... on the popup, then New... on the new popup. Type in a new variable of name openocd_path and use the location of 

<OpenOCD location>/bin

for the value. Click Ok, Ok, then Cancel, and apply this new setting.

Build each project to create the necessary dependencies, and then finally pull up the SuperDemo debugging dialog and select debug with the robot attached to the JTAG adaptor. This should start building and programming the robot.