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

docs: Add step rate benchmark for stm32h7 

Signed-off-by: Konstantin Vogel <konstantin.vogel@gmx.net>
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
D4SK 2022-10-20 22:10:36 +02:00 committed by Kevin O'Connor
parent 00191b5cc4
commit a65e04aff7
2 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
docs/Benchmarks.md
View File

@ -248,6 +248,26 @@ results were obtained by running an STM32F407 binary on an STM32F446
| 1 stepper | 46 | | 1 stepper | 46 |
| 3 stepper | 205 | | 3 stepper | 205 |
### STM32H7 step rate benchmark
The following configuration sequence is used on a STM32H743VIT6:
```
allocate_oids count=3
config_stepper oid=0 step_pin=PD4 dir_pin=PD3 invert_step=-1 step_pulse_ticks=0
config_stepper oid=1 step_pin=PA15 dir_pin=PA8 invert_step=-1 step_pulse_ticks=0
config_stepper oid=2 step_pin=PE2 dir_pin=PE3 invert_step=-1 step_pulse_ticks=0
finalize_config crc=0
```
The test was last run on commit `00191b5c` with gcc version
`arm-none-eabi-gcc (15:8-2019-q3-1+b1) 8.3.1 20190703 (release)
[gcc-8-branch revision 273027]`.
| stm32h7 | ticks |
| -------------------- | ----- |
| 1 stepper | 44 |
| 3 stepper | 198 |
### STM32G0B1 step rate benchmark ### STM32G0B1 step rate benchmark
The following configuration sequence is used on the STM32G0B1: The following configuration sequence is used on the STM32G0B1:

1
docs/Features.md
View File

@ -175,6 +175,7 @@ represent total number of steps per second on the micro-controller.
| SAMD51 | 3077K | 1885K | | SAMD51 | 3077K | 1885K |
| STM32F407 | 3652K | 2459K | | STM32F407 | 3652K | 2459K |
| STM32F446 | 3913K | 2634K | | STM32F446 | 3913K | 2634K |
| STM32H743 | 9091K | 6061K |
If unsure of the micro-controller on a particular board, find the If unsure of the micro-controller on a particular board, find the
appropriate [config file](../config/), and look for the appropriate [config file](../config/), and look for the