When Host and NCP communication going on and there was I seen issue like that : ezspErrorHandler 0x39(EZSP_ERROR_NO_RESPONSE) then NCP rebooted.so there is something wrong behavior in NCP or Host.Can you tell me why this things happen?
#EM357,#UART,#NCP_HOST
Thank you in advance your support.
Regards,
Kanji Viroja
Bluetooth Low Energy
Discussion Forums
Bluetooth Classic
Answered
Answered
Hello Kanji,
This ERROR usually means that the host lost contact with the NCP. A few of questions:
1. What stack version are you using?
2. What was the Host and NCP doing before the reset?
3. Is this ERROR easily reproducible?
-Konrad
0
Hi Konrad,
Please find below answer of your question :
1. What stack version are you using?
A. ncp and host Used 5.3
2. What was the Host and NCP doing before the reset?
A. host and ncp both are communicating via uart and host sending command and getting response from ncp before the reset.
3. Is this ERROR easily reproducible?
A.Yes,this error frequency came and ncp reset.
Thank you.
BR,
Kanji.
0
Hello Kanji,
1. Have you run the UART tests in Application Note AN706?
2. What commands was the host sending to the NCP?
3. Have you run a packet capture from the NCP?
Thanks,
Konrad
0
Hi Konrad,
Yes, UART test working fine.but this issue have not fixed when it will be generate.once I have sent clear Zigbee Event Log command then after I am getting this error.so is there any problem with command or relevant to uart connection.I think this EZSP_ERROR_NO_RESPONSE error showing ncp failed to give respond of that command.so that host set flag for restart ncp and that problem happening.
Thanks,
Best regards,
Kanji.
0
Hello Kanji,
This error would not be triggered on a specific EZSP command. We believe this is related to instability of the UART on your hardware.The EZSP_ERROR_NO_RESPONSE pops up because of an issue with the underlying UART connection.
Regards,
Konrad
Correct Answer
0
Hi Konrad,
I have tested UART-1/2/3 test cases.but there was I have not seen any issue.so How can I say that there was something wrong in UART connection between HOST-NCP.if is there specific issue in UART then definitely that issue will be come on startup point.but here,scenario some how different.when we are frequently send command its looks like over-hitting of command to host that time most probably I got this error.
so in this concern can you help me?
kpszupin wrote:
Hello Kanji,
This error would not be triggered on a specific EZSP command. We believe this is related to instability of the UART on your hardware.The EZSP_ERROR_NO_RESPONSE pops up because of an issue with the underlying UART connection.
Regards,
Konrad
0
Just to wrap up this thread: The problem (after some debugging outside of this thread via an escalated support portal case) ended up being specific to the host/NCP implementation (as Konrad postulated earlier). The NCP had custom code added to it to do a POST (power-on self-test), and this long delay at startup was frustrating the host-side ASH drivers.
ERROR%3A EZSP_ERROR_NO_RESPONSE
Hi,
When Host and NCP communication going on and there was I seen issue like that : ezspErrorHandler 0x39(EZSP_ERROR_NO_RESPONSE) then NCP rebooted.so there is something wrong behavior in NCP or Host.Can you tell me why this things happen?
#EM357,#UART,#NCP_HOST
Thank you in advance your support.
Regards,
Kanji Viroja
Hello Kanji,
This ERROR usually means that the host lost contact with the NCP. A few of questions:
1. What stack version are you using?
2. What was the Host and NCP doing before the reset?
3. Is this ERROR easily reproducible?
-Konrad
Hi Konrad,
Please find below answer of your question :
1. What stack version are you using?
A. ncp and host Used 5.3
2. What was the Host and NCP doing before the reset?
A. host and ncp both are communicating via uart and host sending command and getting response from ncp before the reset.
3. Is this ERROR easily reproducible?
A.Yes,this error frequency came and ncp reset.
Thank you.
BR,
Kanji.
Hello Kanji,
1. Have you run the UART tests in Application Note AN706?
2. What commands was the host sending to the NCP?
3. Have you run a packet capture from the NCP?
Thanks,
Konrad
Hi Konrad,
Yes, UART test working fine.but this issue have not fixed when it will be generate.once I have sent clear Zigbee Event Log command then after I am getting this error.so is there any problem with command or relevant to uart connection.I think this EZSP_ERROR_NO_RESPONSE error showing ncp failed to give respond of that command.so that host set flag for restart ncp and that problem happening.
Thanks,
Best regards,
Kanji.
Hello Kanji,
This error would not be triggered on a specific EZSP command. We believe this is related to instability of the UART on your hardware.The EZSP_ERROR_NO_RESPONSE pops up because of an issue with the underlying UART connection.
Regards,
Konrad
Hi Konrad,
I have tested UART-1/2/3 test cases.but there was I have not seen any issue.so How can I say that there was something wrong in UART connection between HOST-NCP.if is there specific issue in UART then definitely that issue will be come on startup point.but here,scenario some how different.when we are frequently send command its looks like over-hitting of command to host that time most probably I got this error.
so in this concern can you help me?
Just to wrap up this thread: The problem (after some debugging outside of this thread via an escalated support portal case) ended up being specific to the host/NCP implementation (as Konrad postulated earlier). The NCP had custom code added to it to do a POST (power-on self-test), and this long delay at startup was frustrating the host-side ASH drivers.