STM32CubeProgrammer Bugs with Linux and USB DFU

[CodingEngineer]

Hello,

I'm using STM32CubeProgrammer v2.17.0 with Linux (Linux Mint 21.3). There are a some bugs/improvements I discovered:

1. By default, USB DFU devices are not recognized by STM32CubeProgrammer in user mode due to a permissions issue. To resolve this, I manually added an udev rule to allow access to USB DFU devices without requiring root permissions. It's unclear why this isn't the default configuration, especially since udev rules for STLink devices are automatically set up during the installation process.

My udev rule (new file in /etc/udev/rules.d/)

 

Spoiler

# stm32 dfu mode, give access for STM32 cube programmer

SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="df11", \
MODE="660", GROUP="plugdev", TAG+="uaccess"

 

2. It seems that the UI isn't displayed correctly for USB DFU mode. Connecting to the USB device work, but the connect button stays disabled and the status text displays "Not connected". After reading some memory, the button becomes enabled but still displays "Connect". See attached screenshots.

I'm using a NUCLEO-F767ZI board with System Memory Bootloader.

[Imen.D]

Hello @CodingEngineer and welcome to the ST Community,

I escalated this request to involved people to take a closer look at the problem (internal ticket 194294).

We'll make sure to post any updates here as soon as we have an update.

PS: Internal ticket 194294 is not accessible or usable by customers.

[Imen.D]

Hi @CodingEngineer,

For the first point, there is no issue there:

udev rules for ST-LINK are also not copied during STM32CubeProgrammer setup.

Maybe you thought they were automatically copied when installing CubeProgrammer because you previously setup another IDE/programming tool supporting ST-LINK.

On a fresh Linux setup, udev rules for ST-LINK will need to also be copied in etc/udev/rules.d.

This modification is required and documented in UM2237 page 13.

This is the way it is done in CubeProgrammer in order to enable to copy only the rules needed.

For example, if user ONLY uses ST-LINK-V3, he will only need to copy stlinkv3.rules to etc/udev/rules.d, and nothing else.

For the second point : it is under investigation. Our team is looking into it and I'll make sure to post any updates here as soon as I hear back from them.

[Ozone]

> For the first point, there is no issue there:
> udev rules for ST-LINK are also not copied during STM32CubeProgrammer setup.

I beg to disagree.
Other toolchains/debuggers do ask during the installation process, and set up the proper groups for the current user.

Methinks Linux testing and support is a bit lacking on ST's side.

[Imen.D]

Hi @CodingEngineer 

The second issue has just been fixed in the new release of STM32CubeProgrammer v2.20.

Thank you for your contribution.