[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[gandem]

This may be coming from 10.15.4 itself when multiple monitors are attached. As an experiment, please try connecting the two monitors directly to the AMD GPU.

Yes, write it off!

Here's what I get directly out of GPU. No problem getting 60hz. Another interesting observation- If I boot with the 4K monitor hooked up to the dock, the computer will not post giving me 4 beeps. So it appears the patched firmware is preventing the monitor from being detected at boot. Unpatched, computer will post to the 4K monitor hooked up to the dock and I can enter the bios from it.

 

[CaseySJ]

...
Would you have any ideas about why BT wouldn’t show up for me in Mojave, assuming I’m using your lastest Catalina guide? Maybe I’m crazy for using the EFI from my Catalina build.

Let's check a couple of things:

• It's probably a good idea to keep all Hackintosh kexts out of /Library/Extensions even on Mojave because it will make the eventual upgrade smoother in the future. Are any Hackintosh kexts currently installed there?
• Enabling Bluetooth on a Fenvi add-in-card only requires connecting the USB data cable to F_USB and checking IORegistryExplorer --> HS11 or HS12. Feel free to post a screenshot of this.

 

[CaseySJ]

Here's what I get directly out of GPU. No problem getting 60hz. Another interesting observation- If I boot with the 4K monitor hooked up to the dock, the computer will not post giving me 4 beeps. So it appears the patched firmware is preventing the monitor from being detected at boot. Unpatched, computer will post to the 4K monitor hooked up to the dock and I can enter the bios from it.
View attachment 464680

Alas we haven't quite perfected firmware for add-in-cards. Now you see why Elias did not post modified NVM 50 files here. He sent 3 versions by private mail, of which I sent 1 to you. For now I would suggest reverting to the firmware that best suits your needs. Your feedback, though, has been valuable.

 

[gandem]

Alas we haven't quite perfected firmware for add-in-cards. Now you see why Elias did not post modified NVM 50 files here. He sent 3 versions by private mail, of which I sent 1 to you. For now I would suggest reverting to the firmware that best suits your needs. Your feedback, though, has been valuable.

I understand. It looks like NVM 50 does not like video. I tested usb-c to HDMI directly out of the GC-Titan Ridge port, and the HD monitor is not detected, so I don't think that problem is dock related. Have you tried testing the NVM 33 Designare firmware on this card? That was previously mentioned.

 

[bigboosh]

Let's check a couple of things:

• It's probably a good idea to keep all Hackintosh kexts out of /Library/Extensions even on Mojave because it will make the eventual upgrade smoother in the future. Are any Hackintosh kexts currently installed there?
• Enabling Bluetooth on a Fenvi add-in-card only requires connecting the USB data cable to F_USB and checking IORegistryExplorer --> HS11 or HS12. Feel free to post a screenshot of this.

Ive got the kexts in the clover folder and my extensions folder is clean.
got my cable hookd Up! it works in clover when booting, but when I reach the os, it goes bye-bye.
are there any usb enabling differences between your Mojave and Catalina guides? I cant seem to see any.

 

[CaseySJ]

** Micro-Guide for Installing Intel WiFi Driver (Beta) **
Please do not quote this micro-guide in its entirety. Post a link instead.​

In a previous post we described how to install an experimental Intel Bluetooth driver that is being developed by "zxystd".

User @shuhung posted a beta version of an Intel WiFi driver here (and attached below) that is originally from a Chinese website. It supports the on-board Intel WiFi AC-9560 (CNVi) on the Designare motherboard, and a number of other Intel WiFi chipsets. Early experience shows about a 20% increase in transfer rate compared to Fenvi FV-T919.

This message is being posted with the use of native Intel CNVi WiFi and kext.

Prerequisites:

• The Intel CNVi module that is preinstalled on the Designare Z390 motherboard should be present. Some users have intentionally removed the module, so those users should reinstall it.
• This procedure applies to most Gigabyte Z390 motherboards with on-board Intel CNVi WiFi/BT modules.
• OpenCore users can follow the same procedure below, but make changes in the appropriate places inside the OpenCore folder.
• Connect the outboard antenna that comes inside the Designare Z390 box. The antenna should be connected to the two ports on the rear IO panel.
  

Limitations:

• This driver is in early development stage. As such, we must manually enter our WiFi network name (SSID) and password into the Info.plist file inside the kext. Instructions below.
• It will not scan for all available networks.
• Certain functions such as Handoff will not work.
• The purpose of this post is to allow users to experiment with the driver and help support its development.

Procedure:

• Download the Intel WiFi driver attached below. The driver is still in development stage.
  • Unzip the file if it does not unzip by itself.
  • But do not copy it to CLOVER/kexts/Other. We will inject it manually below.
• Mount EFI partition of the macOS SSD.
  • Move the file SSDT-DESIGNARE-Z390-NO-CNVW.aml from CLOVER/ACPI/patched into the CLOVER/misc folder. This means the file is removed from CLOVER/ACPI/patched and exists in CLOVER/misc.
    • This step is necessary to make the Intel WiFi module visible to macOS.
  • If you have a Fenvi or any other WiFi/BT card in the bottom short PCIe x1 slot (RP04), then:
    • Download and copy the attached SSDT-DESIGNARE-Z390-NO-FENVI-RP04.aml to CLOVER/ACPI/patched.
    • This will turn off any device in the bottom short PCIe x1 slot.
  • If you have a third-party WiFi card in any other slot and wish to try the native Intel WiFi driver, please let me know.
• Reboot and log in.
• Locate AppleIntelWiFi.kext. Let's assume it's in the Downloads folder.
• Now let's prepare the kext:
  • Using Finder, right-click on the kext and select Show Package Contents.
  • Now you'll see a file called Info.plist.
    
  • Edit that file with a text editor or plist editor (such as CorpNewt's ProperTree).
  • Enter your WiFi network name (SSID) and WiFi network password in the fields shown below:
    
  • Save the file.
• We're ready to manually inject the kext now.
  • Run Terminal and type the following (which assumes the driver is in your Downloads folder):

cd ~/Downloads
sudo chown -R root:wheel AppleIntelWiFi.kext
sudo kextload AppleIntelWiFi.kext

• That's it. WiFi should activate and connect to your network in about 10-20 seconds. But allow up to 1 minute.
• NOTE / WARNING:
  • The 3 Terminal commands above must be issued each time the system boots. When the driver is further along in its development this won't be necessary.

Verification:

• To check if the new WiFi driver is active, run IORegistryExplorer and find CNVW near the top of the device tree. Does it look like this?
  
• Also open System Information --> WiFi and check if WiFi is enabled.
  

Problem Reporting:

• For now, problems can be reported and issues can be discussed in this thread on TonyMac.
• As of April 24 this driver does not support any of the macOS Handoff capabilities.

Edits:

• 24-Apr-2020: First version

 

[NCMacGuy]

Yes their checksums should be the same. Here's the checksum from my original firmware file:

c8d46c49c43da200b7fd7390cc09531e5e7163a4  Gigabyte-Z390-Designare-TB3-ROM.bin

In step 1: When PSU is connected to motherboard with 24-pin cable and PSU is switched on (not motherboard, but PSU), then and only then should Vcc Pin 8 be disconnected.[/code]

@CaseySJ

Yesterday I flashed the TB3 chip on a recently purchased Designare, and the checksums of the reads of the original ROM matched when I read them, but don't match the checksum you reported above.

ad3c229502f9b2abaa70d116069597dccdc3ed5a Backup1.bin

Here's the output from Terminal when I read, then flashed the chip:

victor@raspberrypi:~ $ sudo su
[sudo] password for victor: 
root@raspberrypi:/home/victor# cd /home/victor/Downloads/DESIGNARE2
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup1.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup1.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup2.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup3.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# shasum Backup1.bin Backup2.bin Backup3.bin
ad3c229502f9b2abaa70d116069597dccdc3ed5a  Backup1.bin
ad3c229502f9b2abaa70d116069597dccdc3ed5a  Backup2.bin
ad3c229502f9b2abaa70d116069597dccdc3ed5a  Backup3.bin
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -w DESIGNARE-Z390-NVM33-Elias64Fr.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r New_Flash.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# shasum New_Flash.bin DESIGNARE-Z390-NVM33-Elias64Fr.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  New_Flash.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  DESIGNARE-Z390-NVM33-Elias64Fr.bin
root@raspberrypi:/home/victor/Downloads/DESIGNARE2#

The first Designare TB3 chip I flashed some weeks ago had these checksums before flashing:

root@raspberrypi:/home/victor/Documents# shasum Designare-1.bin Designare-2.bin Designare-3.bin
1809647344696d2bdc8a4982d1171bafb1dfd630  Designare-1.bin
1809647344696d2bdc8a4982d1171bafb1dfd630  Designare-2.bin
1809647344696d2bdc8a4982d1171bafb1dfd630  Designare-3.bin

CaseySJ's checksums, my first flashing checksums, and my second flashing checksums don't match.

Could this because Gigabyte used different ROM code on the TB3 chip over time?

 

[CaseySJ]

@CaseySJ

Yesterday I flashed the TB3 chip on a recently purchased Designare, and the checksums of the reads of the original ROM matched when I read them, but don't match the checksum you reported above.

ad3c229502f9b2abaa70d116069597dccdc3ed5a Backup1.bin

Here's the output from Terminal when I read, then flashed the chip:

victor@raspberrypi:~ $ sudo su
[sudo] password for victor:
root@raspberrypi:/home/victor# cd /home/victor/Downloads/DESIGNARE2
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup1.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
No EEPROM/flash device found.
Note: flashrom can never write if the flash chip isn't found automatically.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup1.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup2.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r Backup3.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# shasum Backup1.bin Backup2.bin Backup3.bin
ad3c229502f9b2abaa70d116069597dccdc3ed5a  Backup1.bin
ad3c229502f9b2abaa70d116069597dccdc3ed5a  Backup2.bin
ad3c229502f9b2abaa70d116069597dccdc3ed5a  Backup3.bin
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -w DESIGNARE-Z390-NVM33-Elias64Fr.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=1024 -r New_Flash.bin
flashrom  on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Winbond flash chip "W25Q80.V" (1024 kB, SPI) on linux_spi.
Reading flash... done.
root@raspberrypi:/home/victor/Downloads/DESIGNARE2# shasum New_Flash.bin DESIGNARE-Z390-NVM33-Elias64Fr.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  New_Flash.bin
edbbe3cbf8e3fa4a9d991e0681f2a5702b248224  DESIGNARE-Z390-NVM33-Elias64Fr.bin
root@raspberrypi:/home/victor/Downloads/DESIGNARE2#

The first Designare TB3 chip I flashed some weeks ago had these checksums before flashing:

root@raspberrypi:/home/victor/Documents# shasum Designare-1.bin Designare-2.bin Designare-3.bin
1809647344696d2bdc8a4982d1171bafb1dfd630  Designare-1.bin
1809647344696d2bdc8a4982d1171bafb1dfd630  Designare-2.bin
1809647344696d2bdc8a4982d1171bafb1dfd630  Designare-3.bin

CaseySJ's checksums, my first flashing checksums, and my second flashing checksums don't match.

Could this because Gigabyte used different ROM code on the TB3 chip over time?

Just logged back into the Raspberry Pi and grabbed the pre-flashed (original) firmware from my main system:

4fabde53555ea20b88d06b58cc02bdd79d9bd390  main-1.bin
4fabde53555ea20b88d06b58cc02bdd79d9bd390  main-2.bin
4fabde53555ea20b88d06b58cc02bdd79d9bd390  main-3.bin

Maybe there are minor differences in DROM or Digital Signature, etc. I can do a byte-for-byte compare if someone wants to post their original bin file.

 

[NCMacGuy]

Thanks @CaseySJ for helping out and thinking along.

During troubleshooting before clearing CMOS, I have saved screenshots of RP05 and a full dump from IOReg on my Desktop. However, since clearing CMOS I was no longer able to boot into macOS, so I can't access those files or create new ones.

My system is currently still disassembled to allow access for flashing. I will try reassembling and booting, but I it's possible/likely macOS still won't boot.

In my flashing attempts I created many ROM backups, with many different checksums. Due to the sheer amount of reads/backups (in total I'm guessing 100+), I deleted backups and reused backup filenames (overwriting existing backups).
I did save some ROM backups in seperate folders though. Based on timestamps and checksums, the earliest consistent backups (from day 1, around the first attempts) have a checksum of 35aa1ad94d61b67556f926184249130f97d1fec8. The last 25 lines of strings Backup1.bin output for that backup are in the spoiler below:

Assuming TB ROM firmwares are identical across Z390 Designare boards, shouldn't their backup checksums also be identical?

If so, if you have a checksum for the original dumped ROM, it's way easier to spot which backup is the correct one. This original ROM checksum would also help in the programming process to know exactly when a read operation extracted the ROM correctly.

@iRamon

Sorry to hear about your difficulties. I have flashed the TB3 chip on two Designaires. I used the Pomona 5250 clip and RPI4 method. The first time the mobo was left in the case with the power cord unplugged. It took me four attempts to finally read and write the chip successfully.

The second time I just purchased a new board and tried to flash it as received, without installing. I attempted to flash about 10 times without success. Perhaps because I had left the pin 8 line not plugged into the RPI4. I gave up and installed the board into the case.

Once the system was running I decided to flash the TB3 ONE LAST TIME, before giving up. Again the power line was unplugged, and pin #8 was not connected -- probably wrong!

It took about five more attempts to finally read and flash the chip. The Pomona clip is very difficult to properly seat!!!

I looked into purchasing CaseySJ's suggested clip, but delivery was 4-6 weeks. I now have one on-order for delivery next month, just in case I ever need/want to re-flash these or other chips.

I supplied the checksums from the original TB3 ROMs in another post. My checksums for the original ROMs do not match between the two boards.

 

[NCMacGuy]

Just logged back into the Raspberry Pi and grabbed the pre-flashed (original) firmware from my main system:

4fabde53555ea20b88d06b58cc02bdd79d9bd390  main-1.bin
4fabde53555ea20b88d06b58cc02bdd79d9bd390  main-2.bin
4fabde53555ea20b88d06b58cc02bdd79d9bd390  main-3.bin

Maybe there are minor differences in DROM or Digital Signature, etc. I can do a byte-for-byte compare if someone wants to post their original bin file.

Here's the TB3 ROM file read from my first Designare board.