CYW20706 power saving mode wiced_sleep_config

[adam]

Hi @DheerajPK_41 ,

I have the same issue like "https://community.infineon.com/t5/AIROC-Bluetooth/CYBT343026-HCI-UART-CTS-pulldown-needed/m-p/290856.... 

I have tested lateset SDK version unfortunately the issue still there.

I think it is the obvious isuue, but in AIROC™ Bluetooth® SDK 3.3 release notes I don't see any about power saving

If do not use wiced_sleep_config() to save power , do you have better solution for power saving?

[DheerajPK_41 · Accepted solution]

Hi,

Could you please refer the attached code example and try to implement the low power mode in your application. Please use the latest BTSDK3.3

Thanks,

-Dheeraj.P.K

[adam]

Hi @DheerajPK_41 , 

Thanks for reply immediately.

In my case, I need 20706 continue advertising, so deep sleep(HID-off) won't be my decision.

Maybe in 20706 only PMU sleep can be used in my case. 

So....

Have it fixed yet?

[DheerajPK_41]

Hi,

All the issues related to low power mode are resolved. When you connect HCI UART, I recommend you to route the debug logs to WICED_UART or HCI_UART itself.  You can use the BTSpy tool also to capture the logs. It listens the UDB port of clientcontrol. Or Any host can get all the logs you have routed to HCI UART.

Thanks,

-Dheeraj.P.K

[adam]

test environment:
PC connect with 20706

SDK version 3.3.0.23146
enable HCI UART (wiced_transport_init( &transport_cfg ) in APPLICATION_START( ))

enable pUART (init in BTM_ENABLED_EVT)

enable wiced_sleep_config() in APPLICATION_START( )

test step:
(now: HCI UART port close, HCI UART CTS high, pUART port open)
1. ModusToolBox update FW
2. Update FW complete, 20706 pUART Tx write custom init success message(aa bb 81 00 01 00)
3. PC receives init success message through pUART
4. PC write message through pUART
5. 20706 pUART Rx receives message, pUART Tx response message
6. PC receives response message
7. reset 20706
8. 20706 pUART Tx write custom init success message(aa bb 81 00 01 00)
9. PC receives init success message through pUART
10. PC write message through pUART
11. 20706 pUART Tx doesn't response message
12. 20706 timer pUART write message still work，but PC receives corrupted data
(now: HCI UART port close, HCI UART CTS high, pUART port open)
13. open HCI UART port, HCI UART CTS low
14. pUART and all work fine

test result:
HCI UART CTS and wiced_sleep_config() will affect pUART

[adam]

Hi @DheerajPK_41 , 

below is my test result, please  check. 

thanks,

Adam

[adam]

Hi @DheerajPK_41 , 

if I commentate wiced_sleep_config(), UART will work fine. 

[DheerajPK_41]

Update:

If we use WICED_SLEEP_MODE_TRANSPORT, the device will go into sleep mode when the transport is connected and uses the device wake line to wake up.  When the device goes into deep sleep mode (HID-OFF), the entire chip goes to sleep. It can usually wake up on user events (ie. GPIO interrupt or after a certain time defined by the application).

The datasheet says,

"In HIDOFF mode, the CYW20706 baseband and core are powered off by disabling power to VDDC_OUT and PAVDD. The VDDO domain remains powered up and will turn the remainder of the chip on when it detects user events. This mode minimizes chip power consumption and is intended for long periods of inactivity"