The Autel Maxiscan MS509, a popular OBD2 code reader, can sometimes be rendered unusable after a failed firmware update. This article explores a specific case of a bricked MS509 following an attempted upgrade with MS609 firmware, and discusses potential recovery methods using Atmel FLIP software and the correct .bin file.
The Autel MS509 utilizes an Atmel AT89C51RD2 microcontroller. In this instance, the device was bricked after attempting to flash it with firmware intended for the Autel Maxiscan MS609. While the MS509 incorporates an FTDI chip enabling communication with Atmel FLIP software for erasing, flashing, and blank-checking the AT89C51RD2, the incorrect firmware rendered the device unresponsive.
Even after successfully entering flash mode and utilizing a known good .bin file, the MS509 remained bricked. The process involved converting the .bin file to an Intel hex format using two different tools: bin2hex from Atmel’s website and bin2hex from the MCU 8051 IDE by Moravia Microsystems. The resulting hex files differed in their starting characters, one beginning with “:2xxxxxx…” and the other with “:1xxxxxx…”. Neither successfully revived the device.
A key question arises: which hex file format is correct for the AT89C51RD2 in the Autel MS509? Furthermore, is Atmel FLIP even the appropriate tool for restoring the original firmware? Could there be other factors contributing to the unsuccessful recovery, such as specific settings within FLIP or the need for specialized flashing procedures?
While this case highlights the risks of using incorrect firmware, it also underscores the importance of understanding the specific hardware and software requirements for updating OBD2 scanners like the Autel MS509. A successful recovery likely hinges on correctly identifying the appropriate hex file format and ensuring proper execution of the flashing process with Atmel FLIP or a more suitable alternative. Further investigation into the specific requirements of the AT89C51RD2 and the MS509’s internal circuitry is crucial for troubleshooting and resolving this issue. Understanding the nuances of the boot process and memory organization of the microcontroller could also provide valuable insights into the recovery process.
Ultimately, caution is advised when attempting firmware updates on any electronic device. Always verify the correct firmware version and follow the manufacturer’s instructions precisely to avoid potentially irreversible damage. In cases like this, consulting with experienced technicians or seeking support from Autel directly may be necessary to recover a bricked device.
