This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3235S: vs CC3220R: Details on power consumption

Part Number: CC3235S
Other Parts Discussed in Thread: CC3220R,


I am looking for the power consumption comparaison between CC3235S and CC3220R when used as device in always connected and Intermittently connected use case?

-For always connected:
do we have a comparing table for the different "always connected mode" (Network learning alrgorithm, long sleep interval) that we define in our marketing material?
I can see that long sleep interval range we give is from 500msec to 2sec. Are all AP being able to support up to 2 sec? What is the minimum interval that an access point need to be able to support?

-For Intermittently connected:
Do we have power figures for boot again and joining a network?
Do we have some figures on the time it take to go out of "hibernate" and resume the application?

-I have seen the below Appnote/white paper. Are there more documents for power consumption analysis?
Low-Power Internet Connectivity Over Wi-Fi (Rev. A)
CC3x00 Power Management Optimization and Measures

Thanks in advance,


  • Hi,

    The power consumption of the CC3235 and the CC3220 are equivalent, assuming you are comparing the 2.4GHz performance on each. 5GHz has higher active power consumption although given that active TX won't be occurring much at all in typical power-optimized systems the always connected and intermittently connected use case power numbers are still just about the same. You can find the exact numbers in the datasheets of the CC3220R and the CC3235S, in table 5-6 of the CC3220 datasheet and table 5-1 of the CC3235 datasheet.

    The minimum LSI supported by the AP is not set by spec. Technically, it is our CC32xx that is skipping beacon packets from the AP in the hopes that we won't miss broadcast data or any AP-specific traffic that may occur during the long sleep interval. 600ms is the typical 'safe' interval that works with the vast majority of access points, but the application developer will need to ensure that there is code to handle the case where the LSI is set too aggressively and needs to be scaled back.

    The various components that make up the always connected mode such as the use of the network learning algorithm are baked into the power number you see in the datasheet. That being said, the specific LSI time does affect the power consumption further. I will email you a slide deck that covers this LSI settings comparison in addition to a whole collection of other useful info. This slide deck should cover most of your remaining questions.

    Let me know if you have further questions on the power behavior of the CC32xx.