• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 33 subscribers
  • Views 437 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

TCAN4550-Q1: CC2642R: CC2642 and TCAN4550 i.e. SPI to CAN SPI, Abstraction Layer driver for CC2642 MCU to Interface TCAN4550...

TCAN4550-Q1: CC2642R: CC2642 and TCAN4550 i.e. SPI to CAN SDK for CC2642 MCU

Anilkumar Patil
Prodigy 90 points
Part Number: TCAN4550-Q1
Other Parts Discussed in Thread: TCAN4550

Hi Team,

For my new automotive project, I m using CC2642 MCU and TCAN1550 CAN controller, and through SPI interface, so we can achieve the CAN communication.

I have implemented SPI driver for CC2642 MCU, but using that driver, i can able to send data frame over SPI bus(MOSI) properly but i am unable to collect or receive any data from MISO pin, could you please suggest how to collect/receive data from MISO pin.....?

  • 0
    TI__Guru 53575 points

    Hi Anikumar,

    There are a few requirements that must be met to ensure proper SPI communication is possible with TCAN4550-Q1. I'll list some of these out below so we can check that each is satisfied before I suggest some more complex debug. 

    • Ensure all SPI format requirements for TCAN4550 are being met (listed in Section 8.5.1 on the datasheet). 
      • nCS is asserted (pulled low) before the SPI transaction begins.
      • The correct clock polarity (sample on rising edge) is configured by the MCU.
    • Confirm that Vio is supplied and above the UVio threshold.
    • Make sure the device is not in sleep mode - INH output should be active (high).
    • After powerup, the device starts a timer and will automatically go to sleep if not interacted with within a couple of minutes. Make sure that the SPI test is done within this timeframe from initial power-up.
    • Check that the clock or crystal input (OSCx) are active and stable.
      • The clock input is necessary for all non-diagnostic register accesses ('h0800 +). If the diagnostic registers ('h0000 to 'h000C) are available but no other registers are, make sure that the clock input is stable during the access attempt. 

    If all of these conditions are met and you are still unable to read data from TCAN4550, I would like to request a scope shot of the SPI lines (nCS, SDI, SDO, SCLK) to ensure that all the formatting is consistent with device requirements and see the device behavior in that state.

    Regards,
    Eric Schott