h3n3/klipper
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Deploying to gh-pages from @ Klipper3d/klipper@1836ec431c 🚀

Browse Source
This commit is contained in:
KevinOConnor
2025-02-27 01:26:42 +00:00
parent 2e192a93eb
commit 3e3d2b6dc0
15 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Benchmarks.html
View File

@@ -2259,7 +2259,7 @@ 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>f6718291</code> with gcc version
<p>The test was last run on commit <code>14c105b8</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>
@@ -2272,11 +2272,11 @@ Pico and Pico 2 boards.</p>
<tbody>
<tr>
<td>1 stepper</td>
<td>5</td>
<td>3</td>
</tr>
<tr>
<td>3 stepper</td>
<td>22</td>
<td>14</td>
</tr>
</tbody>
</table>
@@ -2299,9 +2299,9 @@ Pico and Pico 2 boards.</p>
</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
scheduling timer and do not correspond to its 200Mhz 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
~42 ARM core cycles and 14 scheduling ticks corresponds to ~225 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">&para;</a></h3>
<p>The following configuration sequence is used on a Raspberry Pi:</p>