Specifications

Although this section describes tasks in terms of the SBT command line flow, you can also carry out most
of these tasks with the Nios II SBT for Eclipse.
Related Information
• Using Version Control on page 4-8
• Copying, Moving, or Renaming a BSP on page 4-9
• Handing Off a BSP on page 4-10
• Changing the Default Linker Memory Region on page 4-14
• Changing a Linker Section Mapping on page 4-15
• Managing Device Drivers on page 4-16
• Creating a Custom Version of newlib on page 4-17
• Creating a BSP for an Altera Development Board on page 4-15
• Creating Memory Initialization Files on page 4-10
• Modifying Linker Memory Regions on page 4-11
• Creating a Custom Linker Section on page 4-12
• Querying Settings on page 4-16
• Controlling the stdio Device on page 4-17
• Configuring Optimization and Debugger Options on page 4-17
• Getting Started with the Graphical User Interface on page 2-1
For more information about carrying out the tasks with the Nios II SBT for Eclipse, refer to the
"Getting Started with the Graphical User Interface" chapter.
Adding the Nios II SBT to Your Tool Flow
A common reason for using the SBT is to enable you to integrate your software build process with other
tools that you use for system development, including non-Altera tools. This section describes several
scenarios in which you can incorporate the build tools in an existing tool chain.
Using Version Control
One common tool flow requirement is version control. By placing an entire software project, including
both source and makefiles, under version control, you can ensure reproducible results from software
builds.
When you are using version control, it is important to know which files to add to your version control
database. With the Nios II SBT, the version control requirements depend on what you are trying to do
and how you create the BSP.
Creating BSP by Running a User Defined Script to Call nios2-bsp
If you create a BSP by running your own script that calls nios2-bsp, you can put your script under version
control. If your script provides any Tcl scripts to nios2-bsp (using the --script option), you must also
put these Tcl scripts under version control. If you install a new release of Nios II EDS and run your script
to create a new BSP or to update an existing BSP, the internal implementation of your BSP might change
slightly due to improvements in Nios II EDS.
For more information, refer to Revising Your BSP for a discussion of BSP regeneration with Nios II EDS
updates.
Related Information
Revising Your BSP on page 4-29
4-8
Adding the Nios II SBT to Your Tool Flow
NII5V2
2015.05.14
Altera Corporation
Nios II Software Build Tools
Send Feedback