V2.23 CLI connection fail extremly slow on arm linux compared to windows

[JSF]

Dear STM Support Team,

the following CLI command takes about 30 seconds on a Raspberry Pi (thanks again btw!) compared to 1 second max on windows:

 

STM32_Programmer_CLI -c port=swd sn=xyz

 

I am using this in a loop to detect whether a MCU is connected.

All other commands i tried are comparable in speed to windows so i guess this is a bug.

The Pi is a Model 5 running Bookworm and a 6.12 kernel.

 

Thank you very much!

 

 

 

[Kouthair]

Hello ​@JSF ,
We are delighted to know that you are enjoying the new STM32CubeProgrammer RPI package!
However, I have tried connecting and performing some operations, but it works instantly.
Can you tell me which device you are using?

[JSF]

Hello ​@Kouthair ,

 

thank you for your reply.

 

I am using a Raspberry Pi 5 with the Linux 6.18.34+rpt-rpi-2712 Kernel and Raspberry Pi OS 64-bit (Trixie).

I just did a fresh install and tried it again, but connect still takes 30 seconds when there is no MCU connected.

Is there a way i can get you more information?

This is my current output:

 

~ $ STM32_Programmer_CLI -c port=swd sn=002D00503039510934393838
      -------------------------------------------------------------------
                        STM32CubeProgrammer v2.23.0                  
      -------------------------------------------------------------------

ST-LINK SN  : 002D00503039510934393838
ST-LINK FW  : V3J16M8B5S1
Board       : STLINK-V3SET
Voltage     : 0.00V
Error: Unable to get core ID
Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication
2nd connect tentative with frequency (8MHz)
ST-LINK SN  : 002D00503039510934393838
ST-LINK FW  : V3J16M8B5S1
Board       : STLINK-V3SET
Voltage     : 0.00V
Error: Unable to get core ID
Error: No STM32 target found! If your product embeds Debug Authentication, please perform a discovery using Debug Authentication