This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wcore [2017/09/11 06:29] latigid_on [Option 2: use a Discovery module] |
wcore [2017/09/16 09:45] latigid_on [Burning the bootloader] |
||
---|---|---|---|
Line 52: | Line 52: | ||
The MCU module has a USB port, but direct programming would only be possible with a USB-UART programmer. It would also require a different bootloader protocol. Instead, we make use of SWD functionality. The MCU module has a typical JTAG/SWD header and these pins are also available on the two 2*25 header rows. | The MCU module has a USB port, but direct programming would only be possible with a USB-UART programmer. It would also require a different bootloader protocol. Instead, we make use of SWD functionality. The MCU module has a typical JTAG/SWD header and these pins are also available on the two 2*25 header rows. | ||
+ | |||
+ | I believe that the BOOT CONFIG switch should be set to SYSTEM, although I think this is more relevant for flashing through UART rather than SWD. | ||
==== Option 1: ST-LINK clone ==== | ==== Option 1: ST-LINK clone ==== |