I’ve changed arduino to V3, and even messed with bootloader mode and the DFU installer, none of it will work, All I can do is get arduino to upload to the board (despite not seeing it in com ports)
V2 and V3 boards literally look identical to the computer.
The only difference is how much power they draw. V3 boards draw more power and can potentially overload a standard USB port. If that is the problem, just disconnect or charge the battery to fix it.
However, it’s much more likely that this board simply has a bad programming and will work just fine once programmed properly.
I’ve ran the arduino code to The board, and it succesfully uploaded.
It’s got the exact same preset as my other board, the only difference is that it’s using "#include “proffieboard_v3_config.h” config at the top.
I’m still unable to see it though, I’m gonna try and find all the troubleshooting steps I found last time.
Edit: it shows up as “serial (interface 0)” in device manager
So, there is a weird thing that happens on windows sometimes, where different boards get different drivers, and people have to use zadig for each new board they install to make it work properly. I don’t actually know what causes that, but it’s got to be either doing something weird with zadig, or some other driver messing it up.
Normally this weirdness only affects the DFU driver though, not the serial port.
What should i be doing inside Zadig?
I see the serial port, and if it’s in bootloader I see STM Bootloader, and the serial changes to “USB
device Interface 0” (correction that stays after unplugging the board, I think it’s unrelated)
Normally, you don’t need zadig, only proffie-dfu-setup.exe.
If you messed something up by using zadig, the way to fix it is to uninstall that driver, you can’t use zadig to fix it.
In case neither of the above help, the right way to use zadig is this: ProffieOS Documentation: Zadig
There may be times when zadig can help with other problems, but I don’t recommend it, because 99% of the time the solution is one of the steps above, not zadig.
Zadig can be useful for figuring out what driver is actually active for a device, but you can also check that using the device properties.
As always, this video may be helpful:
I ran the DFU setup after uninstalling the bootloader drivers, It popped up in arduino while the board was still in bootloader mode, On COM11 which was weird. It didn’t pop back up after plugging it back in.
It might not be a driver issue.
The board might be crashing or freezing on startup for some reason.
I’m not sure, the board starts up and ignites correctly, Theres no abnormalities in the sounds either.
While connected to usb?
Yea It’s working right on Both battery and USB (I have boot volume set really low, so the speaker sounds relatively normal even on USB power)
So I guess it has to be a driver thing then… Crashing would interrupt the audio, so you would notice if that was happening.
Have you tried watching the youtube video I linked and comparing the drivers with the ones shown in the video?
I have not yet, My fault, I’ll go through that again and take my time, I’ve been distracted with other things aswell, but Now I’m able to focus on the saber again.
Alright, I Seemed to have fixed it, after uninstalling the device, immediately after running DFU It showed up on port12, at first it didn’t upload, until I used bootloader again and then it switched to Port11, which let me upload, but then it dissapeared again.
then out of a whim, I did it again, but this time I uninstalled both the serial driver, and the bootloader driver before running DFU, And now it’s uploading and showing in serial monitor.
Thanks for the help, And my apologies for any frustrations.