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.

CCS/LAUNCHXL-F28379D: SPI data transfer from Launchxl-F28379D to Launchxl-CC1310

Part Number: LAUNCHXL-F28379D
Other Parts Discussed in Thread: LAUNCHXL-CC1310, ENERGIA, CC1310, C2000WARE

Tool/software: Code Composer Studio

G’day fine folk of TI!

This has been doing my head in for 2 months and not having a strong embedded background really does my head in!

 For reasons I can’t describe, I need to send data from a Launchxl-F28379d (I’m gonna call this guy 283) to a Launchxl-CC1310 (I’ll call this guy 1310) over SPI.

Out of frustration of dealing with CCS, I currently have a Simulink based example sending continuously incrementing numbers every second, out from 283’s SPI-B bank of pins to 1310’s same SPI pins (code attached as SPILED.slx).

I have an Energia Based SPI slave data reception bit of code flashed onto the 1310 (code attached as SPIPlaya.ino).

My Issue is that I don’t see the numbers being sent from 283, on 1310’s serial monitor.

 

I have tried:

  • CCS based SPI output example codes (tweaked to go out from SPI-B) for the 283
  • CCS based SPI slave input examples for 1310
  • Tweaked energia examples of SPI slave data receiving for the 1310

Could someone help me get data output from the 283 turning up and interpreted on the 1310?TICodeHelp.zip

  • Hi,

    You haven't provided any description of what is the problem you are facing. I have never worked in Simulink. So, I won't be able to help you in that regard.

    If you are willing to work in CCS environment, I can provide suggestions based on your problem description.

    Regards,

    Manoj

  • Hi Manoj,

    Here's my problem.

    My 1310 board isn't receiving data from my 283 board.

    All the physical connections necessary for SPI to work have been made correctly, as follows:

    F28379D -> CC1310

    SPIBCLK -> SPICLK

    SPIBMOSI -> SPIMOSI

    SPIBMISO -> SPIMISO

    SPIBCS -> SPICS

    If it is of any help, this is a screenshot of Simulink code that I am using 

    Inside the SPI transfer block, this is how I have set it up.

    If these simulink models are unfamiliar to you, I have also attached the CCS code equivalent that I tried to use in one of my earlier listed attempts, to get the 283 to transmit data over SPI  (attached as spi_ex1_loopback.zip)

    spi_ex1_loopback.zip

    Hope this helps!

  • I would suggest below steps to get started with your debugging process.

    1. Did you already probe SPI bus and check whether F28379D SPI is transmitting data?
    2. LAUNCHXL-F28379D supports only specific SPI pins. Did you make sure F28379D SPI signals are configured to the pins supported in LAUNCHXL-F28379D
    3. In order for CC1310 SPI to talk with F28379D SPI, you need to make sure CC1310 SPI is configured correctly.

    Regards,

    Manoj

  • Hi Manoj,

    1. I have probed around the board and found that appropriate SPI signals are being sent out.

    2. To determine that these appropriate signals are being sent out, i probed the pins which the attached code suggested, which are the supported pins that you suggested.

    3. Would you please inform me on what the correct configuration is?

    4. Also, do you or does anyone else here know how to run both 283 and 1310 from ccs, with their different codes, at the same time, so that I can see what one board is sending to another and how it receives this as well?

    Thanks a lot!

    3326.spi_ex1_loopback.zip

  • Hi Manoj,

    1. I have probed around the board and found that appropriate SPI signals are being sent out.

    2. To determine that these appropriate signals are being sent out, i probed the pins which the attached code suggested, which are the supported pins that you suggested.

    3. Would you please inform me on what the correct configuration is?

    4. Also, do you or does anyone else here know how to run both 283 and 1310 from ccs, with their different codes, at the same time, so that I can see what one board is sending to another and how it receives this as well?

    Thanks a lot!

    2055.spi_ex1_loopback.zip

  • Shaetrun,

    Correct SPI configuration of SPI depends on your system requirements. Key questions to ask are:

    • Is F28379D. SPI  master (or) slave?
    • Do I want to transmit (or) receive?
    • What is the buad rate?
    • Which polarity clocking scheme you want to use?
    • Do you need to 4 wire SPI (or) 3-wire SPI?
    • Do you need interrupt / polling / DMA based SPI communication?
    • Which CPU control SPI port?

    Example projects available in C2000Ware shows you a generic configuration of SPI peripheral . But, it should help you jump start in your project development.

    Unfortunately, we don't have ready-made F28379D - CC1310 project which talks through SPI. But, I would assume CC1310 should provide example projects for SPI just like C2000 provide example project. Once you understand those example projects for both these devices, you need to modify them according to your system requirements.

    Regards,

    Manoj

  • Hi Manoj, cpologies for the delayed reply.

    Here's what I need help with making and the details I could provide:

    • 283 - Master, 1310 - Slave
    • 283 is the one sending data to the 1310 so it's pretty much just one way.
    • Default as I'm lead to believe, 115200 I guess?
    • Which polarity clocking scheme you want to use? - Rising Edge would be cool
    • Do you need to 4 wire SPI (or) 3-wire SPI? - 4 Wires please
    • Do you need interrupt / polling / DMA based SPI communication? - Nah if it's one way communication, should be simpler than this right?
    • Which CPU control SPI port? - CPU1.

    I have tried to make modifications to the attached code as per earlier post, but not had much success when communication to the other board whoI had set up similarly.

    I hope this helps and thanks in advance!

  • Shaetrun,

    I believe you earlier said that F28379D-SPI is indeed sending the SPI signals which are expected to send to 1310-slave. In that case, the source of the debug should be in 1310 and not F28379D-SPI.

    Is 1310.SPI configured right? Did you 1310.SPI receive the right value transmitted by F28379D.SPI (master).

    Regards,

    Manoj