Announcement

Collapse
No announcement yet.

Lenovo y520-15ikbm most of the time doesn't turn on

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

    Lenovo y520-15ikbm most of the time doesn't turn on

    Hello,

    I've repaired a few laptops in my life but this time my own laptop died😂.
    Funny enough this one is a bit tough on me.
    It doesn't turn on (most of the time).
    Model: Lenovo y520-15ikbm (NM-391).

    The only way to make it turn on is:
    1) unplug battery + charger + rtc (seems irrelevant)
    2) wait a minute
    3) plug battery/charger in
    4) on charger plugin, laptop turns on by itself. On battery plugin you have to press power button. Sometimes nothing happens and you have to try again.
    5) when it turns on it also displays POST but it always turns off after ~10 seconds.
    6) repressing power button doesn't work 9/10 times. If it does work you're lucky the laptops turns back on and stays on (Windows boots)

    Already reprogrammed bios chip (UC3) with a different one from the internet. Has a completely different BIOS and EC version. Same result.

    I immediately suggested the EC (super io chip) IT8226E-128.
    Here are the measurements for all the SIO inputs:
    PIN OK? Comment
    VCORE Y 1.9v. Seems ok
    VCC Y 0v +3VS. Turns on from SUSP# trigger from +3VALW rail. Seems normal
    VSTB Y 3.3v
    VFSPI Y 3.3v
    AVCC Y 3.3v
    CLK_PCI_EC Y 0v. Is generated by PCH. Seems ok?
    PLT_RST# Y 0v. Is generated by PCH. Seems ok?
    ON/OFF Y ON/OFF button input active low
    PECI_EC Generated by PCH.
    NOVO# Y Novo button input active low
    VCCIO_PG Y No stuff. PU901 is not provided. Q3 makes VCCIO so no PG available.
    NTC_V1_GPU Y ~2.8v. Seems normal, drops lower when getting hot.
    NTC_V1_CPU Y ~2.8v. Seems normal, drops lower when getting hot.
    BATT_TEMP Y 0.3v when batt connected. Otherwise 3.3v. Assumed good.
    BATT_I ? 0v even with batt connected.
    ENBKL Y Noisy 0v. Generated by PCH. Assumed good seems to not be relevant.
    ADP_I Y 0v. Seems not relevant.
    ADAPTER_ID Y 2.4v. Assumed good?
    NTC_V3_DIMM Y Seems normal, drops lower when getting hot.
    CPU_PWRGD Y Comes on later when power is already provided. Assumed good.
    MAINPWON Y No stuff. PD601 not available
    LID_SW# Y Lid closed = LOW. Lid open = HIGH
    PM_SLP_S4# Y Goes high when power on. Generated by PCH. Seems to always be low when power off. Assumed good.
    SUSWARN# Y Goes high when power on. Generated by PCH. Seems to always be low when power off. Assumed good.
    PM_SLP_S3# Y Goes high when power on. Generated by PCH. Seems to always be low when power off. Assumed good.
    EC_FAN2_SPEED Y FAN speed from FAN header. Not relevant.
    EC_FAN1_SPEED Y FAN speed from FAN header. Not relevant.
    What I can see:
    The battery charges when the charger is plugged in seen from the voltage going to the battery that increases.
    The battery indicator light is controlled by the super io chip. The indicator light only works when the laptop is on (in that 10 second window).
    When the laptop doesn't respond to the power button the charger indicator light also doesn't work.

    Now my question is do you guys have any other suggestions where to look?
    Is there a way to bypass the SIO chip to validate it is in fact the SIO chip?
    Is this common behaviour for a bad SIO chip?

    I've never replaced a SIO chip and I don't really like the pin pitch.
    I read that I can just replace the chip with a unprogrammed blank one (maybe not even LENOVO text on the ic?). How does that work?
    The SIO is just a microcontroller to my eyes with some fancy stuff in it. How can a laptop power on on a blank SIO?

    Curious to your guys reactions. Lets see what you know 😀

    Attached schematics and board layout. [MOD EDIT] Link to schematic/boardview https://www.badcaps.net/forum/troubl...64#post1768664

    #2
    I dont know how you concluded SIO is faulty. To me,it seems you're heading in a wrong direction.

    Why not stick to basics? You've not shared any info about your diagnosis.

    01.DC-in fets bias correctly and 19V reaches CLR?
    02.What is the resistance to GND on all coils(all powe removed,wait for 2 mins and then measure)
    03.RTCRST#*SRTCRST# status with only cmos battery plugged in(no power attached)

    Comment


      #3
      I might have jumped to the SIO too soon.
      01)
      DC-in fets diode measurements are all good (PQ201, PQ202, PQ203) and 20v reaches PR201 and 12v reaches PR213 (batt removed).
      If they didn't work the laptop wouldn't power on on charger only.
      02)
      COIL RAIL RESISTANCE DIODE measurement
      PL1401 +1.2V_P 27 ohm 0.029
      PL601 +5VALWP 438 ohm 0.441
      PL602 +3VALWP 2.5 kohm 0.328
      PL3502 +1.0VALW_P 35 ohm 0.035
      PL5801
      PL5802
      PL5803
      NVVDD ~0.4 ohm 0.000
      PL1801 +1.55VGS_P
      FBVDDQ
      27 ohm 0.027
      PL3201 VCCSA 33 ohm 0.033
      PL3001
      PL3002
      PL3003
      VCCCPUCORE 5.5 ohm 0.006
      PL3101
      PL3102
      VCCGFXCORE 10.3 ohm 0.012
      03)
      With CMOS batt plugged in:
      PCH_RTCRST#: 3v
      PCH_SRTCRST#: 3v

      I don't see anything wrong here.


      Comment


        #4
        Yes,post#3 measurements are all fine. Some lenovo models require a valid battery to be present to turn it on. case in point is NM_D562(works with adapter only if battery is connected, else cmos cell has to be removed to turn it on from adapter only).

        Comment


          #5
          It does seem like it. Any other ideas?
          My guess is still at the SIO chip. Still don't understand how a blank Lenovo chip could work. A blank microcontroller doesn't do anything.
          Is a Lenovo SIO chip loading it's firmware directly from SPI on power? If so I should be able to see SPI activity when I apply power.

          Comment


            #6
            Yes,most of the lenovo/asus EC firmware is in main bios and it gets self programmed on 1st boot.

            Comment


              #7
              Well a reflow of the super IO chip resolved the issue.
              So either it was a bad solder joint or the chip is going bad. I'll see long term.
              Thanks for the help!

              Comment

              Working...
              X