Deploying to gh-pages from @ Klipper3d/klipper@a46dba08e2 🚀
This commit is contained in:
@@ -1212,8 +1212,8 @@
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040-step-rate-benchmark" class="md-nav__link">
|
||||
RP2040 step rate benchmark
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -1637,8 +1637,8 @@
|
||||
</li>
|
||||
|
||||
<li class="md-nav__item">
|
||||
<a href="#rp2040-step-rate-benchmark" class="md-nav__link">
|
||||
RP2040 step rate benchmark
|
||||
<a href="#rpxxxx-step-rate-benchmark" class="md-nav__link">
|
||||
RPxxxx step rate benchmark
|
||||
</a>
|
||||
|
||||
</li>
|
||||
@@ -2250,8 +2250,8 @@ micro-controller.</p>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<h3 id="rp2040-step-rate-benchmark">RP2040 step rate benchmark<a class="headerlink" href="#rp2040-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the RP2040:</p>
|
||||
<h3 id="rpxxxx-step-rate-benchmark">RPxxxx step rate benchmark<a class="headerlink" href="#rpxxxx-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on the RP2040 and RP2350:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
config_stepper oid=0 step_pin=gpio25 dir_pin=gpio3 invert_step=-1 step_pulse_ticks=0
|
||||
config_stepper oid=1 step_pin=gpio26 dir_pin=gpio4 invert_step=-1 step_pulse_ticks=0
|
||||
@@ -2259,13 +2259,13 @@ config_stepper oid=2 step_pin=gpio27 dir_pin=gpio5 invert_step=-1 step_pulse_tic
|
||||
finalize_config crc=0
|
||||
</code></pre></div>
|
||||
|
||||
<p>The test was last run on commit <code>59314d99</code> with gcc version
|
||||
<code>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</code> on a Raspberry Pi
|
||||
Pico board.</p>
|
||||
<p>The test was last run on commit <code>f6718291</code> with gcc version
|
||||
<code>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</code> on Raspberry Pi
|
||||
Pico and Pico 2 boards.</p>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2040</th>
|
||||
<th>rp2040 (*)</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
@@ -2280,6 +2280,29 @@ Pico board.</p>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<table>
|
||||
<thead>
|
||||
<tr>
|
||||
<th>rp2350</th>
|
||||
<th>ticks</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody>
|
||||
<tr>
|
||||
<td>1 stepper</td>
|
||||
<td>36</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>3 stepper</td>
|
||||
<td>169</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
<p>(*) Note that the reported rp2040 ticks are relative to a 12Mhz
|
||||
scheduling timer and do not correspond to its 125Mhz internal ARM
|
||||
processing rate. It is expected that 5 scheduling ticks corresponds to
|
||||
~47 ARM core cycles and 22 scheduling ticks corresponds to ~224 ARM
|
||||
core cycles.</p>
|
||||
<h3 id="linux-mcu-step-rate-benchmark">Linux MCU step rate benchmark<a class="headerlink" href="#linux-mcu-step-rate-benchmark" title="Permanent link">¶</a></h3>
|
||||
<p>The following configuration sequence is used on a Raspberry Pi:</p>
|
||||
<div class="highlight"><pre><span></span><code>allocate_oids count=3
|
||||
@@ -2426,9 +2449,15 @@ hub.</p>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2040 (USB)</td>
|
||||
<td>873K</td>
|
||||
<td>c5667193</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 10.2.0-4.fc34) 10.2.0</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>rp2350 (USB)</td>
|
||||
<td>885K</td>
|
||||
<td>f6718291</td>
|
||||
<td>arm-none-eabi-gcc (Fedora 14.1.0-1.fc40) 14.1.0</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
</table>
|
||||
|
||||
Reference in New Issue
Block a user