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.

Open Source Enhanced z-stack, based on zstack core 3.6.0

Part Number: CC2652R
Other Parts Discussed in Thread: Z-STACK

Tool/software: TI-RTOS

I have upload it in GitHub

 github.com/.../LuoYiming_zstack_external.git

1, In AF.h,new parameter "afCnfCB" and "cnfParam" was added into message "AF_DATA_CONFIRM_MSG". New function "AF_DataRequestExt" has been
instead of "AF_DataRequest". This change also effect in ZDP and ZCL and "zstacktask" who will execute "AF_DataRequest".

2,  In ZDP and ZCL, "ZDP_SetSendConfirm" and "zcl_SetSendExtParam" can set the "afCnfCB" and "cnfParam" of "AF_DATA_CONFIRM_MSG". Especially in ZDP, "afCnfCB" is executed in Zstack-task, and Application-task who has called ZDP-Command-Request function will receives "zstackmsg_CmdIDs_AF_DATA_CONFIRM_IND" sent by ZDP-layer.

3,  In ZCL, manufacturer code was supported. New attribute control bit "ACCESS_MANU_ATTR" can mark a manufacturer-specific attribute. And "CMD_FLAG_MANUCODE" can mark a manufacturer-specific command.

4,  BDB_REPORTING supports manufacturer-specific attribute and client-attribute.

5,  Correctly Link-Key management. "ZDSecMgrDeviceJoin" is the only access to filter the right joiner. Both directly linking to TC and joining path through Routers, the TC will generate its APS-Link-Key only after "ZDSecMgrDeviceJoin" returns "ZSuccess" . So the "bdbGCB_TCLinkKeyExchangeProcess" is called with "BDB_TC_LK_EXCH_PROCESS_JOINING", the node is first time joining, different from "Rejoin" and "TC-rejoin" .

  • TI  decide to opensource their firmware?

  • No, its my optimizing z-stack.

  • Hi Aries,

    As with your previous efforts and suggestions for Z-Stack, we appreciate your involvement.
    Also from previous discussions you've had on this forum, we internally discuss issues with the development team on what improvements we should add to Z-Stack. What we fix/add for Z-Stack in each SDK is documented in the Z-Stack release notes; please see that for the respective SDK.

    We extensively test Z-Stack before releasing SDKs. This testing is vital for verification of Zigbee functionality.
    We can only test updates made by our development team -- any edits other than this, I would consider a reference.

    Regards,
    Toby

  • Hi DzungPV,

    No, TI does not open source Z-Stack. The edits Aries has made are based on files which are available in the SDK.

    Regards,
    Toby

  • But it seems that TI's zigbee SW team works not hard. Though zstack is based on a good architecture.  The application is designed careless, so I suggest TI 's zigbee team to learn competitor 's zigbee-stack.