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.

LAUNCHXL-CC1350: SPI master\slave issues

Part Number: LAUNCHXL-CC1350
Other Parts Discussed in Thread: CC1350

Greetings

I've stumbled into some issues with implementing SPI connection using two cc1350 launchpads (im using Contiki OS if its important). Despite there are library included it seems like it wasnt ment for slave devices. I was referring to tech. reference manual http://www.ti.com/lit/ug/swcu117g/swcu117g.pdf rom DR register which caused my chip to reboot constantly, i haven't been able to send and read data. So my questions are:

2. Are there any similar examples for configuring slave device?

3. If not, im wondering if someone could explain me what behavior should slave device have for receiving data? What action or event should cause my device to start reading the data?


Best regards
Vladimir.

  • Apologies, 1st question has disappeared.
    So there it is
    1. Are there any ideas how to prevent chip from rebooting every time it reads from register?
  • Hi,

    apologies for the late reply. I am not familiar with the SPI driver in Contiki, but what you describe sounds like the SPI peripheral is not powered up. Before you can access registers of a peripheral unit you need to power the unit up and enable the clocks. Otherwise you will get a bus fault and this will likely cause a reset in Contiki.

  • Greetings, Richard.

    Thank you for your reply. Yes, as far as i remember peripheral was not powered up and initialized. 

    My bad as well, for not updating and closing up this thread.
    I've made a basic implementation of SPI for cc1350 on contiki, based on manual i've linked before. It turns out to be a quiet simple protocol but it still needs a bit of a research when running on contiki.

    Thank you once again. 
    Best regards
    Vladimir