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.

TMS320F28386D: SPI CS Interrupt

Part Number: TMS320F28386D
Other Parts Discussed in Thread: SYSCONFIG

Tool/software:

 Hi I want to get an interrupt when a SPI reception finished.

My setup is the following.

I have an SPI D configured as master with loopback mode. My actual application will be configured as slave but in this case I am writting a test so I need to use the master in loopback mode to stimulate the slave.

I need to know when the SPI reception finished so I can go and check the buffer written by the DMA in charge of the SPI Rx data.

Can I assign the CS GPIO to an XINT interrupt?

It is not working now and I think it might be because it is beeing already controlled by the SPI peripheral as output and is not able to see the input to trig the XINT. But I am not sure.

How would be the way to go? would it work differently If it is set as slave?

Thank you in advance

Agustin J. Gomez

  • Now it is working. I forgot to enable the interrupt in PIE. I think I just needed to ask the question to make it work.

    I have another topic here. I could activate the Interrupt in Sysconfig using a trick. Otherwise it was not possible to configre an XINT in the GPIO, because it was already assigned to the SPI module.

    The workaround was:
    Create a GPIO that is not used. (GPIO0)

    Enable the External Interrupt on it.

    Assign the another GPIO to the input XBAR, the one that is needed

    The warning says that the GPIO does not match.

    There is a better way to go?

  • Agustin,

    This looks right to me, but let me connect you with another expert to confirm your XBAR settings. 
    Best Regards,

    Aishwarya

  • Hi Agustin,

    Since the XINT comes directly from Input XBAR there should be no issue with this approach. The warning is there to prevent you from making a mistake in your configuration but your configuration of the XBAR and GPIO here is intentional. You can ignore this warning but let me know if anything is not working as expected.

    Thank you,

    Luke