• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 102 subscribers
  • Views 97 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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:

TDA2EXEVM: Communication with another SPI slave

TDA2EXEVM: Processors forum

Khai Trinh
Genius 4140 points
Part Number: TDA2EXEVM
Other Parts Discussed in Thread: TDA2

This is actually a follow up question for E2E ticket - https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1000532/tda2exevm-communication-with-another-spi-slave/3736466

The above ticket was asked 7 months ago. We are now in integration and begin activating the SPI instance 0 to communicate with our slave device.

We are hoping to have a small consultation time instead of asking questions thru E2E to minimize on the back and forth before a point is getting across. A half an hour call would do us a great deal and get us over the hurdle since our integration schedule is tight. Please respond to this ticket and let us know if our requested is granted.

Thank you and looking forward to hearing from you.

  • 0
    Genius 4140 points

    Stanley Wrote in above e2e link in quote below:

    "

    If yes, radar SPI driver is implemented in ~/pdk_xx_xx_xx_xx/packages/ti/drv/vps/src/devices/radar_ar12xx/src/bspdrv_ar12xxMcspiCfgPriv.c.

    Only Utils_mcspiInit() is called from use case to add the McSPI instace to GIO device and configure crossbar for interrupt.

    The instance will be opened later by radar SPI driver in PDK.

    To configure radar, we use radar APIs from rl_sensor.c in ~/mmwave_dfp/ti/control/mmwavelink/src/rl_sensor.c, which has the callback hooked to radar SPI driver.

    "

    From what you said in quote above, the usecase application does not interact with the SPI driver directly (ie: it doesn't gain access to the commHdl of the SPI channel instance). Is there a way to gain access to the commHdl of a SPI instance so we can close its commHdl to free up channel resource for another SPI slave using the same SPI instance?

    Thank you.

  • 0 in reply to Khai Trinh
    TI__Mastermind 39735 points

    Hi,

    I am looping in TDA2 experts to answer the above query.

    Khai Trinh said:
    We are now in integration and begin activating the SPI instance 0 to communicate with our slave device.

    Meanwhile, can you please share the details on what issues are you facing?

    Regards,
    Parth