Deploying to gh-pages from @ Klipper3d/klipper@2d4589949c 🚀

This commit is contained in:
KevinOConnor 2025-05-19 16:31:24 +00:00
parent f612ec14fe
commit 56169512c1
14 changed files with 14 additions and 1 deletions

View file

@ -1588,6 +1588,19 @@ others, it is usual that these need an initial Klipper flash via SD card.</p>
print board is not connected with USB to the host, due to some boards 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 being able to feed power back to the board and stopping a flash from
occurring.</p> occurring.</p>
<p>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:</p>
<p>Filename Change Required (usually "stock" print boards):</p>
<p>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.</p>
<p>Automatic File Renaming (usually aftermarket print boards:</p>
<p>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.</p>
<p>Before flashing, make sure to check which behavior your board follows.</p>
<p>For common micro-controllers using Atmega chips, for example the 2560, <p>For common micro-controllers using Atmega chips, for example the 2560,
the code can be flashed with something the code can be flashed with something
similar to:</p> similar to:</p>

Binary file not shown.

Binary file not shown.

Binary file not shown.

File diff suppressed because one or more lines are too long

Binary file not shown.

Binary file not shown.

Binary file not shown.