This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
resources:fpga:altera:bemicro:common [12 Sep 2011 11:39] – created Robin Getz | resources:fpga:altera:bemicro:common [03 Jan 2013 20:42] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | This section presents the steps for developing a software application that will run on the **BeMicroSDK** system and will be used for controlling and monitoring the operation of the ADI evaluation board. |
+ | |||
+ | |||
+ | ===== Create a new project using the NIOS II Software Build Tools for Eclipse | ||
+ | |||
+ | Launch the **Nios II SBT** from the **//Start -> All Programs -> Altera -> Nios II EDS 11.0 -> Nios II 11.0 | ||
+ | Software Build Tools for Eclipse (SBT)// | ||
+ | <WRAP tip> | ||
+ | |||
+ | === 1. Initialize Eclipse workspace === | ||
+ | |||
+ | * When Eclipse first launches, a dialog box appears asking what directory it should use for its workspace. It is useful to have a separate Eclipse workspace associated with each hardware project that is created in SOPC Builder. Browse to the **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | === 2. Create a new software project in the SBT === | ||
+ | |||
+ | * Select **//File -> New -> Nios II Application and BSP from Template// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * Click the **// | ||
+ | * Select the **// | ||
+ | * Set the name of the Application project to “**// | ||
+ | * Select the **//Blank Project//** template under **//Project template// | ||
+ | * Click the **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The tool will create two new software project directories. Each Nios II application has 2 project directories in the Eclipse workspace. | ||
+ | * The application software project itself - this where the application lives. | ||
+ | * The second is the **//Board Support Package (BSP)//** project associated with the main application software project. This project will build the system library drivers for the specific SOPC system. This project inherits the name from the main software project and appends “**// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Since you chose the blank project template, there are no source files in the application project directory at this time. The BSP contains a directory of software drivers as well as a system.h header file, system initialization source code and other software infrastructure. | ||
+ | |||
+ | |||
+ | ===== Configure the Board Support Package ===== | ||
+ | |||
+ | * Configure the board support package to specify the properties of this software system by using the **//BSP Editor//** tool. These properties include what interface should be used for //stdio// and //stderr// messages, the memory in which stack and heap should be allocated and whether an operating system or network stack should be included with this BSP. | ||
+ | * Right click on the **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The software project provided in this lab does not make use of an operating system. All //stdout//, //stdin// and //stderr// messages will be directed to the // | ||
+ | * Select the **// | ||
+ | * Select the // | ||
+ | * Select **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * Select **//File -> Save//** to save the board support package configuration to the // | ||
+ | * Click the **// | ||
+ | * When the generate has completed, select **//File -> Exit//** to close the BSP Editor. | ||
+ | |||
+ | ===== Configure BSP Project Build Properties ===== | ||
+ | |||
+ | In addition to the board support package settings configured using the **//BSP Editor//**, there are other compilation settings managed by the Eclipse environment such as compiler flags and optimization level. | ||
+ | * Right click on the **// | ||
+ | * On the left-hand menu, select **//Nios II BSP Properties// | ||
+ | * During compilation, | ||
+ | * Since our software does not make use of C++, uncheck **//Support C++//**. | ||
+ | * Check the **//Reduced device drivers//** option | ||
+ | * Check the **//Small C library//** option | ||
+ | * Press **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Add source code to the project ===== | ||
+ | |||
+ | In Windows Explorer locate the project directory which contains a directory called **// | ||
+ | |||
+ | * Select all the files and folders and drag them over the **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * A dialog box will appear to select the desired operation. Select the option **//Copy files and folders//** and press **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * This should cause the source files to be physically copied into the file system location of the software project directory and register these source files within the Eclipse workspace so that they appear in the Project Explorer file listing. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Configure Application Project Build Properties ===== | ||
+ | |||
+ | Just as you configured the optimization level for the BSP project, you should set the optimization level for the application software project **// | ||
+ | * Right click on the **// | ||
+ | * On the left-hand menu, select the **//Nios II Application Properties// | ||
+ | * Change the **// | ||
+ | * Press **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== Define Application Include Directories ===== | ||
+ | |||
+ | Application code can be conveniently organized in a directory structure. This section shows how to define these paths in the makefile. | ||
+ | * In the Eclipse environment double click on **// | ||
+ | * Click the **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * Double click on **// | ||
+ | * If you see the message shown here about resources being out of sync, right click on the **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * Select the line **APP_INCLUDE_DIRS :=** | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * Click the **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * Click the **// | ||
+ | |||
+ | ===== Compile, Download and Run the Software Project ===== | ||
+ | |||
+ | === 1. Build the Application and BSP Projects === | ||
+ | |||
+ | * Right click the **// | ||
+ | * When that build completes, right click the **// | ||
+ | |||
+ | These 2 steps will compile and build the associated board support package, then the actual application software project itself. The result of the compilation process will be an // | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | === 2. Verify the Board Connection === | ||
+ | |||
+ | The **BeMicroSDK** hardware is designed with a //System ID// peripheral. This peripheral is assigned a unique value based on when the hardware design was last modified in the SOPC Builder tool. SOPC Builder also places this information in the // | ||
+ | |||
+ | * Select the **// | ||
+ | * Select **//Run -> Run Configurations…// | ||
+ | * Select the **//Nios II Hardware// | ||
+ | * Press the **//New//** button to create a new configuration. | ||
+ | * Change the configuration name to **// | ||
+ | * On the **//Target Connection// | ||
+ | * Select the **// | ||
+ | * Check the **//Ignore mismatched system ID option// | ||
+ | * Check the **//Ignore mismatched system timestamp option// | ||
+ | |||
+ | {{: | ||
+ | {{: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | === 3. Run the Software Project on the Target === | ||
+ | |||
+ | To run the software project on the Nios II processor: | ||
+ | |||
+ | * Press the **//Run//** button in the **//Run Configurations// | ||
+ | |||
+ | This will re-build the software project to create an up–to-date executable and then download the code into memory on the **BeMicroSDK** hardware. The debugger resets the Nios II processor, and it executes the downloaded code. Note that the code is verified in memory before it is executed. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | <WRAP round help>The code size and start address might be different than the ones displayed in the above screenshot.</ | ||