st-flash not working after FW-upgrade of STLink-v2 #956

busier · 2020-05-11T19:15:52Z

Hi,
Unfortunately, STlink Tools not working after firmware upgrade for board ST-LINK/V2.
However this board to works fine with STM32CubeIDE.

Programmer/board type: stlink /v2-clone
Programmer firmware version: V2J37S7
Operating system and version: Ubuntu 20.04
Stlink tools version: st-flash 1.6.0-301-gd11e6f4
Stlink commandline tool name: st-flash, st-util
Target chip (and board if applicable): STM32F407VET6

$ st-flash write foo.bin 0x8000000 
st-flash 1.6.0-301-gd11e6f4
2020-05-12T00:20:24 WARN common.c: unknown chip id! 0x5fa0004
Failed to connect to target

$ st-util --verbose=99
st-util
2020-05-12T00:22:26 DEBUG common.c: *** looking up stlink version
2020-05-12T00:22:26 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-05-12T00:22:26 DEBUG common.c: stlink pid     = 0x3748
2020-05-12T00:22:26 DEBUG common.c: stlink version = 0x2
2020-05-12T00:22:26 DEBUG common.c: jtag version   = 0x25
2020-05-12T00:22:26 DEBUG common.c: swim version   = 0x7
2020-05-12T00:22:26 DEBUG common.c: stlink current mode: debug (jtag or swd)
2020-05-12T00:22:26 DEBUG usb.c: JTAG/SWD freq set to 0
2020-05-12T00:22:26 DEBUG common.c: *** set_swdclk ***
2020-05-12T00:22:26 DEBUG common.c: stlink current mode: debug (jtag or swd)
2020-05-12T00:22:26 DEBUG common.c: *** stlink_jtag_reset ***
2020-05-12T00:22:26 DEBUG common.c: *** stlink_reset ***
2020-05-12T00:22:26 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-05-12T00:22:26 DEBUG common.c: Loading device parameters....
2020-05-12T00:22:26 DEBUG common.c: *** stlink_core_id ***
2020-05-12T00:22:26 DEBUG common.c: core_id = 0x2ba01477
2020-05-12T00:22:26 DEBUG common.c: *** stlink_read_debug32 5fa0004 is 0xe0042000
2020-05-12T00:22:26 WARN common.c: unknown chip id! 0x5fa0004
2020-05-12T00:22:26 DEBUG common.c: *** stlink_reset ***
2020-05-12T00:22:26 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-05-12T00:22:26 DEBUG gdb-server.c: Chip ID is 0x00000004, Core ID is 0x2ba01477.
2020-05-12T00:22:26 INFO gdb-server.c: Listening at *:4242...
^C2020-05-12T00:22:29 DEBUG common.c: *** stlink_run ***
2020-05-12T00:22:29 DEBUG common.c: *** stlink_exit_debug_mode ***
2020-05-12T00:22:29 DEBUG common.c: *** stlink_write_debug32 a05f0000 to 0xe000edf0
2020-05-12T00:22:29 DEBUG common.c: *** stlink_close ***

UPD. Jun 3 2020. 2@nightwalker-87.
I answer here, because the thread closed 4 comments.
Last update is Programmer firmware version: V2J37S7.
I did downgrade firmware V2J36S7 for to work st-flash.
Your versions FW V2.J29.S7 and V2.J34.S7 are too old.

The text was updated successfully, but these errors were encountered:

grzegorz-kraszewski · 2020-05-18T13:14:07Z

I have encountered the same problem after updating ST-Link firmware to 2.37.26 in Nucleo-64 STM32F030R8 board.

chenguokai · 2020-05-18T13:59:01Z

So may we add a comment like "DO NOT UPDATE STLINK FIRMWARE TO THE LATEST VERSION IF YOU WANT TO USE THIS SOFTWARE"?

Nightwalker-87 · 2020-05-18T14:05:44Z

To me it would be more interesting to know why this actually fails...
Maybe a patch is possible for the tools.
The proposed note should only be necessary if this is not possible.

grzegorz-kraszewski · 2020-05-18T14:05:58Z

DO NOT UPDATE STLINK FIRMWARE

For me it is too late... I have downgraded the firmware to the oldest version available on st.com, but it hasn't helped. As a workaround, I've managed to flash my code using bootloader, USART and stm32flash tool, so I know the target device is working.

