I also confirmed that changing the CPU for an STM32 obtained from Farnell on one of these boards fixed the USB issue. It also rather looks to me like a large batch of these particular boards with suspect chips is now in circulation, as I have 6 boards obtained in 3 different orders, 2 from UK stock and 4 in 2 lots from China direct (all last couple of months though). Je possède actuellement une carte de vol Matek f-405, pour la paramétrer sur Betaflight je dois donc installer le driver STM32 VCP, cependant il nest pas disponible sur Windows 10, je nai jamais monté de drone auparavant et je ne my connais pas très bien en informatique. I did successfully get the openCM3 CDC example project to work in VSC/Platformio (after sorting out the STlink programming issue discussed in the link) and Macbeth got the USB to work another way, but as it stands the, it looks as though the current STM32duino code and these chips are incompatible. I have not found any of the STM32duino code (including bootloaders) to work with these chips, whatever they are. When in DFU mode, I can see it as Universal Serial Bus Device/STM32 BOOTLOADER on Device Manager. My PC identifies it as mass storage and portable devices on Windows 10 Pro. I have tested my boards and the configuration bits at 0圎00FFFC0 are a match for Macbeth's when read using using ST-Link Utility, so the manufacturer as read from the chip is not ST if I understand correctly. I found this question 1 where Device Manager reads the STM as Disk drives/STM32. While the discussion is about not being able to program STM32's with STlink, it turns out that the reason it doesn't work is because the CPUID was different than that which would be read from a genuine STM32 part. The link below, second page, has more on these boards. there may of course be versions of the chip with correct markings, not STM32) that that also don't work. Assuming you use an up-to-date STM32CubeMX and library: Enable peripheral UBSOTGFS device only (leave over stuff uncheck) In the clock tab check the clock source is HSE HCLK. I have concluded that while the boards were sold as STM32F103C8T6 system minimum boards and the chips are labelled as STM32F103C8T6, they are in fact something else with STM32 markings. A STM32CubeMX project for Discovery F4 with CDC as USB device should work out of the box. I was have been having problems getting USB to work with recent STM32F103C8T6 system minimum boards, getting 'device not recognised' messages and 'device descriptor request failed' message in device manager (Win 10).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |