Port menu greyed out. Computer does not recognize proffieboard

ProffieOS
1

I got a TXQ proffie recently that will not register when I plug it in with a USB to my computer. I have done every installation step (I have done proffie stuff before) including the dfu, zadig, etc. I have tried setting it into bootloader mode and that is the only way I can get my computer to recognize the board but only as “STM32 BOOTLOADER.” On the bottom right of Arduino on ProffieOS, it says “Proffieboard V3 on [not connected]” and if I try and compile and upload the config file to my board, it will disconnect the “STM32 BOOTLOADER” usb connection off of my computer, requiring me to reinitialize it into bootloader mode to plug it back in. I have tried rerouting drivers using Zadig to no avail, uninstalling the drivers and reinstalling them, nothing. This computer is where I have edited my previous proffie saber, so I don’t believe it is anything having to do with the computer. I have even installed ProffieOS and such on a different computer and the same issue persists. So I want to say it is not a computer problem. I have watched every tutorial even ones linked on this site on this issue and it feels like no one is troubleshooting my exact issue.

I was able to upload a config file to it, and it did the 1-10 error and then eventually it bricked it and won’t turn on because I think I messed something up in the config file. And since then I have not been able to connect the board to the computer. But I still believe the board is operational because it responds to the bootloader initialization

At this point, I just want someone to troubleshoot with me because I feel like I am going insane!

2

so you manually put the board in bootloader mode with the buttons and it shows up to the PC as STM32BOOTLOADER, yes?
What driver does Devices and Printers show is being used for it ?
It should be WinUSB v6.1.7600.16385.
if it’s not, delete the driver and delete the device.
Unplug the board, and run proffie-dfu-setup.exe

Replug in the Proffieboard.
Does it show up to the PC as a Proffieboard?
If so, open Arduino, and try uploading.
If it fails, open Serial Monitor and send RebootDFU to restart the board in bootloader mode (or do the hold BOOT, press and release RESET, release BOOT button dance again), then check the driver for STM32BOOTLOADER again…
If it’s not WinUSB v6.1.7600.16385, then something on your computer is messing with the driver. Look for Guillemot stuff, or Cura3D, or Thrustmaster controller stuff (all known to screw up the STM32 driver)
Remove any/all of those things and run proffie-dfu-setup again, try uploading again, etc…

3

Woah, thanks for responding so quickly!

Devices and Printers label it in the “Unspecified” tab as “STM32 BOOTLOADER”
The driver is correct at 6.1.7600.16835

I tried deleting the device and driver and re-executing the dfu program and nothing

The board is not assigning itself to a COM port, it’s greyed out also. So I cannot use the Serial Monitor

4

is what you want to load a config. Just click upload even with the port greyed out

5

if you see this no need to delete it.

6

It is never permanently bricked. Follow this link:

7

another quote from old notes that might be helpfuL:

" Proffieboard use 2 different drivers on the computer, depending on how it’s booted.

Just like a PC running Windows 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,

Proffieboards either boot into normal mode running ProffieOS, or bootloader mode.

Each of those states looks like a different device to the PC. Different devices require different drivers to talk to your computer properly.

If you install the wrong driver for a device, it’s not going to work, simply put.

When booted normally and running ProffieOS, the board shows up as a “Proffieboard”, a composite serial device (CDC data etc…).

Windows typically sees this device when first connected, installs the driver on its own, and will use usbser.sys driver.

The board should be seen on a COM port in Arduino under menu Tools>Port.

It will not show up here if in bootloader mode.

When it’s in bootloader mode and showing as STM32BOOTLOADER, it needs WinUSB v6.1.7600.16385 driver installed with proffie-dfu-setup or Zadig.

It’s a one-time setup installation when the PC sees the board for the first time in bootloader mode.

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.

Then when the upload is complete, the board reboots back into normal ProffieOS.

*** There is no need to have the board in bootloader mode or even connected at all if you run proffie-dfu-setup.exe to install the STM32BOOTLOADER driver
If for some reason you want to use Zadig instead, here are some notes:
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.

Putting the board into bootloader mode so you can run Zadig and install the correct driver for STM32BOOTLOADER device can be done 2 ways, either with the onboard buttons, or via Serial Monitor in Arduino.

