• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 51 subscribers
  • Views 449 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.

RTOS/CC2650: LAUNCHXL-CC2650

Xavier Williams
Prodigy 20 points
Part Number: CC2650


Tool/software: TI-RTOS

I'm having trouble using the SDSPI.h driver in the CC2650 LAUNCHXL in order to implement an SD card with the micro-controller.  From my understanding with if the SDSPI stuff is initialized correctly BIOS FatFs can be used to do operations on the SD card.  I'm not understanding how to correctly initialize the SDSPI driver. 

  • 0
    TI__Genius 14860 points
    Hi,
    the SDSPI driver in the SDK is only an interface. There is no implementation available for the CC13x0/CC26x0 CPU family. Sorry. You could have a look at the MSP432 SDK or the CC32XX SDK and port the SDSPI driver from there to the CC26X0 SPI driver.
  • 0 in reply to Richard W.
    Prodigy 20 points

    I've been looking at the MSP432 sdk at the SDSPI driver, however i'm noticing there a few big differences between the MSP432 and the.  The MSP432 driver has things written in about performance levels and uses the ClockFreqs.h for a lot of the SDSPI driver.  However, the CC2650 does not any files similar to that.  I'm not really sure how I would port this over.  

  • 0 in reply to Xavier Williams
    TI__Genius 14860 points

    Hi,

    you are right. The SDSPI driver for both the MSP432 and the CC32XX build upon driverlib, the low-level hardware abstraction layer and implement SPI functionality on their own instead of using the high-level SPI driver. I do not know whether the reason was the lack of flexibility or timing issues with the SPI driver. But without knowing the details, I would assume that the SDSPI driver could be implement using the high-level SPI driver interface as well.

    If you want to do that, you should at first get familiar with the SPICC26XXDMA driver and then rewrite the SDSPI driver using that.  On the other hand side you could also rewrite the SDSPI driver based upon DriverLib and without the DMA, but then you should study the SPICC26XXDMA driver even more carefully.