MS2130 / MS2130S EDID helper
This page helps you work with EDID data inside .bin firmware in the browser: locate a contiguous EDID region per the EDID spec, replace it with a new EDID, then repack and download. All work runs locally; files are not uploaded.
固件 .bin
拖放固件到此处
支持 .bin；须通过块 0 及全部声明扩展块的校验，单段最长 512 字节。任一扩展失败则不可替换。
新 EDID
请先在左侧载入固件。
Supported parts & disclaimer
Target parts: Aimed at MacroSilicon MS2130 and MS2130S firmware layouts for EDID region editing and repacking; use caution with other chips or layouts.
Unofficial: Provided by the UltraSemi project site—not a MacroSilicon or OEM firmware tool; no endorsement from the vendor.
No warranty: No guarantee of detection accuracy, output correctness, or outcomes.
Your risk: You accept full responsibility for device issues, capture/display problems, production impact, or data loss; validate on target hardware before production or customer delivery.
Whole-image checksum: After EDID-only replacement, the whole.binchecksum used in MacroSilicon toolchains may no longer match—common on MS2103, MS2130S flows. If your burn or production line checks the full image, recompute and rewrite the whole-image checksum in MacroSilicon’s firmware download tool (or the vendor’s current equivalent) before use.
| Capability | Description |
|---|---|
| Firmware parse | Load .bin, validate EDID header, block 0, and all extension blocks declared by byte 126 of block 0 via checksum; max single region 512 bytes (4×128). If any check fails, no replaceable region is offered and download is disabled. |
| Block compare | After loading a new EDID, each 128-byte block is shown side by side (firmware vs zero-padded new data) in matching cards. |
| New EDID | Binary file only (drop or pick); must not exceed the selected region length; shorter inputs are zero-padded at the end. |
| Checksums | Each 128-byte block after padding must have a correct block checksum; the tool does not auto-fix byte 127. On failure, repack is blocked with guidance to fix the source. |
| Export | Pack & download is enabled only when firmware checks pass and every new-EDID block checksum passes; output name originalname_edid_patched.bin. |
Steps
Prepare files
Use a legitimate.binfor MS2130 / MS2130S that you are allowed to modify from a trusted source.Load firmware
Drop or pick on the left. The large drop zone collapses to a file strip; use Change firmware to re-pick. Then select an EDID region (offset + length—commonly 128 / 256 / 384 / 512 bytes).Load new EDID
Drop or pick on the right; the zone collapses to a file strip; use Change new EDID to re-pick. A firmware vs new EDID block preview appears below (128 bytes per block).Download
After review, use Pack & download .bin in the bottom action area. If any padded block checksum is wrong, the button stays disabled—fix the source EDID and reload.Reset
Clear all resets firmware and new EDID state for a new batch.
Behavior & limits
- Detection (strict): Find standard EDID header
00 FF FF FF FF FF FF 00; block 0 must pass the 128-byte checksum; read extension count from byte 126 of block 0 (max 3 extensions, total ≤512). Every extension block must pass checksum, and the image must cover the declared span. If any extension checksum fails, the image is too short, or block 0 fails, the region is not offered—no shortened fallback—and no new firmware can be built. - Enable repack: Requires at least one fully valid region and correct per-block checksums for the new EDID after padding; any failure disables pack.
- Write model: Overwrites only the selected offset and length; shorter new data is zero-padded to the same length.
- Not supported: Encrypted/compressed/split/non-standard layouts, or mismatches between byte 126 and the real image so extensions cannot all validate—the tool rejects the region.
Flashing & safety
- Whole-image checksum: This tool only patches the EDID area and does not update the whole-image checksum common on MacroSilicon flows. For MS2103, MS2130S, etc., recompute the whole-image checksum with MacroSilicon’s firmware download tool (or vendor equivalent) before production or burn pipelines that verify the full image.
- Keep the original
.binbackup and record version / hashes (e.g. SHA-256). - First flash on a non-production unit; verify display modes, audio, and stability.
- Signed firmware or secure boot may refuse to boot after edits—assess legality and risk yourself.
FAQ
No EDID found or detection failed?
Typical causes: bad extension checksums, file shorter than declared EDID span, byte 126 not matching layout. The tool will not offer a region and Pack & download stays disabled—inspect the image in a hex editor against the platform guide.
Multiple candidates?
Pick the region that matches documented physical offset / partition; others may be reserved or stale.
Still cannot pack after loading new EDID?
Ensure byte 127 checksum is correct for every 128-byte block after padding; the tool does not auto-correct. Fix blocks in an editor or use a known-good EDID binary.
Conflict with OEM tools?
This is a standalone helper; if the vendor ships an official EDID tool, prefer the official flow.