Gigabyte Z490 Vision D (Thunderbolt 3) + i5-10400 + AMD RX 580

[CaseySJ]

Hi,

I'm running into a very strange problem :
I flashed the bleu thunderbolt chip on the rear of a Gigabyte Z490 Vision D with a ch341a_spi programmer and Gigabyte-Vision-D-NVM-50-Elias64Fr-CaseySJ.bin. I made a backup of the original ROM.
I tried many versions of OpenCore, and many SSDT (DTGP + Z490TB3 on RP05) as well as many BIOS versions (F5 / F20 / F21 -> I even managed to flash the BIOS back to previous versions from F21 using the manufacturer Tft.efi version CSME System Tools v14.0.20+ r20), but it doesn't change anything.

Thunderbolt shows as : No UID (0x0000000000000000) / 0Gb/s Link speed / unknown_firmware_version etc.
Whatever ROM I use I get this non working Thunderbolt state. Reverting the Original backup doesn't change a thing. Disabling Thunderbolt in BIOS doesn't work either.
I flashed the ROM properly with flashrom (Homebrew installed) and even NeoProgrammer (on Windows with all options to erase and verify).

I tried on BigSur as well as Monterey.
I'm currently running :
• Gigabyte Z490 Vision D (rev1.0)
• BIOS F20
• Monterey 12.6.3

I'm not new to flashing Thunderbolt chips (already flashed an Alpine Ridge and 3 Titan Ridge Gigabyte add on cards) but I'm no expert as well...

Could it be that the chip is fried though it still accepts to be flashed and verify perfectly ?
Any ideas ? Also if someone has the original bin from the Z490 Vision D, I'd love to compare it with my backup.

All the IOreg & config file (OC 0.7.8) and files I used are in the zip attached to this post.
@CaseySJ : Would you be kind and checksum my backup ROM (OriginalFirmware-BlueChip.bin) against yours to see if it matches ?

View attachment 562911
zip content :
View attachment 562915
Thank you in advance,

Paul

Sure, I’ll take a look at the files you posted. Hopefully none of the tiny surface mount resistors and capacitors in the immediate vicinity of the firmware chip has been dislodged. [‘has’ is grammatically correct because ‘none’ is singular]

Feel free to post a close-up photo of the firmware chip in good light. If you’re using a smartphone, remove GPS location information from the photo before posting. One way of doing this is by dragging-and-dropping the photo to https://jimpl.com

 

[pm974]

Sure, I’ll take a look at the files you posted. Hopefully none of the tiny surface mount resistors and capacitors in the immediate vicinity of the firmware chip has been dislodged. [‘has’ is grammatically correct because ‘none’ is singular]

Feel free to post a close-up photo of the firmware chip in good light. If you’re using a smartphone, remove GPS location information from the photo before posting. One way of doing this is by dragging-and-dropping the photo to https://jimpl.com

I had a close look at the chip itself, making shure it's "legs" were properly making contact but I'm not sure about the tiny resistors around. I'll post a picture (free of metadata) as soon as I'm back from lunch. Thanks for your help.

 

[CaseySJ]

HotPlug doesn't work anymore on Monterey (nor does it works on Z390 Designare).

My Z390 Designare has a flashed Thunderbolt controller. Hot plug works for me with both Monterey and Ventura.

 

[Higgie]

Looks like we’ll need to flash our controllers to regain hot plug functionality then? I wonder why it’s broken all of a sudden.

Also, on an unrelated note, I discovered why every time I update OC it breaks my ability to launch Windows via OC. I have a custom entry - when OC updates via HackinDROM right-click method, all the commas get removed from the drive path. So I have to copy and paste the full path from my previous config.plist to get it back again. Is there a way for HackinDROM to pass through the entry as-is?

 

[CaseySJ]

...

All the IOreg & config file (OC 0.7.8) and files I used are in the zip attached to this post.
@CaseySJ : Would you be kind and checksum my backup ROM (OriginalFirmware-BlueChip.bin) against yours to see if it matches ?

...

All of the files you posted look correct, namely:

• SSDT-TB3HP.aml looks fine although after reading the ACPI Spec recently, I discovered that _PRW (power resources for wake) should be adjusted for each motherboard. Currently we're returning (0x69, 0x03), which may be okay for Gigabyte Z490 Vision D. Later I can compare with actual DSDT.aml.
• OriginalFirmware-BlueChip.bin is also correct.

 

[CaseySJ]

Looks like we’ll need to flash our controllers to regain HotPlug functionality then? I wonder why it’s broken all of a sudden.

Also, on an unrelated note, I discovered why every time I update OC it breaks my ability to launch Windows via OC. I have a custom entry - when OC updates via HackinDROM right-click method, all the commas get removed from the drive path. So I have to copy and paste the full path from my previous config.plist to get it back again. Is there a way for HackinDROM to pass through the entry as-is?

Can you post screenshot of the custom entry?

@Inqnuam -- FYI.

 

[pm974]

Comparing my pictures to another found on the web, I find that I'm missing a tiny component :

Here is the missing component that I may have ripped of the board while placing the clamp :

 

[pm974]

My Z390 Designare has a flashed Thunderbolt controller. Hot plug works for me with both Monterey and Ventura.
View attachment 562917

I thought you asked if it worked without flashing, that was my answer, it doesn't (to my knowledge and testings).

 

[pm974]

The question is can I bridge that small gap with a solder joint and hope it works, or will I be doing more harm ?


Comparing my pictures to another found on the web, I find that I'm missing a tiny component :
View attachment 562924

Here is the missing component that I may have ripped of the board while placing the clamp :
View attachment 562925

 

[Higgie]

Can you post screenshot of the custom entry?

@Inqnuam -- FYI.

I can take a screenshot when I am home tonight.