CC2652

My operation is as follows:
1. On the first CC2652 board, burn the executable file of the zc_light_sink example, then input the d character multiple times through the serial port, enter the menu <COMMISSION> screen, and then input the e character into the serial port. The serial port starts to print the following content cyclically:
< COMMISSION > NF NotOnNwk
Id000 Srch000/00

Then click button1.

2. Burn the executable file for the zr_genericapp example on the second CC2652 board, then click button1.

3. Program the gpd_switch sample executable on the third CC2652 board.

4. Set in the first CC2652 board APP menu
GREEN POWER SINK
 COMMISSIONING
< ENABLED >

5. Click button2 on the third board to see that DIO6 and DIO7 of this board are lit at the same time.

6. Set in the first CC2652 board APP menu
GREEN POWER SINK
 COMMISSIONING
< DISABLED >

7. Click button2 on the third board to see that DIO6 and DIO7 of this board are lit at the same time.

My problem is that I didn't see the phenomenon described in the test description, "Once the GP commissioning mode is disabled, sending the On/Off GPDF with the GP On/Off Switch will toggle the Light Sink LED."

I suppose you should make zc_light_sink form network in your step 1.

But my first step above is really creating and opening the network. Is it the first step to do something wrong?

In your step 1, you mentioned it shows:

< COMMISSION > NF NotOnNwk
Id000 Srch000/00

This means it doesn’t form Zigbee network.

That means the problem may be in the first step. There is content in the zc_light_sink readme to create the network.

"Zigbee coordinators can only create networks and other devices must join the network, this is done using the common interface by enabling Formation Mode and executing the commissioning process in the Commissioning Screen. This sample applications uses the stack notifications (zstackmsg_CmdIDs_BDB_NOTIFICATION) on a successful network Formation process to open the network and allow new devices join, even if the Steering Mode is not enabled from the common user interface. If the network is closed, it can be open again by enabling the Steering Mode and execute the commissioning process in the Commissioning Screen."

I burned the zc_light_sink project, and then I saw that the formation mode is enabled through the serial port. Then I enter the <Commissioning> Screen, then enter e through the serial port, and the serial port starts to print.
< COMMISSION > NF NotOnNwk
Id000 Srch000/00

I thought that this is the first step to complete the work. Is there anything else that needs to be done?

When you see "< COMMISSION > NF NotOnNwk", you should press "E" key to make zc_light_sink form Zigbee network.

First of all, thank you for your patience, because this problem has been bothering me for a long time, and I have not found the reason. For your answer, I will say the result of my operation. After burning zc_light_sink, I enter COMMISSION SCREEN by entering the command 'D'. The serial port prints out <COMMISSION> -- NotOnNwk. At this time, I enter E and the serial port print changes to <COMMISSION > NF NotOnNwk, if I Continue to enter E, serial port printing is still this. What should I do next, and what kind of printing will I eventually need to prove that the first step is successful?

What com port tool do you use? Try to use Putty.

I used putty to test that the result is the same, the serial port still outputs "NF NotOnNwk". I think this has nothing to do with the serial port tool.

I reinstalled simplelink_cc26x2_sdk_2_20_00_36.exe and simplelink_zigbee_sdk_plugin_2_20_00_06.exe, but I tested zc_light_sink and printed the same result as in the previous answer. In addition, I found that if you burned zc_light_sink on the board that once burned gpd_switch, enter E in the COMMISSION screen, it will print <COMMISSION> -- JOIN Open, the same program and hardware, it is different. The result is very confused

I attach my zc_light_sink hex file and you can try to download it to your CC2652 to test again.

zc_light_sink_cc26x2lp.zip

This could be a Nv memory issue from pre-existent code, use Uniflash or CCS to erase all device memory and re-download the default examples, or reset the devices to factory default inside of your terminal.

Regards,
Ryan

I found the problem is to erase the flash before burning the program. Now I erase the flash first, then burn the files you provided and the files I compiled separately, The result is the same now. Atfer enter the <COMMISION> screen and press E, the serial port prints <COMMISSION> -- FORM Open frequently. I think this means that the first step to create the network is successful.

I see the instructions first to add the routing device to the network, then follow the instructions in Interfacing with the GP On/Off Switch Example App to operate the Light Sink. When the TEMP OPEN was printed frequently on the light sink board, I started to press button1 on the zr_genericapp board. I didn't see any changes in the printing on the light sink board. So how do I tell if the zr_genericapp board has been added to the network created by the zc_light_sink board?

If zr_genericapp joins zc_light_sink, the PANID should show the same value. I also suggest you to use Ubiqua Protocol Analyzer to check if zr_genericapp joins zc_light_sink.

I think the pan id you mentioned should be the pan id in the <INFO> screen. I see that the pan id has never changed from power-on. In addition, there is a <PAN ID> screen, I see that the default value is always 0xFFFF, which should be modified by the user.

I want to know what I need to do to add zr_genericapp to zc_light_sink? From the point of view, when zc_light_sink starts to print "form open", you should only need to click button1 of zr_genericapp, but after this operation, I am not sure whether zr_genericapp has joined the network.

You should go to <COMMISSION> on zc_light_sink and press "E" to see "JOIN Open 0xx". Then, go to <COMMISSION> on zr_genericapp and press "E" to join zc_light_sink.

I found that my zr_genericapp board can't switch screens by inputting D or A through the serial port. Even when the power is on, there are no welcome screens. I plugged this board many times and it was all this effect. After I burn this board into zc_light_sink, I can switch between the screens through the serial port input. Later I tried the gpd_sw board, which is a similar problem.

Do you use Putty as COM port tool?

Yes, I tested it with putty and tested it with other serial tools. In putty, I set the zr_genericapp board to have a serial port baud rate of 115200, a data bit of 8, no parity, a stop bit of 1, no Flow control.

Which Z-Stack plugin version and CC26x2 SDk do you use?

Ryan Brown1 What do you mean Z-Stack 3.10? Is it the same to SimpleLink Zigbee SDK Plugin 2.20.00.06?

Yes, now I am testing that the DIO6 light of zc_light_sink can be lit or extinguished by button2 of zw_switch. Is it necessary to have three devices in the green power example? I tested that if only the two boards zc_light_sink and zw_switch are powered on, then DIO6 will not respond.

Yes, it is necessary to have three devices in the green power example.

Z-Stack 3.10 refers to the Zigbee 3.0 stack solution for SimpleLink CC2652R/CC1352 devices and applies to the SDK Plugin.

e2e.ti.com/.../

Regards,
Ryan

I know it refers to the Zigbee 3.0 stack solution for SimpleLink CC2652R/CC1352 devices and applies to the SDK Plugin. However, latest SimpleLink Zigbee SDK Plugin version is 2.20.00.06 and previous plugin version is 1.60.xx.xx. Does Z-Stack 3.10 refer to SimpleLink Zigbee SDK Plugin version is 2.20.00.06 or previous 1.60.xx.xx version?

Z-Stack 3.10 applies to both SDK Plugin versions.

Regards,
Ryan

Oops! That’s confusing. I expect different plugin uses different stack version.