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.

TMS320F28384D: Any difference between SPI-B and SPI-D for SD access?

Part Number: TMS320F28384D

Tool/software:

Hi champs,

I am asking this for our customer.

The user wants to use SPI-D to access SD card by CPU2, but have issues now.

The user can use SPI-B to access SD card by CPU2 and can use SPI-D for general SPI usage 

But now, the user has trouble in using SPI-D to access SD card by CPU2.

The user is debugging it.

Questions:

Is there any difference between SPI-B and SPI-D by CPU2?

Is there any concern when changing SPI-B to SPI-D for SD card usage by CPU2?

  • Hi Wayne,

    Is there any difference between SPI-B and SPI-D by CPU2?

    CPU1 and CPU2 can access all four SPI instances the same. Only thing to note here is to make sure user resets SPI after CPU1 does basic configurations (ie. clocking) and then allocates the resource to the appropriate CPU. We have the following Driverlib functions to help do this 'SysCtl_resetPeripheral()' and 'SysCtl_selectCPUForPeripheral()'.

    Is there any concern when changing SPI-B to SPI-D for SD card usage by CPU2?

    Will loop in expert to confirm this point.

    Best Regards,

    Aishwarya

  • Hi Wayne,

    How is the customer using SPIB and SPID for SD card access? As per the schematic, GPIO 100 - 103 are connected to the onboard micro-SD card reader, so only the SPI mapping to these GPIO can be used to interface with the onboard reader. Is an external reader being used?

    In general, CPU1 and CPU2 should be able to access all SPI instances uniformly as Aishwarya mentioned

    Regards,

    Arnav