Troubleshooting Controller Boot Issues
Last updated
Last updated
It has been discovered that the controller may hang during boot due to external factors, such as a short circuit or other errors, leading to incorrect values being read from the EEPROM. To address this, code checks have been implemented to prevent such occurrences. However, if these checks fail, this guide provides a troubleshooting process to resolve the issue.
To resolve a controller failing to boot due to EEPROM-related issues, follow these steps:
Flash a Recovery Firmware
Flash a firmware version that bypasses reading data from the EEPROM.
This firmware includes a functional factory setup stored internally, enabling the controller to boot successfully.
download recovery fw from this link
To flash the recovery firmware, a suitable procedure needs to be used. The automatic bootloader mode procedure does not work because the firmware hangs during boot-up and does not accept any commands.Method 2:
Perform a Factory Reset
Using the recovery firmware, execute a factory reset.
This process restores the EEPROM data to a default, functional state.
after performed the controller shows "done. flash new fw" in the LCD Display
now you can powere down
Reflash the Current Firmware
After the factory reset is complete, reflash the controller with the current firmware (e.g., version 4.27).
The controller should now boot normally with the restored EEPROM settings.
Perform an additional factory reset depending on your setup.
This troubleshooting process may also be required when upgrading certain boards from very old firmware versions to the latest 4.27 firmware. Ensure you verify compatibility and follow the steps carefully to avoid further issues.
For any questions or further assistance, refer to the support documentation or contact the development team.
