• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 4 answers
  • Subscribers 55 subscribers
  • Views 858 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.

LPSTK-CC1352R: LPSTK-CC1352R

Radwa Ahmed Abdelaziz
Prodigy 120 points
Part Number: LPSTK-CC1352R
Other Parts Discussed in Thread: CC1352R, HDC2010

Hello,

I am building a subGHZ network using LPSTK launchpad.
I need to apply the example of sensors and collector at this link http://dev.ti.com/tirex/explore/node?node=AFU6dryAU8NukjdRPy4T4Q__pTTHBmu__LATEST.

And I knew that all examples under CC1352R launchpad could be applied to LPSTK also but I couldn't do that.

I need to know how could I enable the code and configurations of LPSTK in the CC1352R examples (sensor, collector, etc.).
I tried in the sensor project where LPSTK code is commented under #ifdef LPSTK , I wrote #define LPSTK in the files to enable the code but it ended up giving errors while building like not finding the definitions of LPSTK functions.
So I copied the folder tat includes all header and source files of LPSTK from another project (DMM which was done for LPSTK specifically) into the sensor project but it ended up giving different errors like not finding definitions of LPSTK constants in LPSTK_sensor file.

So please tell me how to enable the projects done for CC1352R launchpad to work with LPSTK sensor tag launchpad also.

Thanks in advance.

  • 0
    TI__Mastermind 19135 points

    Hello Radwa,

    There is an out of the box code that works with the LPSTK.

    This can be found in the DMM sub folder.

    I recommend you follow this tutorial, you should be up and running in 10-15 minutes

    http://dev.ti.com/tirex/explore/node?node=AIKcHFRMmg0MRAyz1RySsg__pTTHBmu__LATEST

    Regards,

    AB

  • 0
    Guru 735455 points

    As I know, examples for CC1352R launchpad should be able to work on LPSTK sensor tag. What do you mean you couldn't do that?

  • 0 in reply to AB
    Prodigy 120 points

    Hello AB,

    Thanks a lot for your response it is totally appreciated.

    Actually I have checked this link and this project, I knew DMM is for LPSTK specifically.

    But I need to apply the examples of CC1352R like collector and sensor projects on LPSTK launchpad.
    I need to know how to enable these mentioned projects to work with LPSTK instead of CC1352R launchpad.


    Best Regards,

    Radwa.

  • 0 in reply to YiKai Chen
    Prodigy 120 points

    I mean when I tried to enable the code of LPSTK that was commented so that I could enable these projects to work with  LPSTK instead of CC1352R, it ended up giving me errors while building when I wrote #define LPSTK.

  • 0 in reply to Radwa Ahmed Abdelaziz
    TI__Mastermind 19135 points

    Radwa,

    1. To include the LPSTK define it is best to include it in define.opts. Which can be found in the application subfolder.
    2. Any example in CC1352 folder will work on the LPSTK, no need to add the define.
    3. If what you want is a purely collector/sensor example without DMM/BLE you have two options
      1. using the DMM examples and disable BLE. Making this a purely 15.4 example
      2. using the collector/sensor examples,
        1. define LPSTK (what you are trying to do) but also
        2. make sure you include/link the necessary onboard sensor drivers to work with the LPSTK sensor example. This includes all of the lpstk subfolder inside application folder and the header files included in those (all of these can be found in the source folder of the sdk)
        3. copy and paste the .syscfg file from the dmm project and remove any dmm/ble definitions. This will configure your pins appropriately.

  • 0 in reply to AB
    Prodigy 120 points

    Hello AB, 

    That is really very helpful, thanks  a lot.

    1) But in step 2 in the collector/sensor examples option; I included LPSTK folder that includes all header and source files, also included the sail folder as LPSK files depend on the files in sail.
        But I am having 1 error that I couldn't resolve.
       "unresolved symbol usleep, first referenced in <whole-program>"
        I found this symbol in one of the files in sail folder. (HDC2010.c) but couldn't find its definition. And only its prototype is written in unistd.h.


    2) And as per the second option of using DMM examples, should I do anything else beside removing BLE and DMM from .syscfg file ? so that I could wok with Ti15.4 only

  • 0 in reply to Radwa Ahmed Abdelaziz
    TI__Mastermind 19135 points

    Hello Radwa,

    Let's walk through option 1.

    follow these steps and let me know if they work.

    1. download latest sdk(4.10)
    2. import sensor project 
    3. go to application->defines
      1. open the opts file
      2. add -DLPSTK
    4. copy the lpstk folder from the dmm lpstk example 
    5. paste it in application folder of the sensor project
    6. copy the sail folder from the dmm lpstk example 
    7. paste it in sensor project
    8. right click on the sensor project and select project properties at the end
      1. in build->arm compiler->include settings add
        1. ${PROJECT_ROOT}/application/lpstk
    9. on sensor.c in sensor_init(), comment out this line :

      1. Ssf_PendAppSem();

    Let me know if this works, it worked for me.

  • 0 in reply to AB
    Prodigy 120 points

    Hello,

    Thanks a lot for your help, it is totally appreciated.

    I have followed these steps but I have these errors (shown in the attached image) when I build the project.

    Best Regards.

  • 0 in reply to Radwa Ahmed Abdelaziz
    TI__Mastermind 19135 points

    ok, this is expected...

    I forgot to mention to open the dmm .syscfg file as a text file (right click, open with, text editor) and copy and paste all the sensors definitions into the new syscfg file.

    These are new components that we have added to syscfg on the latest SDK and we are working on making them modifiable through the GUI. For now this is the quickest way to get it working