da08c35edd
The idea is simple: if you want to time a portion of code precisely, turn on the Debug LED (see config.h for DEBUG_LED_PIN) at the start of sequence and turn it off when done. Running this in SimulAVR, you have two flanges precise to the clock cycle which exactly reflect the time taken to run this code sequence. Ideally, you run this code n a loop to get a number of samples, if it doesn't run in a loop anyways. Time taken can then be measured in GTKWave. For convenience and for a better overview, run-in-simulavr.sh also extracts all the delays into it's own signal, so it can be viewed as an ongoing number. |
||
|---|---|---|
| .. | ||
| .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 | ||