Tool/software: Code Composer Studio
Hi,
we are developing a very simple battery powered device which will do very simple task to continuously broadcasting BLE beacon every 200ms with low Tx power through out battery life. Tx power in the range of -6dBM is good enough for our application.
We chose CC2640 for its ultra-low power features.
we are using tirtos_simplelink_2_13_00_06 for our development.
The device will not required any other IO or any other features except broadcasting pre-configured BLE beacon at a pre-configured interval.
We are looking for the most power optimised setup that we can set on Code Composer Studio SimpleBleBroadcaster project to have the longest battery lifespan.
we plan to use 2000mAH non-rechargeable battery in our product which we expect to last for at least 18 - 24 months before we need to change battery.
we have several question as follow:
#1:
In pre-define symbol at CCCS project we have activate POWER_SAVING
there are other pre-defined symbol that we are not really sure on the usage and whether or not it can affect on power usage of the CC2640 module such as:
USE_ICALL
SBB_TASK_STACK_SIZE=700
GAPROLE_TASK_STACK_SIZE=520
TI_DRIVERS_SPI_DMA_INCLUDED
TI_DRIVERS_LCD_INCLUDED
HEAPMGR_SIZE=3072
ICALL_MAX_NUM_TASKS=3
ICALL_MAX_NUM_ENTITIES=6
xdc_runtime_Assert_DISABLE_ALL
xdc_runtime_Log_DISABLE_ALL
CC26XXWARE
CC26XX
DEBUG
on the SimpleBleBroadcasterStack project we have another set of pre-defined symbol
USE_ICALL
FLASH_ROM_BUILD
POWER_SAVING
INCLUDE_AES_DECRYPT
xPM_DISABLE_PWRDOWN
xTESTMODES
xTEST_BLEBOARD
OSAL_CBTIMER_NUM_TASKS=1
HALNODEBUG
xDEBUG_GPIO
xDEBUG_ENC
xDEBUG_SW_TRACE
NEAR_FUNC=
DATA=
CC26XXWARE
CC26XX
DEBUG
would you be able to guide us on what can be done other than POWER_SAVING pre-define symbol to achieve the most power saving setup on our software level?
#2: referring to SimpleBleBroadcaster project in BLE SDK provided by TI, is there any line that we need to add or comment out in the source code on top of serveral pre-define symbol in order to further power optimized our software design?
#3:
Another application note that we come across is AN swra486a which discuss various power mode, i.e. active, idle, standby, shutdown. It seems to be quite complicated to handle. Do we have to handle those power management on our software level?
Any tips or guide will be very much appreciated.
