• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 123 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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-CC1312R1: Configure the LAUNCHXL-CC1312R1 launchpad as a secondary device

Danilo A.
Mastermind 24715 points
Part Number: LAUNCHXL-CC1312R1

Hi Team,

Our customer would like to configure the LAUNCHXL-CC1312R1 launchpad as a secondary device while the Arduino is the primary. Is this possible? Please see the details of our customer's inquiry below.

I'm hoping to use a sensor and arduino to send information to the CC1312R1 over I2C or another protocol. Is there documentation about programming such an interface? I know there are examples for interfacing with a temperature sensor (like https://e2e.ti.com/support/wireless-connectivity/sub-1-ghz-group/sub-1-ghz/f/sub-1-ghz-forum/1029166/cc1312r-i2c-communication-between-cc1312-and-2-different-ics?tisearch=e2e-sitesearch&keymatch=CC1312%20I2C# ), but I am more interested in using the arduino as the master controller and the CC1312 as the slave, which will just be used for its RF sensor, to communicate with a mesh net, is there documentation about configuring CC1312 as a slave device?

Regards,

Danilo

  • 0
    TI__Mastermind 20332 points

    Hi Danilo,

    This should be possible. We do have SPI master and SPI slave example in our SDK.

    https://dev.ti.com/tirex/explore/node?node=AOUiCAFNjPzDk1C4wQaVtA__BSEc4rl__LATEST

    But is there a reason for this architecture? Depending on the interface, it could be better to just use the cc1312 device to interface with the sensor so that only one chip is used. 

    Regards,

    Sid

  • 0 in reply to Sid
    TI__Mastermind 24715 points

    Hi Sid,

    Please see the feedback of our customer below.

    Thank you so much for the SDK example! This is a huge weight off my shoulders to know that there's a documented way to do this. I agree that the architecture is a bit redundant with two microcontrollers, but the main reason for using the arduino is to ensure compatibility with our sensor (which has extensive libraries for use with the arduino SDK), and because I already had one on my desk. The sensor can communicate over I2C, but right now we're at the proof-of-concept stage so I'm trying to keep the software side as simple as possible, which happens to make the hardware a bit obtuse. Thank you again for your help!

    Regards,

    Danilo