BertoldVdb / ms-tools

Program, library and reference designs to develop for MacroSilicon MS2106/MS2109/MS2130 chips.
MIT License
117 stars 10 forks source link

There's a windows tool capable of doing the vid&pid modifications mentioned here (MS21XX&91XXDownloadTool_1.7.0_BUILD20221024): https://twitter.com/aaaarrrriaaannn/status/1678837967756902404?t=u_ezQ04APCLDtlgRT5tYlA&s=19 #11

Closed parbzip closed 1 year ago

parbzip commented 1 year ago
          There's a windows tool capable of doing the vid&pid modifications mentioned here (MS21XX&91XXDownloadTool_1.7.0_BUILD20221024): https://twitter.com/aaaarrrriaaannn/status/1678837967756902404?t=u_ezQ04APCLDtlgRT5tYlA&s=19

Originally posted by @matiaspl in https://github.com/BertoldVdb/ms-tools/issues/9#issuecomment-1631819412

Is it convenient to give the tool download address, thank you

ariankordi commented 1 year ago

Hi I posted this, here’s some mirrors to a zip with the tool: https://cdn.discordapp.com/attachments/1021093985432895568/1100633845218410527/MS2130.zip

https://mega.nz/file/HfpAnIzB#UY7eqQpnL4wJM2C5Lne6Y_5GpIF37_AqLIG4hosE0sk

Enjoy.

tablesturn commented 8 months ago

@ariankordi Can you tell us which device driver you installed to use the .exe?

I am trying to get the firmware of a MS9122 (VID345F PID9132, just like the MS9132) by using the WinUSBDisplay_Windows_V3.1.5.75 driver but the software can't connect to the device.

I also tried a generic LibUSB driver which didn't work, too. Maybe the .exe checks if it actually is a MS9132, or I am just using the wrong Windows driver.

tablesturn commented 8 months ago

@ariankordi Never mind, the WinUSBDisplay_Windows_V3.1.5.75 driver works after (partially) patching my MS9132 to be a MS2106 (which seems to have broken some things haha) using the ms-tools cli, modified to assume that the device is a MS2106.