- Nov 11, 2018
- Gigabyte Z490 Vision D
- RX 580
- Classic Mac
- Mobile Phone
Yes that is correct. In fact, this post by @joevt helps to explain why @Elias64Fr and I were not getting the right CRC32_C value. Specifically, this is what we were doing wrong:
This is your SSDT from the Mini Guide for Thunderbolt DROM, with chechum "0x47, 0xDE, 0x1F, 0x21,"
Sorry this is what @joevt told me about the checksum for GIGABYTE Z390 DESIGNARE. so I modified your SSDT
I tried to do the checksum by myself with Sunshine's calculator following what @joevt said: "from byte 13 exclude to the end"
If the checksum of your SSDT
If the checksum @joevt said me is correct so this result is also correct because
0x211FDE47 = 0x47, 0xDE, 0x1F, 0x21,
My scripts converts Suneshins result to 0xFF then insert it in DROM
- Byte 0x0E of the DROM specifies the total length of the DROM.
- The length of DROM begins at offset 0x0D and includes everything from that point forward.
- MacOS seems to compute the DROM length by itself and compares it against byte 0x0E. MacOS also computes the "correct" CRC32_C checksum using the correct length value, so its checksum does not match our checksum.
- Specify the correct DROM length in Byte 0x0E and compute CRC32_C from the sunshine2k.de website. This is based on all bytes of DROM starting with Byte 0x0D.