• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 33 subscribers
  • Views 127 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.

TCAN4550-Q1: Support MCAL asynchronous SPI

Grey Guo
Intellectual 2160 points
Part Number: TCAN4550-Q1
Other Parts Discussed in Thread: TCAN4550

Tool/software:

Hi team,

My customer is using TCAN4550-Q1 and IFX MCU with AutoSAR MCAL. They want to use MCAL asynchronous SPI to communicate with TCAN4550-Q1. Can TCAN4550-Q1 support asynchronous SPI? Thanks!

Best Regards

Grey

  • 0
    TI__Mastermind 33030 points

    Hi Grey,

    The TCAN4550-Q1 only has a single SPI interface that supports a protocol of either a Read or Write transaction. There are separate data out (SDO) and data in (SDI) pins so that data can flow between the TCAN4550-Q1 and the MCU simultaneously, but I'm not sure if this is what is implied by the "asynchronous" specification. 

    Because there is only a single SPI bus, the MCU can only perform a single write or read operation on a register or MRAM cell at a time.  It can't be writing to one register or MRAM cell while simultaneously reading back data from a different register or MRAM cell.

    I hope this clarifies the SPI operation of the device enough to answer your question.

    Regards,

    Jonathan

  • 0 in reply to Jonathan Nerger
    TI__Intellectual 2160 points

    Hi Jonathan,

    Thanks for reply. Asynchronous SPI means non-blocking SPI, a method of communicating using the SPI protocol where data transfers happen without blocking the main program flow, meaning the microcontroller can continue executing other tasks while the SPI transfer is in progress.

    Best Regards

    Grey

  • +1 in reply to Grey Guo
    TI__Mastermind 33030 points

    Hi Grey,

    Then this seems to be a question of the MCU capabilities rather than the TCAN4550.

    Regards,

    Jonathan