• State
  • Locked Locked
  • Replies 15 replies
  • Subscribers 66 subscribers
  • Views 4903 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

BQ28z610 bricked

Charles-henri Mousset
Prodigy 110 points
Other Parts Discussed in Thread: BQ28Z610, BQSTUDIO

Hello,

I am evaluating BQ28Z610 with the EVM. I tried to put the device in SHUTDOWN mode via bqmanager.

The bq28z610 did went in shutdown (XCHG & XDSG = 1, then bqmanager loses connection), which is as expected as per the reference manual.

The issue is that the bq28z610 did never resumed normal operation. I pushed P4 (which sends P2 voltage to PACK+ and should wake the bq28z610) but it did not woke up.

I also disconnected completely the batteries and let the board sit all night but that did not change anything.

How can I fix this or prevent this issue?

  • 0
    Intellectual 765 points
    From manual "bq28z610EVM Quick Start Guide" try:
    "Wake-up the device up from SHUTDOWN (WAKE)
    Press the Wake pushbutton switch S1 to temporarily connect BAT+ to PACK+. This applies voltage to
    the PACK pin on the bq28z610 to power-up the regulators and start the initialization sequence."
  • 0 in reply to jury noname
    Prodigy 110 points

    sorry I made a typo, it's S1 I pushed not P4.

    Bottom line, I already tried that. It didn't woke the IC up as written in the documentation.

  • 0 in reply to Charles-henri Mousset
    TI__Guru* 76230 points

    hi
    Try applying a charger voltage, 8.4V for a 2s config and 4.2 for a 1s config to pack+ and pack -. That is what pressing the s1 pin does essentially. also make sure that VC2 is seeing sufficient voltage of atleast 3V because that is the power supply to the chip.
    thanks
    Onyx

  • 0 in reply to Onyx Ahiakwo
    Intellectual 420 points
    Was there ever any resolution to this issue? I appear to be having the same problem, where my system was communicating until a SHUTDOWN command. I have a 2s battery stack at 7.93 V attached, a power supply at 8.4 V connected across Pack+/-, and I've been pressing S1, but nothing appears to recover the device. I've removed everything to completely power off, then reconnected, and it still won't work.
  • 0 in reply to MR Flashlight
    Prodigy 110 points

    No, I never got the device to wake up anymore.

    As recommended I did try to apply a voltage at the PACK terminals but that did not change anything. I also tried to disconnect completely the cells, with no luck.

    Soooo... I'll use another chip.

    Good thing we are testing before putting this into production.

    PS: VC2 was indeed correct.

  • 0 in reply to Charles-henri Mousset
    Intellectual 420 points
    I did manage to get mine to respond. I held down S1 and initiated a reprogram from bqStudio. Obviously this isn't a viable fix on a production device, so I'm a bit leery about using this chip, even if it does test out well. Luckily I have an alternative from another company that I'm also testing.
  • 0 in reply to MR Flashlight
    TI__Guru* 76230 points
    if you had to reprogram your chip to get it functional, it means you must have some how put it into ROM mode. We have customers using this IC in production without issues and i will be happy to help resolve yours. Given that this IC by default is configured to work for 2s, you need to power it up as 2s OR power the IC up from pack p, clear the CC0 flag in DA configuration of df to set it up for 1s, extract an srec and program all your devices with it. That way you do not have to change the cc0 flag on each device.

    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 420 points
    If trying to send the shutdown command puts the chip into ROM mode, you've got a serious design issue. I'm using it in a 2s configuration, so that's never been a problem. The initial problem I had was sending the shutdown command bricking the device. A new problem I had was draining the batteries too far making the system unrecoverable, but I'm assuming that has something to do with the permanent fail function. That was resolved by removing and re-attaching the batteries.
  • 0 in reply to MR Flashlight
    TI__Guru* 76230 points
    Sending the shutdown command does not put the design into shut down mode. Even if you drain the battery too low and the device goes into shudown mode, onceyou apply a charger, the device will be powered on from the packp pin and the charge pumps that drive the chg and dsg fets will come on allowing you to charge your battery.

    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Intellectual 420 points
    All of what you've said is what *should* happen, but it is not the behavior that I observed, and it does not appear to be the behavior Charles observed.
  • 0 in reply to MR Flashlight
    TI__Guru* 76230 points
    That is what is happening on my board, The device is behaving as expected. If you are still evaluating this board, i will be happy to set up a webex session to ensure you aren't doing anything wrong that is bricking the device. I have sent you a friend invite so we could co-ordinate correspondence.
    thanks
    Onyx
  • 0 in reply to Onyx Ahiakwo
    Prodigy 10 points

    Hi,

    i have exact the same problem. If i discharge so that undervoltage shutdown will be active, i can not communicate with the pack again. Also putting the pack into the charger will not work.

    same problem if i test short circuit.

    how was the problem solved?

    thank you

    best regards

    philipp

  • 0 in reply to Philipp Aigner
    Intellectual 420 points
    My problem was solved by dropping the part altogether in favor of a solution where I can get the support I need for my designs (as you can see, it took 3 months for anyone to get back to me). Maybe Onyx there will be able to help you.
  • 0 in reply to MR Flashlight
    Prodigy 110 points

    We finally got the 28Z610 'unbricked'

    We had to run the EXEC command to 'unbrick' the device.

    The protocol is as follows:

    - Send the SHUTDOWN command from bqstudio (once)

    - bq28z610 shuts down after ~10s, as we can tell from bqstudio losing communication and Iq falling below 10µA

    - apply >3V on Vpak (6V for example)

    - bqstudio still has no communication with the bq28z610.

    - send the EXEC command

    - bqstudio can now read the bq28z610 registers.

    This is 100% repeatable.

    The behaviour is different from what described in the reference manual "12.2.10 AltManufacturerAccess() 0x0010 SHUTDOWN Mode" : there is no mention of the bq28z610 needing the EXEC command to recover from the SHUTDWN command.

     can you confirm?

  • 0 in reply to Charles-henri Mousset
    TI__Guru* 76230 points
    Charles,
    That doesn't seem right. The gauge going into shut down shouldn't put it in ROM mode. Sending the execute command takes the gauge out of ROM mode. The fact that you resume communication after sending that command means the device got into ROM mode. Can you confirm what firmware version is on the device?

    thanks
    Onyx