Nios II Classic Software Developer’s Handbook

ID 683282
Date 5/14/2015
Public
Document Table of Contents

15.1.5. nios2-bsp-create-settings

Usage

nios2-bsp-create-settings [--bsp-dir <directory>] 

 [--cmd <tcl command>] [--cpu-name <cpu name>] 

 [--debug] [--extended-help] [--get-cpu-arch] 

 [--help] [--jdi <filename>] 

 [--librarian-factory-path <directory>] 

 [--librarian-path <directory>] [--log <filename>]

 [--script <filename>] [--set <name> <value>] 

 --settings <filename> [--silent] 

 --sopc <filename> --type <OS name> [--type-version <version>] [--verbose] [--version]

Options

  • --bsp-dir <directory>: Path to the directory where the BSP files are generated. Use . for the current directory. The directory <directory> must exist. This command overwrites preexisting files in <directory> without warning.
  • --cmd <tcl command>: Runs the specified Tcl command. Multiple --cmd options are allowed.
  • --cpu-name <cpu name>: The name of the Nios II processor that the BSP supports. Optional for a single-processor system. Use ? to list available Nios II processor names.
  • --debug: Sends debug information, exception traces, verbose output, and default information about the command's operation, to stdout.
  • --extended-help: Displays full information about this command and its options. Also displays Tcl command help for the --cmd and --script options.
  • --get-cpu-arch: Queries for processor architecture from the processor specified. Does not create a BSP.
  • --help: Displays basic information about this command and its options.
  • --jdi <filename>: The location of the JTAG Debugging Information File (.jdi) generated by the Quartus Prime software. The .jdi file specifies the name-to-node mappings for the JTAG chain elements. The tool inserts the JTAG Debugging Information File (.jdi) path in public.mk. If no .jdi path is specified, the command searches the directory containing the SOPC Information File (.sopcinfo), and uses the first .jdi file found.
  • --librarian-factory-path<directory> : Comma-separated librarian search path. Use $ for default factory search path.
  • --librarian-path<directory> : Comma-separated librarian search path. Use $ for default search path.
  • --log <filename>: Creates a debug log and write to specified file. Also logs debug information to stdout.
  • --script <filename>: Run the specified Tcl script with optional arguments. Multiple --script options are allowed.
  • --set <name> <value>: Sets the setting called <name> to <value>. Multiple --set options are allowed.
  • --settings <filename>: File name of the BSP settings file to create. This file is created with a .bsp file extension. It overwrites any existing settings file.
  • --silent: Suppresses information about the command's operation normally sent to stdout.
  • --sopc <filename>: The .sopcinfo file used to create the BSP.
  • --type <OS name>: BSP type. Use ? or types to list available BSP types for this option. Use names to list the display names of available BSP types. For a Nios II DPX system, always set this argument to lwhal.
  • --type-version <version>: BSP software component version. By default the latest version is used. default value can be used to reset to this default behavior. Use ? to list available BSP types and versions.
  • --verbose: Sends verbose output, and default information about the command's operation, to stdout.
  • --version: Displays the version of this command and exits with a zero exit status.

Description

If you use nios2-bsp-create-settings to create a settings file without any command-line options, Tcl commands, or Tcl scripts to modify the default settings, it creates a settings file that fails when running nios2-bsp-generate-files. Failure occurs because the nios2-bsp-create-settings command is able to create reasonable defaults for most settings, but the command requires additional information for system-dependent settings. The default Tcl scripts set the required system-dependent settings. Therefore it is better to use default Tcl scripts when calling nios2-bsp-create-settings directly. For an example of how to use the default Tcl scripts, refer to the nios2-bsp script.

If no command-line arguments are specified, this command returns an exit value of 1 and sends a help message to stderr.

Note:

For more information about this command, use the --extended-help option to display comprehensive usage information.

Example

nios2-bsp-create-settings --settings my_settings.bsp --sopc \
 ../my_sopc.sopcinfo --type hal --script default_settings.tcl