ST-Link V2 clone: "unknown chip id! 0x3748" after FW update to V2J37S7 #1012

JelmerT · 2020-08-05T07:13:41Z

Programmer/board type: [v2-clone]
Programmer firmware version: [V2J37S7]
Operating system and version: [macOS]
Stlink tools version and/or git commit hash: [1.6.1] (homebrew version)
Stlink commandline tool name: [All]
Target chip (and board if applicable): [none]

Commandline-Output:

$ st-flash --debug erase                                                                                                                                                                             
st-flash 1.6.1
2020-08-05T00:04:19 DEBUG common.c: *** looking up stlink version
2020-08-05T00:04:19 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-08-05T00:04:19 DEBUG common.c: stlink pid     = 0x3748
2020-08-05T00:04:19 DEBUG common.c: stlink version = 0x2
2020-08-05T00:04:19 DEBUG common.c: jtag version   = 0x25
2020-08-05T00:04:19 DEBUG common.c: swim version   = 0x7
2020-08-05T00:04:19 DEBUG common.c: *** looking up stlink version
2020-08-05T00:04:19 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-08-05T00:04:19 DEBUG common.c: stlink pid     = 0x3748
2020-08-05T00:04:19 DEBUG common.c: stlink version = 0x2
2020-08-05T00:04:19 DEBUG common.c: jtag version   = 0x25
2020-08-05T00:04:19 DEBUG common.c: swim version   = 0x7
2020-08-05T00:04:19 DEBUG common.c: stlink current mode: mass
2020-08-05T00:04:19 DEBUG usb.c: JTAG/SWD freq set to 0
2020-08-05T00:04:19 DEBUG common.c: *** set_swdclk ***
2020-08-05T00:04:19 DEBUG common.c: stlink current mode: mass
2020-08-05T00:04:19 DEBUG common.c: *** stlink_enter_swd_mode ***
2020-08-05T00:04:19 DEBUG common.c: *** stlink_jtag_reset ***
2020-08-05T00:04:19 DEBUG common.c: *** stlink_reset ***
2020-08-05T00:04:19 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-08-05T00:04:19 DEBUG common.c: Loading device parameters....
2020-08-05T00:04:19 DEBUG common.c: *** stlink_core_id ***
2020-08-05T00:04:19 DEBUG common.c: core_id = 0x00003748
2020-08-05T00:04:19 DEBUG common.c: *** stlink_read_debug32 3748 is 0xe0042000
2020-08-05T00:04:19 WARN common.c: unknown chip id! 0x3748
Failed to connect to target

$ st-info --probe                                                                                                                                                                                    
Found 1 stlink programmers
 serial:     513f6a06506752541626213f
 hla-serial: "\x51\x3f\x6a\x06\x50\x67\x52\x54\x16\x26\x21\x3f"
 flash:      0 (pagesize: 0)
 sram:       0
 chipid:     0x0748

$ st-util -v99                                                                                                                                                                                                
st-util
2020-08-05T00:05:06 DEBUG common.c: *** looking up stlink version
2020-08-05T00:05:06 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-08-05T00:05:06 DEBUG common.c: stlink pid     = 0x3748
2020-08-05T00:05:06 DEBUG common.c: stlink version = 0x2
2020-08-05T00:05:06 DEBUG common.c: jtag version   = 0x25
2020-08-05T00:05:06 DEBUG common.c: swim version   = 0x7
2020-08-05T00:05:06 DEBUG common.c: *** looking up stlink version
2020-08-05T00:05:06 DEBUG common.c: st vid         = 0x0483 (expect 0x0483)
2020-08-05T00:05:06 DEBUG common.c: stlink pid     = 0x3748
2020-08-05T00:05:06 DEBUG common.c: stlink version = 0x2
2020-08-05T00:05:06 DEBUG common.c: jtag version   = 0x25
2020-08-05T00:05:06 DEBUG common.c: swim version   = 0x7
2020-08-05T00:05:06 DEBUG common.c: stlink current mode: mass
2020-08-05T00:05:06 DEBUG usb.c: JTAG/SWD freq set to 0
2020-08-05T00:05:06 DEBUG common.c: *** set_swdclk ***
2020-08-05T00:05:06 DEBUG common.c: stlink current mode: mass
2020-08-05T00:05:06 DEBUG common.c: *** stlink_enter_swd_mode ***
2020-08-05T00:05:06 DEBUG common.c: *** stlink_jtag_reset ***
2020-08-05T00:05:06 DEBUG common.c: *** stlink_reset ***
2020-08-05T00:05:06 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-08-05T00:05:06 DEBUG common.c: Loading device parameters....
2020-08-05T00:05:06 DEBUG common.c: *** stlink_core_id ***
2020-08-05T00:05:06 DEBUG common.c: core_id = 0x00003748
2020-08-05T00:05:06 DEBUG common.c: *** stlink_read_debug32 3748 is 0xe0042000
2020-08-05T00:05:06 WARN common.c: unknown chip id! 0x3748
2020-08-05T00:05:06 DEBUG common.c: *** stlink_reset ***
2020-08-05T00:05:06 DEBUG common.c: *** stlink_write_debug32 5fa0004 to 0xe000ed0c
2020-08-05T00:05:06 DEBUG gdb-server.c: Chip ID is 0x00000748, Core ID is 0x003748.
2020-08-05T00:05:06 INFO gdb-server.c: Listening at *:4242...

