Using Arriba is practically as easy as opening a workspace and selecting the build button! This chapter discusses building and running an entire example project from start to finish.
Arriba comes complete with a variety of examples.
For the sake of this brief introduction, we will focus on the example of a standalone PIC32 application.
Simply run Arriba via the “Start” button or via the Arriba icon on the desktop.
At this point you will observe the Arriba Workspace Launcher dialog. Select a directory on your host computer that Arriba can use to store projects and the workspace. Ensure that you have write permission for this directory.
More on Eclipse projects and the workspace can be found in the Eclipse documentation: http://help.eclipse.org/kepler/index.jsp
Arriba Welcome Screen
If you have selected a new workspace, Arriba will start at the welcome screen.
- Shows a quick overview of Arriba for PIC MCUs
- Shows the web resources available with Arriba for PIC MCUs. You can, for example, download versions of the MPLAB XC C compiler from this resource.
- Enter the Arriba workbench.
Creating a Project
Project Types Selection Dialog
Arriba will now present a list of project types to choose from. You may need to check/uncheck the “Show project types and toolchains…” checkbox to show all-available project types for PIC MCUs.
Select “PIC32 Sample” for this exercise and enter “PIC32” for Project name. Click “Next” to move to the C Project Dialog.
Device and Hardware Tools
Arriba will now require that you specify some information about the PIC MCU target on which the resulting code generated by the project will execute. By default, no information is specified for the project and you’re required to enter the device family, device, and hardware tools associated with the newly created project.
Note that you can always modify these choices after the project has been created.
For this exercise, click on “Configure” to select these data and Arriba will open the Device and Hardware Tools Configuration Dialog.
Device and Hardware Tools Configuration Dialog
Again for this exercise, we recommend that you keep the default options specified in this dialog, and simply click “OK” to close the Hardware Tools Configuration Dialog. Then click on “Finish” to create the project.
Arriba will offer to open the “C” perspective. Click "Yes".
Building the Project
You should see the following Arriba desktop:
Arriba C/C++ Perspective
- You can select “C/C++” button to view the C perspective at all time
- Edit/view source files by double-clicking on it under the Project Explorer
- Arriba Connect status indicator should show “active” in the lower left hand corner. If not, your Arriba installation is not properly running; contact Viosoft support.
At this point, you’re ready to build the PIC32 project. Note that you must install the MPLAB XC32 C compiler toolchain prior to using Arriba in order to build this PIC32 application. (For other PIC MCUs, you may need to select a different MPLAB XC C compiler.)
Building is simply done by clicking on the build button in the toolbar:
Build Button in Toolbar
You should see the following messages in the Console view:
Debugging the Project
Before you debug, it is recommended that you select the PIC32 entry in the Project Explorer, as shown below, before opening the Debug Configuration Dialog. Doing so will enable eclipse to automatically fill out the necessary debug configuration information.
Debug Configuration Dialog
Now you can debug the “PIC32” application by selecting Run->Debug Configurations, or by clicking on the tiny down arrow next to the cockroach and select “Debug Configurations” as shown in Figure below.
Opening Debug Configuration Dialog
From the Debug Configuration Dialog:
- Select Microchip Config in the launch list
- Double click on the plus icon in the toolbar to create a new debug configuration for the PIC32 project
You should see the Main Debug Tab shown below:
Main Debug Tab
At this point, Arriba should offer the Debug perspective and you shall accept, as shown below.
Switching to Debug Perspective
From the Debug perspective shown in Figure 28, you can press “Resume” button to resume execution, or “Halt” to suspend execution. Notice that the debug view should annotate your current program location within the execution flow. In addition, breakpoints, register, and memory viewing are all available with just a few mouse clicks!
Debugging of Application in Debug Perspective
The project building and execution facilities of Arriba are discussed in greater detail in subsequent chapters of this guide. Hopefully, this chapter illustrates just how easy it is to get a project up and running with Arriba!
For more information on working with Arriba, consult the Arriba User Guide that comes with the product, or the online help.