CC1352P: mt_sapi.c & mt_sapi.h files not present in SimpleLink CC13x2 26x2 SDK (4.20.01.04)

Hello Ryan Brown1,

Thanks for the information.

Will you please help me to know,

1. How can I implement the permit joining request & get device info request as they are based on the sapi request frame format?

2. Is there any alternative for them?

I am using the CC1352P-2 module as a ZNP device & our some devices will be based on the CC3538.
I would like to provide support for both type of devices. 
In our privius version application the permit joining is implemented using MT_SAPI_PERMIT_JOINING_REQ (as in ZNP-Host-Framework Application)

Will you please help me to tackel this problem?

Regards,
Shiv Patil.

As previously stated, it is your responsibility to port the SAPI functionality if desired for your application.

Regards,
Ryan

Hello Ryan Brown1,

I understood that I have to port the SAPI functionality to the SimpleLink CC13x2 26x2 SDK (4.20.01.04).

But, I would like to know,

Why the SAPI functionality was discontinued from simplelink?

&

If this SAPI functionality was discontinued from simplelink then what is the alternative permit joining functionality & get device info?

(i.e. which MT command shlould be used instead of MT_SAPI_PERMIT_JOINING_REQ)

Will you please help me to know that?

Regards,

Shiv Patil.

Hello YiKai Chen,

What will be the value of the TCSignificance in the command ZDO_MGMT_PERMIT_JOIN_REQ????

&

What about the network commands given in file <proj_dir>/Application/mt/mt.h

/***************************************************************************************************
* NWK COMMANDS
***************************************************************************************************/

/* AREQ from host */
#define MT_NWK_INIT 0x00

/* SREQ/SRSP */
#define MT_NLDE_DATA_REQ 0x01
#define MT_NLME_NETWORK_FORMATION_REQ 0x02
#define MT_NLME_PERMIT_JOINING_REQ 0x03
#define MT_NLME_JOIN_REQ 0x04
#define MT_NLME_LEAVE_REQ 0x05
#define MT_NLME_RESET_REQ 0x06
#define MT_NLME_GET_REQ 0x07
#define MT_NLME_SET_REQ 0x08
#define MT_NLME_NETWORK_DISCOVERY_REQ 0x09
#define MT_NLME_ROUTE_DISCOVERY_REQ 0x0A
#define MT_NLME_DIRECT_JOIN_REQ 0x0B
#define MT_NLME_ORPHAN_JOIN_REQ 0x0C
#define MT_NLME_START_ROUTER_REQ 0x0D

You can also refer following document,

See section 3.2.2

https://zigbeealliance.org/wp-content/uploads/2019/12/docs-05-3474-21-0csg-zigbee-specification.pdf

Regards,

Shiv Patil

TCSignificance should be set as true. Basically, you shouldn’t have to use NLME related APIs.

hello YiKai Chen,

Understood,

But do you know what is the reason behind discontinuing the SAPI functionality?
Is it because of some restrictions by the Zigbee Group or was it TI's sole decision?

Provided we want to go for Zigbee certification later on, how do you recommend we proceed with this?

Regards,

Shiv Patil

Hello Ryan Brown1,

Thanks for the inforamtion,

In addition, I would like to know the alternative option for getting znp device info using ZB_GET_DEVICE_INFO SAPI request.

I am more interested in getting the current network channel used by the CC1352P-2 znp device.

Will you help me to know that?

Regards,

Shiv Patil.

Shiv,

You could try ZDO_EXT_NWK_INFO: https://dev.ti.com/tirex/explore/node?node=AEEJ0Z3BgvagEoglvx9r1g__pTTHBmu__LATEST 

Regards,
Ryan

Hello YiKai Chen & Ryan Brown1,

Thank you for shareing the information.

This resolved my problems.

Regards,

Shiv Patil.