Skip to content

Commit

Permalink
Deploying to gh-pages from @ bbfa192 πŸš€
Browse files Browse the repository at this point in the history
  • Loading branch information
wanda-phi committed Dec 3, 2023
1 parent adbe3b2 commit 563ea16
Show file tree
Hide file tree
Showing 5 changed files with 15 additions and 5 deletions.
Binary file modified .doctrees/environment.pickle
Binary file not shown.
Binary file modified .doctrees/xc9500/jtag.doctree
Binary file not shown.
10 changes: 8 additions & 2 deletions _sources/xc9500/jtag.rst.txt
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ IR Instruction Register Notes
``11101001`` ``ISPENC`` ``ISPENABLE`` XC9500XL/XV only
``11101010`` ``FPGM`` ``ISPCONFIGURATION``
``11101011`` ``FPGMI`` ``ISPDATA``
``11101100`` ``FERASE`` ``ISPCONFIGURATION`` XC9500 only
``11101100`` ``FERASE`` ``ISPCONFIGURATION`` XC9500 revision 2 and up only
``11101100`` ``FERASE`` ``ISPADDRESS`` XC9500XL/XV only
``11101101`` ``FBULK`` ``ISPCONFIGURATION`` XC9500 only
``11101101`` ``FBULK`` ``ISPADDRESS`` XC9500XL/XV only
Expand Down Expand Up @@ -58,7 +58,7 @@ IDCODE
The IDCODE for XC9500* devices can be determined as follows:

- bits 0-11: vendor code, ``0x093``
- bits 12-19: number of FBs in the device
- bits 12-19: number of FBs in the device encoded as BCD
- bits 20-27: device kind

- ``0x95``: XC9500
Expand All @@ -67,6 +67,9 @@ The IDCODE for XC9500* devices can be determined as follows:

- bits 28-31: device revision (varies)

For XC9500, device revisions older than 2 do not support the ``FBULK`` instruction and
require using ``FERASE``.


Boundary scan register
======================
Expand Down Expand Up @@ -184,6 +187,9 @@ There are two instructions that erase fuses:
- ``FBULK``: erases either all main areas on the device at once, or all UIM wire-AND areas
at once

Note that the ``FBULK`` instruction is not supported on (rarely seen) XC9500 devices with
revision older than 2.

An erase operation is triggered by the following sequence:

1. The DR is written in one of the above opcodes with strobe set to 1 and valid set to 0
Expand Down
2 changes: 1 addition & 1 deletion searchindex.js

Large diffs are not rendered by default.

8 changes: 6 additions & 2 deletions xc9500/jtag.html
Original file line number Diff line number Diff line change
Expand Up @@ -168,7 +168,7 @@ <h2>IR<a class="headerlink" href="#ir" title="Link to this heading"></a></h2>
<tr class="row-even"><td><p><code class="docutils literal notranslate"><span class="pre">11101100</span></code></p></td>
<td><p><code class="docutils literal notranslate"><span class="pre">FERASE</span></code></p></td>
<td><p><code class="docutils literal notranslate"><span class="pre">ISPCONFIGURATION</span></code></p></td>
<td><p>XC9500 only</p></td>
<td><p>XC9500 revision 2 and up only</p></td>
</tr>
<tr class="row-odd"><td><p><code class="docutils literal notranslate"><span class="pre">11101100</span></code></p></td>
<td><p><code class="docutils literal notranslate"><span class="pre">FERASE</span></code></p></td>
Expand Down Expand Up @@ -246,7 +246,7 @@ <h2>IDCODE<a class="headerlink" href="#idcode" title="Link to this heading"><
<p>The IDCODE for XC9500* devices can be determined as follows:</p>
<ul class="simple">
<li><p>bits 0-11: vendor code, <code class="docutils literal notranslate"><span class="pre">0x093</span></code></p></li>
<li><p>bits 12-19: number of FBs in the device</p></li>
<li><p>bits 12-19: number of FBs in the device encoded as BCD</p></li>
<li><p>bits 20-27: device kind</p>
<ul>
<li><p><code class="docutils literal notranslate"><span class="pre">0x95</span></code>: XC9500</p></li>
Expand All @@ -256,6 +256,8 @@ <h2>IDCODE<a class="headerlink" href="#idcode" title="Link to this heading"><
</li>
<li><p>bits 28-31: device revision (varies)</p></li>
</ul>
<p>For XC9500, device revisions older than 2 do not support the <code class="docutils literal notranslate"><span class="pre">FBULK</span></code> instruction and
require using <code class="docutils literal notranslate"><span class="pre">FERASE</span></code>.</p>
</section>
<section id="boundary-scan-register">
<h2>Boundary scan register<a class="headerlink" href="#boundary-scan-register" title="Link to this heading"></a></h2>
Expand Down Expand Up @@ -365,6 +367,8 @@ <h3>Erasing fuses β€” XC9500<a class="headerlink" href="#erasing-fuses-xc9500" t
<li><p><code class="docutils literal notranslate"><span class="pre">FBULK</span></code>: erases either all main areas on the device at once, or all UIM wire-AND areas
at once</p></li>
</ul>
<p>Note that the <code class="docutils literal notranslate"><span class="pre">FBULK</span></code> instruction is not supported on (rarely seen) XC9500 devices with
revision older than 2.</p>
<p>An erase operation is triggered by the following sequence:</p>
<ol class="arabic simple">
<li><p>The DR is written in one of the above opcodes with strobe set to 1 and valid set to 0</p></li>
Expand Down

0 comments on commit 563ea16

Please sign in to comment.