Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.

handheldgames

macrumors 68000
Apr 4, 2009
1,939
1,169
Pacific NW, USA
Post edited to remove any possible confusion about it.

144.0.0.0.0 diffs from 142.0.0.0.0 with 0 insertions, 8 deletions and 39 modifications.

One thing that got my attention was the first time Apple updated AppleGraphicsPolicy.efi since I'm tracking the modules differences between BootROM releases.

View attachment 834729 View attachment 834730


Everything that changed between 142.0.0.0.0 and 144.0.0.0.0, sorted by GUID order:

Code:
18CEC42B-F0FC-4EFA-84AE-27D2184E873A - ??
2374EDDF-F203-4FC0-A20E-61BAD73089D6 - IoTrap
240612B7-A063-11D4-9A3A-0090273FC14D - UsbBus.dxe
2FB92EFA-2EE0-4BAE-9EB6-7464125E1EF7 - UhciDxe
35B898CA-B6A9-49CE-8C72-904735CC49B7 - DxeMain
4CF484CD-135F-4FDC-BAFB-1AA104B48D36 - HfsPlus.efi
4D37DA42-3A0C-4EDA-B9EB-BC0E1DB4713B - PpisNeededByDxeCore.pei
7EC21E57-CE8A-4FDE-B147-0F7C0959CD3F - ??
8A107CC5-DCDA-4FB7-A272-4243B41AFBFE - AppleGraphicsPolicy.efi
8E6BD67D-1872-4932-A39A-FC9DCA4A98CF - ??
A1F436EA-A127-4EF8-957C-8048606FF670 - UndiRuntimeDxe
AB8DDBAA-9C47-429B-9D12-326F273D9B88 - ??
ABBCE13D-E25A-4D9F-A1F9-2F7710786892 -- Platform
B0D6ED53-B844-43F5-BD2F-61095264E77E - PchSmiDispatcher
B2CB10B1-714A-4E0C-9ED3-35688B2C99F0 -- public keys
BB1FBD4F-2E30-4793-9BED-74F672BC8FFE - PchResetRuntime
BB65942B-521F-4EC3-BAF9-A92540CF60D2 - SataController
C194C6EA-B68C-4981-B64B-9BD271474B20 - PchSpiRuntime.efi
C3E36D09-8294-4B97-A857-D5288FE33E28 - BIOS version
CC582C73-F48F-4B62-83E8-A586B4C88F84 - AppleFirmwareFeatures.efi
CFFB32F4-C2A8-48BB-A0EB-6C3CCA3FE847 - APFSJumpStart
DF9A9591-B646-4621-AF0D-18143A73289F - LegacyBootFS.efi
E052D8A6-224A-4C32-8D37-2E0AE162364D - PchSmbusDxe
EF0C99B6-B1D3-4025-9405-BF6A560FE0E0 - SmbiosMisc
FC1B7640-3466-4C06-B1CC-1C935394B5C2 - PchSerialGpio

144.0.0.0.0 have changes on various subsystems and seems a great update without any unintended problems identified until now.

IMO... The changes look positive. Changes to AppleGraphicsPolicy , APFSJumpStart, SataController and SmbiosMisc lines up with addressing the issue @crjackson2134 has been battling against for some time. Now if Apple can get MS to clean up their EFI mess.... Has anyone thought of entering bugs @ microsoft in Redmond WA for the EFI disaster they are causing??
 

tsialex

Contributor
Original poster
Jun 13, 2016
12,946
13,169
Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin shasum from MP51.007F.B03 to 144.0.0.0.0:

Code:
741777e4655c55e60c89f71d96ca71064858f674  ./7F/MP51_007F_03B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674  ./83/MP51_0083_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674  ./84/MP51_0084_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674  ./85/MP51_0085_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674  ./87/MP51_0087_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674  ./89/MP51_0089_00B_LOCKED.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
e57e098eb14b6448c7d225155977b53faa8434a7  ./138/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
ab6c04d2d19908ad545c272566cf2b916fa028d1  ./139/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674  ./140/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674  ./141/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
741777e4655c55e60c89f71d96ca71064858f674  ./142/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin
e57e098eb14b6448c7d225155977b53faa8434a7  ./144/MP51.fd.dump/Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.bin

