With my STM32F429 board, the virtual com port shows up on connection to just CN1.This was before the latest code was running on the board that does the USB initialization and I'm fairly certain the connection didn't work.Why didn't I think of doing this earlier? Well, I did, and did do it, but two things: Just to be clear about the USB connections on the board, CN1 is the USB connection that provides power to the board, and CN5 is the USB connection on the opposite end of the board. I then examine the board and don't notice any anomalies, then suddenly think 'hey, why not try and plug a USB cable into CN5 and connect it to the Win 10 machine', I do so, and bingo, 'STMicroelectronics Virtual COM Port (COM4)' shows up under 'Ports' in Device Manager. I step thru the code as you suggest, and definitely see it going through the USB init steps. Really appreciate your willingness to help me with this, Ant. Think I should try getting a new STM32F411 board? I prefer to not spend $20 on something I already have, but I can afford it. It costs around $20 USD to order a new one. HAL_GPIO_TogglePin(GPIOD, GPIO_PIN_12 | GPIO_PIN_13 | GPIO_PIN_14 | GPIO_PIN_15) Īt this point I'm wondering if something is physically wrong with my STM32F411 board. So, the only code I add to the generated project are the following two lines in main's while loop: If you look at the attached IOC in Cube MX you'll notice I've activated GPIO pins D12, D13, D14 and D I do this because in the main loop I toggle the LEDs on the board just to make sure something works. I also did various comparisons between it and the IOC from your F429 TraceAlyzer project and I'm not seeing any outlying, obvious differences that could be causing the problem. I've attached my latest IOC file with the modifications you've suggested. I followed your instructions, but unfortunately still no 'STMicroelectronics STLink Virtual COM Port' listed under Ports of Device Manager when making these modifications, generating code and running it on the STM32F411 board I'd be very appreciative of any other thoughts. Really lost on this one and really need to get this to work. I've attached my CubeMX IOC in case you'd be so kind to take a look. It looks like the closest I can get is 36 MHz: can't remember off the top of my head if you can actually do that. Maybe see if you can output the 48 MHz USB clock on the MCO pin to verify. Itcouldbe clock related, or maybe you are missing the USB interrupts being enabled (check in CubeMX). I unplug it, and plug in my STM32F411 using the same USB cable and port and nothing I plug my STM32F429 in and ''STMicroelectronics STLink Virtual COM Port (COM5)'' shows up under ''Ports''. A few comments with regards to your previous advice:Įven if you don't ''connect'' to the device, it should show up in device manager on your PC as plugging it in starts the enumeration process and establishes the connection. Thanks in advance.Īnt - Thanks for the reply. 'STMicroelectronics STLink Virtual COM Port' still appears.Ĭan you provide any insight into why this happens? Just trying to understand this better. However, since then I've flashed different software (like just a simple light blink example), I unplug the board, plug it back in and it's surprising to me that the COM port for the I've studied the 'USB F4 VCP Device' section of the PDF you've linked to but nothing there is making it entirely clear why this suddenly works.Īt first I figured the COM port appeared because the Tracealyzer software running on the board activated certain peripherals to cause the 'connection' to happen. However, what I don't understand is what exactly happened with the board/software/driver that caused the COM port to work. I built the Tracealyzer demo, flashed it to the board and the 'STMicroelectronics STLink Virtual COM Port' magically appeared under 'Ports' in 'Device Manager'. Note: this post was migrated and contained many threaded conversations, some content may be missing.Īnt - Thanks for the reply! I actually have an STM32F429 board in addition to my STM32F411. I am quite certain COM1 is in no way related to my STM32F411 board. The installation appears to work, but no ''ST Microelectronics'' COM port shows up in my device manager, only COM1: Since I have 64 bit Windows 10 I rundpinst_amdexe. Double click on dpinst_amdexe if you are running a 64-bits OS version Double click on dpinst_xexe if you are running a 32-bits OS version run the installation process and also note in the contained readme.txt it says:ġ- Uninstall previous versions (Start-> Settings-> Control Panel-> Add or remove programs)ģ- Go to Your installation directory - Example, C:\Program Files (x86)\STMicroelectronics\Software\Virtual comport driverĤ- Go to Your OS version directory ( or ) 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |