docs: Remove outdated stm32f1.md document
The stm32f103 has become popular in the "skr mini" series of boards. As a result, the stm32f1.md document is no longer relevant. Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This commit is contained in:
parent
e0afc74cc7
commit
f07292084b
|
@ -62,8 +62,6 @@ communication with the Klipper developers.
|
||||||
|
|
||||||
- [Bootloaders](Bootloaders.md): Developer information on
|
- [Bootloaders](Bootloaders.md): Developer information on
|
||||||
micro-controller flashing.
|
micro-controller flashing.
|
||||||
- [stm32f1](stm32f1.md): Information on the STM32F1 micro-controller
|
|
||||||
port.
|
|
||||||
- [Beaglebone](beaglebone.md): Details for running Klipper on the
|
- [Beaglebone](beaglebone.md): Details for running Klipper on the
|
||||||
Beaglebone PRU.
|
Beaglebone PRU.
|
||||||
- [stm32f0](stm32f0_CAN.md): Information on the STM32F0 micro-controller
|
- [stm32f0](stm32f0_CAN.md): Information on the STM32F0 micro-controller
|
||||||
|
|
|
@ -1,49 +0,0 @@
|
||||||
This document describes how the STM32F1 port operates and how it can be used on
|
|
||||||
STM32-based boards, such as the "Blue Pill". STM32 MCUs are not used on any
|
|
||||||
Arduino boards, so their restrictions aren't as widely known and less straight
|
|
||||||
forward compared to common Arduino compatible boards. There aren't any standard
|
|
||||||
pin mappings either.
|
|
||||||
|
|
||||||
General considerations
|
|
||||||
======================
|
|
||||||
|
|
||||||
The port is currently designed for and tested with STM32F103xB series
|
|
||||||
MCUs, but it should work with any STM32F103 series MCUs with minimal
|
|
||||||
changes.
|
|
||||||
|
|
||||||
Unlike Arduino-based boards, typically there is no automatic reset on serial
|
|
||||||
connection with STM32 boards. Please use `restart_method: command` with the
|
|
||||||
STM32F1 port.
|
|
||||||
|
|
||||||
Fixed pins
|
|
||||||
==========
|
|
||||||
|
|
||||||
When using USB, the PA11 (D-) and PA12 (D+) pins are reserved. The USB
|
|
||||||
code assumes that PA12 (D+) has a fixed pullup resistor attached to
|
|
||||||
it.
|
|
||||||
|
|
||||||
SPI uses pins PB13/PB14/PB15, but the pins can be used as general I/O
|
|
||||||
if SPI is not used.
|
|
||||||
|
|
||||||
Digital I/O
|
|
||||||
===========
|
|
||||||
|
|
||||||
All pins that aren't part of the fixed set can be used for digital I/O. Pins are
|
|
||||||
referred to by their primary name, e.g. `PA1`. Do not try to use Arduino pin
|
|
||||||
aliases in your configuration. See ST's datasheets for more details. The
|
|
||||||
[STM32Duino](http://wiki.stm32duino.com/index.php?title=Blue_Pill) wiki has more
|
|
||||||
info on the popular "Blue Pill" board.
|
|
||||||
|
|
||||||
Analog inputs
|
|
||||||
=============
|
|
||||||
|
|
||||||
All ADC-capable pins can be used as analog inputs with the same naming as
|
|
||||||
digital I/O pins. Small packages MCUs (e.g. LFQP48) have 10 channels (PA0-PA7,
|
|
||||||
PB0-PB1), while larger package devices have 16 channels (PA0-PA7, PB0-PB1,
|
|
||||||
PC0-PC5).
|
|
||||||
|
|
||||||
SPI
|
|
||||||
===
|
|
||||||
|
|
||||||
SPI uses pin PB13 (SCK), PB14 (MISO) and PB15 (MOSI). The clock speed range is
|
|
||||||
0.15..18 MHz. Chip select pins do not have any restrictions.
|
|
Loading…
Reference in New Issue