/usr/share/doc/avrdude/avrdude-html/Atmel-DFU-bootloader-using-FLIP-version-1.html is in avrdude-doc 6.3-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 | <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<!-- Created by GNU Texinfo 6.4.90, http://www.gnu.org/software/texinfo/ -->
<head>
<title>Atmel DFU bootloader using FLIP version 1 (AVRDUDE)</title>
<meta name="description" content="Atmel DFU bootloader using FLIP version 1 (AVRDUDE)">
<meta name="keywords" content="Atmel DFU bootloader using FLIP version 1 (AVRDUDE)">
<meta name="resource-type" content="document">
<meta name="distribution" content="global">
<meta name="Generator" content="makeinfo">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<link href="index.html#Top" rel="start" title="Top">
<link href="index.html#SEC_Contents" rel="contents" title="Table of Contents">
<link href="Programmer-Specific-Information.html#Programmer-Specific-Information" rel="up" title="Programmer Specific Information">
<link href="Platform-Dependent-Information.html#Platform-Dependent-Information" rel="next" title="Platform Dependent Information">
<link href="Atmel-STK600.html#Atmel-STK600" rel="prev" title="Atmel STK600">
<style type="text/css">
<!--
a.summary-letter {text-decoration: none}
blockquote.indentedblock {margin-right: 0em}
blockquote.smallindentedblock {margin-right: 0em; font-size: smaller}
blockquote.smallquotation {font-size: smaller}
div.display {margin-left: 3.2em}
div.example {margin-left: 3.2em}
div.lisp {margin-left: 3.2em}
div.smalldisplay {margin-left: 3.2em}
div.smallexample {margin-left: 3.2em}
div.smalllisp {margin-left: 3.2em}
kbd {font-style: oblique}
pre.display {font-family: inherit}
pre.format {font-family: inherit}
pre.menu-comment {font-family: serif}
pre.menu-preformatted {font-family: serif}
pre.smalldisplay {font-family: inherit; font-size: smaller}
pre.smallexample {font-size: smaller}
pre.smallformat {font-family: inherit; font-size: smaller}
pre.smalllisp {font-size: smaller}
span.nolinebreak {white-space: nowrap}
span.roman {font-family: initial; font-weight: normal}
span.sansserif {font-family: sans-serif; font-weight: normal}
ul.no-bullet {list-style: none}
-->
</style>
</head>
<body lang="en">
<a name="Atmel-DFU-bootloader-using-FLIP-version-1"></a>
<div class="header">
<p>
Previous: <a href="Atmel-STK600.html#Atmel-STK600" accesskey="p" rel="prev">Atmel STK600</a>, Up: <a href="Programmer-Specific-Information.html#Programmer-Specific-Information" accesskey="u" rel="up">Programmer Specific Information</a> [<a href="index.html#SEC_Contents" title="Table of contents" rel="contents">Contents</a>]</p>
</div>
<hr>
<a name="Atmel-DFU-bootloader-using-FLIP-version-1-1"></a>
<h3 class="section">5.2 Atmel DFU bootloader using FLIP version 1</h3>
<p>Bootloaders using the FLIP protocol version 1 experience some very
specific behaviour.
</p>
<p>These bootloaders have no option to access memory areas other than
Flash and EEPROM.
</p>
<p>When the bootloader is started, it enters a <em>security mode</em> where
the only acceptable access is to query the device configuration
parameters (which are used for the signature on AVR devices). The
only way to leave this mode is a <em>chip erase</em>. As a chip erase
is normally implied by the <samp>-U</samp> option when reprogramming the
flash, this peculiarity might not be very obvious immediately.
</p>
<p>Sometimes, a bootloader with security mode already disabled seems to
no longer respond with sensible configuration data, but only 0xFF for
all queries. As these queries are used to obtain the equivalent of a
signature, AVRDUDE can only continue in that situation by forcing the
signature check to be overridden with the <samp>-F</samp> option.
</p>
<p>A <em>chip erase</em> might leave the EEPROM unerased, at least on some
versions of the bootloader.
</p>
</body>
</html>
|