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.

CC1310: MSP432 as gateway and CC1320 as nodes, some challanges we will face

Part Number: CC1310
Other Parts Discussed in Thread: ENERGIA, TIDC-01002, ENERGYTRACE

Dear All,

After implementing the solution for sub1 GHz collector (MSP432 + CC1310 launchpad as co-processor) and another CC1310 as sensor, and using the example projects, provided by TI (described in details in answer of my previous and related to this one post, I was able to connect the sensor and the collector but no information for the ambient temperature, etc. is received.

This is the sensor monitor - 

Starting...
State Changed: 1
Started: 0x1
Channel: 1
State Changed: 3

and this is the collector one:


----------------------------
SimpleLink 15.4 Stack Collector Demo
----------------------------

Collector init complete

Started
Channel: 1
PermitJoin-ON
Joined: 0x1

Can you help me to figure out what is the issue?

Thank you and best regards,

Stanislav

  • Hey Stanislav,

    Can you verify using a sniffer that the devices associate and stay connected?

  • Dear Ammar,

    For sure devices associated, as you can see they exchange and connect in the channel. 

    Unfortunately, we have only two CC1310, so no sniffer available. Are there other options for debugging or the only option is RF sniffer?

    Best Regards,

    Stanislav

  • Latest update: I have checked the CC1310 launchpads with Energia examples - simple send/receive and they work as expected. 

    So, most likely I cannot properly start the examples from SDKs where TI-RTOS is used.

  • I am also using the latest SDK for CC1310 and MSP432. Should I reverse to the earliest versions to test if then the node and the collector will exchange data ? 

  • Hey Stanislav,

    Just to be clear, you've taken the TIDC-01002 and implemented it for a CC1310 and an MSP432 (replacing the CC3220)?

    Have you stepped through the code/enabled breakpoints to ensure that the MSP432 is sending the correct data to the CC1310 for a data message? What were the results there? If you need help figuring out where to set breakpoints, let me know and I can provide some insight.

    If your application is using timers to send sensor messages (like in our SDK examples), is the timer callback entered?

    The only data messages the collector sends to the sensor are tracking requests and config messages. I assume you are using a similar method on the TI RTOS side to the simple send/receive api's in Energia to send messages, correct? Can you provide some insight on how this was implemented on your end?

  • Hello Ammar,

    Yes, this is the case - I have used TIDC-01002 and implemented it for a CC1310 and an MSP432 (replacing the CC3220). No changes in the code from the examples. I tried several breakpoints, but since the TI-RTOS concept is new for me, it was hard for me to comprehend what exactly to look for. If you help me with the exact places where to look in, I will be very grateful.

    For Energia examples, actually I used the EasyLink examples, just to send forth and back some data, no TI-RTOS whatsoever. My intention was just to confirm that the two boards are in good shape and work electrically, which is the case.

    So any help in regards to the SDK examples, which use the TI-RTOS is most appreciated. Thank you in advance.

    Best Regards,

    Stanislav

  • Hey Stanislav,

    Here's some helpful documentation that'll shed some light on our 15.4 Stack, as well as go through our examples using CCS instead of Energia.

    A good example of the api's called when a network is formed and when data is exchanged is located in the User's Guide. For example, if you're using non-beacon mode, you can find the diagram here.

    There's also useful debugging information there as well. Please go through this and follow up with any questions!

  • Thank you Ammar, 

    I have looked at the links provided. Moreover, I had a look at Energia libs as well. Looks like there are nicely wrapped stuff there - WiFi Server, clients, etc. So it looks like building the project in Energia will reduce significantly the development time, compared to the ti-rtos option. The two concerns for me are if Energia addresses stuff like Low Power Mode for the microcontroller, as well the security of the communication. Do you have some guidelines on these subjects, as well the general idea for using Energia for such kind of projects?

  • Hey Stanislav,

    I'm not too familiar with Energia unfortunately. My understanding is there is a sleep() function that you can call to put the device to sleep. You can then go further and use EnergyTrace to verify the current of the device to check that the device is sleeping.

    I'm unsure about your question regarding security. Do you mean the communication on the 802.15.4 network or through something else like UART?

    When it comes to our 802.15.4 stack, I'm not aware of any examples we have with Energia.

    I would start debugging the TI-RTOS project by ensuring that the collector device sends a config request to the sensor and the sensor receives it, as you've stated prior that the terminal that the devices seem to successfully connect. The code for this is located in the collector.c and sensor.c files.

  • Thank you, Ammar

    You gave me all the necessary tools and guidelines to work on this project! Now it is clear for me how to approach this.

    Best Regards,

    Stanislav