The Autel MS509 Maxi-Link is a popular OBD2 scanner known for its affordability and functionality. However, attempting to upgrade its firmware with incompatible software, such as the Autel MS609’s, can brick the device. This article explores the process of recovering a bricked Autel MS509 using Atmel FLIP software and addresses the challenges encountered during the firmware flashing process.
The Autel MS509 utilizes an Atmel AT89C51RD2 microcontroller and an FTDI chip for communication. While the FTDI chip enables communication and allows for erasing, flashing, and blank checking the AT89C51RD2 using Atmel FLIP software, the process is not straightforward when dealing with a bricked device. Even with the correct .bin file, simply flashing the microcontroller doesn’t guarantee recovery. The Maxi-Link software refuses to communicate with the device in “flash” mode, further complicating the process.
A common issue arises when converting the .bin file to the Intel hex format required by FLIP. Different conversion tools, such as the one from Atmel’s website and the one from MCU 8051 IDE by Moravia Microsystems, produce different hex files. One starts with “:2xxxxxx…” while the other begins with “:1xxxxxx…”, raising the question of which file is correct for the Autel MS509.
Furthermore, even after successfully flashing the converted hex file using FLIP, the MS509 might remain unresponsive, indicated by a blank screen. This suggests potential issues beyond simply flashing the firmware, possibly related to the bootloader or other critical components within the device. Successfully recovering a bricked Autel MS509 requires careful consideration of the correct hex file and potentially deeper troubleshooting of the device’s hardware and firmware interaction.
While Atmel FLIP offers a potential solution for recovering a bricked Autel MS509, the process is complex and requires a thorough understanding of the device’s hardware and firmware. The discrepancy between different hex conversion tools adds another layer of complexity. Further investigation is needed to determine the correct procedure for utilizing the Autel Ms509 Maxi-link Software and recovering the device from a bricked state. This might involve analyzing the original firmware, understanding the bootloader process, and potentially using more advanced debugging techniques. Ultimately, preventing such issues by avoiding incompatible firmware upgrades is the most effective solution.
