From 2d4589949c2f77568fbabc265ab6a273bc9222f2 Mon Sep 17 00:00:00 2001 From: JamesH1978 <87171443+JamesH1978@users.noreply.github.com> Date: Mon, 19 May 2025 17:30:39 +0100 Subject: [PATCH] docs: Update Installation.md - Flash loop protection (#6935) Added a paragraph about flash loop protection on some motherboards. It has been noted that not all people know about the need to change the bin filename on some stock boards or other methods that may hinder progress. Signed-off-by: James Hartley --- docs/Installation.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/Installation.md b/docs/Installation.md index 0401774a..fd53ca22 100644 --- a/docs/Installation.md +++ b/docs/Installation.md @@ -139,6 +139,25 @@ print board is not connected with USB to the host, due to some boards being able to feed power back to the board and stopping a flash from occurring. +Please note, that most print boards that use SD cards for flash will +implement some kind of flash loop protection for when the sd card is left +in place. There are two common methods: + +Filename Change Required (usually "stock" print boards): + +These boards require the firmware file to have a different name each +time you flash (for example, firmware1.bin, firmware2.bin, etc.). +If you reuse the same filename, the board may ignore it and not update. + +Automatic File Renaming (usually aftermarket print boards: + +Other boards allow using the same filename, commonly firmware.bin, +but after flashing, the board renames the file to firmware.cur. +This helps indicate the firmware was successfully flashed and prevents +it from flashing again on the next startup. + +Before flashing, make sure to check which behavior your board follows. + For common micro-controllers using Atmega chips, for example the 2560, the code can be flashed with something similar to: