• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 103 subscribers
  • Views 1101 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.

SPI1 compared to SPI0

Ioan
Prodigy 105 points
Other Parts Discussed in Thread: TMS320DM355

I'm using the DM355, and found using the I2C drivers relatively straight forward. I'm now tring to use SPI1, but most comments/documentation on the SPI busses refer to SPI0. What are the difference between the two (if any), and can anyone give me a tip on an approach to using SPI1?

Many thanks for any help,

Ioan.

  • 0
    TI__Guru 63205 points

    Ioan said:

    I'm now tring to use SPI1, but most comments/documentation on the SPI busses refer to SPI0. What are the difference between the two (if any)

    The SPI interface peripherals on the DM355 are identical.

     

     

    Ioan said:

     

    and can anyone give me a tip on an approach to using SPI1?

     

    I would suggest utilizing the TMS320DM355 datasheet and the TMS320DM35x DMSoC Serial Peripheral Interface (SPI) User's Guide (SPRUED4).

    Have you started to the SPI0 interface?  There would be some pin muxing options that would be unique for SPI1 versus SPI0, but the register set would be identical.
    Another item to look at is the Power and Sleep Controller described in the TMS320DM355 Digital Media System-on-Chip ARM Subsystem Reference Guide (SPRUFB3) as this may have unique control bits for each SPI interface instance.

  • 0
    Prodigy 40 points

    Hi Ioan,

     

    I have not looked at the DM355 code in awhile but when I was working with it, SPI1 was not enabled in the Linux drivers (I assume you want Linux support?)

     

    I had to add the SPI platform setup code which is found with all the other platform setup in the kernel (sorry I don't have it in front of me). The one gotcha is that a SPI interrupt is shared with the DMA engine (I believe it is the CCERR interrupt_. You have to modify the DMA code to not register this interrupt (or at least register it as SHARED).

     

    HTH.

     

    -- Pete

  • 0 in reply to Peter Sommerfeld3576
    Prodigy 105 points

    Thanks Pete, most usefull. Mentioning that 'gotcha' might have saved me hours of work..!!

    Regards,

    Ioan

  • 0 in reply to Ioan
    Intellectual 380 points
    Loan,

    Did you ever get this working? I would love a peek at the code!

    Thank you!

    David