MSI_LED.MSI_1562Led Laptop Keyboard Led Driver

mahirgu15a702e4

mahirgu15a702e4

New member
Joined
Sep 28, 2022
Messages
5
The model of the computer is Crosshair 17 and the bios version is E17L2IE2
Hello, May laptop using MSI_LED.MSI_1562Led and using this 2 files
1664358418671.png

The keyboard backlight of my computer is broken and the device that was previously displayed as VID_MSI = 5218 PID = 5474 in device manager, but it is no longer visible.

1664358151563.png


I think I need an update for this. Is there a firmware update for the MCU that controls the leds under the keyboard?
When I reverse engineered the existing keyboard lighting program, I found the following codes and coded them with c# appropriately. It informs me that the required hardware is not installed.

Is there anyone who can help me with this?

I also found an update file for another keyboard in the Dragon Center software. As far as I understand there is such a "bin" file for each keyboard. File name is FWRescue.exe. A "bin" file and update program came out of the file.
1664358273242.png

Where can I find the "bin" file needed for my own keyboard?
 
Last edited:
I do not think you need to edit the code.
The laptop support Mystic light. You can adjust the keyboard backlight by adjust mystic light from MSI Center.
 
I decompiled the program and found this code in it.
I runned this code with my own rgb controller app and I no longer see the usb RGB controllers device in device manager.
1696635837841.png

I guess I need to reprogram this MCU.
Can anyone help me fix this?
 
mahirgu15a702e4 said:
The model of the computer is Crosshair 17 and the bios version is E17L2IE2
Hello, May laptop using MSI_LED.MSI_1562Led and using this 2 files
View attachment 164052
The keyboard backlight of my computer is broken and the device that was previously displayed as VID_MSI = 5218 PID = 5474 in device manager, but it is no longer visible.

View attachment 164050

I think I need an update for this. Is there a firmware update for the MCU that controls the leds under the keyboard?
When I reverse engineered the existing keyboard lighting program, I found the following codes and coded them with c# appropriately. It informs me that the required hardware is not installed.

Is there anyone who can help me with this?

I also found an update file for another keyboard in the Dragon Center software. As far as I understand there is such a "bin" file for each keyboard. File name is FWRescue.exe. A "bin" file and update program came out of the file.
View attachment 164051
Where can I find the "bin" file needed for my own keyboard?
Click to expand...
The BIOS version you use seems different from the MSI website, try to update the latest BIOS?
I think changing the code might have some unpredictable side effects, try to use F3 Recovery and use mystic light to control the keyboard light.
 
# Keyboard LED MCU Recovery Guide

This guide details the step-by-step process used to recover the keyboard LED controller (MCU) on the **Game Garaj Slayer XL** (MSI MS-17L2 barebone platform) after it became unresponsive and stuck in bootloader mode.

---

## 1. Root Cause Analysis
* **Action:** The `ResetMCU()` function in the C# codebase was executed, which sent a reset command (`0x01, 0x5B`) to the keyboard controller chip.
* **Result:** The microcontroller (manufactured by **Artery Technology**) entered its factory **In-Application Programming (IAP) / Bootloader** mode.
* **Symptom:** Keyboard LEDs turned completely off, and the device changed its USB hardware identity to **`VID_2E3C & PID_AF01`** (identifying itself as `HID IAP`), causing the management software to report *"Keyboard LED Controller is NOT connected"*.

---

## 2. Default HID Driver Requirement
* **Important Note:** By default, Windows binds the standard **`HIDUSB` (USB Input Device / HID-compliant device)** driver to this chip. **Do NOT use Zadig or other tools to replace the driver with WinUSB**, as doing so makes the device invisible to standard HID communication APIs.
* If Zadig was previously used to replace the driver:
1. Open **Device Manager** and locate the `HID IAP` device under *Universal Serial Bus devices*.
2. Right-click, select **Uninstall device**, check the box to *Attempt to remove the driver for this device*, and click uninstall.
3. Scan for hardware changes to restore the default Windows `HIDUSB` driver.

---

## 3. Sending the Native HID Jump Command
* **Action:** Standard USB DFU tools do not work because the chip implements a custom HID IAP protocol. To exit the bootloader and jump to the application memory, a jump command must be sent over the Interrupt Out endpoint.
* **Resolution:** Run the custom PowerShell script ([recover2.ps1](file:///C:/Users/mahir/Downloads/test/recover2.ps1)) which uses native Windows APIs to write directly to the HID device:
```powershell
# Run this script using Windows PowerShell:
powershell -NoProfile -ExecutionPolicy Bypass -File "recover2.ps1"
```
* **How it works:** The script calls native `WriteFile` to send the Artery jump command **`0x5AA6`**:
```csharp
byte[] buf = new byte[caps.OutputReportByteLength];
buf[0] = 1; // Report ID
buf[1] = 0x5A; // Artery IAP Sync Prefix
buf[2] = 0xA6; // Jump to Application Command
WriteFile(hFile, buf, (uint)buf.Length, out written, IntPtr.Zero);
```

---

## 4. Verification
* **Result:** The Artery MCU immediately processes the command, exits the bootloader, and reconnects under its normal MSI operating identity: **`VID_1462 & PID_1564`** (Status: `OK`), restoring the keyboard lighting.
 
Back
Top