• State TI Thinks Resolved
  • Locked Locked
  • Replies 21 replies
  • Answers 1 answer
  • Subscribers 66 subscribers
  • Views 1589 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.

BQ40Z80: BQ40Z80 pin 13 problem in DISP mode

Dmitriy Krlv
Prodigy 245 points
Part Number: BQ40Z80
Other Parts Discussed in Thread: BQSTUDIO

Hello! 

In the BQ40z80 Tech.Ref i can see  information about Pin 13 likе this :

>>Set Settings:Pin Configuration[MFP13_SEL0][MFP13_SEL1][MFP13_SEL2] = 000 to select DISP. When this mode is selected, the pin is used for an LED display button function. In this mode, a normally opened switch button is connected between this pin and VSS. When the button is pressed, the pin is shorted to VSS. This pin includes an internal 18-kΩ pullup resistor to the internal LDO, which biases the pin high when the button is not pressed. The gauge monitors the pin periodically to detect when the button has been pressed, and then enables the LEDs while it is held.

unfortunately, my push-button on my film keyboard have a ~65 ohm resistance then pressed.  I have ~ 1.75v  on disp pin before pressing, and ~1.2v after.  How can i check this 18k pull up?

If i use forceps to short pin13 to GND i can see my SOC through leds.  but with my button-  i can't.

