Functions listed in Table 3-3 are categorized into different files. Functions for SPI receive and transmit are included in bridge_spi.c and bridge_spi.h. Functions for CAN receive and transmit are included in bridge_can.c and bridge_can.h. The structure of the FIFO element is defined in user_define.h.

Users can separate functions by file. For example, if only SPI functions are required, users can reserve bridge_spi.c and bridge_spi.h to call the functions.

For the basic configuration of peripherals, this project integrates a SysConfig configuration file. Users can easily modify the basic configuration of peripherals by using SysConfig.

Applications requiring this functionality must include the CAN module and API and SPI module API. All API files are included with the SDK download.

Table 3-4 lists the footprint of the CAN-SPI bridge design in terms of flash size and RAM size. Table 3-4 have been determined using the Code Composer Studio (Version: 12.7.1.00001) with optimization level 2.

The user can adjust the size of the FIFO. A larger FIFO means more cache capacity, but requires more RAM space. For details, see the relevant content in Application Aspects. The user can configure the data field size according to the actual data length. As listed in Table 3-4, using a data field with less bytes can significantly reduce RAM usage.