Section_PE32_image_8A107CC5-DCDA-4FB7-A272-4243B41AFBFE_body.png

Someone with IDA Pro license should take a look on the exact function of the table that Apple has been changing with 138/139/144.0.0.0.0.
 
Last edited:
  • Like
Reactions: dabotsonline

mrtang42

macrumors member
Apr 19, 2019
73
18
IMO... The changes look positive. Changes to AppleGraphicsPolicy , APFSJumpStart, SataController and SmbiosMisc lines up with addressing the issue @crjackson2134 has been battling against for some time. Now if Apple can get MS to clean up their EFI mess.... Has anyone thought of entering bugs @ microsoft in Redmond WA for the EFI disaster they are causing??
We actually got contact by Apple regrading on this issue. I only know the other group still put this project on hold since last time I talked to them. I have no idea why.
 

tsialex

Contributor
Original poster
Jun 13, 2016
12,946
13,169
Continuing from #3307, #3308, #3311 and #3314. EFI version and BIOS versions are working now:

binwalk - Spacedust.png


I'll probably improve BIOS version later on, for now I'm getting every char as a byte one by one, since it's not a string.

EFI version weirdly is a string.
[doublepost=1556812247][/doublepost]
binwalk - MP41_0081_07B_LOCKED.fd.png
 
  • Like
Reactions: zoltm and h9826790

bsbeamer

macrumors 601
Sep 19, 2012
4,306
2,702
I wonder if they can improve Mac Pro itself boot time. It tooks nearly 15 seconds to see anything on screen. PC's start much faster.

Wouldn't count on it. If any improvements, they're likely accidental or coincidence vs. actually trying to improve boot times. If you have NVMe system drive, it will slow boot down but easily makes up for it with system operation. Personally cannot complain about the boot times on my authentic MP5,1 with NVMe and RX580 in Mojave. Find it slightly faster than High Sierra. I basically turn this machine on/off once per day at most, so it's not a big deal.
 

Nabru50

macrumors member
Aug 24, 2017
42
61
United States
I wonder if they can improve Mac Pro itself boot time. It tooks nearly 15 seconds to see anything on screen. PC's start much faster.

It is my understanding that this is due to more system memory. My 16GB 2009 Mac Pro takes about 10 seconds to get the chime, while my 2GB 2007 Mac mini takes about 2.
 
Last edited:

crjackson2134

macrumors 601
Mar 6, 2013
4,822
1,948
Charlotte, NC
It is my understanding that this is due to more system memory. My 16GB 2009 Mac Pro takes about 10 seconds to get the chime, while my 2GB 2007 Mac mini takes about 2.

It's that, and a little more...

Simply put, the more hardware you have to detect and initialize (memory, PCIe, Storage, etc...), the longer it will take the cMP to boot. Some hardware won't necessarily increase the boot times, but it's a general rule of thumb.

Don't expect the BootROM to have a great affect on that...
 

pbsxr

macrumors newbie
May 4, 2019
29
1
Hi,
i think I have a general problem in updating firmware.

Mac Pro 4.1>5.1 (currently on 140.0.0.0) w Sappire Radeon7950 mac edition (original)...

But i can‘t install 10.14.4 from a stick. It says fw update required... but the machine did not shut down... manual sutdown does not the trick... even pressing the the button until sound produces just a normal startup with no fw update

any ideas?!
 

tsialex

Contributor
Original poster
Jun 13, 2016
12,946
13,169
Hi,
i think I have a general problem in updating firmware.

Mac Pro 4.1>5.1 (currently on 140.0.0.0) w Sappire Radeon7950 mac edition (original)...

But i can‘t install 10.14.4 from a stick. It says fw update required... but the machine did not shut down... manual sutdown does not the trick... even pressing the the button until sound produces just a normal startup with no fw update

