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.
Part Number: CC2538
Hello E2E community,
I am working on the znp-host-framework application using the CC2538 znp device interfaced with the UART protocol.
I am trying to send the MT_ZDO_NODE_DESC_REQ, but I am not getting successfull response from the znp device.
Source addr (ZNP) : 0x0000
Destination addr : 0xB599
I am sending you the logs of the znp host framework applocation will help you to undrstand the problem.
NOTE : I am using the default znp-host-framwork application with out doing any modifications.
Command: ZDO_NODE_DESC_REQEnter DstAddr: (2B)0x0000Enter NwkAddrOfInterest: (2B)0xB599rpcSendFrame: Blocking on RPC semrpcSendFrame: Sending RPCrpcTransportWrite : len = 9writing 8 bytes (offset = 0, remain = 9)writing 1 bytes (offset = 8, remain = 1)SOC OUT --> 9 Bytes: SOF:FE, Len:04, CMD0:25, CMD1:02, Payload:00:00:99:B5, FCS:0FrpcSendFrame: waiting for SRSP rpcTransportRead: read 4 bytesSOC IN <-- 6 Bytes: SOF:FE, Len:01, CMD0:FE, CMD1:01, Payload:65, FCS:02rpcProcess: fcs error 2:9brpcTransportRead: read 1 bytesrpcProcess: No valid Start Of Frame found [6d:1]rpcSendFrame: SRSP Error - CMD0: 0x25 CMD1: 0x02rpcWaitMqClientMsg: timeout=1000rpcWaitMqClientMsg: waiting on queue 1000:1573208190:0rpcWaitMqClientMsg: processing MTmtProcess: CMD0:4f, CMD1:80, not handled
rpcWaitMqClientMsg: timeout=1000rpcWaitMqClientMsg: waiting on queue 1000:1573208190:0rpcWaitMqClientMsg: processing MTmtProcess: CMD0:4f, CMD1:80, not handled
rpcWaitMqClientMsg: timeout=1000rpcWaitMqClientMsg: waiting on queue 1000:1573208190:0rpcWaitMqClientMsg: Timed out [-1] - Connection timed out
Will you please help me to know why is this happening?...
Is there any configurations need when we initialize the znp device?.
What are you using as host to the ZNP?
Try debugging the ZNP and see if it actually receives the command (see function MT_ZdoCommandProcessing).
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
I also suggest you to use sniffer to check what happens over the air.
If my post answers your question, please click on "This Resolved my issue" button to benefit others who have the same issue.
How to use two UARTs in CC26x2 and CC13x2
How to add you own custom board files to CC26xx BLE stack
SwitchBot DIY using LPSTK-CC1352R , SG90 servo motor, and ProjectZero to away from COVID-19.
How to use two endpoints in SIMPLELINK-CC13X2-26X2-SDK Z-Stack.
CC13xx TRX WOR project.
How to create a periodic event to toggle BLE Advertising in CC26xx simple_peripheral example
How to use indication in simple_peripheral example and use Btool to enable indication
How to check APS ack in TI Z-Stack
How to detect button hold in CC26x2, CC13x0, CC13x2 SDK.
660 Zigbee devices in the same Zigbee network!
In reply to YiKai Chen:
Hello YiKai Chen,
In my case the command will not able to send over the network. there is no activity noticed on sniffer logs.
I am reffering following document.
Refer the ZDO_NODE_DESC_REQ in section 188.8.131.52
Am I doing any thng wrong while sending the following command over uart.SOC OUT --> 9 Bytes: SOF:FE, Len:04, CMD0:25, CMD1:02, Payload:00:00:99:B5, FCS:0F
In reply to Toby Pan:
hello Toby Pan,
In your question, What are you using as host to the ZNP?
I am not able to understand what do you means to reffer the host?...
Will you ask more specific so I am able to answer you questions.
In reply to shiv patil:
Make sure you use correct DstAddr and NWKAddrOfInterest.
Yes, I have verified the both addr values. I have also mentioned them in my question.
In general, NWKAddrOfInterest should be the same as DstAddr.
If you look at the permit joining request on the Zigbee Gateway Application for the same device. you will be able to see the
the NWKAddrOfInterest should be the addr of device which we wants to add in to the network.
Even in Z-Stack Monitor and Test API document its mentioned clearly
Attribute Length (byte) DescriptionDstAddr 2 Specifies NWK address of the device generating the inquiry.NWKAddrOfInterest 2 Specifies NWK address of the destination device being queried.
refer following image you will be aple to understand this.
Since I can see node description request is sent in your sniffer log, why do you said “ the command will not able to send over the network. there is no activity noticed on sniffer logs.”?
hello YiKai Chen,
The above sniffer logs are reffering to the Permit Join Request using the Zigbee Gateway Application.
Not for the ZNP Host Framwork application.
I have post this becouse you said..
Using ZNP Host Framework I am not able to get successfull response for the MT_ZDO_NODE_DESC_REQ.
If you look over the sniffer logs you will be able to understand that,
NWKAddrOfInterest is the addr of the device which node information is requested.DstAddr is the addr who is requesting the information.
If that request is successfully run over the Zigbee Gateway Application then why it is not working on the ZNP Host Framework Application?...
*** Also I need to know that, Is ZNP Host framework application is tested thoroughly or not & it is deployable for production??????......
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.