I'm using the CC1352R1F3RGZR MCU for a radio sensor project where high battery life is important. Most of the time, the RF Core is running the receive command with the synth on, transmitting at 900MHz, and then being turned off as the sensor enters a low power state. The problem that I'm running into is that initializing the RF Core with RF_Open() would permanently cause an increase in current draw, even if I'm no longer using the RF Core and closing the handle and telling it to shut off.
When my sensor is in low power mode, I'm getting a current draw of 80uA * sec. However, if I call RF_Open() and use the RF Core, I'm getting 1.7 mA * sec current draw even if I shut down the RF Core and close my handle.
In my code, I would initialize the RF driver with RF_open(). Then later when the sensor is entering low power mode, I would cancel all the commands and close the handle with:
RF_cancelCmd(handle, RF_CMDHANDLE_FLUSH_ALL, 0);
RF_close(handle);
to shut down the RF core. However, I'm still getting the increased 1.7mA * sec current draw even if I shut down the RF Core. I've also tried RF_yield() and RF_flushCmd(handle, RF_CMDHANDLE_FLUSH_ALL, 0) as well. I think that there might be some persistent RAM or something that isn't getting shut off when the RF Core is ran. If I never initialize the RF Core with RF_Open(), then I would get around 80uA * sec when my sensor is in deep sleep mode.
If I reset the entire CC1352 MCU, then the current draw would return to 80uA * sec. However, due to some design restrictions, I cannot reset the MCU. Does anyone have some suggestions or knowledge about what could be causing this increased current draw when the RF Core is turned on and even when it gets shut off?
