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/LAUNCHXL-CC1310: cc1310

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: TIDA-01066, CC1310

Tool/software: TI-RTOS

Dear Sirs,

I'm trying to compile the cc1310 TIDA-01066 Firmware with the latest CCSv7, but as the recent TI-RTOS is 2.20 I get a build error:

Product 'com.ti.rtsc.TIRTOSCC13XX_CC26XX' v2.18.1.04 is not currently installed and no compatible version is available. Please install this product or a compatible version.   

I tried to locate v2.18.1.04 version of TI-RTOS, but in the download page the closest I find is 2.18.0.3.

Anyway, I installed and tried, but no luck.

Can you suggest how to get access to v2.18.1.04?

Thanks in advance

Nik

  • - To test the TI design as is, use the hex files included in the distribution
    - The TIDA-01066 firmware is based on a old TI-RTOS and 15.4 stack version. A lot has changed both in TI-RTOS and the stack since the version this was based on so if you intend to use the code as a starting point for your own application I would recommend you to download the newest SDK (dev.ti.com/.../, the 15.4 stack is a part of the SDK) and add the code that is required for the sensors in this TI design to the example code that could be found in the SDK.
  • Hi TER,

    Thank you for the prompt answer! I don't mind starting from some of the existing examples, my concern is if we can achieve same power consumption as TIDA-01066 w/o too much efforts to optimize them? Can you suggest as well the best starting point - I see several examples to be used as potential starting point:

    • SimpleLink SDK / Examples / Development Tools / CC1310 LaunchPad / TI Drivers / rfXxxxx
    • SimpleLink SDK / Examples / Development Tools / CC1310 LaunchPad / EasyLink /
    • SimpleLink SDK / Examples / Development Tools / CC1310 LaunchPad / TI802.15.4 Stack

    There is also different approach described in the tutorial in SimpleLink Academy / Labs / TI 15.4 Stack / Using TI 15.4 stack and portable...

    Again, my concern is the power consumption, I believe I'll be able to optimize any of this examples to reach the results similar to TIDA-01066, but I have to accomplish this with reasonable efforts.

    Thanks in advance

    Nik

  • The 3 example groups you are listing here are examples for different abstraction for the radio. The TI drivers shows how to use the driver directly, EasyLink adds a small abstraction layer making the radio a bit easier to use and the 15.4 shows how to use the stack.

    You can achieve the same power consumption starting from all of them given that you wake up at the same interval. Since the TI design uses the stack it would probably be easiest to start from the 15.4 examples.

    It also depend a bit what you want to do in the end. Do you want to use the stack (and be limited to 50 kbps or LRM) or do you want more flexibility with the cost of writing more software yourself?
  • Hi TER,
    the application I'm working on is simple battery powered temperature measuring node, nothing fancy or complex. One measurement per few minutes shall be fine. May ask you to elaborate on "Since the TI design uses the stack it would probably be easiest to start from the 15.4 examples". You mentioned that EasyLink adds only just small abstraction layer. The way I read it is that the performance shall be the same, but easier to use. I assume I miss some details, can you suggest?
    Regards
    Nik
  • Both EasyLink and the stack is easy to use but the later would require a bit more reading.

    Again it depends what type of system you want to implement. If you just are going to make a very simple system with one or two node the stack could be overkill. For this Easylink is probably the best. If you on the other hand need a full star network with multiple nodes, use the stack.
  • Dear TER,

    Your answer just increased my confusion. To my understanding, the wrapper layer (like EasyLink) shall not limit the functionality of the underlying stack. Where this 1-2 sensors limition comes from? Actually I plan for about 15 nodes.

    Regards

    Nik

  • Easylink is a wrapper layer over the basic RF commands. So if you use Easylink you have to add code to handle 15 nodes at the same time (basically adding stack functionality). Therefore with your use case using the 15.4 stack would require less work.
  • Thanks a lot for the prompt support! Will start the project as you recommended.

    Regards

    Nik