• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 357 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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-CC1352R1: TI15.4 Stack "Adding a new sensor" tutorial in simplelink Academy, can't find "Ssf_genericCMD()"

ddb
Intellectual 464 points
Part Number: LAUNCHXL-CC1352R1


Hi everyone,

I recently started working with the CC1352R1 launchpad, more specifically with TI15.4 stack. I've been following the tutorials in simplelink Academy (5.10.00.00) and I found a problem or maybe I'm missing something. 

In "TI 15.4 Stack - Adding a new sensor" (https://dev.ti.com/tirex/explore/node?devtools=LAUNCHXL-CC1352R1&node=AHs0wbxuPRpRbJcHasQeYw__pTTHBmu__LATEST) there is an issue in task 2 -> edit sensor.c -> step 5, where a new case statement is inserted in dataIndCB for the new generic sensor that was added. However in this new snippet there is this line "cmdBytes[1] = Ssf_genericCMD();" which eventually creates an error when building, because this function Ssf_genericCMD() doesn't exist and it was not created either during the turorial.

What am I missing here? Did the tutorial fail to mention the creation for that? If so, what is it expected to be placed inside that function, what is it supposed to do?

Thanks  

  • 0
    TI__Guru* 86581 points

    Hi

    someone will be assigned to follow up your questions.

    BR

    Siri

  • +1
    TI__Mastermind 20412 points

    Hi Joao,

    This seems to be an oversight. It shall be fixed. 
    Meanwhile, I suggest you to just comment the out line "cmdBytes[1] = Ssf_genericCMD();". The project builds successfully and the rest of the tutorial can be followed as is, and the expected output can be seen. 

    BR
    Sid

  • 0 in reply to Sid
    Intellectual 464 points

    Yes that's what I did and it worked.

    Nonetheless I was wondering what would that function do.. Because the new generic sensor is added to the normal report message packet, however the turorial also goes through the creation of the new generic sensor request and response message, which aren't used at all in the example, so I was curious how would that work, and for what purpose. So it's a pitty that content is missing from the turorial.

    Anyways, thank you.

    Joao