busier · 2020-05-18T14:10:17Z

So may we add a comment like "DO NOT UPDATE STLINK FIRMWARE TO THE LATEST VERSION IF YOU WANT TO USE THIS SOFTWARE"?

I think: YES.
I was downgrade my st-link to stsw-link007_V2-36-26.

chenguokai · 2020-05-18T14:12:59Z

Maybe this link can provide some help

https://community.st.com/s/question/0D50X00009XkhxW/downgrade-stlinkv2-firmware-revision

Edit:

https://www.st.com/resource/en/release_note/dm00107009-firmware-upgrade-for-stlink-stlinkv2-stlinkv21-and-stlinkv3-boards-stmicroelectronics.pdf

RN0093 may also be helpful.

Could anyone figure out which version is the last known good one?

grzegorz-kraszewski · 2020-05-20T14:27:37Z

Could anyone figure out which version is the last known good one?

Unfortunately these old firmwares have only Windows updater. And, as one may guess, this updater does not work under wine.

chenguokai · 2020-05-20T15:23:43Z

Unfortunately these old firmwares have only Windows updater. And, as one may guess, this updater does not work under wine.

If I remember, I upgraded my stlink v2 clone with a java edition of the updater on macOS. The device functions well after the upgrade. I will check tomorrow if I still have that firmware on my computer.

Nightwalker-87 · 2020-06-03T00:09:36Z

I'll upgrade my STLINKv2/clone to the latest firmware and report if I run into any issues.

Nightwalker-87 · 2020-06-03T12:20:57Z

I have tested the original approach with the official firmware versions V2.J29.S7 and V2.J34.S7 and Release v1.6.1:

$USER@$DEVICE:/$LOCAL_PATH/Blinker/Release$ st-flash write Blinker.bin 0x8000000
st-flash 1.6.1
2020-06-03T14:19:16 INFO common.c: F1xx Medium-density: 20 KiB SRAM, 64 KiB flash in at least 1 KiB pages.
file Blinker.bin md5 checksum: 16277ff2c027d497361dbae4255081a1, stlink checksum: 0x0004644a
2020-06-03T14:19:16 INFO common.c: Attempting to write 3520 (0xdc0) bytes to stm32 address: 134217728 (0x8000000)
2020-06-03T14:19:16 INFO common.c: Flash page at addr: 0x08000000 erased
2020-06-03T14:19:16 INFO common.c: Flash page at addr: 0x08000400 erased
2020-06-03T14:19:16 INFO common.c: Flash page at addr: 0x08000800 erased
2020-06-03T14:19:16 INFO common.c: Flash page at addr: 0x08000c00 erased
2020-06-03T14:19:16 INFO common.c: Finished erasing 4 pages of 1024 (0x400) bytes
2020-06-03T14:19:16 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2020-06-03T14:19:16 INFO flash_loader.c: Successfully loaded flash loader in sram
  4/4 pages written
2020-06-03T14:19:16 INFO common.c: Starting verification of write complete
2020-06-03T14:19:16 INFO common.c: Flash written and verified! jolly good!