Button sequence is HOLD BOOT, PRESS and RELEASE RESET, then RELEASE BOOT.

Alternately, you could also hold BOOT with one hand, and connect the other end of the USB to the computer while holding BOOT.

Either result in the same sequence that is required; powering on the board while the BOOT button is held.

Serial Monitor command is simply choosing the COM port with the “Proffieboard” under Arduino menu Tools>Port, and sending the command RebootDFU.

If the computer has forgotten the driver, or the driver was overwritten, or SOME stupid Windows thing happened… you might just need to re-run proffie-dfu-setup or Zadig.

If things still don’t continue working once this is done, you may have another device using a conflicting driver, see this thread for info:

Login Required | The Rebel Armory"

1 Like
8

IMHO, this is POD worthy material :wink:

1 Like
9

I am a little confused about the Serial monitor note (sorry I’m slow). It won’t let me access the serial monitor at all because I cannot select any port, saying “Not connected. Select a board and port to select automatically”.

I have also tried many times to try and upload it just by plugging it in and through bootloader mode. It fully does the process, attached is my output (idk if it will upload correctly), but when it finishes through the 0-100% downloading stage, the computer makes the USB-detaching sound when it was attached in bootloader mode. Obviously without it being in bootloader, it never was even recognized by my computer as anything.

So yes, I have the correct drivers, correct settings on Arduino, I did not find any of the conflicting perpetrators that you suggested, and my cable and board seem to work as they respond to the bootloading process. But when I put it into bootloader mode, the computer will recognize it as “STM32 BOOTLOADER.” Furthermore, my Tools>Port is greyed out.

10

And if you don’t mind explaining which thread may be useful in The Rebel Armory. For me, the link didn’t work as intended. Thank yall for your help, it’s very much appreciated!!

11
12

That is the sign of a successful upload.

Once successfully uploaded you don’t want to see STM32BOOTLOADER anymore, until you are ready for the next upload.

Now you want to see “Proffieboard V3 on COM3” so you can play with the Serial Monitor.

13

@profezzorn what I meant about POD worthy material is: “I think what Bryan wrote/pasted above is a lot easier to understand for less tech-savvy / less fluent in English person than what is in the POD.”

Can that be added to the POD ?

14

I forgot to say after the USB disconnected sound plays after the 0-100% download, the Port option is stil greyed out, Arduino says nothing is connected, and the saber does nothing. Any thoughts?

15

The only thing that comes to mind is: post your config so we can take a look.

So no lights and no sound ?

16

Are u on windows 11, I was having a similar problem after an update.

once upload was complete the board went into DFU mode, while in DFU mode go into device manager and uninstall it, then run proffie-dfu-setup this sorted the problem out for me,

17

Correct. No lights no sound. And I am on windows 10. Is DFU mode = bootloader mode?

I asked the company I bought my saber from (Theory Sabers) for their config file for my 2 button, 1 blade proffie. This is what was sent
Theory2Button.h (39.1 KB)

18

Yes, go into device manager locate it under usb devices then uninstall/delete the driver then run dfu setup

19

Yes and no, kinda. I believe in the way that @Aaron_Hilditch describes it, it’s yes.

But, and @profezzorn please correct me if I am wrong, your Proffieboard can run 2 “programs”: ProffieOS or STM32BOOTLOADER. DFU is the program that runs on your computer to access STM32BOOTLOADER to upload a new ProffieOS on your Proffieboard.

Every time you upload a new config to your saber, the whole of ProffieOS (newer or not) gets re-uploaded as well, not “just” the config.

We often mix the terms DFU and Bootloader (or STM32BOOTLOADER) to imply the same thing.

So no they are not the same, but yes we mean the same thing!

Clear as mud ?

20

DFU stands for Device Firmware Upgrade.

DFU Mode typically refers to running the board in bootloader mode.

DFU systems are a part of the bootloader, if that makes sense.

On the computer side it’s just a virtual serial port that streams the binary code blob (with some extra steps) to the board for the DFU software on board to replace the current “user program” with. In this case ProffieOS.

Things in firmware tend to not be so clear-cut in purpose as one would like to conceptually think they are. By necessity and for the sake of simplicity. Honestly many concepts are not so black and white.

1 Like