Differences

This shows you the differences between two versions of the page.

--- wcore [2017/09/10 07:58] – [Sub parts] latigid_on
+++ wcore [2017/09/18 06:07] (current) – [Flashing over SWD] latigid_on
@@ Line 1: / Line 1: @@
 ====== wCoreF4 ======
-===== Introduction =====
+This is a cross-grade of the STM32F4 Core based on the [[http://www.waveshare.com/wiki/Core407V|Core407v]] breakout board from Waveshare. There are other versions of MCU breakouts, but the Waveshare one seems quite a reputable source with decent distribution and documentation.
-This is a cross-grade of the STM32F4 Core based on the [[http://www.waveshare.com/wiki/Core407V|Core407v]] breakout board from Waveshare. There are other versions of breakouts, but the Waveshare one seems quite a reputable source with decent distribution and documentation.
 ==== Pros ====
@@ Line 43: / Line 45: @@
 The actual MCU module is available from several sources:
+  * [[https://eckstein-shop.de/Core407V]]
+  * [[http://www.waveshare.com/core407v.htm]]
+  * [[http://www.ebay.com/itm/Core407V-STM32F407VET6-STM32-ARM-Cortex-M4-Development-Board-Full-I-O-Expander-/261045971937?hash=item3cc78d6be1:m:mp6HjVptDe-JUZfdAfbgOvg|eBay]]
 ===== Burning the bootloader =====
-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 ST-LINK-like functionality. The MCU module has a typical JTAG header and these pins are also available on the two 2*25 header rows. So even if the header had to be removed for space reasons, it should always be possible to re-flash the MCU.
+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 ====
@@ Line 54: / Line 61: @@
 ==== Option 2: use a Discovery module ====
-The Discovery module (even if connected to a MIDIbox Core) can be used for programming.
+The Discovery module (even if connected to a MIDIbox Core) can be used for programming. To do so, remove the two CN3 jumpers labelled ST-LINK/DISCOVERY. This disconnects the SWD interface from the STM32F4 MCU on the Discovery board:
+{{:wcore:discojumpers.png?nolink&300|}}
+Note that pin 1 of the 6-pin SWD interface on CN2 of the Discovery board only **detects** the voltage of the target. Thus the most foolproof method of flashing is to connect a mini USB cable to the 407v board and set the power switch to USB. This ensures that the board is always powered up when programming. After the bootloader is burned in, the 407v board can be installed in the wCore PCB through the two 2*25 headers.
+==== Flashing over SWD ====
+The following five connections should be made with DuPont cables:
+  * 3v3
+  * 0V/ground
+  * DIO
+  * CLK
+  * RESET
+{{::wcore:flashing.png?nolink&600|}} \\
+//Of course, only one programmer should be connected to the 407v board!//
+After that, [[http://www.ucapps.de/mbhp_core_stm32f4.html|follow the instructions]] for the initial flash of a Discovery module.
+If the JTAG/SWD header of the 407v board had to be removed and the MCU required re-flashing, it's possible to do so using the named pins on the 2*25 header.