$USER@$DEVICE:/$LOCAL_PATH/git/stlink$ st-util --verbose=99
st-util
2020-06-03T13:13:44 DEBUG common.c: *** looking up stlink version
2020-06-03T13:13:44 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-06-03T13:13:44 DEBUG common.c: stlink pid     = 0x3748
2020-06-03T13:13:44 DEBUG common.c: stlink version = 0x2
2020-06-03T13:13:44 DEBUG common.c: jtag version   = 0x22
2020-06-03T13:13:44 DEBUG common.c: swim version   = 0x7
2020-06-03T13:13:44 DEBUG common.c: *** looking up stlink version
2020-06-03T13:13:44 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-06-03T13:13:44 DEBUG common.c: stlink pid     = 0x3748
2020-06-03T13:13:44 DEBUG common.c: stlink version = 0x2
2020-06-03T13:13:44 DEBUG common.c: jtag version   = 0x22
2020-06-03T13:13:44 DEBUG common.c: swim version   = 0x7
2020-06-03T13:13:44 DEBUG common.c: stlink current mode: mass
2020-06-03T13:13:44 DEBUG usb.c: JTAG/SWD freq set to 0
2020-06-03T13:13:44 DEBUG common.c: *** set_swdclk ***
2020-06-03T13:13:44 DEBUG common.c: stlink current mode: mass
2020-06-03T13:13:44 DEBUG common.c: *** stlink_enter_swd_mode ***
2020-06-03T13:13:44 DEBUG common.c: *** stlink_jtag_reset ***
2020-06-03T13:13:44 DEBUG common.c: *** stlink_reset ***
2020-06-03T13:13:44 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-06-03T13:13:44 DEBUG common.c: Loading device parameters....
2020-06-03T13:13:44 DEBUG common.c: *** stlink_core_id ***
2020-06-03T13:13:44 DEBUG common.c: core_id = 0x2ba01477
2020-06-03T13:13:44 DEBUG common.c: *** stlink_read_debug32 20036410 is 0xe0042000
2020-06-03T13:13:44 DEBUG common.c: *** stlink_read_debug32 ffff0040 is 0x1ffff7e0
2020-06-03T13:13:44 INFO common.c: F1xx Medium-density: 20 KiB SRAM, 64 KiB flash in at least 1 KiB pages.
2020-06-03T13:13:44 DEBUG common.c: *** stlink_reset ***
2020-06-03T13:13:44 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-06-03T13:13:44 DEBUG gdb-server.c: Chip ID is 0x00000410, Core ID is 0x2ba01477.
2020-06-03T13:13:44 INFO gdb-server.c: Listening at *:4242...
2020-06-03T14:07:48 DEBUG common.c: *** stlink_force_debug_mode ***
2020-06-03T14:07:48 DEBUG common.c: *** stlink_reset ***
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 3 to 0xe0002000
2020-06-03T14:07:48 DEBUG common.c: *** stlink_read_debug32 261 is 0xe0002000
2020-06-03T14:07:48 INFO gdb-server.c: Found 6 hw breakpoint registers
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe0002008
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe000200c
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe0002010
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe0002014
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe0002018
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe000201c
2020-06-03T14:07:48 DEBUG gdb-server.c: init watchpoints
2020-06-03T14:07:48 DEBUG common.c: *** stlink_read_debug32 0 is 0xe000edfc
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 1000000 to 0xe000edfc
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe0001028
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe0001038
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe0001048
2020-06-03T14:07:48 DEBUG common.c: *** stlink_write_debug32 0 to 0xe0001058
2020-06-03T14:07:48 INFO gdb-server.c: GDB connected.
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qSupported:multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386
2020-06-03T14:07:48 DEBUG gdb-server.c: query: Supported;multiprocess+;swbreak+;hwbreak+;qRelocInsn+;fork-events+;vfork-events+;exec-events+;vContSupported+;QThreadEvents+;no-resumed+;xmlRegisters=i386
2020-06-03T14:07:48 DEBUG gdb-server.c: send: PacketSize=3fff;qXfer:memory-map:read+
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: vMustReplyEmpty
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: !
2020-06-03T14:07:48 DEBUG gdb-server.c: send: OK
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: Hg0
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qTStatus
2020-06-03T14:07:48 DEBUG gdb-server.c: query: TStatus;
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: ?
2020-06-03T14:07:48 DEBUG gdb-server.c: send: S05
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qfThreadInfo
2020-06-03T14:07:48 DEBUG gdb-server.c: query: fThreadInfo;
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qL1200000000000000000
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: Hc-1
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qC
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qAttached
2020-06-03T14:07:48 DEBUG gdb-server.c: query: Attached;
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: g
2020-06-03T14:07:48 DEBUG common.c: *** stlink_read_all_regs ***
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 00000001fc7f000000d37f1f01f8dd32000000010000000100000001000000010000000100000001000000010000000100000001000000010000000100000001
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qL1200000000000000000
2020-06-03T14:07:48 DEBUG gdb-server.c: send: 
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qXfer:memory-map:read::0,1000
2020-06-03T14:07:48 DEBUG gdb-server.c: query: Xfer;memory-map:read::0,1000
2020-06-03T14:07:48 DEBUG gdb-server.c: Xfer: type:memory-map;op:read;annex:;addr:0;length:4096
2020-06-03T14:07:48 DEBUG gdb-server.c: send: m<?xml version="1.0"?><!DOCTYPE memory-map PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"     "http://sourceware.org/gdb/gdb-memory-map.dtd"><memory-map>  <memory type="rom" start="0x00000000" length="0x10000"/>  <memory type="ram" start="0x20000000" length="0x5000"/>  <memory type="flash" start="0x08000000" length="0x10000">    <property name="blocksize">0x400</property>  </memory>  <memory type="ram" start="0x40000000" length="0x1fffffff"/>  <memory type="ram" start="0xe0000000" length="0x1fffffff"/>  <memory type="rom" start="0x1ffff000" length="0x800"/>  <memory type="rom" start="0x1ffff800" length="0x10"/></memory-map>
2020-06-03T14:07:48 DEBUG gdb-server.c: recv: qXfer:memory-map:read::27c,1000
2020-06-03T14:07:48 DEBUG gdb-server.c: query: Xfer;memory-map:read::27c,1000
2020-06-03T14:07:48 DEBUG gdb-server.c: Xfer: type:memory-map;op:read;annex:;addr:636;length:4096
2020-06-03T14:07:48 DEBUG gdb-server.c: send: l

