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.
Part Number: TMS570LS1227
I'm experimenting some issues regarding an SPI comunication between two devices: a TMS570LS1227 and an IMX6 processor. The TMS570 is configured as SPI slave and the IMX6 as master.
Both the devices have been configured with clock polarity = 1 and clock phase = 1. The SPI communication happens, but there is a shift in the received bits (the first one and last one are sometimes wrong).
After looking into the configuration we might have found the problem:
the TMS570 is configured as clock polarity = 1 and clock phase = 1 under the TI mode, while the IMX6 processori s configured as clock polarity = 1 and clock phase = 1 under the Motorola mode.
I have understood that there is a translation table, as follows:
Motorola mode 0 (Polarity 0 Phase 0) = TI Polarity 0 Phase 1
Motorola mode 1 (Polarity 0 Phase 1) = TI Polarity 0 Phase 0
Motorola mode 2 (Polarity 1 Phase 0) = TI Polarity 1 Phase 1
Motorola mode 3 (Polarity 1 Phase 1) = TI Polarity 1 Phase 0
Could you please confirm that
1) the TMS570 follows the TI spi mode? Does it have a Motorola mode?
2) the translation table (Motorola to TI mode) I have reported is correct ?
3) why in the TMS570 TRM or datasheet this topic about the SPI mode is not emphasized? It could be a topic prone to errors, since some TI devices follow the Motorola mode, some not.
4) two devices belonging to the same Group (Motorola or TI) must have the same configuration (clock rate, size, clock polarity, clock phase) in order to communicate?
5) two devices belonging to different Groups (Motorola and TI) must match the configuration in the translation table in order to communicate
Thank you very much for your valuable support,
Clocking modes for TMS570LS1227 are described in TRM, Section 28.2.7 . Follow the figures for clocking modes to match the clock mode needed to connect other device.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.