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" .