any ideas?!
Read the Upgrade firmware from USB note from MP5,1: What you have to do to upgrade to Mojave.

Blank_00.JPG
Blank_01.JPG
Blank_02.JPG
Blank_03.JPG
Blank_04.JPG
Blank_05.JPG
Blank_06.JPG
Blank_07.JPG
Blank_08.JPG
Blank_09.JPG
 
Last edited by a moderator:

tsialex

Contributor
Original poster
Jun 13, 2016
12,946
13,169
Continuing from #3307, #3308, #3311, #3314, #3355, #3360.

Improvements:

  • hardwareID LBSN/MLB + BuildDate
  • hardwareID HWC
  • hardwareID override-version / Base_xx
binwalk_mattclones.png


Note: this BootROM showed above is the one sent with every matt card, so it's a "public" one cloned numerous times. No personal hardwareIDs here.
[doublepost=1556965185][/doublepost]BTW, more info about the matt clones here: #19
 

tsialex

Contributor
Original poster
Jun 13, 2016
12,946
13,169
the machine was on Mojave:

Boot ROM Version 140.0.0.0.0

SMC Version (system) 1.39f5

SMC Version (processor tray) 1.39f5

Don't make a diff if you already are on Mojave, you still have to download and run the full installer for the current Mojave version, 10.14.4 is the current one, from macOS to upgrade the firmware to BootROM 141.0.0.0.0. USB firmware upgrades don't work.

10.14.0 installer don't ask for a firmware upgrade because it's BootROM is 138.0.0.0.0 and you already have 140.0.0.0.0. 10.14.4 needs 141.0.0.0.0, so it asks you to upgrade the BootROM.

Read the first post of this thread and the first post of MP5,1: What you have to do to upgrade to Mojave, all info you need are in these two first posts.
 
Last edited:
  • Like
Reactions: JedNZ

tsialex

Contributor
Original poster
Jun 13, 2016
12,946
13,169
Why Apple include NVMe EFI modules with Macs that you can't connect a M.2 blade, like late-2012 Mac mini?

binwalk.MM61.tsialex.png


MP6,1 dumps usually have more problems than MP5,1, no news here. MemoryConfig is stored differently than MP5,1, just noticed this for the 1st time.

A tool for MP6,1 NVRAM clean up would be a good idea in the future.

binwalk.MP61.saulinpa.png


MP3,1 has a different BootBlock and MemoryConfig, but most things are the same:

binwalk.MP31.Macschrauber.png

[doublepost=1557020918][/doublepost]Btw, I only have three dumps from MP6,1s and it's not enough for testing. If you have a MP6,1 and want binwalk support for it, please dump the SPI flash with ROMTool and get in touch with me.
 
Last edited:
  • Like
Reactions: dabotsonline

LightBulbFun

macrumors 68030
Nov 17, 2013
2,808
3,125
London UK
I was going to comment on the NVMe thing but i was not sure if you where referring to just 2009-2010 Mac or every Pre 2013 Mac without a PCIe SSD built in

on the 2011-2012 macs its for thunderbolt, if someone plugs in a thunderbolt SSD, more and more of them are NVMe based these days and people will want to boot from them from time to time :)
 

tsialex

Contributor
Original poster
Jun 13, 2016
12,946
13,169
I was going to comment on the NVMe thing but i was not sure if you where referring to just 2009-2010 Mac or every Pre 2013 Mac without a PCIe SSD built in

on the 2011-2012 macs its for thunderbolt, if someone plugs in a thunderbolt SSD, more and more of them are NVMe based these days and people will want to boot from them from time to time :)
Yep, that explains the NVMe EFI module for Macs that are Thunderbolt capable, but don't have a PCIe connection like Mini late-2012.
 

edgerider

macrumors 6502
Apr 30, 2018
281
149
@tsialex :
you can actually have several m2 nvme ssd on any mac with thunderbolt with a pcie chassis since HS. including 2012 macmini.
it is very used in video specially with notebook and minis, were there is no way to have fast internal storage.
 
  • Like
