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). OS versions prior to Windows® 7 are compatible with the Windows® 7 installations included in the package. 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). The STSW-STM32102 software package contains four installation files based on the various versions of the Microsoft® operating system. 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. 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 (. I've found this group to offer mostly substance and very little pomp.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. Of course if you still have questions the more experienced users always seem glad to help out. Once a member is familiar with the Wiki and Files sections they are able to do a lot of self-help on their own. ![]() Im using a custom PCB, and this PCB has an older code that was not generated by the STM32CubeIDE where the USB port reads pendrives. I installed 'STM32 Virtual COM Port Driver'. I tested inverting the D+ and D- signals of the USB cable. In the future I will additionally provide a direct link when referring a member to either of those locations. And Windows 10 does not detect the USB device. You are not the only new member that has expressed difficulty initially locating the group's Wiki and Files section. Thanks for confirming that the driver located in the Wiki also works. To see what Zadig installed and it was a different driver called "libwdi" USB Same driver and version number (1.4) that Windows update installed. Visit the ST website and navigate to STSW-LINK009, as indicated in. ST-LINK Driver for Windows (32/ 64-bit versions 7, 8, and 10): It is available on the STs website. PS: I read somewhere turning on VSense makes problems, too. No need to install the very old ST VCP driver on your system. If you do all of that, the Windows 10 out-of-the-box VCP driver can be used. ST-Link in-circuit debugger and programmer. Since you do not return any values, the virtual com port remains as driver-not-loaded. The Wiki link and it did install correctly in Windows 8.1. The ST-Link driver means the driver for the ST-Link in-circuit debugger and programmer interface, as depicted in Figure 1. I also tried downloading the driver from ST at ![]() hi, please provide a link for stm32 virtual com port driver for windows 8.1 (64bit) only. The Wiki when I made my original request for help. I see multiple people having this problem but not seen an answer why or a solution: The Virtual COM Port driver (1.4) is not working for Windows 10 users. stm32 virtual com port driver for windows 8.1. I am new to this group and did not fully understand the driver reference in
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |