Visible to Intel only — GUID: mwh1416946844940
Ixiasoft
Visible to Intel only — GUID: mwh1416946844940
Ixiasoft
7.8.2. Assumptions and Requirements
Typically, you are developing a device driver or software package for eventual incorporation in a BSP. The driver or package is to be incorporated in the BSP by an end user who has limited knowledge of the driver or package internal implementation. To add your driver or package to a BSP, the end user must rely on the driver or package settings that you create with the tools described in this section.
For more information on how file names and directory structures conform to certain conventions, refer to the “File Names and Locations” chapter.
If your driver or software package uses the HAL auto initialization mechanism (alt_sys_init()), certain macros must be defined in a header file.
For more information about this header file, refer to the “Header Files and alt_sys_init.c” chapter.
For more information about integrating a HAL device driver, refer to AN 459: Guidelines for Developing a Nios II HAL Device Driver.
For more information about the commands you can use in a driver Tcl script, refer to the "Nios II Software Build Tools Reference" chapter.