Need help to interpret log

Hello everyone. I am repairing macbooks and other laptops and i recently found a tool to read raw Intel EFI debug log. It is clear what GUID mean, however i am trying to understand codes in one particular section:

Apple ROM Version
  BIOS ID:      MBP152.88Z.F000.B00.2304171349
  Model:        MBP152
  EFI Version:  1968.120.12.0.0
  Built by:     root@pdffq
  Date:         Mon Apr 17 13:49:03 2023
  Revision:     1968.120.12 (B&I)
  ROM Version:  F000_B00
  Build Type:   Official Build, RELEASE
  Compiler:     clang-1403.0.22.11
  UUID:         66EFDDF7-633C-31D9-86CA-9391E39C4181
  UUID:         29CAAA43-487B-3043-9071-66E993407C55
Hardware Info
  CPUID 0x806ea [MCU 0xf100000000]
   SA DID/RID 0x3ed0/0x08
   GT DID/RID 0x3ea5/0x01
  PCH DID/RID 0x9d84/0x30
#[PEI|+]
#[PEI|D] 001 9B3ADA4F-AE56-4C24-8DEA-F03B7558AE50
#[PEI|D] 002 AE265864-CF5D-41A8-913D-71C155E76442
#[PEI|D] 003 4F1F379F-2A62-48BB-AC34-D3F135C6E2B7
#[PEI|D] 004 38317FC0-2795-4DE6-B207-680CA768CFB1
#[PEI|D] 005 8412DBD9-2C5C-11E7-891E-B8E8562CBAFA
#[PEI|D] 006 A3C7A8BA-094A-47C6-9F66-F6DE5E42A6E7
#[PEI|D] 007 1B99796D-2A26-437E-BEE0-014F0EBBECE1
#[PEI|D] 008 36544866-6D93-7A48-88FB-669582D2516B
#[PEI|D] 009 D9CF9BEB-86D9-11E4-91D0-B8E8562CBAFA
#[PEI|D] 010 2943220C-BC8D-457B-9533-20979FEC8318
#[PEI|D] 011 649760C0-B779-4383-93E9-0C7F9416A6DA
#[PEI|D] 012 2FAC2694-400C-480C-844F-4EC474DD3A2B
#[PEI|D] 013 3FB1A55F-DDEF-42D9-8FAF-891039769F8D
#[PEI|D] 014 A1F39391-B841-4C3E-A458-71E312DD6CB9
#[PEI|D] 015 EEEE611D-F78F-4FB9-B868-55907F169280
#[BTPU]
#[RS3M] P 75541000 180000 3F7000000
#[PEI|D] 016 A8499E65-A6F6-48B0-96DB-45C266030D83
#[0x80] 0x0000dd00
#[0x80] 0x0000dd1e
#[0x80] 0x0000dd20
#[0x80] 0x0000dd21
#[0x80] 0x0000dd22
#[0x80] 0x0000dd23
#[0x80] 0x0000dd24
#[0x80] 0x0000dd26
#[0x80] 0x0000dd27
#[0x80] 0x0000dd29
#[0x80] 0x0000dd28
#[0x80] 0x0000ddff

module 015 A8499E65-A6F6-48B0-96DB-45C266030D83 which is = SiInitPreMem
is most likely responsible for initializing CPU and its power system.
I have a board i am trying to pull data from, and i already replaced CPU from known working system, it did not solve the issue. After that i put CPU back on working board and it solved the problem. I already recovered data by other method but i was interested in figuring out how to interpret #[0x80] 0x0000dd** codes. Non working board stalls with code ddff
i have two questions:

  1. did someone ever seen such logs and if there is documentation from that. It is not particularly PCH debug(debug seems to be disabled on apple machines if you look up the ME config), however it works through USB 2.0 interface, via UART at 125Mbod.
  2. is there a way to produce such log on other platform, i mean, it should definetely be configurable by editing ME/PCH configuration. This log is also partially rendered if you press CMD+V at power of any intel mac.

this would probably be a huge step in intal Mac as well as Laptop repairs because it would potentially provide much more than any POST card or similar. I also believe it will help in modding since you can clearly see whole init process till it gives control to MacOS kernel
I will attach a log of a working machine:

Search results for ‘A8499E65-A6F6-48B0-96DB-45C266030D83’ - Win-Raid Forum (level1techs.com)

EDIT:
Its is what it is… take as you want and make your owns conclusions.
I just pointed you some reading about it, nothing more.
Go read EDK PEI structure initialization
Good luck with it.

i do not see how could it help me to figure execution codes of this module.
It might also include SPD profile / strap recognition. However, this board had known good CPU and known good RAM. i also checked if there are any broken traces between CPU and RAM.