I have tried to resolder IC to new one, but ,my problem still is my (

Thanks for you answer!

  • 0
    TI__Guru** 105590 points

    Hello Dmitriy,

    With 65 Ohms to ground the display should still work. Can you try double checking the continuity of the push button? if you are getting a partial voltage drop there appears to be some kind of voltage divide happening and the push buttons path to ground has a few thousand Ohm resistance.

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 245 points

    Hello!. I have tried another PCBs, Nothing good. 

    But i can not see any dividers on my board between BQ IC and film panel =) 

    here are the video

    drive.google.com/.../view

  • 0 in reply to Dmitriy Krlv
    Prodigy 245 points

    Here are my SREC

  • 0 in reply to Dmitriy Krlv
    Prodigy 245 points

    Here is my HW and FW versions.

    HW - 0xA1

    FW - 0x0004

    I just have understood that 0.025A  through this pin  than shorting it to GND - max 1v8 LDO current in Bq40z80. And then i short this pin IC is gonna heating fast 

    Seems like there are not 18k resistor , and pin 13 is shorted to internal 1v8 

  • 0 in reply to Wyatt Keller
    Prodigy 245 points

    And here are my SCH file.

    I really hope that you can help me with this problem

    Thanks!

    Battery_board_7S.pdf

  • 0 in reply to Dmitriy Krlv
    TI__Guru 52115 points

    I suggest you try a pushbutton like the one we use on the bq40z80EVM and see whether it works.

  • 0 in reply to Andy Liu (BMS)
    Prodigy 245 points 
    Of course I did. A short to PIN13 on the ground is equivalent to this button. 
    I closed PIN13 using an ammeter and it showed 0.025A (see the video above), 
    the Bq40z80 starts to get very hot.
     Perhaps it’s the hardware version of the chip? 
    The datasheet says about 18k, but in practice
     I have the feeling that there is a direct short circuit to the internal LDO 1.8V.
     Can you simulate my settings on a debug board?
     I have been working with this product for several years, but it was mainly the Bq40z50, 
    so I believe that there are no obvious errors. 
    However, the application above has circuitry and an SREC file. Thanks!
  • 0 in reply to Andy Liu (BMS)
    Prodigy 245 points

    I cant find anything information about ADTH , RCPUP, RCWKUP


    It seems to me that in the mode [MFP13_SEL0] [MFP13_SEL1] [MFP13_SEL2] = 000,

    instead of enabling ADTH, one of the keys below is turned on.

    Since in GPIO mode the pin is functioning.

    ATTENTION Another strange point: in Pin Configuration mode [MFP13_SEL0] [MFP13_SEL1] [MFP13_SEL2] = 011

    sending 0x0004 word to register 0x49 do nothing.

    But in Pin Configuration [MFP13_SEL0] [MFP13_SEL1] [MFP13_SEL2] = 110 works and high state and low

    It seems to me. somewhere here an error crept in

    I am using BQ studio 1.3.97. Maybe this is the problem?

  • 0 in reply to Andy Liu (BMS)
    Prodigy 245 points

    Please, look at this. 


    I'm completely at a loss

    https://drive.google.com/file/d/1ZK994kx3BuEn2xfpNQdrSMNtgcgjFGqy/view?usp=sharing   

    https://drive.google.com/file/d/1mBUNOKZIG-KTSV5AFeht2gmuiqumx_an/view?usp=sharing 

    I tried several different boards, several chips, a stable and test version of BQstudio. I want to try on firmware 002, but I can’t find it, can you throw it off?

    Let's come up with something with this problem, it all looks very suspicious

  • 0 in reply to Dmitriy Krlv
    TI__Guru 52115 points

    See the v0.02 firmware below.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/196/bq40z80_5F00_v0_5F00_02_5F00_build_5F00_3.srec

     Andy

  • 0 in reply to Andy Liu (BMS)
    Prodigy 245 points

    Hello.

    Sorry, but NOPE. 

    0.02 firmware has the same problems

    I checked DISP mode on other pins. It works correctly only on PIN17. The pull_up really works there, and when it is shorted to the ground through the 200ohm resistance, the charge indication LEDs light up.

    On PIN13, 0.025A is still required to activate the LEDs, which, apparently, destroys the microcircuit because of overheating.

    How can we  check that they are made by you in your factory.?  are there some information about it? 

    And, huge request, check the mode described by me on your hardware.

    I will try to buy a debug board in the near future, but right now I do not have such an opportunity, but I have problems with 32 battery assemblies for the customer.

    All incomprehensible problems are described by me above. First of all, this is a problem with DISP mode on PIN13. The second is a completely incomprehensible story with the GPIO mode PIN13. Perhaps something else does not work as it did in TRM, I did not check.

  • 0 in reply to Dmitriy Krlv
    TI__Guru** 105590 points

    Hello Dmitriy,

    We have been trying to recreate the behavior on our side and it looks like we have been able to from some tests we have done. We are thinking this could be a firmware related issue.

    We are talking with the firmware team about what could be causing this, we will try to get back to you quickly.

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 245 points

    Hi!


    This is a very good news.

    I really look forward to the result and a new firmware. When do you manage to do this?

    Regards, D

  • 0 in reply to Dmitriy Krlv
    TI__Guru** 105590 points

    Hello Dmitriy,

    We have been looking into this issue and confirmed there is a bug in the FW, pin 13 is not being pulled through the internal 18-kOhm resistor. We are now working to solve this issue with the FW team and it will be fixed in the next firmware update.

    We would recommend using one of the other multifunction pins for the DISP feature until the new firmware is released.

    Sincerely,

    Wyatt Keller

  • 0 in reply to Wyatt Keller
    Prodigy 245 points

    Good day. Unfortunately, I have no way to change the pin,

    since all the pins of the IC are busy and in use.

    I really hope that you can fix this problem quickly

    and test it on my device before putting it into production,

    since I already need to transfer them to use


    Thank you for not ignoring the problems, but fixing them. I appreciate it.

    Regards, D

  • 0 in reply to Wyatt Keller
    Prodigy 245 points


    Good day!

    Do you have an understanding of the timing implementation of the patch?

    I do not want to seem annoying, but at the moment I have no other solution to this problem,

    except for waiting for these corrections in the firmware

    Tnanks! D.

  • 0 in reply to Dmitriy Krlv
    TI__Mastermind 42060 points

    Hello Dmitriy,

    Unfortunately due to the current team's workload, the firmware update won't be released until later this year. 

    I apologize for the inconvenience. 

    Best Regards,

    Luis Hernandez Salomon

  • 0 in reply to Luis H. S.
    Prodigy 245 points

    Good afternoon, luis

    I know what "busy developers" are, because I myself work in the development field.

    And also I know what a dissatisfied customer is.

    And in this case, I am one of them, since I bought a READY device from a cool company TI,

    and it has a bug that, most likely, can be corrected in test mode for a couple of days, if you want.


    You offer to wait a few months for me, and it seems to me that this is incorrect on your part in this case,

    yet I bought your product as a finished product, and not as a test one

    I suppose, and I hope, this situation is urgent enough to slightly shift the priorities of your team,

    I believe that a lot of other users faced with a similar problem simply bypassed it, or abandoned this solution, I do not think that you pursue such goals.
    Thanks you!

    I will be very grateful for the answer

    Best Regards, D.

  • 0 in reply to Dmitriy Krlv
    TI__Mastermind 24870 points

    Hello Dmitriy,

    Thank you for bringing this to our attention.

    I have let my management know the feedback as well.

  • 0 in reply to Kang Kang
    Prodigy 245 points


    Good day!

    Is there any news on my problem? It is still relevant.

    Regards,D

  • 0 in reply to Dmitriy Krlv
    TI__Mastermind 24870 points

    So far, not yet. I will keep you posted. Closing the thread for now.