Tried it, but it gets stuck on "Searching for Flight Controllers.". Then I found about Impulse RC Driver Fixer software, which should basically find any connected FCs, download their drivers and install them automatically. Which is, apparently, a generic and non-descriptive error, coming from a damaged or corrupt driver and designed to ruin my mood for weeks. STMicroelectronics Virtual COM Port Version 1.4.0.0.Īnd, it results in a "This device cannot start" Code 10 error. However, since it didn't change anything either, I then deleted the pair in VSPD again and uninstalled that software.Īnother thing which I tried was going into Device Manager - highlighting Ports (COM and LPT) section - Action - Add Legacy Hardware - manual selection - Ports (COM and LPT) - STMicroelectronics. They did appear in Device Manager next to the COM1 port. There, I created a pair of virtual COM ports (COM2, COM3). Well, as you can see in the image above, I don't have USB Serial Converter.Īfter searching for a solution, I tried installing VSPD software - Virtual Serial Port Drive by Eltima. I noticed some people having similar issues were recommended to open Device Manager, find USB Serial Converter, go into Properties and -somewhere- tick the VCP option, to make virtual COM ports appear. So, again, I install them, the message about successful installation appears, and boom. So, I tried to google STM32 bootloader drivers, and after some digging, I downloaded basically the same VCP driver I was installing earlier. This is how my Device manager looks like, FC connected. When connected while holding a button on the FC (which I presume forces it to connect in bootloader mode), the red LED stays lit, and another small red LED turns on.When connected as it is, one red LED stays lit all the time, while a blue one keeps flashing. I don't even hear the "USB device connected" sound in Windows, and nothing happens in the Device Manager after connecting it. There's an issue with connecting it to my computer, it seems the system doesn't recognize it at all after plugging the FC in a USB port. My computer is running Windows 10 64-bit, updated to build 17763.529. I'm building a mini FPV drone based on the MATEKSYS F405-CTR flight controller - link.Īfter some reading, I decided to flash BetaFlight firmware on the FC. The problematic PCB would not have the same problem when I connect it to my main computer, but the problem persists on the (multiple) target computers.After several days of unsuccessful attempts I decided to reach out to this forum, asking for help. However, after 1-10 minutes, the computer can’t recognize the device again, even if I unplug and re-plug the device – that is, until I try to clean the contacts again.Ģ. After cleaning the MCU and USB port pins’ contacts with the pads (using flux, rework gun, and flux cleaner), the problem goes away temporarily after re-plugging the USB. Around 20-30% of the PCBs would have the problem you described in the beginning of your article, and there are be 2 odd things that happens:ġ. F072 is advertised to be capable of crystal-less USB 2.0, so I did not put any external oscillators in the design. That said, I have made a batch of USB device PCBs, using STM32 F072 as the MCU. Hello, very useful guide! :) I am a pretty novice PCB designer, so forgive me if I lack the troubleshooting skills.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |