LAUNCHXL-CC1352P: Z-Stack, End Device power consumption measuring (zed_sw, Sleepy)

I use the same SDK and the same predefined symbols as yours.

I start comissioning on zc_light and press button BTN-1 on zed_sw to start comissioning as well.

Then I press BTN-2 on zed_sw, but the led on zc_light doesn't toggle.

Added:

Actualy I don't see any activity with the sniffer when I press BTN-1 on zed_sw.

Try to debug if pressing BTN-1 would start BDB commission.

Ok, I will, but pressing BTN-1 (and BTN-2) works fine when CUI and UART are enabled.

But the button handler is not used when CUI_DISABLED is defined.

How could I start comissioning?

Obviously that this breakpoint works when I press BTN-1 only if CUI_DISABLE is not defined.

Probably CUI is mandatory if I want to use buttons, but how would you explain that the UART still works even if BOARD_DISPLAY_USE_UART is not defined?

You can try to pressKey related key outside CUI_DISABLE to make it work.

I think enable CUI which would enable UART by default.

YiKai Chen said:

I can disable CUI_DISABLE and BOARD_DISPLAY_USE_UART without problem.

What did you mean by this?

Did it mean that you could just compile the project with these settings (I could too) or that ZED_SW was working and commissioning with ZC_LIGHT after the change?

I just compile the code but don’t test it by pressing BTN-1. According to handle press key is put inside CUI_DISABLE, it won’t work after you define CUI_DISABLE.

ok, so looks like we don't have ZED examples that wouldn't use CUI and had efficient power consumption, because all of them send data via UART periodically (~1s) and we can't stop it. Because if we disable CUI, we can't start comissioning, because buttons doesn't work. A vicious circle.

I tested:

zed_sw + zc_light

zed_sampleapp + zc_sampleapp

zed_genericapp + zc_genericapp

All of them use CUI.

Thanks, I wil try

In real product, we usually remove CUI and use a button to do commissioning.