• State TI Thinks Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 2 answers
  • Subscribers 57 subscribers
  • Views 603 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

every versions of Z-stack not support Diagnostics cluster correctly.

Aries Lord
Genius 5390 points

Other Parts Discussed in Thread: Z-STACK

In z-stack, "Diagnostics" calls "zcl_registerReadWriteCB" to register the function “zclDiagnostic_ReadWriteAttrCB” to read or write Diagnostics cluster 's Attribute. But in zcl.c, if the function has been register by “zcl_registerReadWriteCB”   is wanted be called, the Attribute should be register in attribute array by “zcl_registerAttrList” with "attr->dataPtr = NULL" .

  • 0
    TI__Guru**** 222447 points
    Hi Aries,

    I am currently having the Software Development Team investigate, please hold for further information.

    Regards,
    Ryan
  • 0
    Genius 3415 points
    Diagnostics cluster attributes are defined in DiagsStatsTable variable of type DiagStatistics_t. When there is a read attribute command for this cluster the stack resolves automatically that zclDiagnostic_ReadWriteAttrCB() needs to be used when is registered and this callback propose is to get the attribute pointers for the read attribute response.

    The reason why attr->dataPtr = NULL in zcl_registerAttrList is because the pointer for those attributes are not accessible for the application and this is the way that you tell that the pointer will be retrieved using a callback function.
  • 0 in reply to Jose Maria Alvarez
    Genius 5390 points
    Yes, as myunderstanding, if I want to use ZCL diagnostics, I should add the diagnostics cluster attributes into attribute-list of my application endpoint, to make zclDiagnostic_ReadWriteAttrCB valid.

    But, in BDB_Reporting, the diagnostics cluster attributes can't be accessed by reporting because the BDB_Reporting can't access attributes that can only be accessed by ReadWriteAttrCB.
  • 0
    Genius 5390 points

    In z-stack, the attribute value of ZCL diagnostic is accessed by zclDiagnostic_ReadWriteAttrCB which has been registered by zcl_registerReadWriteCB. But in z-stack 's BDB reporting and zcl_SendReportCmd,  the attribute value is accessed only by attr->dataPtr in Attribute-List except by pfnReadWirteCB. Only zcl_SendReadRsp can access correct attribute value by both attr->dataPtr and pfnReadWirteCB.

  • 0 in reply to Aries Lord
    Genius 3415 points

    Aries Lord,

    The issue is related to that. Let me test a couple of things and then generate a patch for this issue.

    Regards

  • 0 in reply to Aries Lord
    TI__Guru**** 222447 points
    Updates have been made to the Zigbee Known Issues and Proposed Fixes Wiki page:processors.wiki.ti.com/.../Zigbee_Known_Issues_and_Proposed_Fixes

    Please review and let us know if your issue has been fully resolved. I believe this also addresses your other E2E post: e2e.ti.com/.../704130

    Regards,
    Ryan