Reactions: Synchro3

tsialex

Contributor
Original poster
Jun 13, 2016
12,946
13,169
So since now we now which part is responsive for the RAM configuration, maybe it would be easier to bypass the 8 slots limitation on the xserve
No, nothing changed. This was always known, it's the memory configuration for each DIMM, not the EFI module responsible for doing the setup or reading the NVRAM after that.

@tsialex :
you can actually have several m2 nvme ssd on any mac with thunderbolt with a pcie chassis since HS. including 2012 macmini.
it is very used in video specially with notebook and minis, were there is no way to have fast internal storage.
Yes, makes sense that every Mac with Thunderbolt can boot from NVMe.
Blank_00.JPG
Blank_01.JPG
Blank_02.JPG
Blank_03.JPG
Blank_04.JPG
Blank_05.JPG
Blank_06.JPG
Blank_07.JPG
Blank_08.JPG
Blank_09.JPG
 
  • Like
Reactions: dabotsonline

angelsevov

macrumors newbie
Jun 29, 2006
22
12
Why Apple include NVMe EFI modules with Macs that you can't connect a M.2 blade, like late-2012 Mac mini?
View attachment 835327

MP6,1 dumps usually have more problems than MP5,1, no news here. MemoryConfig is stored differently than MP5,1, just noticed this for the 1st time.

A tool for MP6,1 NVRAM clean up would be a good idea in the future.

View attachment 835328

MP3,1 has a different BootBlock and MemoryConfig, but most things are the same:

View attachment 835331
[doublepost=1557020918][/doublepost]Btw, I only have three dumps from MP6,1s and it's not enough for testing. If you have a MP6,1 and want binwalk support for it, please dump the SPI flash with ROMTool and get in touch with me.

Hi @tsialex, i couldnt send you a DM so ill try here.
i have a MP6,1
3,5 GHz 6-Core Intel Xeon E5

and MP5,1 Mid 2010
2 x 3.33 GHz 6-Core Intel Xeon
(which have win 7 and 10 on it (bios mode)) and wanted to share SPI dumps with you.

my SPI is MX25L3205D on cMP and dumped to a bin file.

but for MP61 where is this chip located? which one is right one?
Screenshot-2019-05-05-at-12.43.46.png
 

nos1609

macrumors member
Jun 8, 2015
40
26
Moscow
No, nothing changed. This was always known, it's the memory configuration for each DIMM, not the EFI module responsible for doing the setup or reading the NVRAM after that.
@tsialex Can you please point me where to seek for the dimm slot config?
photo_2019-05-05_15-41-31.jpg
Here is a difference between the two roms with the MemoryConfig explicitly defined.
googling for module description I have only found out that SaveMemoryConfig is responsiblefor writing the config to nvram, while MemorySubClass reads the currently installed DRAM config. So the only possible MemoryConfig -aware module in the firmware is the UncoreInitPeim. But inside the module is the hex config which I barely able to understand as you might see:).

Since MP5,1 ROM successfully boots up on XS3,1 with the only issue being the 8 out of 12 RAM slots operational, I suppose that is easier fixing that isuue rather then trying adding the microcode etc. I currently have two quadcore logicbords to test with, and a dualcore logicboard on the way, and since I recently purchased a CH341a I am not afraid of bricking at least on of the mobo during such severe tests...
[doublepost=1557061222][/doublepost]
Hi @tsialex, i couldnt send you a DM so ill try here.
i have a MP6,1
3,5 GHz 6-Core Intel Xeon E5

and MP5,1 Mid 2010
2 x 3.33 GHz 6-Core Intel Xeon
(which have win 7 and 10 on it (bios mode)) and wanted to share SPI dumps with you.

my SPI is MX25L3205D on cMP and dumped to a bin file.

but for MP61 where is this chip located? which one is right one?
Screenshot-2019-05-05-at-12.43.46.png
According to this, it is the second option you might chose
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.