Contribute
Register

Thunderbolt 4, modified firmware, Full Thunderbolt Bus tree

Thanks for the input!
OK, so I have to get a CH341A programmer. I was researching in other forums to see if someone with the same motherboard had done it previously, but I guess I would be the first!
Motherboards can be tricky to work with. It may be best to remove/disconnect all devices before attempting to read or write the flash ROM. This includes GPU, NVMe SSDs, DRAM modules. Fans should be disconnected from the fan headers (but no need to remove the fans themselves).

Of course you may try first without disconnecting or removing these components. But if the CH341a cannot find and read the chip after multiple attempts, then it would be necessary to remove/disconnect all components.
 
Motherboards can be tricky to work with. It may be best to remove/disconnect all devices before attempting to read or write the flash ROM. This includes GPU, NVMe SSDs, DRAM modules. Fans should be disconnected from the fan headers (but no need to remove the fans themselves).

Of course you may try first without disconnecting or removing these components. But if the CH341a cannot find and read the chip after multiple attempts, then it would be necessary to remove/disconnect all components.
got it! thanks for the advice
 
having problems accessing the site
Use the "contact us" link at the bottom of this page. Let the Admins know your IP address that is blocked.

Screenshot 1.jpg
 
@CaseySJ @gandem
I have attached GC-Maple Ridge firmware with port@C & port@D enabled (2 Downstream USB4 ports)... like on my firmware.. We could have another behaviour on Sleep ?!
I flashed this version of firmware yesterday, but alas no change. The saga continues... ;)
 
Hello @CaseySJ
:) pretty difficult to solve this Sleep issue...

Could you try this patch ? :
  • identifiers: com.apple.driver.AppleThunderboltNHI
  • comment: replace Go2Sx to Go2Sx_No_Wake for PCIE2TBT (Ventura & Sonoma)
  • find: 0083C64C 4889C7BA 05000000
  • replace by: 0083C64C 4889C7BA 07000000
If nothing solved :
  • Could you try GC-MapleRidge on a mobo without TBTHeader/TBT capability ?
  • Could you try GC-MapleRidge on a compatible mobo with TBTHeader plugged (compatibility attached)?
Capture d’écran 2024-04-09 à 20.01.59.png
 
Hi @Elias64Fr,

I’ll try this patch soon.

I also decided to order an ASRock Thunderbolt 4 AIC. It’s not available in the United States so I ordered it from an online retailer in Germany (I have purchased from them before).

Update: Same sleep issue! It also seems that previous DROM without ports 0xC and 0xD works better in that system does not reboot on second/third auto-wake from sleep.
 
Last edited:
Thank you @Elias64Fr and @CaseySJ for all your efforts and time spent on this topic. I just want to provide another few data points for you all to consider:

  • ProArt Z790-Creator
  • Onboard Thunderbolt4 enabled in BIOS
  • BIOS version: PROART Z790-CREATOR WIFI BIOS 2102
  • config.plist kext patches NOT enabled
  • Thunderbolt firmware version NVM38 (UNPATCHED)
  • SSDT for Thunderbolt4 enabled (see attached)
  • Sleep WORKS
  • System Information > Thunderbolt/USB4 show enabled Thunderbolt bus
  • System Information > Thunderbolt/USB4 Thunderbolt bus updates port speed from Up to 40Gb/s x1 to Up to 10Gb/s x 2 when Thunderbolt 10GBE adapter is plugged in
  • System Information > PCI devices + Ethernet show Thunderbolt 10GBE adapter
  • ioreg registers hot plug of Thunderbolt 10GBE adapter
Happy to pull any requested diagnostic information in order to help progress this topic forward.

System Information.png


Thunderbolt bus after hot plug.png


PCI devices after hot plug.png


Ethernet devices afrer hot plug.png


No matter what I tried, flashing any type of firmware (modified or original) for Thunderbolt from UEFI shell would always fail. Primarily the error was
Code:
cant find file NVM.bin
or
Code:
cant find file XXX.bin
where XXX.bin is whatever path I input for the location of the firmware. I can assure you the firmware files were on the filesystem and could be access through the UEFI, however trying relative and absolute paths to the firmware files yet it would throw the error.

I can't explain why it seems to be working in some capacity. Not sure if this will be of assistance or not.

Thank you,

Michael
 

Attachments

  • SSDT-THB4-RP05.aml
    2.1 KB · Views: 36
Hello @Inmike09,

Welcome to this party!

One quick question before I ask or say anything more: Which version of macOS are you running?

Is it Big Sur?
 
Hello @Inmike09,

Welcome to this party!

One quick question before I ask or say anything more: Which version of macOS are you running?

Is it Big Sur?
Thanks @CaseySJ !

So I am running latest Sonoma 14.4.1.
 
Back
Top