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). 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. Double click on it, select Update Driver. Now you should have a STM32 BOOTLOADER device with yellow triangle. Right click, select Uninstall Device, check Delete driver software box, then press Uninstall. I have not found any of the STM32duino code (including bootloaders) to work with these chips, whatever they are. If you see a device with a similar name to STM32 Bootloader. The single-wire interface module (SWIM) and JTAG/serial wire. I have found that under the windows 11 control panel the ST-Link driver is not correctly recognized. The ST-LINK/V2 is an in-circuit debugger and programmer for the STM8 and STM32 microcontrollers. ![]() If new uninstalled devices show on, repeat. With your picture : The STM32 ST-Link Utility uses the ST-Link part of your board to flash it. Then right click on the ST-LINK, select Install, Browse for drivers. The ST-Link part is used to flash the microcontroller and can be used to flash any other STM32F4 device through SWD. 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. The ST-Link debugger part The rest with the actual microcontroller. 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. INF file, the compatible hardware model will be displayed in the model list. Once Windows has found the required driver. The PC autoselects the correct INF file, in this case STDFU.INF. ![]() there may of course be versions of the chip with correct markings, not STM32) that that also don't work. the driver directory is located in your install path (C:Program filesSTMicroelectronicsDfuSeDriver), then click OK. 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. The ST-LINK/V2 (mini) should be connected to the STM8 application via the SWIM interface. 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). Click on the link to download : ST-LINK/V2 USB driver for Windows 7, Vista and XP.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |