Hi @Jeevan,
Yes, it can still work. Just make sure to initialize the appropriate pin and configure it during the SPI initialization.
In the case of the lpspi_interrupt_b2b_transfer_slave_cm7 example code from the SDK, you can achieve this by changing "slaveConfig.whichPCS" value from kLPSPI_Pcs0 to kLPSPI_Pcs1:
BR,
Edwin.
Hi @Jeevan,
SPI polling would be a simpler solution, but it can also require a much higher load of work on the CPU. Interrupt increases the complexity of the transmissions but is much better for performance in the CPU. I would depend on how often you expect an ADC/DAC conversion, and how "real-time" you want this conversion to be processes, but I would recommend using the interrupt method, and basing your code on the example project we provide in our SDKs.
BR,
Edwin.
Hi @EdwinHz ,
Thank you for your valuable information.
Just had one query.
Will the SPI communication work from eval board to eval board if chip select 0 selected on one board and chip select 1 selected on another board.
Board connection:
Eval board 1 <--> Eval board 2
CS0 <-> CS1
Clock <-> Clock
MOSI <-> MISO
MISO <-> MOSI
GND <-> GND
Hi @Jeevan,
Yes, it can still work. Just make sure to initialize the appropriate pin and configure it during the SPI initialization.
In the case of the lpspi_interrupt_b2b_transfer_slave_cm7 example code from the SDK, you can achieve this by changing "slaveConfig.whichPCS" value from kLPSPI_Pcs0 to kLPSPI_Pcs1:
BR,
Edwin.