Other Parts Discussed in Thread: BQ25611D, DRV2625
Tool/software:
Hi Ti,
We are using the following battery gauging module BQ27421-G1B EVM along with a charger module BQ25611dEVM, and it’s all interfaced with ARM processor (Running Linux: Yocto).
I’ve set up haptic feedback using the DRV2625EVM to alert when the battery is low, and this low battery haptic feedback is controlled through software. The BQ27421-G1B’s GPOUT pin is configured to SOC_INT, which goes low when the battery voltage drops. I’ve connected that to the TRIG/INT pin on the DRV2625EVM so it triggers a haptic response when waking up from a dead state, since the GPOUT pin state goes HIGH after power up.
The issue is, when I press the power button after the battery has charged enough to turn on the device (even if it’s only at 1% or 2%), the haptic feedback keeps running until the DRV2625 is fully configured. I’m attaching the configuration I’ve used for the haptics EVM.
I know the DRV2625 is RAM programmable, so it loses its configuration when it loses power. Is there any way to address this?"
Attaching the register configuration of the DRV2625 below.
DRV2625_write(client,0x07,0X01);
DRV2625_write(client,0x08,0X88);
DRV2625_write(client,0x0F,0X01);
DRV2625_write(client,0x10,0X81);
DRV2625_write(client,0x11,0X81);
DRV2625_write(client,0x12,0X81);
DRV2625_write(client,0x13,0X81);
DRV2625_write(client,0x14,0X81);
DRV2625_write(client,0x15,0X01);
DRV2625_write(client,0x16,0X81);
//loop control
DRV2625_write(client,0x17,0XFF);
DRV2625_write(client,0x18,0XFF);
Hardware Configuration Block Diagram: