The Autel MaxiScan MS509 is a popular OBD2 scanner, but attempting an incorrect software upgrade can brick the device. This article explores a common scenario: attempting to flash the MS509 with MS609 firmware, and the subsequent steps to recover the device using Atmel FLIP software and the correct .bin file.
Understanding the Problem: Incorrect Firmware Flashing
A common mistake is attempting to upgrade the Autel MaxiScan MS509 with firmware intended for the Autel MaxiScan MS609. These devices, while similar, have different hardware and firmware requirements. Using the wrong firmware can corrupt the MS509’s system, rendering it unusable – often resulting in a blank screen. This is commonly referred to as “bricking” the device. The MaxiLink software, unfortunately, doesn’t always prevent this mismatched flashing, leading to potential issues.
Recovery Process: Utilizing Atmel FLIP
The Autel MaxiScan MS509 utilizes an Atmel AT89C51RD2 microcontroller. Fortunately, this chip includes a flash memory that can be reprogrammed. Recovery involves using Atmel FLIP software, a utility specifically designed for programming Atmel microcontrollers. The process generally involves these steps:
-
Connecting to the MS509: The MS509 incorporates an FTDI chip, enabling communication with a computer via USB. This connection allows Atmel FLIP to interact with the AT89C51RD2 microcontroller.
-
Entering Flash Mode: The AT89C51RD2 needs to be put into programming or “flash” mode to accept new firmware. This usually involves specific button combinations or shorting specific pins on the device.
-
Selecting the Correct .bin File: Obtaining the correct .bin file for the MS509 is crucial. Using the MS609 file or any other incorrect file will fail to restore the device.
-
Converting .bin to .hex: Atmel FLIP requires an Intel hex file (.hex) for flashing. Converting the .bin file to .hex can be done using various tools, including bin2hex utilities available from Atmel or other microcontroller IDEs. Discrepancies in the generated hex files (e.g., starting with :1xxxxxx or :2xxxxxx) might indicate issues with the conversion process and require further investigation. Ensure the chosen converter is compatible with the AT89C51RD2.
-
Flashing the Device: Using Atmel FLIP, select the converted .hex file and program the AT89C51RD2. After successful flashing, the MS509 should be restored to its original working condition.
Troubleshooting: Common Issues and Solutions
Even with the correct procedures, issues can arise. If the MS509 remains unresponsive after flashing:
-
Verify the .bin File Integrity: Ensure the downloaded .bin file is not corrupted. Checksum comparison or downloading from a reputable source can help confirm its integrity.
-
Double-Check Flash Mode: Confirm the MS509 is correctly entering flash mode. Incorrect procedures can prevent successful programming.
-
Explore Alternative Conversion Tools: If using a specific bin2hex tool results in a non-functional hex file, try an alternative tool to ensure proper conversion.
-
Hardware Issues: In rare cases, a hardware fault may be preventing the recovery process. This requires more advanced troubleshooting or professional repair.
Conclusion
Recovering a bricked Autel MaxiScan MS509 after an incorrect software upgrade is possible using Atmel FLIP and the correct firmware. Careful attention to detail, ensuring the correct file and procedures are used, is critical for success. If issues persist, verifying file integrity, confirming flash mode, and exploring alternative conversion tools are recommended troubleshooting steps.
