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.

CCS/LAUNCHXL-CC1352R1: Easylink Subghz conflict with ZStack [Attempt to implement DMM of Zigbee and Easylink Subghz]

Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: SYSCONFIG

Tool/software: Code Composer Studio

Hi Everyone,

I am having an issue integrating the DMM with ZStack and Easylink Subghz.

At first I tried including the Easylink Libaries in the Zstack genericapp example and tried to compile it, but then I got an error saying that I got variable conflicts

In my understanding they are both using the ti_radio_config.c/h which causes the conflict.

Is there a way to integrate ZStack and Easylink together for DMM? Our requirements doesn't need to make ZStack and Subghz work concurrently.

Thank you and Regards,

Jonathan

  • Hi Jonathan,

    There is currently no such examples available, but there is nothing in the DMM that would prevent you from doing this. You would however need to sort out the joining of the projects as a first step.

    I would suggest you start by looking in the build log to see which other file it is conflicting with.

  • Hi M-W,

    Thank you for your response. As I have attached here are the variables that got conflict.

    Would it be okay to rename this variables? Will it still work the same for ZStack or Easylink library?

  • Hi Jonathan,

    Those errors does not say much of which files are conflicting. We could assume the Zstack uses these "default" structure names already. You could possibly change the Easylink version but you would also need to change all Easylink references to the structures to match the new name. An alternative is to not use Easylink but work directly with the RF driver, you could then choose to export settings with another name prefix.

  • DMM may be unnecessary since concurrency is not required.  Can you determine the stack you would like to use on device startup or will you be switching between stacks during runtime?  Which SDK version are you using?  Through previous experience I think that you will need to disable SysConfig and create specific variable names for each stack to avoid overlap.  

    Regards,
    Ryan

  • Hi M-W

    I have resolved the variable conflicts by adding a prefix in those variables. EasyLink made it easy via sysconfig.

    Hi Ryan,

    I have been thinking too that DMM is not required. But I still have no Idea on how can I achieve the task.

    On Zigbee I have been using Zigbee End Device and I am running SDK version 3.40.00.02.

    On startup I only need the zigbee to reconnect to coordinator. or if not, find a network to connect to.

    And after the zigbee connection has been secured. The coordinator may send command to my end device like transmit a command to other subghz module using Easylink.

    Would it be possible to done without DMM?

  • Hi Jonathan,

    If you plan on maintaining a Zigbee network while also sending EasyLink Sub-GHz commands then DMM will be required.

    Regards,
    Ryan

  • Hi Ryan,


    But what if I don't need to maintain zigbee network while doing Sub-Ghz Commands? Let's say I will drop the zigbee network for 1 second to do a sub-ghz command.

    Is there a way to abort zigbee connection for a brief time?

  • Hi Jonathan,

    This is theoretically possible since you are using a sleepy ZED but this would require the use of RF commands to switch to the sub-1 GHz MAC/PHY, there are no TI examples which demonstrate this that I am aware of. 

    Regards,
    Ryan