![]() ![]() *** If you do not put the Proffieboard into bootloader mode before running Zadig, you are doing it wrong, and installing the wrong driver for the board because it’s still connected as a “Proffieboard” composite device at that point. Then when the upload is complete, the board reboots back into normal ProffieOS. It needs this because Arduino is going to put the board in this bootloader mode when you hit Upload so that the board can receive programming. It’s a one-time setup installation when the PC sees the board for the first time in bootloader mode. When it’s in bootloader mode and showing as STM32BOOTLOADER, it needs WinUSB v.16385 driver installed with Zadig. It will not show up here if in bootloader mode. ![]() When booted in ProffieOS, the board should be seen in on a COM port in Arduino under menu Tools>Port. ![]() ![]() Windows typically sees this device when first connected, installs the driver on its own, and will use usbser.sys driver. When booted normally and running ProffieOS, the board show up as a “Proffieboard”, a composite serial device (CDC data etc…). If you install the wrong driver for a device, it’s not going to work, simply put. Different devices require different drivers to talk to your computer properly. Proffieboards either boot into normal mode running ProffieOS, or bootloader mode.Įach of those states looks like a different device to the PC. Just like a PC would boot into normal Windows OS or into the BIOS to set core settings, or an Android phone can boot into normal Android or bootloader, Proffieboard use 2 different drivers on the computer, depending on how it’s booted. Understand how Proffieboards appear to the PC: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |