The latest protocol stack based on TI, core lib buggy I also don't change, only for people TI pointed out that to let them to change, but I don't have to write good code where I can change is good, and a lot of application layer, the function of the original protocol stack to support is too little, it silabs have all have no, I had to do it yourself,

TI protocol stack some, silabs also have no, especially some network interface, can optimize the network,

Based on the TI CC2652, SDK version 3.40

https://github.com/zigbee-luo/LuoYiming_zstack_external.git



New feature:

1 in AF. J h, a new parameter "afCnfCB" and "cnfParam" has been added to the message "AF_DATA_CONFIRM_MSG", new feature "AF_DataRequestExt" has replaced "AF_DataRequest", this change can also affect the will perform "AF_DataRequest ZDP and ZCL" and "zstacktask",

Refer to figure 2, in the ZDP and ZCL, "ZDP_SetSendConfirm" and "zcl_SetSendExtParam" can set the "AF_DATA_CONFIRM_MSG" "afCnfCB" and "cnfParam", especially in the ZDP afCnfCB in Zstack - task execution, calls the ZDP - Command - Request function Application - task will send "zstackmsg_CmdIDs_AF_DATA_CONFIRM_IND", receives the ZDP layer

3, in ZCL, support the manufacturer code, a new attribute control bits "ACCESS_MANU_ATTR can tag manufacturer specific attributes," and "CMD_FLAG_MANUCODE" can tag manufacturer specific commands,

4, BDB_REPORTING support specific to the manufacturer's and client attribute,

5, the correct Link Key management, "ZDSecMgrDeviceJoin" is the only access to filter the correct connector, TC directly linked to the TC and join path through a router, only after the "ZDSecMgrDeviceJoin" return "ZSuccess" TC will generate the APS - Link - the Key, therefore, to use "BDB_TC_LK_EXCH_PROCESS_JOINING" call "bdbGCB_TCLinkKeyExchangeProcess", the node is the first time to join, and "Rejoin" and "TC - Rejoin" different,