I'll do a second test with the previous release for investigation. However, we can already confirm that there is no general problem with current STLINKv2 firmware versions, even if used with cloned programming devices.

Nightwalker-87 · 2020-06-03T12:32:15Z

* Programmer firmware version: stsw-link007_V2-37-26

@busier: This is the version of the upgrade tool, not the firmware version of the programmer. The latter is determined by the upgrade tool and the latest available version is displayed afterwards. Please retry with your hardware and only use official tools and versions from ST.

Nightwalker-87 · 2020-06-03T14:56:35Z

UPD. Jun 3 2020. 2@nightwalker-87.
I answer here, because the thread closed 4 comments.
Last update is Programmer firmware version: V2J37S7.
I did downgrade firmware V2J36S7 for to work st-flash.
Your versions FW V2.J29.S7 and V2.J34.S7 are too old.

The thread is open again. These are the latest versions which are offered for a STLINK-v2 & and STLINK-v2 clone programmer here via the ST firmware-update tool. I personally can not test on any other hardware, sry.
If there is no further verification and contribution then we can't do anything about it, I'm afraid.

Nightwalker-87 · 2020-06-03T15:22:37Z

Another test with Release v1.6.1 and Firmware V2.J36.S7 (tool-updated to 2.5.3):

$USER@$DEVICE:/$LOCAL_PATH:~/Schreibtisch/Blinker/Release$ st-flash write Blinker.bin 0x8000000
st-flash 1.6.1
2020-06-03T17:14:50 INFO common.c: F1xx Medium-density: 20 KiB SRAM, 64 KiB flash in at least 1 KiB pages.
file Blinker.bin md5 checksum: 16277ff2c027d497361dbae4255081a1, stlink checksum: 0x0004644a
2020-06-03T17:14:50 INFO common.c: Attempting to write 3520 (0xdc0) bytes to stm32 address: 134217728 (0x8000000)
2020-06-03T17:14:50 INFO common.c: Flash page at addr: 0x08000000 erased
2020-06-03T17:14:50 INFO common.c: Flash page at addr: 0x08000400 erased
2020-06-03T17:14:50 INFO common.c: Flash page at addr: 0x08000800 erased
2020-06-03T17:14:50 INFO common.c: Flash page at addr: 0x08000c00 erased
2020-06-03T17:14:50 INFO common.c: Finished erasing 4 pages of 1024 (0x400) bytes
2020-06-03T17:14:50 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2020-06-03T17:14:50 INFO flash_loader.c: Successfully loaded flash loader in sram
  4/4 pages written
2020-06-03T17:14:50 INFO common.c: Starting verification of write complete
2020-06-03T17:14:50 INFO common.c: Flash written and verified! jolly good!

We are getting closer - there is ANOTHER update available in the meanwhile which deploys V2J37S7 - so you are correct. I have tested the latter as well with the same result.
You may need a st-flash erase before flashing. Anyhow I still can't reproduce.

Nightwalker-87 · 2020-06-03T16:05:10Z

Good news:
The latest firmware V2.J37.S7 (fw-tool-updated to 2.5.4) even works with Release v1.6.0.

