• State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 351 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CC1352P: Unable to get the Attribute reports on ZNP-Host-Framework Application using the CC1352 ZNP module

shiv patil
Genius 3356 points
Part Number: CC1352P
Other Parts Discussed in Thread: CC2538

Hello Community,

I am working on the CC1352P-2 Lauch Pad as ZNP Device with ZNP-Host-Framework Application.

So for,

I am able to join the device to the network & able to make achuation over it. 

Now I wold like to get the actuation reports generated from the device.

For that I have enabled all callbacks using the MT_ZDO_MSG_CB_REGISTER = 0xFFFF

After that I am manual turning on & off the ED to generate the actuation reports.

I am able to see the reports on Snffer logs.
But there is no message printed on ZNP-Host-Framework Application side.

Also I am getting the ZDO_SRC_RTG_IND which is sent from the ED.

mtZdoSrcRtgIndCb
DstAddr: 0xFE66
RelayCount: 0x00

 

Note : getting same problem with CC2538 default znp code on ZNP-Host-Framework Application &  able get reports using both CC1352 & CC2538 on Zigbee Linux Gateway Application.

 

Will you please help me to know,

1. what should I do to get the reprots sent from the ED.

2. What are the required configuration for ZNP devicce.

Regards,

Shiv Patil.

  • 0
    TI__Guru**** 213107 points

    Hi shiv,

    shiv patil said:
    For that I have enabled all callbacks using the MT_ZDO_MSG_CB_REGISTER = 0xFFFF

    That isn't how the ZNP compile flags work.  They are further described in Section 1.2 of the Monitor and Test API but you can also reference the ZNP project code.  You need to enable the MT_AF_CB_FUNC.  Once again, know that ZNP Host Framework remains untested with Zigbee 3.0 Specification ZNP solutions.

    Regards,
    Ryan