Some awesome hackery going on there! You should have made a video or something.
Although this part didn't make much sense to me - "I examined both rom dumps and tried to stitch them together (at the end of this project I realized it was of no need)." - stitch them?
"After flashing the custom rom onto the chip using a Universal rom programmer it was soldering time." - So the 2010 MP ROM needs to be flashed on to the 2009 MP chip or you actually just modified the 2009 ROM?
So the only difference between the 2009 and 2010 models is EFI rom chip has microcode to support new B1 stepping processors on the 2010?
Go to netkas.org, someone made an app to do this without even opening your mac pro![]()
Go to netkas.org, someone made an app to do this without even opening your mac pro![]()
So what do you need to make your 2009 Mac Pro a 2010 Pro??
- Access to both 2009 and 2010 Mac Pro
- A soldering iron
- A hot air blower
- Solder/desoldering skills
- EPROM Reader/Programmer
- Solder
- New CPU's to test it out
- A lot of time in your hands and patience
Go to netkas.org, someone made an app to do this without even opening your mac pro![]()
I would be willing to upgrade my 2009 to 6 cores but there seems to be a problem with memory not running at the right speed. Can anyone confirm they used netkast app with 2009 and has 6 cores and memory running right?
-Thanks
I'm ready to try this upgrade, i'm just unsure which westmere processores to use in my 09 mac with 2x2.26ghz. Is it the EP versions? Do I have to be carefull with the TDP's?
Kudos to other poster @netkas.org. I have a software solution as well (different way than his) I'm not releasing it because it contains apple copyrighted material, as well as his. He must be careful
Kudos to other poster @netkas.org. I have a software solution as well (different way than his) I'm not releasing it because it contains apple copyrighted material, as well as his. He must be careful
His application downloads the firmware from apple's site.
P.S. have you noticed any problems with your "update"? assuming you only did the flash.
There is a user stating:
Amazing stuff! But here's a strange thing, running Mac Pro EFI Update 1.5 (for the 2010 Mac Pro) brings up a 'This software is not supported on your system.' alert box, whilst EFI Update 1.4 (for the 2009 Mac Pro) brings up 'This computer does not need this update.'. So even after applying the EFI Upgrade the Mac Pro is still somehow identifying itself as a 2009 model, despite System Profiler showing 'MacPro5,1'.
His application downloads the firmware from apple's site.
P.S. have you noticed any problems with your "update"? assuming you only did the flash.
There is a user stating:
Amazing stuff! But here's a strange thing, running Mac Pro EFI Update 1.5 (for the 2010 Mac Pro) brings up a 'This software is not supported on your system.' alert box, whilst EFI Update 1.4 (for the 2009 Mac Pro) brings up 'This computer does not need this update.'. So even after applying the EFI Upgrade the Mac Pro is still somehow identifying itself as a 2009 model, despite System Profiler showing 'MacPro5,1'.
Stitching is the combining of different parts. This would involve knowing what binary is what, which is essentially impossible, so he'd have had to reverse engineer the ROM dumps (decompile the binaries into pseudo code to know what's going on, then write a new ROM based on both of these, and recompile). Not easy to do.Although this part didn't make much sense to me - "i examined both ROM dumps and tried to stitch them together (at the end of this project i realized it was of no need)." - stitch them?
"after flashing the custom ROM onto the chip using a universal ROM programmer it was soldering time." - so the 2010 mp ROM needs to be flashed on to the 2009 mp chip or you actually just modified the 2009 ROM?
I had suspected the EFI Update Util didn't write the entire ROM. Only Foxconn did this during manufacturing, thus keeping the MP Identifier data in tact for any subsequent flashes via the Update Utility. But perhaps this isn't the case, and it starts from the beginning address on the ROM, not an offset address (would make it a lot easier to write an EFI Update Utility IMO).I did look into making a EFI flashing utility several times, and i always knew the apple updater probably wasn't doing anything complicated.
Finally someone figured it out.
Unfortunately this isn't the case, as that's dictated by the chipset. DP systems don't use the X58, and although the 5520 is an X58 with a second QPI, it cannot shut down a QPI link. DP CPU's can, and is why they'll work on an X58 board.I'm wondering if a single w3680 would work on a DP board...
Depends on how he did it from what I understand of IP laws. If there was no reverse engineering/modification of Apple's IP (i.e. came up with the Update Utility totally on his own), it's legal (maybe an IP attorney could opine on this, as it's like walking a mine field).kudos to other poster @netkas.org. I have a software solution as well (different way than his) I'm not releasing it because it contains apple copyrighted material, as well as his. He must be careful
You'd need to do a flash of the SMC ROM on the backplane board.The only problem i have is 2009 mac pro serial with 2010 mac pro firmware = voided applecare, also 2010 aht and asd not running as they validate against smc firmware which I'm still working on.
Unfortunately this isn't the case, as that's dictated by the chipset. DP systems don't use the X58, and although the 5520 is an X58 with a second QPI, it cannot shut down a QPI link. DP CPU's can, and is why they'll work on an X58 board.
someone with W3570/3580 may apply this upgrade an test wether or not the RAM clock speeds up to 1333 MHz (if provided by the modules).
Damn it. Thanks for the info.
Time to figure out what would be cheaper, a single 5600 series CPU (which will work on the DP system), or a 3600 CPU with a new daughter board.
Can't wait for someone to confirm the update utility.