TMDXICE110: SPI or McSPI driver interface

Hi
First thing we want to clarify is that these files are not for normal EtherCAT Mode and only the ET1100 SPI mode. http://software-dl.ti.com/processor-industrial-sw/esd/docs/indsw/EtherCAT_Slave/01_00_10/PRU_ICSS_EtherCAT.html#ti-esc-spi-interface-to-support-asic-mode-for-ethercat

If you want to use SPI peripheral for normal communication with SPI hardware like the ADC, you can directly use the SPI drivers. The description of the driver and examples we have is present here : https://software-dl.ti.com/processor-sdk-rtos/esd/docs/06_03_00_106/AM335X/rtos/index_device_drv.html#mcspi-qspi-ospi

Regards
Dhaval Khandla

Hi.  Thanks for the reply.  I was using the ti_spi_master code as an example of the SPI calls.  I understand the protocol in there is specific to the ET1100 communications.  Your link is very helpful, but I have a couple more simple questions.  None of the examples I have seen used 2 chips on one SPI link.

In my system, I will have the ADC on SPI1, CSO, and an accelerometer on SPI1, CS1.  The TMDX110 configuration calls this SPI1_launchpad, which is the interface used for the ET1100 communications as well.

I am thinking for my system I need to use the MCSPI device like this:

peripheralNum = 1;
channel = ADC_CHANNEL;
ADC_handle = MCSPI_open(peripheralNum, channel, &spiParams);

channel = ACCEL_CHANNEL;
ACCEL_handle = MCSPI_open(peripheralNum, channel, &spiParams);

Where ADC_CHANNEL is 0, and ACCEL_CHANNEL is 1.

Then use the MCSPI_transfer() functions.

Does that sound right?

I forgot to add that in the link you sent, this link is broken to the SYSBIOS document, as are the XDAIS and FC links on the page

processors.wiki.ti.com/index.php

Sorry for the stream of questions...  One more:

I need to set up the CS assert and deassert delays and other things like that.  Can I just use the CSL library calls to set up the chip, and then use the MCSPI driver interface to manage the transfers?  It's not clear to me that I can intermix CSL calls and DRV level calls. 

Thanks.

Hello?  Is there anyone here?

Hi John,

Apologies for the delayed reply.

For your first question about using two chips on one SPI link, you can use one slave on one chip-select, and then the second slave on another chip-select. Within the following path there is example code for using multiple channels, and it is very similiar to the code that you provided. 

ti_am335x_06_03_00_106_install\pdk_am335x_1_0_17\packages\ti\drv\spi\test\src\main_mcspi_test.c

#ifdef MCSPI_MULT_CHANNEL
/*
*  ======== spi_test_multiple_channel ========
*/
bool spi_test_multiple_channel(void *arg)

spi[chn] = MCSPI_open(instance, chn, &mcSpiParams);

And for your question about CSL, CSL calls can be used in combination with the driver calls, but you just need to be careful where you use the CSL calls. You want to make sure that the driver calls don't interfere with the chip select configuration. 

For example, you could open the MCSPI driver, then make your CSL calls to configure the chip-select, and then check that the MCSPI registers are still valid. 

And if that doesn't work, the next option would be to try adding the CSL calls that you need for chip-select configuration into the MCSPI driver code, and then rebuild the MCSPI driver.

Best regards,

Dillon