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.

Handling request for TC Link Key on Join?

Other Parts Discussed in Thread: CC2530

Hi,

I'm having some problems getting the CC2530 configured for the security model I need. Can anyone help?

 

I have some existing ZigBee End Devices which I'd like to use with a CC2530 acting as a Coordinator. If possible, I do not wish to change the firmware in the end devices to use a different security model.

On joining, the devices expect to receive the NWK key in the clear. This is working fine. However, the devices then request the trust center link key from the coordinator and never receive a response.

The request they make is APS Request Key which I can see defined in APSMEDE.h as APSME_CMD_REQUEST_KEY.

Is there an option I can enable to respond to the request?

Or, do I need to add code myself to ZStack to do it? If so, where?

 

Thanks.

 

  • Hi Toby,

    I know in the ZigBee core spec there is a primitive to request the link key, but it appears you are not using the pre-configured trust center link key method of joining?
    This is the mode where the network key is not sent in the clear. The APS transport key message from the coordinator is encrypted with the pre-configured trust center link key (which is defined in nwk_globals.c). To enable this method of joining, the devices should be enabled with the TC_LINKKEY_JOIN compile option.

    What do you request the link key for, to encrypt APS packets?

  • Hi

         This is the mode where the network key is not sent in the clear. The APS transport key message from the coordinator is encrypted with the pre-configured trust center link key (which is defined in nwk_globals.c).

         how can i know when will need to set this compile option and when don't need to ?