diff options
Diffstat (limited to 'docs/Bootloaders.md')
| -rw-r--r-- | docs/Bootloaders.md | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/Bootloaders.md b/docs/Bootloaders.md index 9c7d42d9..1f7aa24d 100644 --- a/docs/Bootloaders.md +++ b/docs/Bootloaders.md @@ -305,7 +305,7 @@ is a [fork with builds specific to the SKR Mini E3 1.2]( https://github.com/Arksine/STM32_HID_Bootloader/releases/latest). For generic STM32F103 boards such as the blue pill it is possible to flash -the bootloader via 3.3v serial using stm32flash as noted in the stm32duino +the bootloader via 3.3V serial using stm32flash as noted in the stm32duino section above, substituting the file name for the desired hid bootloader binary (ie: hid_generic_pc13.bin for the blue pill). @@ -382,7 +382,7 @@ make flash FLASH_DEVICE=/dev/ttyACM0 It may be necessary to manually enter the bootloader, this can be done by setting "boot 0" low and "boot 1" high. On the SKR Mini E3 "Boot 1" is not available, so it may be done by setting pin PA2 low if you flashed -"hid_btt_skr_mini_e3.bin". This pin is labeld "TX0" on the TFT header in +"hid_btt_skr_mini_e3.bin". This pin is labeled "TX0" on the TFT header in the SKR Mini E3's "PIN" document. There is a ground pin next to PA2 which you can use to pull PA2 low. @@ -390,7 +390,7 @@ which you can use to pull PA2 low. The [MSC bootloader](https://github.com/Telekatz/MSC-stm32f103-bootloader) is a driverless bootloader capable of flashing over USB. -It is possible to flash the bootloader via 3.3v serial using stm32flash as noted +It is possible to flash the bootloader via 3.3V serial using stm32flash as noted in the stm32duino section above, substituting the file name for the desired MSC bootloader binary (ie: MSCboot-Bluepill.bin for the blue pill). @@ -419,7 +419,7 @@ It is recommended to use a ST-Link Programmer to flash CanBoot, however it should be possible to flash using `stm32flash` on STM32F103 devices, and `dfu-util` on STM32F042/STM32F072 devices. See the previous sections in this document for instructions on these flashing methods, substituting `canboot.bin` -for the file name where appropriate. The CanBoot repo linked above provides +for the file name where appropriate. The CanBoot repository linked above provides instructions for building the bootloader. The first time CanBoot has been flashed it should detect that no application @@ -448,8 +448,8 @@ When building Klipper for use with CanBoot, select the 8 KiB Bootloader option. ## STM32F4 micro-controllers (SKR Pro 1.1) -STM32F4 microcontrollers come equipped with a built-in system bootloader -capable of flashing over USB (via DFU), 3.3v Serial, and various other +STM32F4 micro-controllers come equipped with a built-in system bootloader +capable of flashing over USB (via DFU), 3.3V Serial, and various other methods (see STM Document AN2606 for more information). Some STM32F4 boards, such as the SKR Pro 1.1, are not able to enter the DFU bootloader. The HID bootloader is available for STM32F405/407 @@ -458,8 +458,8 @@ Note that you may need to configure and build a version specific to your board, a [build for the SKR Pro 1.1 is available here]( https://github.com/Arksine/STM32_HID_Bootloader/releases/latest). -Unless your board is DFU capable the most accessable flashing method -is likely via 3.3v serial, which follows the same procedure as +Unless your board is DFU capable the most accessible flashing method +is likely via 3.3V serial, which follows the same procedure as [flashing the STM32F103 using stm32flash](#stm32f103-micro-controllers-blue-pill-devices). For example: ``` |