This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TM4C1294NCPDT: SSI communication

Part Number: TM4C1294NCPDT
Other Parts Discussed in Thread: EK-TM4C1294XL

Hi Team,

I am using TI - EK-TM4C129XL board. I wants to write SPI communication for external EEPROM.

I have installed TI- SDK & imported the code example ssi_master_slave_xfer in CCS. The sample code location below,

C:\ti\TivaWare_C_Series-2.2.0.295\examples\boards\ek-tm4c1294xl\ssi_master_slave_xfer

To receive the data   MAP_SSIDataGet(SSI0_BASE, &pui32DataRx[ui32Index]); API is used

similarly C:\ti\TivaWare_C_Series-2.2.0.295_1\examples\peripherals\ssi sample code

I can find the receive data API SSIDataGet(SSI0_BASE, &pui32DataRx[ui32Index]);

MAP_SSIDataGet the call used rom mapping and SSIDataGet it directly called the SPI driver itself

My question here is - Is there any difference between MAP_SSIDataGet  and direct calling SSIDataGet

Kindly help.

Thanks & Regards,

Thalapushpam

  • Hi,

      Basically, no. The TivaWare APIs are also stored in the ROM so users can save flash spaces for their application. However, not all APIs in ROM are up to date. Some may be deprecated for use. This is the reason the MAP_ will either direct to the API in ROM or build the API at compile time depending if the version in the ROM is up to data or not. Please refer to section 7.4 on the TivaWare user's guide. There is a very good explanation on this. https://www.ti.com/lit/pdf/spmu373