Specifications

if {$first_jtag_uart == "none"
}
{
set first_jtag_uart $slave_desc
}
}
# Track last character device in case no JTAG UARTs found.
if { [is_char_device $slave_desc] }
{
set last_stdio $slave_desc
}
}
if {$first_jtag_uart != "none"}
{
return $first_jtag_uart
}
return $last_stdio
}
# Call routine to determine stdio set default_stdio [choose_default_stdio]
# Set stdio settings to use results of above call.
set_setting hal.stdin $default_stdio set_setting hal.stdout
$default_stdio set_setting hal.stderr $default_stdio
Related Information
• Specifying BSP Defaults on page 4-34
• Developing Device Drivers for the Hardware Abstraction Layer on page 7-1
For more information about slave descriptors, refer to the "Developing Device Drivers for the
Hardware Abstraction Layer".
• Specifying BSP Defaults on page 4-34
For more information about determining what device to use for stdio, refer to "Specifyin BSP
Defaults".
Revising Your BSP
Your BSP is customized to your hardware design and your software requirements. If your hardware
design or software requirements change, you usually need to revise your BSP.
Every BSP is based on a Nios II processor in a hardware system. The BSP settings file does not duplicate
information available in the .sopcinfo file, but it does contain system-dependent settings that reference
system information. Because of these system-dependent settings, a BSP settings file can become inconsis‐
tent with its system if the system changes.
You can revise a BSP at several levels. This section describes each level, and provides guidance about when
to use it.
Rebuilding Your BSP
Rebuilding a BSP is the most superficial way to revise a BSP.
What Happens
Rebuilding the BSP simply recreates all BSP object files and the .a library file. BSP settings, source files,
and compiler options are unchanged.
NII5V2
2015.05.14
Revising Your BSP
4-29
Nios II Software Build Tools
Altera Corporation
Send Feedback