CC2652P: Is endpoint 1 already used in Zigbee Linux Gateway demo?

Hi Ryan,

I checked with the customer and found that endpoint 1 is registered by the customer for sending user's data, and they also need to use the same endpoint for OTA because that is what other devices in their network use.

The custoemr followed the OTA example which registered the OTA endpoint (the endpoint was modified to be 1), and came across the "endpoint is already registered" error. I assume the endpoint should not be registered again, but I'm not sure about how to modify the example to use the same endpoint for data exchange and OTA. Would you please provide some help? Thanks.

BR,

Shuyang

You can add OTA cluster support to the existing endpoint 1.

I agree with YK that it should be possible to add the OTA cluster to your simple descriptor and modify the OTA files to reference this endpoint.  Another option is to use afDelete followed by afRegister if they need to revise the existing endpoint. 

Regards,
Ryan

Hi Ryan,

Would you please elaborate on how to add the OTA cluster to an existing endpoint? Thanks.

BR,

Shuyang

You can refer to zed_sw_ota example (search OTA_CLIENT_INTEGRATED) in latest simplelink_cc13xx_cc26xx_sdk_6_10_00_29.

Hi YK,

Do you have the steps using the Linux gateway demo? I'm having trouble to find the similar files in the gateway code, thanks.

BR,

Shuyang

Linux gateway would act as OTA server and your device is OTA client. Do you meant to integrate OTA cluster client side into the same application endpoint on device or OTA cluster server side into the same application endpoint on Linux Gateway? I don't have steps for Linux Gateway server side.

Hi Shuyang,

YK and I have already pointed to all of the resources currently available for using OTA on the Zigbee Linux gateway.

Regards,
Ryan

Hi Ryan,

I'm still not clear about how to integrate the OTA cluster to the server side on Linux gateway, can you point out which file should I look into? Thanks.

BR,

Shuyang

source\Projects\zstack\linux\otaserver, source\Projects\zstack\OTA\Source, and the User's/Developer's Guides.

Regards,
Ryan

Hi Ryan and YK,

I have one more question about the OTA: does the server and client have to use the same endpoint number during OTA? I'm asking because I just found the zed_sw_ota_client uses SAMPLESW_ENDPOINT=8 while zc_ota_server uses ZCL_OTA_ENDPOINT=20, and they seem to work OK.

If the server and client do not have to use the same endpoint, does that mean the Zigbee Linux gateway can perform the OTA to an OTA-enabled client no matter which endpoint it is using?

Is there any other limitation that the server and client must follow to establish the OTA communication?

BR,

Shuyang

server and client do not have to use the same endpoint. There’s no further limitation.

Hi Ryan,

For compatibility reason, the customer still need to use the same endpoint (endpoint 1) for the gateway server and OTA server. I'm met a problem when trying to merge the OTA cluster into the gateway server. Can you please help with that?

I did the following in the Linux gateway code:

1. Add endpoint 1 for OTA in gateway_config.tlg

//************ OTA Endpoint definitions *****************//
// Device IDs
#define DeviceID_ZCL_SE     0x0507

// Cluster IDs
#define OTAClusterId 0x0019

// endpointdefs define all fields for a simple descriptor (with the exception of the endpoint id)
//  uint16 profileid;
//  uint16 deviceid;
//  uint8  devicever;
//  input clusterlist;
//  output clusterlist;
endpointdef OTAEpDef { ha_profile, DeviceID_ZCL_SE , 0, OTAInputClusters, OTAOutputClusters }

// clusterlists include a list of clusters
// for some common ZigBee clusters there is an internal keyword defined, that can optionally be used instead of a number or an explicit #define. These keywords are: basic, identify, groups, scenes, onoff.
// - supporting as server (accepting client to server commands):
clusterlist OTAInputClusters { basic, identify, OTAClusterId }
// - supporting as clients (accepting server to client commands):
clusterlist OTAOutputClusters { basic }

// attribute definition include cluster id, attribute id, data type, and access control
//  uint16  attrid;         // in hex (0x050E) or decimal (0, 99, etc..)
//  uint8   datatype;       // Enther a keyword or any supported ZigBee type value. Supported keywords are: uint8, uint16, uint32, boolean, octetstr, charstr, enum8
//  uint8   accesscontrol;  // one of the keywords: rdonly, rdwr
// special case: if attribute datatype is charstring or octetstring, a length byte follows the type
//               { 99, charstring, 16, rdwr } // a character string up to 16 bytes
attr Basic_HwVersionAttr { basic, 0x0003, uint8, rdonly }

// attrlists are a collection of attributes
attrlist OTAAttrList { Basic_ZCLVersionAttr, Basic_HwVersionAttr, Basic_PowerSourceAttr, Basic_ClusterRevision, Identify_IdentifyTimeAttr, Identify_ClusterRevision }


//************ 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 { 0x04, CombinedInterfaceEpDef, CombinedInterfaceAttrList }
endpoint { GreenPowerEndpoint, GPProxyBasicEpDef, GPProxyBasicAttrList }
endpoint { 0x01, OTAEpDef, OTAAttrList }

2. Comment out the code for OTA endpoint registration in source/Projects/zstack/linux/otaserver/zcl_otaserver_lnx.c -> appInitPhase3:

    //Register OTA Endpoint
    //if (FALSE == zotaRegEndpoint(&zotaDongleSimpleDesc))
    //{
    //  uiPrintfEx(trUNMASKABLE, "\nError - Could not register OTA endpoint with zstackserver."
    //    "Exiting...\n\n");
    //  return 5;
    //}

3. Change the ZCL_OTA_ENDPOINT definition to 1 in source/Projects/zstack/linux/otaserver/zcl_ota.h:

#define ZCL_OTA_ENDPOINT    1

4. Run setup.sh to rebuild the gateway demo.

After the steps, I tried to input "O" in the demo application to start an OTA, but there is no response on the client side. I'm not sure if it is feasible to register the endpoint 1 in the gateway server but run other OTA APIs in the OTA server? After all these are different threads.

Best regards,

Shuyang

Hi Ryan,

I did some debug and found that the zclOTA_ServerHdlIncoming callback in zcl_otaserver_lnx.c is not called when I moved the endpoint registeration to gatewaysrvr.c., therefore the linux OTA server did not response to the QueryNextImageReq.

I guess it is because the zcl_registerPlugin call does not take effect without a af_register_req in the same server. Can you confirm this?

If that is the case, does it mean it is not possible to share the same endpoint between the gateway server and OTA server?

BR,

Shuyang

Hi Ryan,

I migrated the content from otasrvr.proto to gateway.proto and did some modification in the gateway code, it works with a ZED running the client example now.

Thanks for the guidance, I will let you know if there's further questions.

Best regards,

Shuyang