This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
resources:fpga:altera:ced1z:ad7938 [28 May 2012 16:20] – [Software Tools] Andrei Cozma | resources:fpga:altera:ced1z:ad7938 [26 Jan 2021 01:23] (current) – update arrow links after their web site update Robin Getz | ||
---|---|---|---|
Line 3: | Line 3: | ||
====== Overview ===== | ====== Overview ===== | ||
- | This document presents the steps to setup an environment for using the **[[adi> | + | This document presents the steps to setup an environment for using the **[[adi> |
{{ : | {{ : | ||
Line 18: | Line 18: | ||
* [[adi>/ | * [[adi>/ | ||
* [[http:// | * [[http:// | ||
- | * [[http:// | + | * [[https://www.micrium.com/ |
====== Getting Started ====== | ====== Getting Started ====== | ||
Line 37: | Line 37: | ||
* [[http:// | * [[http:// | ||
* [[https:// | * [[https:// | ||
- | * [[http:// | + | * [[https://www.micrium.com/ |
The **Quartus II** design software and the **Nios II EDS** is available via the Altera Complete Design Suite DVD or by downloading from the web. | The **Quartus II** design software and the **Nios II EDS** is available via the Altera Complete Design Suite DVD or by downloading from the web. | ||
Line 160: | Line 160: | ||
====== NIOS II Software Design ====== | ====== NIOS II Software Design ====== | ||
- | {{page>: | + | |
+ | |||
+ | This section presents the steps for developing a software application that will run on the **CED1Z** 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 **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The memory used by the design is should be changed from OnChip ram to SRAM. | ||
+ | * Select **//Linker Script//** tab. | ||
+ | * Change all possible **//Linker Region Name//** from **// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | * 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. | ||
+ | |||
+ | ===== 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. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ===== 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 **CED1Z** 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: | ||
+ | |||
+ | * Before running the the software project, the FPGA located on the CED1Z must be programmed with the Nios II system image. To program the FPGA run the // | ||
+ | * Press the **//Run//** button in the **//Run Configurations// | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | <WRAP round help>The code size and start address might be different than the ones displayed in the above screenshot.</ | ||
====== uC-Probe Interface ====== | ====== uC-Probe Interface ====== |