filenames doesn't matter. if you want to work with TI TPS53679 only include the correct XML file.
<Name>TPS53679 (PMBus)</Name>
<Data>7901</Data>
CPUs must be powered.
VRM modify ICC_MAX to run high TDC OEM cpu
- Thread starter RolloZ170
- Start date
Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.
<Name>TPS53679 (PMBus)</Name>
<Data>7901</Data>
CPUs must be powered.
you can select Profile "TPS53679" choose Addr. 60 i.e. and manualy "Add" a controller to the list on the left.
then select it and check "Monitoring" to see the IOUT_MAX of the Device, the right should be 150-228A
Don't program it unless you are sure to have the right ones.
Thank you for setting up this place to brush it outyou can select Profile "TPS53679" choose Addr. 60 i.e. and manualy "Add" a controller to the list on the left.
then select it and check "Monitoring" to see the IOUT_MAX of the Device, the right should be 150-228A
Don't program it unless you are sure to have the right ones.
I scan and found these address 60 62 70 72, but when i run command can not successfully.
@RolloZ170 What did i was wrong ? Thank you.
@RolloZ170 What did i was wrong ? Thank you.
just connect to DB_VR_P0 / DB_VR_P1 and -scan for supported devices, you have to figure out the pinout, Ground should be easy to find.
if the CPU VRM controller is an Infineon IRxxxxx Model i can not help. then you need Infineon software PowIRCenter and Infineon USB Dongle USB005
Pls after I connect to the DB_VR_P0 with USB005, is it possible to adjust this place with PowIRCenter software
Last edited:
different naming.
i have never modified a IR35215 system myself. but you can try change 228A -> 255A and check with high TDC CPU.
edit: 2nd CPU IR35215 is at DB_VR_P1 then
Another success report for Dell 7920 Tower. The utility works flawlessly!
I chose to solder a header on to it. Yet I spent a huge amount of painful time debugging (downgrading BIOS, etc.) until I finally traced the problem to a faulty Dupont wire.
Debugging tips: If stuck on Device Detection Error, you may "listen to the bus" at the MCP2221 end and see if there's any activity on the I2C bus. Since I2C is a shared bus, other system activities will be visible on the wire. In my case, I saw clock activity on SCL but no activity on SDA when there was SCL, which led me to the conclusion that my SDA wire was faulty.
Thank you @RolloZ170 for the awesome tool and @PandaChan for the detailed walkthrough. I have nothing to add.
I chose to solder a header on to it. Yet I spent a huge amount of painful time debugging (downgrading BIOS, etc.) until I finally traced the problem to a faulty Dupont wire.
Debugging tips: If stuck on Device Detection Error, you may "listen to the bus" at the MCP2221 end and see if there's any activity on the I2C bus. Since I2C is a shared bus, other system activities will be visible on the wire. In my case, I saw clock activity on SCL but no activity on SDA when there was SCL, which led me to the conclusion that my SDA wire was faulty.
Thank you @RolloZ170 for the awesome tool and @PandaChan for the detailed walkthrough. I have nothing to add.
Last edited:
Thank you！
According to the method you described, I successfully used 8259CL on x11dai-n.
but the D1 and D2 memory modules on CPU 2 were mapped out.
The CPU bases on the CPU and motherboard were fine (repeatedly reinstalled and swapped), and all memory modules were recognized before upgrading to 8259CL.
because of reachiing ECC error thresholds. clean contacts of CPU and DIMM.
maybe channel D of your 8259CL is broken.
edit:
to get back the mapped out RAM slots you need a full clear CMOS and NVRAM.