Incomplete recovery of bricked Synaptics VMM2322 MST hub from backup eeprom dump #3562
Replies: 3 comments 1 reply
-
|
Did you use Intel GPU for the connection? Which CPU? Any other GPU probably won't work with a bricked MST Hub because the dp aux device for those other GPUs won't appear for the port that has the MST hub unless a display is connected to the MST hub - and you can't do that with your bricked MST Hub. In the case of an Intel GPU, the three DP aux devices are always present even if nothing is connected to them. I guess it's a GPU driver choice? I see you used 1.5.8. I wonder if compiling 1.6.1 or whatever the current version is would change anything. The bugged rom is just 64K of 0xFF bytes. The two other roms appear to be valid. At least they have a similar format, with a EDID at the beginning. I don't have any info about what a firmware file should look like and I can't say if they're compatible with each other. I only have the firmware files for the newer MST hubs I have (VMM5xxx). They are 512K in size with 128K being mostly duplicated in each. Your 64K roms don't appear to have a duplicated part, but at least the first couple K bytes are similar. The Tesla firmware does not have the 0xFF padding at the end to make the file an even 64K like the original rom does. I don't know if it matters. I found the VmmDPTool.exe at a https://kb.cablematters.com/index.php?View=entry&EntryID=147 |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, Intel graphics on an i5 2400. Couldn't install 1.6.1 because I couldn't download some of the necessary python programs to build it. The two firmware I had attempted to install came with version history notes that included the number of the fimrware on my Sunix (2.15.002), so that's why I thought they might be compatible and would be worth a shot. But I guess the second number, |
Beta Was this translation helpful? Give feedback.
-
|
Hi. wich adapter from StarTech with vmm2326 did you try? |
Beta Was this translation helpful? Give feedback.
-
On the cable: In the tool output: |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I eventually fixed my problem by using a combination of fwupd followed by vmmDPtool and vmmUpdater in Windows, but I thought I should give a synopsis of what did and didn't work.
thanks to @joevt for helping me use fwupd
Describe the bug
Used
--install-bloband--ignore-vid-pidto attempt to install the original factory .eeprom file to a bricked Sunix DPU3000. Received the following error:Steps to Reproduce
I'll just give you the full history of events.
I was trying to use vmmUpdater in Windows to install different firmware on my Sunix DPU3000 to see if I could solve some if its problems with certain resolutions and refresh rates.
The firmware weren't intended for this hub, but they were designed for devices that used the Synaptics vmm2322 chipset, like Lenovo and HP docks.
Before I attempted to install anything, I used VmmDPTool, found in the Windows Store, to make a backup of my original eeprom.
Here is the original firmware and info dump: Sunix DPU3000 orignal firmware.zip
I tried various firmware, and eventually caused a significant brick where the hub's power light wouldn't turn on, and the hub could no longer be detected by my graphics card or the Synaptics software.
Here is the firmware responsible for the brick:
Lenovo vmm2322 2.24 firmware.zip
So then I tried to use fwupd to restore the orignal .eeprom file.
Just using 'install-blob' I would get a board mismatch error:
I had to use
--ignore-vid-pidto get around this, and the install started but ultimately failed with this error:However, this failed install did put the Sunix hub in a state where it could now be detected in Windows by GPU's and Synaptics software again.
At this point, I made another dump via VmmDPTool to see what went wrong during the install with fwupd, and got these files:
Bugged install from fwupd.zip
Notice that in the info dump, the firmware name and version are blank.
At this point, I was able to use vmmUpdater in Windows to correctly install the orignal firmware, and the MST hub was fully functional again.
So in the end, fwupd did save the Sunix by at least getting it to a point where it would communicate with Synaptics Windows app again
fwupd version information
1.5.8 with Ubuntu 21.04
Beta Was this translation helpful? Give feedback.
All reactions