$USER@$DEVICE:/$LOCAL_PATH:/$LOCAL_PATH/git/stlink$ /$LOCAL_PATH/git/stlink/build/Release/st-info --version
v1.6.0
$USER@$DEVICE:/$LOCAL_PATH:/$LOCAL_PATH/git/stlink$ /$LOCAL_PATH/git/stlink/build/Release/st-flash erase
st-flash 1.6.0
2020-06-03T17:53:24 INFO common.c: Loading device parameters....
2020-06-03T17:53:24 INFO common.c: Device connected is: F1 Medium-density device, id 0x20036410
2020-06-03T17:53:24 INFO common.c: SRAM size: 0x5000 bytes (20 KiB), Flash: 0x10000 bytes (64 KiB) in pages of 1024 bytes
Mass erasing
$USER@$DEVICE:/$LOCAL_PATH:/$LOCAL_PATH/git/stlink$ /$LOCAL_PATH/git/stlink/build/Release/st-flash write /$LOCAL_PATH/Blinker/Release/Blinker.bin 0x8000000
st-flash 1.6.0
2020-06-03T17:54:22 INFO common.c: Loading device parameters....
2020-06-03T17:54:22 INFO common.c: Device connected is: F1 Medium-density device, id 0x20036410
2020-06-03T17:54:22 INFO common.c: SRAM size: 0x5000 bytes (20 KiB), Flash: 0x10000 bytes (64 KiB) in pages of 1024 bytes
2020-06-03T17:54:22 INFO common.c: Attempting to write 3520 (0xdc0) bytes to stm32 address: 134217728 (0x8000000)
Flash page at addr: 0x08000c00 erased
2020-06-03T17:54:22 INFO common.c: Finished erasing 4 pages of 1024 (0x400) bytes
2020-06-03T17:54:22 INFO common.c: Starting Flash write for VL/F0/F3/F1_XL core id
2020-06-03T17:54:22 INFO flash_loader.c: Successfully loaded flash loader in sram
  4/4 pages written
2020-06-03T17:54:22 INFO common.c: Starting verification of write complete
2020-06-03T17:54:22 INFO common.c: Flash written and verified! jolly good!

Nightwalker-87 · 2020-06-03T16:23:32Z

I have encountered the same problem after updating ST-Link firmware to 2.37.26 in Nucleo-64 STM32F030R8 board.

@grzegorz-kraszewski: Your board uses a different programmer hardware: STLINK-v2-1.
Please open a separate issue for that if still relevant. This ticket is solely related to STLINK-v2. Thx.

@chenguokai: I think we should close this now as resolved, as the original problem obviously does not relate to the stlink toolset.

busier · 2020-06-03T16:24:21Z

don't changes:

:~/stlink/build/Release/bin$ ./st-flash write ~/Downloads/monitor_lmi.bin 0x8000000
st-flash 1.6.0-364-g60f8461
2020-06-03T19:18:40 WARN common.c: unknown chip id! 0x5fa0004
Failed to connect to target

Nightwalker-87 · 2020-06-03T16:36:28Z

@busier: As shown, this is not a problem of the stlink toolset itself. Firmware is provided by ST Microelectronics as a commercial, proprietary product. Therefore you need to refer to the official ST-Link support forum. We can not provide firmware-support, because it is not part of this project nor do we have developer access to it.

chenguokai · 2020-06-04T03:34:50Z

My local test with a ST Link v2 clone seems fine with FW version V2J37S7 too.

Could there be some issues specific to the on-board ST Links?

Nightwalker-87 · 2020-06-04T09:32:55Z

We don't know yet, but that's why I suggested @grzegorz-kraszewski to open a separate ticket, if the problem persists on an onboard V2-1 module.

busier · 2020-06-04T13:59:41Z

For Ubuntu 20.04 and Ubuntu 18.04.
STM32CubeProgrammer with STM32F103C8T6 (bluepill).
STM32CubeProgrammer with STM32F407VET6.
But st-flash out haven't any changes:

st-flash 1.6.0-364-g60f8461
2020-06-03T19:18:40 WARN common.c: unknown chip id! 0x5fa0004
Failed to connect to target

Nightwalker-87 · 2020-06-04T14:02:28Z

@busier: This ticket is closed and will not be reopened. Please do not recycle it.

