Announcement

Collapse
No announcement yet.

Help to identify component HUAWEI MATEBOOK 15- USB-C POWER - Looping from 5V to 0.9V - IC U20 90º celsius HOT!!

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Help to identify component HUAWEI MATEBOOK 15- USB-C POWER - Looping from 5V to 0.9V - IC U20 90º celsius HOT!!

    First of all, thank you all for the help you provide in this forum.

    HUAWEI Matebook D15 Laptop - Mod: BOB-WAH9 - Motherboard: DAH98MMB8D0 REV D

    Can anyone help me locate the manufacturer of this IC? and tell me if the IC U20 is really the problem.

    When looking at the board with the thermal camera, the integrated U20 is set to 90-95 degrees Celsius and the USB-C tester that I have between the charger and the laptop, oscillates between 5V and when it reaches 95º, it drops to 0.9V... .and so on in loop mode.

    There are no apparent shorts in the capacitors or coils, and if we apply cold with an air compressor to the U20 chip, the loop stops and the 5V goes to 20V
    (USB-C switching), curiously, voltage only enters when the USB-C cable is on one side, if we turn it, no voltage enters the pins of the USB-C connector. Tested with 3 different chargers, and it does the same. The USB-C connector looks ok at microscope.(external and internal pins)

    Measuring with the working side of the USB-C cable, Pins 4-5-14-15 give 5V, and drop to 0.9V when the chip is turned to 95º...and the loop begins.

    Attached detailed photographs of the motherboard part.

    The integrated U20, on the front of the chip it says 4GD and a Chinese logo very small, looking with the microscope from the side, it has 3x3 solder balls.

    There is no schematic or boarview available anywhere.

    Thanks a lot!!

    #2
    Post the best picture you can take of this WLCSP9 packaged device.

    Comment


      #3
      Here they are, U20 zoomed at max.


      Comment


        #4
        What is nearby? Usb connector? The limited boardview balls seem to hint this to be a load switch.

        Comment


          #5
          I unsoldered it to take the photo below, and we put new tin on it and assembled it. And it does the same.
          The chip is part of the current input circuit of the single USB-C port, I have also changed the previous mosfet (EMB20P03), and nothing.
          Attached Files

          Comment


            #6
            Can you trace the wiring from the USB-C port pads to this device? This may be a low capacitance ESD suppressor that has taken a hit. Such devices use a flow-through pinout and will not impact the USB operation as long as this device is not defective but the ESD protection is then lost.

            Comment


              #7
              https://es.aliexpress.com/item/1005003719441982.html

              https://www.mouser.es/datasheet/2/30..._D-2314121.pdf

              Can this be?

              Comment


                #8
                Review the pinout from the full datasheet.

                Check the resistance from the I2C lines (SCL / SDA) of this device's PCB pads to the VCC rail. What is the measurement of each? This is to confirm that the pull-up resistors are present on the board for the I2C lines. The readings should be close to each other.

                FUSB302B - FUSB302B Programmable USB Type‐C Controller w/PD (onsemi.com)

                Comment


                  #9
                  Thank you Mon!! I try it.

                  Comment


                    #10
                    I was wrong...

                    FUSB302B, Don't works

                    I need Ground in B3 and VBUS in A1, I try it with :

                    NX20P0477

                    https://www.mouser.es/ProductDetail/...jptM09NA%3D%3D


                    Comment


                      #11
                      I found a user with the same problem, and he find it...is the same IC

                      https://www.badcaps.net/forum/troubl...h98ambad0-dead

                      The shit IC: https://www.richtek.com/assets/produ...DS1711H-04.pdf

                      Comment


                        #12
                        Solved, works!

                        Comment

                        Working...
                        X