SENSOR-CONTROLLER-STUDIO: Error during patch assembly

Part Number: SENSOR-CONTROLLER-STUDIO
Other Parts Discussed in Thread: SIMPLELINK-CC13X2-26X2-SDK

Hello Guys,

Good day.

Our customer is working on a solution that uses CC2652 Sensor Controller core. When he try to generate the code for his tasks he get an undocumented error (please see attached PNG image) both in Sensor Controller Studio GUI and Code Composer Stuidio CLI:

Note that all the tasks are compiled successfully, so the APIs should be used correctly, however during the PATCH assembly something went wrong.

If you want I could request for the customer to provide his  Sensor Controller Studio project.

Thanks in advance.

Art

  • Hello Art,

    Has the customer referenced the Sensor Controller SimpleLink Academy Labs and Sensor Controller Studio documentation?  What addition to the project settings causes the error to occur?  Can you please clarify what is meant by "PATCH assembly"?

    Regards,
    Ryan

  • Hello Ryan,

    The customer followed the documentation provided both inside the SCS IDE and the ones referenced on the launchpad page/forum.

    The issue appeared when he added the third task ("pressure" in his project). With "PATCH assembly" (he meant RAM) He is  referring the last step that perform the SCS compiler before aborting due to errors. In the screenshot I previously attached, highlighted are the errors he is getting. Those error are listed under "Assembling RAM image", after all the tasks were compiled.

    Thanks and regards,

    Art

  • Hello Art,

    Please have the customer provide their project or fully explain their event3 setup.  Perhaps they should try removing the task completely and re-initialize it inside the Sensor Controller Studio.

    Regards,
    Ryan

  • Hello Ryan,

    Below are the response from the customer in verbatim:

    "I removed the "pressure" task in the original project and started again. The problem arise when I add the "GPIO Event Trigger", even with an empty task. I attach the same project I originally enclosed in this ticket, with the "pressure" task configured with a digital input (dummy) and the "GPIO Event Trigger" enabled, plus a setup/teardown of such trigger. If you try to compile such project in scs you will notice the same problem as before.

    A brief description of the project: the sensor controller has 3 tasks that share the I2C bus. Each task is in charge to read and store in RAM some samples from various environment sensor."

    He tried a new, empty project with 2 tasks which configure a digital input and a GPIO trigger each (see attached). The same problem occurs. Is this a bug in the compiler?

    poc_gpio_trigger.zip

    Thanks and regards,

    Art

  • I am not seeing issues with the output of the project attached using Sensor Controller Studio v2.8, can they confirm this is the version they are using?  What SIMPLELINK-CC13X2-26X2-SDK version have they downloaded?

    Regards,
    Ryan

  • Hello Ryan,

    It now builds correctly on the customers system. He made a mistake before. He has multiple project opened in SCS but there is only one "Code Generator" Tab shared across the projects.

    Just a follow-up question though, He is currently running SCS Version 2.8.0.170 and got 2 different SDKs installed: "simplelink_cc13x2_26x2_sdk_4_30_00_54" and "simplelink_cc13x2_26x2_sdk_5_10_00_48". The former is the one he used from project day one, the latter was installed recently. How can he choose which SDK to use with SCS? He remember a form that allow you to pick one by specifying the paths, but he was not able to find it. Any suggestion?

    Thanks and regards,

    Art

  • Hello Art,

    I'm glad to hear that the user's issue is resolved.  Please refer to the Getting Started Guide and Help Documentation for Revision History and Update Service.  SCS v2.8.0 does not inherently support the v5.10 SDK (up to v4.40) but drivers generated in SCS will normally be compatible with future SDK releases because it depends only on basic SDK functionality.

    Regards,
    Ryan

  • Hello Ryan,

    Sorry for the misunderstanding. Sadly, on the original proeject, he still have the same issue. Can you try to compile the project inside "speleologger.zip" on your side?

    speleologger.zip

    Thanks and regards,

    Art

  • Hello Art,

    I am able to observe the issue with their project.  The issue disappears if I delete any of the task event handling triggers (along with the relevant code to resolve build errors) but the chip should be able to support 3 event triggers, one for each task, so I am asking the SCS Development Team whether they know anything more about this behavior.

    Regards,
    Ryan

  • Hi Art,

    This problem has been identified as a bug which the development team is currently investigating, meanwhile the customer can do one of the following as a workaround:

    • Search for the string "0,0,2,3" in the scp file and replace it with "0,1,2,3", then reopen the project
    • Follow this procedure:
      • Go to the task panel for the "temp" task
      • Change "Simultaneous event trigger count" to 2
      • Change " Event index 1 shall trigger" from "Event Handler A Code" to "Event Handler B Code"
      • Change "Simultaneous event trigger count" back to 1

    Thanks for reporting this behavior and having patience as we continue to address the cause.

    Regards,
    Ryan