fdfd202e5d
As it's still a bit cumbersome to go through the whole .vcd file to find the highest delay between On and Off, do this search automatically and output an statistics. Can look like this: Statistics (assuming a 20 MHz clock): LED on occurences: 838. Sum of all LED on time: 262055 clock cycles. LED on time minimum: 306 clock cycles. LED on time maximum: 717 clock cycles. LED on time average: 312.715 clock cycles. This should give an reasonable overview of wether and roughly how much a particular code change makes your code slower or faster. It should also show up showblockers, like occasionally huge delays. BTW., the above data was collected timing the step interrupt when running short-moves.gcode with the current firmware. |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| excessive-digits.gcode | ||
| nullmoves.gcode | ||
| run-in-simulavr.sh | ||
| save-file-velocities.gtkw | ||
| short-moves.gcode | ||
| smooth-curves.gcode | ||
| straight-speeds.gcode | ||
| triangle-odd.gcode | ||
| triangle.gcode | ||