Hi,
I'm new to SPI and have some problems to connect DM368 and DM6435 through SPI.
DM368 uses SPI1 as SPI Master and DM6435 uses McBSP as SPI Slave.
When DM368 sends a byte stream, DM6435 couldn't receive the whole data.
It seems that SPI's chip select signal doesn't act like McBSP's FSX when byte stream is transferred.
I observed that DM368's SPI doesn't change the chip select signal while transferring byte stream.
DM368's McBSP seems that its FSX signal goes to the inactive state when each byte is transferred.
And, DM6435's McBSP User's Guide also says that the McBSP requires an active edge of the slave-enable signal on the FSX input for each byte transfer.
SPI waveforms from googling also show no change in chip select signal for byte stream transferring.
Question 1)
Even though McBSP supports SPI protocol, does SPI master should reset chip select signal for each byte transfer?
Question 2)
With SPIDAT.CSHOLD = 0 and SPIDEF.SCS0DEF = 1, DM368 deactivates chip select signal at the end of each byte.
This configuration ensures that DM6435 receives the whole data.
But, DM368 receives a corrupted data (it looks like some bits are shifted on oscilloscope) and C2TDELAY and T2CDELAY don't work at all.
How to set DM368 SPI peripheral to generate a valid chip select signal for McBSP?
It seems that It'll be goot to use McBSP at both sides.
But, it is not possible currently.
Best Regards,
Jinkyu Park