Hi, engineer TI,
Recently, we are debugging two AWR1642 for SPI communication. One of them can send data as master, but 1642 as slave cannot receive correct data. All the data read are 0xFF.Where to look for this problem.
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.
Hi, engineer TI,
Recently, we are debugging two AWR1642 for SPI communication. One of them can send data as master, but 1642 as slave cannot receive correct data. All the data read are 0xFF.Where to look for this problem.
Hi,
Please take a look at the SPI driver's HTML documentation: (double-click this file in your SDK folder)
C:/ti/mmwave_sdk_02_01_00_00/packages/ti/drivers/spi/docs/doxygen/html/index.html
This document discusses how to handle slave and master modes. For slave mode, namely:
If you are accounting for these things and still don't see correct data, you should check that the pinmux is set correctly for SPI. There are examples of this in the SPI driver test code.
Hi,db_woodall:
Thank you for your answer. I have solved this problem, but I have another problem.
How to send data to the master device from slave device, the slave device clock needs to be provided by the master device, so it is necessary to keep reading in the master device to generate the clock? and whether there are registers to set the clock generation and stop.
Hi, sorry for the delay. Have you found a solution to this issue? If not, please open a new thread.
Thanks, dave