Other Parts Discussed in Thread: BQSTUDIO
Hello;
In my original post regarding I2C ACK errors, I mentioned that my host synchronizes to the ALERT interrupt and asks the 78350 for voltages, current, temperature, faults, SoC, SoH, etc. And while doing so, will encounter multiple ACK errors. To address this, I tried delaying for 150 ms after the ALERT interrupt, in an attempt to schedule my SMBus traffic after the 78350 gathered its data from the 920 However, this had little effect, and the ACK errors remained.
My guess then was as it remains now, is that the 78350 is busy, and when so, does not ACK its I2C address (contrary to the SMBus spec.).
SO, I really need answers for two questions:
1. Does bqStudio encounter these same random ACK errors when communicating with the 78350 eval board? Is bqStudio written to deal with these, retransmitting its requests if encountering an ACK error?
2. IF the ACK errors indeed occur because the 78350 is busy, are there any means to avoid them?
Would you please check into the engineers that wrote or maintain bqStudio to get confirmation on this? I'd really appreciate it, as that would remove any doubt of the efficacy of my driver
Thanks!
