Hi,
When our coordinator (ESP) sends out an initiate Key Establishment to a IPD that has already joined correctly the IPD responds with a Key Establishment default response instead of continuing with the Key Establishment.
We have tested with the TI examples using a Smart RF05 board as the co-ordinator and a EXP430F5438 board (running ZAP) as the IPD and we get the same incorrect default response as above.
If we Test with 2 Smart RF05 boards (one co-ordinator, one IPD ) we get the correct action and the Key Establishment proceeds correctly.
All firmware versions are using the sample apps supplied in 2.5.0.
Any ideas of what we are missing in the ZAP version?
We need this to pass SEP1.1 testing.
Is device end point is correctly mentioned in Initiation command for Key Establishment for IPD. Else you have to discover the end point for key establishment cluster before starting it.
--Varun
Yes it is correct. It works in the SmartRf05 setup but not the ZAP setup.
Also this issue was brought to our attention by our Testing Lab who have exactly the same issue with our product and we can reproduce it.
Hello Kiwi,
Can you verify the following, when creating the ZNP image did you use the live Certicom library and also had the following compile options when creating the ZNP image:
POWER_SAVINGZCL_KEY_ESTABLISHTC_LINKKEY_JOINTEST_CERT_DATASECURE=1
Also, when using the ZAP project you had -DSECURE=1 in the zap.cfg file and TC_LINKKEY_JOIN enabled.
I was able to create a setup with ZAP-ZNP (IPD) and CC2530 (ESP) with out of box sample SE applicaiton to have succesful Key Establishment procedure.
Let me know if this is able to help you. Thanks
Regards
Thankyou for your reply.
I think you may have missed that the initial CBKE process works fine and everything works perfectly.
It is when the ESP initiates another Key Establishment as per the SEP 1.1 Test Specification 075384r30 test case 15.30.
In this case it does not continue with the key establishment process but sends a Default response.
If needed I can send you a capture of this.
Thanks
Can you please provide us the sniffer capture of your observation. We are trying to understand the issue and that will be helpful in providing the solution.
Thanks Carlo.
Hi Carlo,
Below is a sniffer screenshot.
The highlighted line shoes the incorrect response.
I have also emailed you the original file.
Attached this time..
From the log, line 303, I see that the Initiate Key Establishment Request is sent to endpoint 0x0C while the KeyEstablishment cluster on your device is supported on endpoint 0x0A, I think this as the first time the end-device initiates the Key-Establishment procedure it does it from the Endpoint 0x0A. When initiating the Key Establishment for the second time from the coordinator can I ask you to start by sending the request to endpoint 0x0A or you can start by sending a match descriptor request for Key Establishment cluster from the coordinator or employ some code to determine on which end point is the key establishment supported on the remote device and then start the key establishment procedure. Please let me know if you have any question and let me know if this helps you. Thanks
Thankyou you are correct.
What we didn't realise ( and our test house didn't notice either) was when using ZAP the Key Establishment is on a different endpoint from the other clusters.
Thanks again.