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.

  • Resolved

BQ27426EVM-738: About BQ27426EVM

Genius 5070 points

Replies: 6

Views: 539

Part Number: BQ27426EVM-738


Dear, All

The customer uses BQ27421EVM-G1A to acquire data.
In another configuration,
- BQ21040EVM-777
- EV2300
- Electronic load
- Battery used by customers
Also, they use bqStudio.
There was a message that an error might occur in log data while data acquisition is being performed.
I did not own BQ27421EVM so I ran it on BQ27426EVM-738 instead.
As a result, the following error occasionally occurred during incoming data.

TimetestLogCaptiontestError CodetestError String
2017-01-17 18: 29: 12 testRemCaptest 772 test No acknowledge from device.
2017-01-17 18: 29: 20 testInt Temptest 772 test No acknowledge from device.
2017-01-17 18: 29: 26 testTrue StateOfChgtest772testNo acknowledge from device.
2017-01-17 18: 29: 46 testRemCaptest 772 test No acknowledge from device.
2017-01-17 18: 29: 54 testInt Temptest 772 test No acknowledge from device.
2017-01-17 18: 31: 01 testCtrlStatustest772testNo acknowledge from device.
2017-01-17 18: 31: 01 testTemperaturetest772testNo acknowledge from device.

This occurs both during charging and discharging.
When it occurs, it seems that we can not temporarily access the EVM from the PC.
I would like to know the cause and measures to be taken.

Thanks, Masami M.

  • Something causes the EV2300 to not get an ACK on the I2C. Please verify that the voltage levels on SCL and SDA (and the edges) are within spec.
  • In reply to Dominik Hartl11:

    Hi, Dominik-san,

    Thanks for your support.
    I saw the waveforms of SCL and SDA and adjusted the voltage level.
    As a result, the number of errors decreased, but the following errors remained.

    TimetestLogCaptiontestError CodetestError String
    2017-01-19 10:59:02testDOD0test772testNo acknowledge from device.
    2017-01-19 10:59:43testDOD0test772testNo acknowledge from device.
    2017-01-19 11:00:22testDOD0test772testNo acknowledge from device.
    2017-01-19 11:01:02testDOD0test772testNo acknowledge from device.
    2017-01-19 11:01:43testDOD0test772testNo acknowledge from device.
    2017-01-19 11:02:22testDOD0test772testNo acknowledge from device.

    What could be considered?


    Thanks, Masami M.
  • In reply to Masami Michino:

    Hello Masami-san,

    Do you have access to an EV2400 or a TI gauge GDK?
    What's the firmware version of your EV2300?

    Please check that the gauge is always powered up during the test.

    Regards,
    Dominik.
  • In reply to Dominik Hartl11:

    Hi, Dominik-san,

    I do not have EV2400 and TI gauge GDK.
    FW Ver of EV2300 is 3.1c.

    A battery is connected to the gauge, and voltage is always applied.
    A voltage is supplied from the regulated power supply to the I2C pull-up resistor.

    Thanks, Masami M.

  • In reply to Masami Michino:

    Masami-san,

    Please try this with an EV2400. Something causes the I2C transactions to fail with the EV2300. I can't debut this remotely without access to your setup.

    Regards,

    Dominik.

  • In reply to Dominik Hartl11:

    Hi, Dominik-san,

    I got EV2400 and confirmed the operation.
    As a result, I confirmed that no error occurred.

    Thank you very much.

    Thanks, Masami M.

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.