So I have someone with an issue and STM32 bootloader drivers don’t seem to be showing up after installing Zadig. Hopefully the picture attached shows, but is there a driver on there that might be blocking STM32? bootloader? V3.9 board. Yes I know we’re doing this the old way, but if anyone might be able to help. Thanks.
First: The board needs to be in bootloader mode in order for it to show up in device manager in a meaningful way for troubleshooting STM32 driver issues.
Then, normally the board will show up under “COM & LPT Ports,” not under anything USB. (Maybe there’s something that could bork it to show up elsewhere, but under normal circumstances)
If you can find the STM32 device, pop open properties, and check which driver is installed, then you can pinpoint whether or not it’s a driver issue. If it’s a driver conflict, it’ll be pretty obvious by seeing which driver is in use for the proffieboard/STM32 device. (As opposed to the expected WinUSB driver)
Yes they have pushed the 2 buttons to reset the board. Does the boot up sound when they do and still does not show under any devices. Have tried to uninstall Zadig and reinstall and nothing. I did notice in the screenshot they sent me has gaming devices, and they did mention a ps4 controller that was plugged in. I read in older posts on here that a gaming device can sometimes block it. Just wasn’t sure if there was something on the picture would be the culprit. Doing some more attempts tomorrow but if anyone has any tips we’d be much appreciated.
Do you mean the board is making noise? If so, then the board absolutely is not entering bootloader mode. It’s possible the buttons are being confused, or that they’re just not actually being pressed (on account of being so small). I suggest a pair of (non-metallic) tweezers, credit card, or long fingernail.
You can only use Zadig to install the WinUSB driver if the board is in bootloader mode and you can select STM32 BOOTLOADER as the device to install the driver for. Are you installing random drivers to random devices? Are you just installing the program and not actually running/using it? (Perhaps these are dumb questions, but I want to cover all the oversight/edge cases)
In the picture you’re showing the section for USB “Controllers.” Even if we saw the devices section, that wouldn’t be all the devices plugged in via USB, just those registering in windows as USB devices, and it still wouldn’t tell us what drivers were being used.
Simply put, there’s not really enough info in that picture to go by. (And it’s something of a roundabout way of trying to figure out the problem)
P.S. Apologies if I seem like I’m coming off terse, I don’t intend to convey irritation or annoyance… I just find myself writing in a more terse manner.
I’ll make sure they’re pressing the buttons down correctly. They said it would make the boot up sound after they did that. So something may not be right there.
No we’re not installing random drivers to anything. After selecting List All Devices when we reset the board, STM32 does not show up on the list. I’ll have him check his USB devices and see if it even shows up when he connects. We know it can send data because he plugged it into his tablet and the computer automatically asked what to do with the files.
An no apologies needed, I know you’ve probably heard so many problems from people, but I find the knowledge you all have it’s pretty damn awesome. I would come here when I first got my proffie and you guys helped with what I needed, I just want to pass it on and help others as well.
That sounds like Mass Storage is enabled, and ProffieOS is running to allow access to the SD card via USB. If ProffieOS is running (and those files can indeed be accessed via USB), then that’d be another sign the board isn’t in bootloader mode.
Gotcha.
Yeah, it does seem then like the board just isn’t getting into bootloader mode proper.
Out of curiousity, is there any reason to not using proffie-dfu-setup.exe? It’s good to know how to reboot to bootloader mode in general, so I think the exercise isn’t necessarily a waste, but the setup tool installs the drivers without the board needing to be in bootloader mode, which seems like it’d circumvent much of this process’s difficulties.
The top post of this thread is violating board policies. (no photos of screens if screenshots will work.)
Unless the top post is fixed, this thread will be deleted shortly.
I have fixed rhe original post.
1 Like