Other Parts Discussed in Thread: BQ76952, BQ34Z100-G1, , BQ34Z100, EV2400
Hi,
I have a design where a BQ76952 and a BQ34Z100-G1 are connected to the same I2C bus. I know that both devices work, and that they are communicating correctly over i2c, as the host MCU can communicate with both without issue.
When trying to use BQ-STUDIO I can communicate ok with the BQ34Z100-G1 device, but BQ76952 is impossible to get to work right. It seems that BQ-Studio is autodetecting the BQ34 on I2C address 0xAA, and that this auto-detection is forcing BQStudio to communicate only on address 0xAA. If I manually select the protector ("Monitor_76952_0_36_bq76952.bqz"), BQ studio starts, but is unable to read sensible data from the device, due to communicating on address 0xAA (which is the BQ34 device) instead of 0x10 that the BQ76952 is on. This is also shown in the dashboard next to the chip.
Here are two screenshots, one of the working BQ34Z100 communication with sensible values on address 0xAA. And a second screenshot of trying to communicate with the BQ76952, where BQStudio uses address 0xAA instead of 0x10, with useless values as a result.
Since BQStudio tries to communicate with the BQ34z100 as if it is a BQ76952, then it gets responses, but crazy data.
Setting i2c address to 10 in the dashboard and clicking "Detect" has no effect, and setting "Auto Detect at Launch" = Disabled in Preferences has no effect, and the BQ34z100 detection still overrides any other choices I make during startup. At this point it is currently impossible to communicate with the BQ76952 with BQStudio, even though I can communicate without problems from the MCU. When using BQStudio, the host MCU is halted and does not interfere with the I2C bus.
Using BQStudio-TEST 1.3.111 on Windows 10 with a EV2400 (fw 0.32)