Possible duplicate of #956

V2 clone was working just fine, noticed it was on older firmware, upgraded it with STSW-LINK007 (2.37.26) - STLinkUpgrade 3.3.4 to version V2J37S7.

Upgrade went fine, but independent of what is connected to the programmer I'm getting the unknown chip id! 0x3748 error.
Tested with known good board (bluepill).

this comment in #956 reports 1.6.1 working with a V2 Clone with firmware V2J37S7. So I have no clue what's going wrong here.

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

Nightwalker-87 · 2020-08-09T13:59:15Z

@JelmerT: Have you tried to overwrite the firmware on the programmer again?

JelmerT · 2020-08-13T19:14:21Z

@Nightwalker-87 do you mean re-flashing the st-link clone to V2J37S7 with the ST upgrade tool? -> Yes tried that a couple times. No difference.

I have not tried downgrading it to an earlier version. Is this possible? (I'm struggling making earlier versions of the tool work on macOS)

dwinters42 · 2020-08-19T21:32:53Z

Programmer/board type: [v2-clone]
Programmer firmware version: [V2J36S7] and [V2J37S7]
Operating system and version: [macOS Catalina]
Stlink tools version and/or git commit hash: [1.6.1] (homebrew version) + lastest master baab8ca

FWIW, I can reproduce the same behavior as seen by @JelmerT with several bluepill (STM32F103) boards on both 1.6.1 and latest master after a recent firmware update to versions V2J36S7 and V2J37S7.

Interestingly, STM32F401 controllers still get detected fine:

$ st-info --probe
Found 1 stlink programmers
serial: 573f6f06483f52553241063f
hla-serial: "\x57\x3f\x6f\x06\x48\x3f\x52\x55\x32\x41\x06\x3f"
flash: 262144 (pagesize: 16384)
sram: 65536
chipid: 0x0423
descr: F4xx (low power)

Nightwalker-87 · 2020-08-19T22:32:29Z

@JelmerT: I don't know if a downgrade is possible. Maybe you can try an older version of the firmware updater?

alexandrefdutra · 2020-08-19T23:06:41Z

Same problem here!

$ st-info --probe
Found 1 stlink programmers
serial: 46310a002c135737334d4e00
hla-serial: "\x46\x31\x0a\x00\x2c\x13\x57\x37\x33\x4d\x4e\x00"
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0748

@JelmerT: I don't know if a downgrade is possible. Maybe you can try an older version of the firmware updater?

I've done some downgrades but it didn't solve. I can only write once and then I lose the connection with the message unknown chip id! 0x3748! I don't know what else to do.

larsks · 2020-08-29T19:09:17Z

I came by to report the same problem, but I found this issue already here. I have an st-link v2 clone, and I upgraded it to the latest firmware while trying to get it working with the arduino ide. Now it reports "chipid: 0x0748", and and flashing operations seem to fail with unknown chip id! errors.

I've tried downgrading to 2.32.22, which is the earliest version offered on https://www.st.com/en/development-tools/stsw-link007.html, but the problem persists.

$ st-info --probe
Found 1 stlink programmers
 serial:     343f72064155353410300257
 hla-serial: "\x34\x3f\x72\x06\x41\x55\x35\x34\x10\x30\x02\x57"
 flash:      0 (pagesize: 0)
 sram:       0
 chipid:     0x0748

dltech · 2020-08-30T18:09:52Z

clive1 (NFA Crew) (Community Member)
Edited by STM Community July 21, 2018 at 5:44 PM
Posted on March 06, 2014 at 16:28
Google had these when I went fishing yesterday..

https://drive.google.com/folderview?id=0Bzv7UpKpOQhnbXJVVEg4VUo2M1k

Clones with new firmware does not work at all, but with V12.J21.S4 works well, I downgraded my clone in the Virtualbox. By the way if you are interested in my homemade clone you can find it here https://github.com/dltech/stlinkv2.

kusumah99 · 2020-10-14T07:04:16Z

I'm using mac, it only happen with my STM32H743, not my STM32F4xx using V2J37S7.
Yes now I know, stm32H7 is still not supported by stlink 1.6.1.

One more thing is, on V2J37S7 fw, if the stlink is not connected to any board, the chipid still detected as 0x0748

$ st-info --probe
Found 1 stlink programmers
serial: 3f7e010110134753384c4e00
hla-serial: "\x3f\x7e\x01\x01\x10\x13\x47\x53\x38\x4c\x4e\x00"
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0748

Ant-ON · 2020-11-12T05:57:37Z

It looks like a reset issue. The fix can be checked in this branch: https://github.com/Ant-ON/stlink/tree/try_h7_debug

2ni · 2020-12-20T14:49:49Z

When compiling try_h7_debug I get the following errors:

Scanning dependencies of target stlink-static
[  2%] Building C object CMakeFiles/stlink-static.dir/src/common.c.o
[  5%] Building C object CMakeFiles/stlink-static.dir/src/stlink-lib/chipid.c.o
[  8%] Building C object CMakeFiles/stlink-static.dir/src/stlink-lib/flash_loader.c.o
[ 11%] Building C object CMakeFiles/stlink-static.dir/src/stlink-lib/logging.c.o
[ 13%] Building C object CMakeFiles/stlink-static.dir/src/stlink-lib/md5.c.o
[ 16%] Building C object CMakeFiles/stlink-static.dir/src/stlink-lib/sg.c.o
[ 19%] Building C object CMakeFiles/stlink-static.dir/src/stlink-lib/usb.c.o
/www/lora-e5/stlink-try_h7_debug/src/stlink-lib/usb.c:1121:75: error: implicit conversion loses integer precision: 'size_t' (aka 'unsigned long') to 'int'
      [-Werror,-Wshorten-64-to-32]
        int t = libusb_bulk_transfer(slu->usb_handle, slu->ep_trace, buf, trace_count, &res, 3000);
                ~~~~~~~~~~~~~~~~~~~~                                      ^~~~~~~~~~~
/www/lora-e5/stlink-try_h7_debug/src/stlink-lib/usb.c:1129:12: error: implicit conversion loses integer precision: 'size_t' (aka 'unsigned long') to 'int'
      [-Werror,-Wshorten-64-to-32]
    return trace_count;
    ~~~~~~ ^~~~~~~~~~~
2 errors generated.
make[3]: *** [CMakeFiles/stlink-static.dir/src/stlink-lib/usb.c.o] Error 1
make[2]: *** [CMakeFiles/stlink-static.dir/all] Error 2
make[1]: *** [all] Error 2
make: *** [release] Error 2

Ant-ON · 2020-12-21T03:08:37Z

@2ni Now all the changes are merged in develop. Compilation issue fixed. Can you try the develop branch instead?

2ni · 2020-12-21T08:43:46Z

I uploaded some code with cubeIDE which is running on a STM32WLE5JB module connected to a chinese stlink v2. This is what I get now:

09:38 $ ./build/Release/bin/st-info --probe
Found 1 stlink programmers
  version:    V2J37S7
  serial:     321c130012144d43574d4e00
  hla-serial: "\x32\x1c\x13\x00\x12\x14\x4d\x43\x57\x4d\x4e\x00"
  flash:      0 (pagesize: 0)
  sram:       0
  chipid:     0x001f

I hoped to get rid of cubeIDE...

geocine · 2020-12-28T08:21:36Z

Programmer/board type: V2 clone
Programmer firmware version: V2J37S7
Operating system and version: Mac OS (10.14.6)
ST-Link version: v1.6.1-200-gddac731 (latest develop)
Target chip/board: STM32F103C8T6/Blue Pill

$ st-info --probe
 Found 1 stlink programmers
   version:    V2J37S7
   serial:     0a240f002b135937334d4e00
   hla-serial: "\x0a\x24\x0f\x00\x2b\x13\x59\x37\x33\x4d\x4e\x00"
   flash:      0 (pagesize: 0)
   sram:       0
   chipid:     0x0748

geocine · 2020-12-28T09:35:53Z

I managed to solve this problem, by following what has been stated here and here

Windows (ST-Link Utility)

Using ST-Link Utility

In ST-Link Utility go to Settings -> Mode -> Connect under reset
Then connect the last board you used before it malfunctioned (I'm not entirely sure if it has to be that board or you can use any other board which has a reset button) with your ST-Link V2 and hold RESET button of that board
Click "connect to the target" , just after clicking, release the RESET button
Then click "Target" -> "Erase chip"

Using `st-flash` on All Platforms

Tap RESET , do not hold

Quickly execute this command

st-flash --connect-under-reset --reset erase

If you want to re-flash without erasing you can do this on `st-flash`

Tap RESET , do not hold

Quickly execute your flash command

st-flash --connect-under-reset —reset --format binary write /path/to/file.bin 0x8000000

Ant-ON · 2020-12-29T08:56:13Z

@geocine st-flash alredy have --connect-under-reset options. But there is no information about it in the help. Can you try it option?

geocine · 2020-12-29T09:00:24Z

@Ant-ON
I just tried literally just now, yes it is working I will update my comment. Have to quickly execute the flash with connect-under-reset once you tap reset ,

st-flash --connect-under-reset —reset --format binary write bootloader-generic.bin 0x8000000

Nightwalker-87 · 2020-12-29T11:45:27Z

So this reads as if this issue is about to be resolved very soon...

geocine · 2020-12-29T15:02:07Z

I think I derailed the issue a little bit, the way I understood the original issue is st-* tools is detecting the chip as chipid: 0x0748 in the following scenarios

No target chip/board is connected to programmer
A target chip/board is connected but cannot be detected (due to a number of reasons which can be solved through ST-Link V2 clone: "unknown chip id! 0x3748" after FW update to V2J37S7 #1012 (comment))

Nightwalker-87 · 2020-12-30T20:40:23Z

Another case: Programming STM32F103ZET6 or STM32F105VCT6 for the VERY first time (using ST-LINK utility)

salacpavel · 2021-03-24T08:54:51Z

Experiencing some issue with GD32F105RBT6. I was able to flash once, but I get unknown chip id! 0x4278b7 ever since then.
As this is no target board with no rst pins exposed, I would like to ask you guys to release 1.6.1 with bugfix backported, please?
As I assume 1.6.2 release date is not set.

dltech · 2021-03-24T09:42:07Z

Experiencing some issue with GD32F105RBT6. I was able to flash once, but I get unknown chip id! 0x4278b7 ever since then.
Unknown chip ID usually means bad physical connection, check supply voltage and mcu connection.

Ant-ON · 2021-03-24T09:44:11Z

@salacpavel Try add --connect-under-rese to command line

salacpavel · 2021-03-24T09:49:57Z

@salacpavel Try add --connect-under-rese to command line

C:\apps\stlink-1.6.1\bin>st-flash --format ihex --connect-under-reset write 323.hex
st-flash 1.6.1
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_DEBUG_RESETSYS
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_DEBUG_READCOREID
2021-03-24T10:49:00 ERROR common.c: Failed to read core_id
[!] send_recv read reply failed: LIBUSB_ERROR_PIPE
[!] send_recv STLINK_JTAG_READDEBUG_32BIT
2021-03-24T10:49:00 WARN common.c: unknown chip id! 0x4278b7
Failed to connect to target

dltech · 2021-03-24T09:50:08Z

@salacpavel --connect-under-reset affects reset pin, but we do not have it.

dltech · 2021-03-24T09:52:59Z

libusb error? try "apt install stlink-tools" in ubuntu

Ant-ON · 2021-03-24T09:54:12Z

@salacpavel Are you using stlink v1?

salacpavel · 2021-03-24T09:58:45Z

some clone of ST-LINK v2. And I am on Windows, sadly. I should highlight I am not having such a problem with supposedly genuine STM32F105RBT6, I am seeing this with GD32F105RBT6 by GigaDevice only so far. hese two are supposed to be compatible tho. And the first flash went all right.

digitalentity · 2021-03-24T10:08:25Z

@salacpavel the firmware you flashed on your GD32F105RBT6 probably remapped the SWD pins (used them as GPIO, AF or entirely disabled JTAG/SWD module). The only way to recover is to connect under reset unfortunately.

salacpavel · 2021-03-24T10:14:51Z

Thank you guys for your help. I have disassembled the board and managed to connect jumper wire to nrst pin (7). Once on ground, I run:

C:\apps\stlink-1.6.1\bin>st-flash --format=ihex --reset --connect-under-reset write 323.hex
st-flash 1.6.1
2021-03-24T11:11:59 WARN common.c: unknown chip id! 0xffffffff
Failed to connect to target

Nightwalker-87 · 2021-03-24T17:53:42Z

@salacpavel I don't really see any relation to this issue. Not the same chip-id error, not the same chip, no obvious coincidence of your problem with the mentioned programmer firmware version and also the chip id error message is different. Please open a new ticket and do not recycle this one. To answer your question: There will be no patches or any maintenance for older versions of this toolset. Users are encouraged to work with the latest version or the develop tree if necessary.

Nightwalker-87 · 2021-03-25T07:48:22Z

This reason for the appearance of unknown chip id! 0x3748 is now also mentioned in our tutorial.

Nightwalker-87 · 2021-03-26T20:13:37Z

@digitalentity @geocine What is the current state of this by now?
Can you re-test with the latest develop and summarize your findings?

digitalentity · 2021-03-27T13:14:25Z

@Nightwalker-87 my original issue reported here #1012 (comment) was root-caused to a faulty ST-Link/V2 clone. No idea why it works on earlier firmwares, but V2J37S7 makes the device useless regardless of st-flash version. I've replaced the debugger with another cloned ST-Link/V2 which works perfectly fine with either 1.6.1 or the latest develop and firmware V2J37S7.

Nightwalker-87 · 2021-03-28T00:12:09Z

The input by @geocine has been added to our tutorial in commit 229c721.
Based on the issue context and the feedback from @digitalentity we can conclude that some (obviously cheap) ST-LINK/V2 clone programmers brick themselves on official firmware updates, which makes this topic related to individual hardware.

To give a statement on this I personally can't generally recommend not to use ST-LINK/V2 clone programmers, as quite a few seem to have a good cost benefit ratio and are implemented quite well. However one should be aware of that there is scrap on the market as well. The best advise I can give is to check reviews and sites like e.g. this one: https://wiki.cuvoodoo.info/doku.php?id=jtag to help finding the appropriate ones. I personally have two STLINK/V2 clones around which have so far accepted all official firmware updates without any special occurrences.

Against this background we cannot allocate a general malfunction in the toolset and I am closing this issue now as resolved.

Nightwalker-87 added component/st-flash error/unknown-chipid os/macOS programmer/STLINK/V2 Clone non-official clone devices labels Aug 5, 2020

Nightwalker-87 added this to the v1.6.2 milestone Aug 5, 2020

Nightwalker-87 changed the title ~~[ST-Link V2 clone]: "unknown chip id! 0x3748" after FW update to V2J37S7~~ ST-Link V2 clone: "unknown chip id! 0x3748" after FW update to V2J37S7 Aug 31, 2020

Nightwalker-87 added the bug/needs-fix label Dec 28, 2020

Ant-ON mentioned this issue Dec 29, 2020

STM32G0 not found and not supported? #1083

Closed

1 task

Nightwalker-87 added needs/investigation needs/issuer-feedback and removed bug/needs-fix labels Dec 29, 2020

Ant-ON mentioned this issue Mar 17, 2021

[doc] Updated documentation on target resetting #1107

Merged

Nightwalker-87 self-assigned this Mar 20, 2021

Nightwalker-87 added the general/documentation label Mar 25, 2021

Nightwalker-87 added status/no-bug status/resolved status/resolved-verified and removed needs/issuer-feedback needs/testing needs/investigation labels Mar 27, 2021

Nightwalker-87 modified the milestones: v1.6.2, (2011-2021) Resolved questions & general issues Mar 28, 2021

Nightwalker-87 closed this as completed Mar 28, 2021

frankplow mentioned this issue Apr 7, 2021

[STM32F407VG]: unknown chip id! 0x374b #1122

Closed

6 tasks

Nightwalker-87 modified the milestones: (2011-2021) Resolved questions & general issues, Resolved questions & general issues Jan 4, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

ST-Link V2 clone: "unknown chip id! 0x3748" after FW update to V2J37S7 #1012

ST-Link V2 clone: "unknown chip id! 0x3748" after FW update to V2J37S7 #1012

JelmerT commented Aug 5, 2020

Nightwalker-87 commented Aug 9, 2020

JelmerT commented Aug 13, 2020

dwinters42 commented Aug 19, 2020

Nightwalker-87 commented Aug 19, 2020

alexandrefdutra commented Aug 19, 2020

larsks commented Aug 29, 2020

dltech commented Aug 30, 2020

kusumah99 commented Oct 14, 2020 •

edited

Loading

Ant-ON commented Nov 12, 2020

2ni commented Dec 20, 2020 •

edited

Loading

Ant-ON commented Dec 21, 2020

2ni commented Dec 21, 2020

geocine commented Dec 28, 2020

geocine commented Dec 28, 2020 •

edited

Loading

Ant-ON commented Dec 29, 2020

geocine commented Dec 29, 2020

Nightwalker-87 commented Dec 29, 2020

geocine commented Dec 29, 2020 •

edited

Loading

Nightwalker-87 commented Dec 30, 2020 •

edited

Loading

salacpavel commented Mar 24, 2021

dltech commented Mar 24, 2021

Ant-ON commented Mar 24, 2021

salacpavel commented Mar 24, 2021

dltech commented Mar 24, 2021

dltech commented Mar 24, 2021

Ant-ON commented Mar 24, 2021

salacpavel commented Mar 24, 2021

digitalentity commented Mar 24, 2021

salacpavel commented Mar 24, 2021 •

edited

Loading

Nightwalker-87 commented Mar 24, 2021 •

edited

Loading

Nightwalker-87 commented Mar 25, 2021

Nightwalker-87 commented Mar 26, 2021 •

edited

Loading

digitalentity commented Mar 27, 2021

Nightwalker-87 commented Mar 28, 2021 •

edited

Loading

ST-Link V2 clone: "unknown chip id! 0x3748" after FW update to V2J37S7 #1012

ST-Link V2 clone: "unknown chip id! 0x3748" after FW update to V2J37S7 #1012

Comments

JelmerT commented Aug 5, 2020

Nightwalker-87 commented Aug 9, 2020

JelmerT commented Aug 13, 2020

dwinters42 commented Aug 19, 2020

Nightwalker-87 commented Aug 19, 2020

alexandrefdutra commented Aug 19, 2020

larsks commented Aug 29, 2020

dltech commented Aug 30, 2020

kusumah99 commented Oct 14, 2020 • edited Loading

Ant-ON commented Nov 12, 2020

2ni commented Dec 20, 2020 • edited Loading

Ant-ON commented Dec 21, 2020

2ni commented Dec 21, 2020

geocine commented Dec 28, 2020

geocine commented Dec 28, 2020 • edited Loading

Windows (ST-Link Utility)

Using st-flash on All Platforms

If you want to re-flash without erasing you can do this on st-flash

Ant-ON commented Dec 29, 2020

geocine commented Dec 29, 2020

Nightwalker-87 commented Dec 29, 2020

geocine commented Dec 29, 2020 • edited Loading

Nightwalker-87 commented Dec 30, 2020 • edited Loading

salacpavel commented Mar 24, 2021

dltech commented Mar 24, 2021

Ant-ON commented Mar 24, 2021

salacpavel commented Mar 24, 2021

dltech commented Mar 24, 2021

dltech commented Mar 24, 2021

Ant-ON commented Mar 24, 2021

salacpavel commented Mar 24, 2021

digitalentity commented Mar 24, 2021

salacpavel commented Mar 24, 2021 • edited Loading

Nightwalker-87 commented Mar 24, 2021 • edited Loading

Nightwalker-87 commented Mar 25, 2021

Nightwalker-87 commented Mar 26, 2021 • edited Loading

digitalentity commented Mar 27, 2021

Nightwalker-87 commented Mar 28, 2021 • edited Loading

kusumah99 commented Oct 14, 2020 •

edited

Loading

2ni commented Dec 20, 2020 •

edited

Loading

geocine commented Dec 28, 2020 •

edited

Loading

Using `st-flash` on All Platforms

If you want to re-flash without erasing you can do this on `st-flash`

geocine commented Dec 29, 2020 •

edited

Loading

Nightwalker-87 commented Dec 30, 2020 •

edited

Loading

salacpavel commented Mar 24, 2021 •

edited

Loading

Nightwalker-87 commented Mar 24, 2021 •

edited

Loading

Nightwalker-87 commented Mar 26, 2021 •

edited

Loading

Nightwalker-87 commented Mar 28, 2021 •

edited

Loading