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.
Randy,
I few things come to mind. Reading the registers would help provide some insight as to what is going on.
I think it is worth looking into find a way to read your registers. The support I can offer on getting that configured is limited, but I can tell you how I would go about it. There is a package for Linux SoCs called i2c-tools. That package has several i2c debug tools.
You could hookup the EVM to an SoC dev board, configure i2c, use i2cdetect to confirm the presence of the BQ25887, and use i2cdump to show the contents of the registers.
Alternatively you could purchase an EV2400 and I could offer more support on that
Some resources:
https://manpages.debian.org/unstable/i2c-tools/i2cdetect.8.en.html
https://manpages.debian.org/unstable/i2c-tools/i2cdump.8.en.html
TP7 measures 4.92V. This seems to indicate it is not in VINDPM.
TP15 voltage increases as the battery voltage increases during charging. TP15 is slightly greater than the battery voltage by the voltage across the current sense resistor. This only make sense.
If CV is constant voltage, it is not in that mode either. The current is changing and the voltge is increasing with charge time. When it gets close to +8.4 volts it reduces charge to about 0.9 mA. this seems to be good safe operation. When I try to charge an only slightly discharged battery pack, it charges slowly to top it off and cuts out as expected. Overall, it works great.
I am purchasing a EC2400. You can guide me through that in a few days.
I have run a full charge/discharge cycle. I am pleased with the performance in all areas except this one we are discussing. I am getting good enough results to find the part acceptable. Now just to tweek it a bit to get maximum performance.