• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 63 subscribers
  • Views 372 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Original question:

EV2300 Firmware update request

BQ40Z60: ManufacturerAccess Data Ready

PatWit
Intellectual 330 points
Part Number: BQ40Z60
Other Parts Discussed in Thread: BQSTUDIO, BQ40Z50

Hi TI-E2E Community,

right now i am developing on the communication with the BQ40Z60. It is working so far (asking for the device name and so on).

I have the following issue:

When I am asking for the Chem-ID (ManufacturerAccess) I have to wait several ms for the data to be ready.

For example when I am using a Breakpoint between sending the CMD and reading the data, the data the uC reads looks good.

Without the break, the data is wrong.

Now my question:

Does the BQ40Z60 somehow signal that the data is ready?

When i am meassuring the communication between EV2300 and BQ40Z60 the delay time is varying. So i think there is some condition that the BQStudio knows that the data is ready.

I haven't found anything in the documentation of the BQ40Z60 neither of SMB Bus.

I am looking forward to your answer.

Best regards

Patrick

  • 0
    TI__Mastermind 24870 points
    I don't recommend this device. Please refer to the bq40z50-R3
  • 0 in reply to Kang Kang
    Intellectual 330 points
    Hi Kang Kang,

    sorry to say this, but this doesn't solve my problem.
    Especially because the BQ40Z50 is not recommended for new designs (writen in the datasheet).

    Is there no other possible Solution?
    There must be people how have developed a communication with the BQ40Z60 and I think they didn't just wait x-ms for the response.

    Best regards
  • 0
    Intellectual 330 points
    Hi People,

    just if somebody is interested. I solved my communication problems (without delay).
    The problem was that i didn't use to send a CRC at the end. The funny thing is sometimes it worked and sometimes not.
    After implementing the CRC everything worked fine.

    I hope this will help somebody.
    Best regards.