I would like to program a stm32vldiscovery from Linux.
Unfortunately, the board has a STLink V1 embedded. Is it possible to upgrade a STLink to STLink/V2?
Or is it possible to directly flash the board with an external STLink/V2?
GitHub - texane/stlink: stm32 discovery line linux programmer
Not sure if it a right finding:
$ make && [sudo] ./st-util There are a few options: ./st-util - usage: -h, --help Print this help -vXX, --verbose=XX Specify a specific verbosity level (0..99) -v, --verbose Specify generally verbose logging -s X, --stlink_version=X Choose what version of stlink to use, (defaults to 2) -1, --stlinkv1 Force stlink version 1 -p 4242, --listen_port=1234 Set the gdb server listen port. (default port: 4242) -m, --multi Set gdb server to extended mode. st-util will continue listening for connections after disconnect. -n, --no-reset Do not reset board on connection.
No way. ST-LINK hardware limitation.
Frankly I meant st-link/v2-1 which gives nice features (Virtual COM, mass storage).
The MCU for st-link seems to be the same for both v1 and v2.
The F103 part supporting the ST-LINK does not support V2 functionality (smaller memory, less functionality).
One could inject SWDIO/SWCLK via the Target side of the CN3 Jumper block. SB11 may need to be removed to disconnect the NRESET
To be honest probably better choices available at this point, either via a Nucleo, or more modern STM32 parts.
From the ST-LINK MCU perspective we have the following hw versions:
st-link/v1 - STM32F103C8T6 (the flash does not fit v2-1 firmware)
st-link/v2 - STM32F103C8T6 (the flash does not fit v2-1 firmware)
st-link/v2-1 - STM32F103CBT6
So the MCU for v1 and v2 seems to be the same, v2-1 has bigger flash MCU.
There are other HW differences between the v1 and v2 but I have not studied them carefully.
I got a look to the schematics, the STM32F103C8T6 is not connected to the same signals in st-link/v1 and st-link/v2.
Maybe that's why it is not possible to upgrade v1 to v2 in STLinkUpgrade.jar ?
I think it's not possible without additional PCB hacking. The MCU jest ok. I gave up ( I have a few boards).
On the other hands v2-1 really matters I guess. v2 has not Virtual COM for example.
Why do you need v2?
Because I am using Linux, v1 is not compatible
It works fine with texane/stlink. Thanks a lot.
is it possible to directly flash the board with an external STLink/V2?
I would go so far to recommend this explicitly.
The ST-Link V1 was a totally messed-up implementation, that totally screwed up the Linux USB driver when it came out.
Agree. That's why I rejected the idea as well. I like STM32VLDiscovery boards because of their compactness, and onboard 8MHz xtal.
Retrieving data ...