cancel
Showing results for 
Search instead for 
Did you mean: 

connect problem - no response at all

stryga
Associate II

Using STM32_Programmer_CLI.exe (v2.13.0, on Win10) I try to connect via ST-Link / SWD, It works perfectly in the GUI but if I try

STM32_Programmer_CLI --connect port=SWD ap=1

nothing happens, not even an error, it just terminates. I can even write nonsense after the --connect - no response. 

--list works fine:

-------------------------------------------------------------------
STM32CubeProgrammer v2.13.0
-------------------------------------------------------------------

===== DFU Interface =====

No STM32 device in DFU mode connected

===== STLink Interface =====

-------- Connected ST-LINK Probes List --------

ST-Link Probe 0 :
ST-LINK SN : 003E00303331511134333834
ST-LINK FW : V3J11M3B5S
Access Port Number : 1
Board Name : STLINK-V3SET
-----------------------------------------------

===== UART Interface =====

Total number of serial ports available: 1

Port: COM6
Location: \\.\COM6
Description: STMicroelectronics STLink Virtual COM Port
Manufacturer: STMicroelectronics

What am I missing here? Thanks!

1 ACCEPTED SOLUTION

Accepted Solutions
stryga
Associate II

If found a work around, maybe someone else is interested: 
On my workstation there is also the CubeIDE installed, which brings its own STM32_Programmer_CLI.exe. For the failed attempts I tried to use the CLI-exe from the "normal" windows program folder, where also the GUI version is located. In my case C:\"Program Files"\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe

Now I switched to the IDE-version at C:\ST\STM32CubeIDE_1.12.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.0.600.202301161003\tools\bin\STM32_Programmer_CLI.exe and it works as expected. Maybe dll-hell deep inside, I won't investigate further. 

View solution in original post

2 REPLIES 2
stryga
Associate II

If found a work around, maybe someone else is interested: 
On my workstation there is also the CubeIDE installed, which brings its own STM32_Programmer_CLI.exe. For the failed attempts I tried to use the CLI-exe from the "normal" windows program folder, where also the GUI version is located. In my case C:\"Program Files"\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin\STM32_Programmer_CLI.exe

Now I switched to the IDE-version at C:\ST\STM32CubeIDE_1.12.1\STM32CubeIDE\plugins\com.st.stm32cube.ide.mcu.externaltools.cubeprogrammer.win32_2.0.600.202301161003\tools\bin\STM32_Programmer_CLI.exe and it works as expected. Maybe dll-hell deep inside, I won't investigate further. 

Kmax18
Senior