Updating STM32F373 over USB DFU Fails to Connect

[LMorr.3]

I'm able to connect to my STM32F373 board over a USB virtual port com successfully.  I'm also able to set BOOT0 high via a jumper and boot into the bootloader.  The Linux  'dmesg' command shows:

[3552008.377434] usb 3-2: new full-speed USB device number 101 using xhci_hcd
[3552008.526223] usb 3-2: New USB device found, idVendor=0483, idProduct=df11, bcdDevice=22.00
[3552008.526227] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[3552008.526229] usb 3-2: Product: STM32  BOOTLOADER
[3552008.526230] usb 3-2: Manufacturer: STMicroelectronics
[3552008.526231] usb 3-2: SerialNumber: 2077345D2039

 However when I run the STM32CubeProgrammer, it does not connect to the STM32F373 or even show it listed in the USB Port dropdown box.  It shows 'No DFU detected'.

I have set the boot jumper on my board and it does seem to be detected as 'STM32 BOOTLOADER' via the 'lsusb' command.

Am I able to use the USB DEVICE in CubeMX as a virtual port com, and then also use it as a USB DFU mode when it's in boot mode?

Any ideas on what I could try?

Best,

[LMorr.3]

UPDATE:  I tried setting the USB DEVICE to DFU in CubeMX instead of virtual port com, and it still would not connect or show the device the USB dropdown of STM32CubeProgrammer.

The ST-Link does work though but not sure how to get the USB DFU connection going.

UPDATE2: It works on a Mac, but not on Linux.  Anyone else have issues running USB DFU on Linux?

UPDATE3: If I'm running arm64 Linux, will the ST32CubeProgrammer work with USB DFU?  Is this true: "Install STM32CubeProgrammer for linux on an X86_64 system"???

[LMorr.3 · Accepted solution]

The solution was to add a udev rule for the device.