I'd understand if the random old "DISCO" board I have, doesn't support certain features, but I also have a brand new ST-LINK/V2, there isn't a /V2.1, and everyone seems to just be using whatever the new thing is that enables VCP. According to one hack, the difference is (also, apparently a couple pins got swapped around?) down to one singular character: the STM32F103C8T6 substituted by a STM32F103C BT6 (which happens to be double the Flash, a rather important difference). Maybe that's the problem, it doesn't know I can put a more functional version on here? (Can I?) The best I can figure right now, - and I have no fucking clue how this isn't made clear anywhere in the documentation - it seems that ONLY the ST-LINK V2.1, NOT the -A or -B, NOT the ST-LINK/V2 that's sold, NOT the STM32F429I-DISCO (but yes the -DISC1?), and probably so on with other boards (Nucleo etc.), support VCP and DFU (or some combination anyways). I suspect the V2.1 stuff will also work with the older V2. I guess that would be okay for updating the ST-Link, but I can already do that with the updater tool, at least with whatever firmware version it detects I should have. The V2.1 drivers are for the mbed enabled version of the ST-LINK Id start by using the ST-LINK Utilities, make sure you update the firmware, and then use the V2 or V2.1 driver package as appropriate, and the 32-bit or 64-bit installer depending on your version of Windows. it looks like he's working with a Maple board, using Arduino IDE or something like that? And you suppose the tools might be similar enough to ST-Link stuff that there's a procedure that might work? I don't need a DFU, that appears to be a USB bootloader thing. Thanks, that was quite an effort! I don't see where he's doing anything that applies here though.
ass ) extension (substation subs) Did that in 10 minutes do not expect perfection The hack presented may worth the time wasted learning it Paul Save the script as the same name of the video with (. Perhaps Segger might release a Linux/Mac variant of the reflash tool in the future, but I can't speak for what they plan to do.Code:  Title: MapleMiniHack ScriptType: v4.00+ WrapStyle: 0 ScaledBorderAndShadow: yes YCbCr Matrix: TV.601 PlayResX: 1280 PlayResY: 720 Format: Name, Fontname, Fontsize, Primar圜olour, Secondar圜olour, OutlineColour, BackColour, Bold, Italic, Underline, StrikeOut, ScaleX, ScaleY, Spacing, Angle, BorderStyle, Outline, Shadow, Alignment, MarginL, MarginR, MarginV, Encoding Style: Default,Arial,20,&H00FFFFFF,&H000000FF,&H00000000,&H00000000,0,0,0,0,100,100,0,0,1,2,2,2,10,10,10,1 Format: Layer, Start, End, Style, Name, MarginL, MarginR, MarginV, Effect, Text Dialogue: 0,0:07:07.38,0:07:10.02,Default,0,0,0,After finishing this procedure we must press RESET and the COM port should appear as usual. Now you should have a STM32 BOOTLOADER device with yellow triangle. Right click, select Uninstall Device, check Delete driver software box, then press Uninstall. If you see a device with a similar name to STM32 Bootloader: n. You could, on Linux etc, use Wine for this purpose, or run a VirtualBox machine with Windows in it. Right click on the start button, then select Device Manager: n n. I have two computers - a Mac where I do most work, and an (old, bought it on EBay) Windows machine for doing things that can only be done on Windows. Hi, can I install the ST-LINK, ST-LINK/V2, ST-LINK/V2-1, STLINK-V3 USB driver dpinstamd64. The STLink conversion tool works solely on Windows, because. or am I missing a Mac-enabled flasher somewhere? Nice! You mention OSX, but I assume you had to use Windows to flash the board. An issue remains finding the "J-Link" Serial number of the discovery board on Mac OS X, but I used the JLinkProgrammer tool for that.
I just reflashed the STLink on my STM32F7 discovery board and it works like a J-Link now ! The only disappointing thing is the lack of SWO support, but I guess the virtual com port can be used for that.