busier added the needs/investigation label May 11, 2020

busier changed the title ~~[Your device name]: [Title]~~ [ST-Link V2]: [fw upgrade] May 11, 2020

busier changed the title ~~[ST-Link V2]: [fw upgrade]~~ [ST-Link V2]: [st-flash not work after fw upgrade] May 11, 2020

Nightwalker-87 added component/st-flash os/linux programmer/STLINK/V2 Clone non-official clone devices target/stm32f4 labels May 12, 2020

Nightwalker-87 added this to the v1.6.2 milestone May 12, 2020

Nightwalker-87 changed the title ~~[ST-Link V2]: [st-flash not work after fw upgrade]~~ st-flash not work after fw upgrade of STLink-v2 May 12, 2020

Nightwalker-87 changed the title ~~st-flash not work after fw upgrade of STLink-v2~~ st-flash not working after FW-upgrade of STLink-v2 May 12, 2020

Nightwalker-87 added the target/stm32f0 label May 18, 2020

Nightwalker-87 added the error/unknown-chipid label May 18, 2020

Nightwalker-87 self-assigned this Jun 3, 2020

Nightwalker-87 added component/st-util and removed needs/investigation labels Jun 3, 2020

Nightwalker-87 removed their assignment Jun 3, 2020

Nightwalker-87 self-assigned this Jun 3, 2020

Nightwalker-87 closed this as completed Jun 3, 2020

Nightwalker-87 added status/no-bug status/resolved-verified status/wont-fix labels Jun 3, 2020

stlink-org locked as resolved and limited conversation to collaborators Jun 4, 2020

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

st-flash not working after FW-upgrade of STLink-v2 #956

st-flash not working after FW-upgrade of STLink-v2 #956

busier commented May 11, 2020 •

edited

grzegorz-kraszewski commented May 18, 2020

chenguokai commented May 18, 2020

Nightwalker-87 commented May 18, 2020

grzegorz-kraszewski commented May 18, 2020

busier commented May 18, 2020

chenguokai commented May 18, 2020 •

edited

grzegorz-kraszewski commented May 20, 2020

chenguokai commented May 20, 2020

Nightwalker-87 commented Jun 3, 2020

Nightwalker-87 commented Jun 3, 2020

Nightwalker-87 commented Jun 3, 2020

Nightwalker-87 commented Jun 3, 2020 •

edited

Nightwalker-87 commented Jun 3, 2020 •

edited

Nightwalker-87 commented Jun 3, 2020

Nightwalker-87 commented Jun 3, 2020

busier commented Jun 3, 2020 •

edited

Nightwalker-87 commented Jun 3, 2020

chenguokai commented Jun 4, 2020

Nightwalker-87 commented Jun 4, 2020

busier commented Jun 4, 2020

Nightwalker-87 commented Jun 4, 2020

st-flash not working after FW-upgrade of STLink-v2 #956

st-flash not working after FW-upgrade of STLink-v2 #956

Comments

busier commented May 11, 2020 • edited

grzegorz-kraszewski commented May 18, 2020

chenguokai commented May 18, 2020

Nightwalker-87 commented May 18, 2020

grzegorz-kraszewski commented May 18, 2020

busier commented May 18, 2020

chenguokai commented May 18, 2020 • edited

grzegorz-kraszewski commented May 20, 2020

chenguokai commented May 20, 2020

Nightwalker-87 commented Jun 3, 2020

Nightwalker-87 commented Jun 3, 2020

Nightwalker-87 commented Jun 3, 2020

Nightwalker-87 commented Jun 3, 2020 • edited

Nightwalker-87 commented Jun 3, 2020 • edited

Nightwalker-87 commented Jun 3, 2020

Nightwalker-87 commented Jun 3, 2020

busier commented Jun 3, 2020 • edited

Nightwalker-87 commented Jun 3, 2020

chenguokai commented Jun 4, 2020

Nightwalker-87 commented Jun 4, 2020

busier commented Jun 4, 2020

Nightwalker-87 commented Jun 4, 2020

busier commented May 11, 2020 •

edited

chenguokai commented May 18, 2020 •

edited

Nightwalker-87 commented Jun 3, 2020 •

edited

Nightwalker-87 commented Jun 3, 2020 •

edited

busier commented Jun 3, 2020 •

edited