Announcement

Collapse
No announcement yet.

HP 245 G7 - HAGRID 6050a2983601-MB-A02(A2) - Power Sequence Loop?

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

    HP 245 G7 - HAGRID 6050a2983601-MB-A02(A2) - Power Sequence Loop?

    figured out after two days without any progress, no shorts present anywhere on the board. unit still responded on power button press without picture on lcd & hdmi, power consumption cycling between 0.6 - 1.2A. removing ram stick no blinking indicator present with power consumption steady at 0.65A with or without screen attached. all power rails present during 0.6 - 1.2A cycle. tried flashing bios chip 3 times using file from https://www.badcaps.net/forum/troubl...3601-mb-a02-a2 without any changes

    i've noticed during "power cycling", LCM_VDDM controling P3V3S_LCDVDD went on & off with and without screen attached also PVCORE_NB changing between 0.9 - 1.0V but PVCORE is steady at 0.9V, replaced C66600 & Q66610 with same result, haven't try to replace U66000 since i still had doubt the U66000 causing the problem.

    one other thing, when power cycling happen i probe bios chip (U365/CN365) pin-1 (SPI_CS1#) using DMM power cycling immediately stop but still no picture on lcd & hdmi, i'm thingking maybe SPI_CS1# line to SOC broken or a resistor on that line broken, but when i compare actual board with boardview it diferent (photo attached) and finally i decided to ask it here. hoping someone had similiar issue or maybe can lead me where to look.

    all files needed atached
    Attached Files

    #2
    DRAMRST# present?

    Comment


      #3
      try put the power on button, then press the power on button and insteanly remove the power on button from the conector.

      Comment


        #4
        Originally posted by mcplslg123 View Post
        DRAMRST# present?
        since this board use DDR4, i can't found DRAMRST# signal on ram slot. if you mean MB_RST# (found on ram slot) it read 0V on my multimeter

        i've uploaded boardview here: https://www.badcaps.net/forum/troubl...-x01-boardview. the boardview is not same model but that boardview i could find on net that had similiar layout

        Comment


          #5
          Originally posted by Rush volkov View Post
          try put the power on button, then press the power on button and insteanly remove the power on button from the conector.
          i'm sorry if i'm not too clear to describe the symptom, the power indicator light is always on after pressing power button and turned off when long pressing it, not turning on then off like you expect when you had problem on ffc cable or the button it self. FYI i never attached the power button board (if it's removable from main board using connector) when diagnosing any motherboard issue, i always use tweezers or direct bare wire that connected to ground to turn on and off a motherboard i worked on

          so, as far as i can tell it's not power board or button or ffc cable connected to motherboard issue. but thank's for remind me
          Last edited by kodox; 06-17-2024, 11:34 PM.

          Comment


            #6
            Pin108 on the ram slot is for DRAMRST#. the name may be different for amd platform.

            Comment


              #7
              Originally posted by mcplslg123 View Post
              Pin108 on the ram slot is for DRAMRST#. the name may be different for amd platform.
              yes, pin 108 on the ram slot is the only pin with RST naming and measured 0V

              Comment


                #8
                Without Dramrst# present, there is no point troubleshooting display as mb is not even posting. You need to check ram slot requirements. Try with another ram stick. Sometimes DRamrst# is pulled low due to corrupt bios-so flash known good bios as well.
                Check SMBUS communication of ram with APU preferably with DSO. If all these fails then you are staring at likely APU fault.

                Comment


                  #9
                  since i don't have DSO yet, i think i just gave up on this & consider as APU fault. but thank's anyway

                  Comment

                  Working...
                  X