RTOS/LAUNCHXL-CC1352P: Sequence Command for TICC1352P_2

Benuvel Victor

Part Number: LAUNCHXL-CC1352P
Other Parts Discussed in Thread: Z-STACK

Tool/software: TI-RTOS

Dear TI,

I'm working Zigbee of TICC1352P launchpad. I flashed ZNP code to drive the commands from an external micro-controller via UART command. Can someone share the sequence command from an external microcontroller via UART?

Regards
Benuvel Victor

over 5 years ago

0 YiKai Chen over 5 years ago

Guru 735455 points

Try to refer to sunmaysky.blogspot.com/.../use-ztool-z-stack-30-znp-to-set-up.html

0 Ryan Brown1 over 5 years ago

TI__Guru**** 202096 points

Hi Benuvel,

Besides YK's suggestion, you can also refer to the MT API: dev.ti.com/.../Z-Stack Monitor and Test API.pdf
There are also the ZNP and MT sections of the Z-Stack Users Guide: dev.ti.com/.../developing_zigbee_applications.html

Regards,
Ryan

0 Benuvel Victor over 5 years ago in reply to Ryan Brown1

Prodigy 50 points

Hi Ryan & YK

Thanks for your support. TICC1352 acts as Zigbee co-ordinator now.

I'm experiencing difference in the response of UTIL_GET_DEVICE_INFO command as am using Host ZNP stack which is older.

We understand from the PDF that (Page 4, Version 1.15), UTIL_GET_DEVICE_INFO response has been reduced and not backward compatible. Which version of ZNP shall i use on my TICC1352 to fix this error?

0 YiKai Chen over 5 years ago in reply to Benuvel Victor

Guru 735455 points

I suppose you should run latest Z-Stack ZNP on your CC1352.

0 Ryan Brown1 over 5 years ago in reply to Benuvel Victor

TI__Guru**** 202096 points

Hi Benuvel,

You should use the v2.30 SimpleLink SDK CC13x2 ZNP Zigbee project. As of May 2017 the UTIL_GET_DEVICE_INFO now returns Reduce
Function Devices associated to the local device instead of all devices in the association table. This is not a reduction of use or failure to be backward compatible and cannot be corrected by using a different ZNP version. You will need to use other MT commands to get the exact information you are seeking from the Zigbee network.

Regards,
Ryan

0 Benuvel Victor over 5 years ago in reply to YiKai Chen

Prodigy 50 points

Hello YK Chen
Thank you for your reply.

With the help of the link you shared, I made my TICC1352 as Zigbee co-ordinator. However, the Commissioning process is incomplete, as Zigbee End device or Router is not properly get commissioned (disconnecting in the middle) with my TICC1352. Kindly help me sharing required details to make the commissioning progress successful.

0 YiKai Chen over 5 years ago in reply to Benuvel Victor

Guru 735455 points

Can you elaborate what you mean "Zigbee End device or Router is not properly get commissioned (disconnecting in the middle) with my TICC1352"? I would also suggest you to setup sniffer to check what happens over the air.

0 Ryan Brown1 over 5 years ago in reply to Benuvel Victor

TI__Guru**** 202096 points

What is your ZED/ZR device? If you are trying to connect a pre-Zigbee 3.0 device, make sure that BDB_DEFAULT_TC_REQUIRE_KEY_EXCHANGE (from bdb_interface.h) is set to FALSE. Otherwise, a sniffer log as YK suggested would be extremely insightful.

Regards,
Ryan

Zigbee & Thread

Zigbee & Thread forum

RTOS/LAUNCHXL-CC1352P: Sequence Command for TICC1352P_2