CCS/CC1350STK: CC1350 SensorTag Development

You can either use the CC-DEVPACK-DEBUG or the launchpad to debug the sensortag.

Yes, you can deploy custom code on the sensor tag. The launchpad is in many cases preferred for development since all IOs are easily accessible and it's easy to measure chip power consumption in the lowest power modes. On the sensor tag you will also get a contribution from the sensors.

Can you verify that those 3 components are enough to setup a point to point sensor data transfer?

Also, can you point me to example code for reading the sensors? I found a few examples, but they do not appear to be comprehensive.

Thanks

Yes. You only need the sensor tag and the LP to make a point to point transfer.

For the sensors that uses a I2C interface, the following example may be used as a starting point. Some middleware functions are also available under <sdk install path>\source\ti\mw\sensortag

I looked through that source folder and see code for that 9250 and other sensors. Forgive me, but I just got burned on the wifisensortag and the MSP-EXP430F5529LP by "assuming" there would be functional code examples for either of them. Looking through the \source\ti\mw\ folder I see lots of references to the CC26XX. Everything I have experienced with the TI example code up to this point tells me that this code will not run on the CC1350. I hope I'm wrong, but "fool me once, fool me twice..." hopefully you appreciate my over abundance of skepticism. I've already spent $150 on useless boards, I'd like to be absolutely sure before I throw another $75 down the drain to find out this code is not compatible with the CC1350.

The SensorTagTest source file does not appear to be part of any formal example code, so I tried creating a new blank project. I should note that I find CCS incredibly un-intuitive, so this maybe as much a CCS question as a CC1350 question.

First off, creating an empty project with main.c results in the following compiler/linker error
undefined first referenced
symbol in file
--------- ----------------
ResetISR

error #10234-D: unresolved symbols remain
warning #10062-D: entry-point symbol "ResetISR" undefined
error #10010: errors encountered during linking; "testCC1350.out" not built



With the MSP430 blank project, at least it compiled right off the bat.

How do I get this \source\ti\mw\sensortag code into a project that I can compile for the sensortag 1350?

Did you try to start from one of the examples here?

dev.ti.com/.../

For sensors, start with dev.ti.com/.../README.html and modify this to what you need.

That i2ctmp007 project seems to have compiled for the CC1350. I'm not sure why an empty project doesn't compile, but I can work from this example projec. So it appears the CC26xx source files are "mostly" compatible with the CC1350. That's a pleasant surprise coming from the MSP430, where practically nothing is compatible from one processor to another.

It also looks like there's no source for the out-of-the-box demo for the sensortag. Is this the case, or have I just not found it yet? (thanks)

The CC13x0 and CC26x0 are the same platform and more or less all sub modules are equal (except for the radio core) Hence a lot of the drivers are named CC26xx but used also on CC13xx.

Ok, I finally received the sensortag and the launchpad. It seems like a good place to start is with the rfEasyLinkRx_CC1350_LAUNCHXL_tirtos_ccs and rfEasyLinkTx_CC1350STK_tirtos_ccs examples. When I try and compile, I get this:

Referenced project 'tirtos_builds_CC1350_LAUNCHXL_release_ccs' does not exist in the workspace. Project 'rfEasyLinkRx_CC1350_LAUNCHXL_tirtos_ccs' may not build as expected.

Obviously I need to add that, but I'm not sure how to go about adding that, and from where?

When you import a project from the SDK you should get both the example and the TI-RTOS build.

How did you import the project and which SDK version do you use? Try to start with a clean workspace.