Nios® II Software Developer Handbook

ID 683525
Date 8/28/2023
Public
Document Table of Contents

5.7.2.1. What Happens

Regenerating a BSP has the following effects:
  • Reads the .sopcinfo file for basic system parameters such as module base addresses and clock frequencies.
  • Retrieves the current system identification (ID) from the .sopcinfo file. Ensures that the correct system ID is inserted in the .elf file the next time the BSP is built.
  • Adjusts the default memory map to correspond to changes in memory sizes. If you are using a custom memory map, it is untouched.
  • Retains all other existing settings in the BSP settings file.
Note: Except for adjusting the default memory map, the SBT does not ensure that the settings are consistent with the hardware design in the .sopcinfo file.
  • Ensures that the correct set of BSP files is present, as follows:
    • Copies all required source files to the BSP directory tree. Copied BSP files are listed in the "Copied BSP Files" (Table 4–8 on page 4–23).

      If a copied file (such as a HAL source file) already exists, the SBT checks the file timestamp against the timestamp of the file in the Nios® II EDS installation. The tools do not replace the BSP file unless it differs from the distribution file.

    • Recreates all generated files. Generated BSP files are listed in the "Generated BSP Files" table (Table 4–7 on page 4–23).
Note: You can disable generation of any BSP file in the BSP Editor, or on the command line with the set_ignore_file Tcl command. Otherwise, changes you make to a BSP file are lost when you regenerate the BSP. Whenever possible, use BSP settings, or custom device drivers or software packages, to customize your BSP.
  • Removes any files that are not required, for example, source files for drivers that are no longer in use.