This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
resources:fpga:altera:bemicro:common [16 Sep 2011 10:56] – changed the name of some folders Andrei Cozma | resources:fpga:altera:bemicro:common [03 Jan 2013 20:42] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== NIOS II Software Design ====== | ||
- | |||
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. | 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. | ||
Line 8: | Line 6: | ||
Launch the **Nios II SBT** from the **//Start -> All Programs -> Altera -> Nios II EDS 11.0 -> Nios II 11.0 | 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)//**. | Software Build Tools for Eclipse (SBT)//**. | ||
- | <note tip> | + | <WRAP tip> |
=== 1. Initialize Eclipse workspace === | === 1. Initialize Eclipse workspace === | ||
Line 14: | Line 12: | ||
* 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 **// | * 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 === | === 2. Create a new software project in the SBT === | ||
Line 28: | Line 26: | ||
* Click the **// | * Click the **// | ||
- | {{ : | + | {{ : |
The tool will create two new software project directories. Each Nios II application has 2 project directories in the Eclipse workspace. | The tool will create two new software project directories. Each Nios II application has 2 project directories in the Eclipse workspace. | ||
Line 34: | Line 32: | ||
* 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 “**// | * 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. | 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. | ||
Line 44: | Line 42: | ||
* Right click on the **// | * 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 // | 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 // | ||
Line 64: | Line 62: | ||
* During compilation, | * During compilation, | ||
* Since our software does not make use of C++, uncheck **//Support C++//**. | * 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 **// | * Press **// | ||
- | {{ : | + | {{ : |
===== Add source code to the project ===== | ===== Add source code to the project ===== | ||
Line 74: | Line 74: | ||
* Select all the files and folders and drag them over the **// | * 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 **//OK//**. | * A dialog box will appear to select the desired operation. Select the option **//Copy files and folders//** and press **//OK//**. | ||
Line 82: | Line 82: | ||
* 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. | * 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 ===== | ===== Configure Application Project Build Properties ===== | ||
Line 92: | Line 92: | ||
* Press **// | * Press **// | ||
- | {{ : | + | {{ : |
===== Define Application Include Directories ===== | ===== Define Application Include Directories ===== | ||
Line 100: | Line 100: | ||
* Click the **// | * Click the **// | ||
- | {{ : | + | {{ : |
* Double click on **// | * Double click on **// | ||
* If you see the message shown here about resources being out of sync, right click on the **// | * If you see the message shown here about resources being out of sync, right click on the **// | ||
- | {{ : | + | {{ : |
* Select the line **APP_INCLUDE_DIRS :=** | * Select the line **APP_INCLUDE_DIRS :=** | ||
Line 126: | Line 126: | ||
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 // | 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 === | === 2. Verify the Board Connection === | ||
Line 138: | Line 139: | ||
* Change the configuration name to **// | * Change the configuration name to **// | ||
* On the **//Target Connection// | * On the **//Target Connection// | ||
- | * Select the **//jtag_uart_1//** as the **//Byte Stream Device//** for //stdio//. | + | * Select the **//jtag_uart//** as the **//Byte Stream Device//** for //stdio//. |
+ | * Check the **//Ignore mismatched system ID option// | ||
+ | * Check the **//Ignore mismatched system timestamp option//**. | ||
- | {{: | + | {{: |
{{: | {{: | ||
- | {{ : | + | {{ : |
=== 3. Run the Software Project on the Target === | === 3. Run the Software Project on the Target === | ||
Line 155: | Line 158: | ||
{{ : | {{ : | ||
- | <note>The code size and start address might be different than the ones displayed in the above screenshot.</ | + | <WRAP round help>The code size and start address might be different than the ones displayed in the above screenshot.</ |