Windows binaries

[CubikingChill]

• Programmer/board type: STLINK/V2-1
• Operating system an version: Win10 IoT LTSC
• stlink tools version and/or git commit hash: 1.8.0 (Latest Windows Binary Release)
• stlink commandline tool name: All
• Target chip (and board, if applicable): STM32F401RE (NUCLEO-F401RE)

When I attempt to flash in VSCodium:

https://pastebin.com/Wk4HVQwB

ERROR:

[build] C:/Program Files (x86)/stlink/config/chips: No such file or directory

It seems that the location to the config folder is somehow fixed. I ve searched through MyProject, a project that uses stlink, and found nothing related to this fixed location.

[a-michelis]

Are you trying to use stlink as a library into your project?

That's not something baked into the codebase yet -a lot of rework has to be done for a providing a versatile API.

I've managed to do it with some modifications on the codebase on my fork (it's not available anymore) but that was just a temporary solution.

[CubikingChill]

No. I just follow the suggested way of installation.

I am not sure if anyone has managed to JUST unzip the binary into /Program Files (x86) and everything works like a charm.

Basically the latest windows binary release is packed in a weird form. There is a /Program Files subfolder which makes 0 sense.

[a-michelis]

Oh, I see now.

as per CMakeLists.txt, the default MCU configuration directory should be ./config/chips rather than what you see on the error message.

# MCU configuration files
if (WIN32)
set(CMAKE_CHIPS_DIR ./config/chips)
else ()
    set(CMAKE_CHIPS_DIR ${CMAKE_INSTALL_FULL_DATADIR}/${PROJECT_NAME}/config/chips)
endif()
add_definitions( -DSTLINK_CHIPS_DIR="${CMAKE_CHIPS_DIR}" )
file(GLOB CHIP_FILES ${CMAKE_SOURCE_DIR}/config/chips/*.chip)
install(FILES ${CHIP_FILES} DESTINATION ${CMAKE_CHIPS_DIR})

I see this as a bug, but I do not know how are the pre-built binaries compiled, so I'm not sure if that's the case.

That said, I just downloaded the windows binaries and I too find it confusing to understand it how it should be installed.

For plain usage, you should create a C:\Program Files (x86)\stlink\bin folder, place the contents of bin there. You should also place the config folder inside C:\Program Files (x86)\stlink, as hinted by the folder structure. Additionally, you may want to add C:\Program Files (x86)\stlink\bin to PATH environment library, so you can help with discovery by other tools. Of course, I suppose you already have libusb-1.0 installed in your system. If not, download the latest binary (.dll) and place it also under C:\Program Files (x86)\stlink\bin.

@Nightwalker-87 thoughts on this? I believe windows binaries could be shipped without fixed config path, as this would only make sense for library usage. Maybe changing Program Files path to a user oriented such as %APPDATA% would benefit less-permissive installations (per-user).