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: Is there any standards defined for the endpoints by TI or Zigbee Alliance

Part Number: CC1352P


Hello Community,

I am working on the CC1352P ZNP device with the ZNP Host Framework Application & Zigbee Linux Gateway 3.0 Application.

I would like to know about the endpoint definition standards.

As the TI mentioned the following endpoints in gateway_config.tlg.

//************ Endpoint definitions *****************//

// Application endpoints IDs may be in the range 1-254, except:
// endpoint IDs 0 is reserved by the system (ZDO)
// endpoint ID 14 is reserved as well (OtaMgr)
// endpoint ID 244 is reserved for green power
// the same endpointdef may be used by more than one endpoint
// endpoint { ID, EndpointDef, AttrDef }
endpoint { 0x02, CombinedInterfaceEpDef, CombinedInterfaceAttrList }
endpoint { GreenPowerEndpoint, GPProxyBasicEpDef, GPProxyBasicAttrList }

I would like to know the following things...

  1. Is it compulsory to use the same endpoint as mentioned by the TI?

  2. If Yes, What conflicts may generate if we modify these endpoints?

  3. What are the Zigbee Alliance standards for the endpoint definition?

Regards,

Shiv Patil.

  • Basically, you shouldn't use endpoint 0 which is reserved for ZDO. For OTA and GP endpoint, I suggest you to follow the instruction or it might cause compatibility issue. For other endpoint between 1 and 254, I see no constrains.

  • Hi Shiv,

    The ZDO is always 0x00 as defined in the Zigbee Specification.  242 (0xF2) is the endpoint value also reserved for Green Power applications by the Zigbee Spec, 244 is actually a typo.  The OTA endpoint is recommended to be 20 (0x14) as this is the value recognized by the TI OtaServer Windows application, however you can change this if using a different server.  All other endpoint values are available for your use.

    Regards,
    Ryan