Portable board-specific symbols.
The Board header file should be included in an application as follows:
This header serves as device-independent interface for applications using peripherals connected to the device via standard digital interfaces; e.g, GPIO, SPI, I2C, UART, etc. Its purpose is to enable application code that references a peripheral to be portable to any device and board that supports the peripheral.
Board_init()
must be called before any other driver API. This function is owned by the user (typically generated by SysConfig), and is responsible for device specific initialization; e.g., initializing clocks and power management functionality.
Go to the source code of this file.
Functions | |
void | Board_init (void) |
Performs "early" board-level initialization required by TI-DRIVERS. More... | |
void Board_init | ( | void | ) |
Performs "early" board-level initialization required by TI-DRIVERS.
Board_init() must be called before any other TI-DRIVER API. This function calls all device and board specific initialization functions needed by TI-DRIVERS; e.g., to initialize clocks and power management functionality.
This function should only be called once and as early in the application's startup as possible. In most applications, a call to Board_init() is the first statement in main()
.
Board_init
must be called after every CPU reset and prior to enabling any interrupts.