-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ST-Link V2 clone: "unknown chip id! 0x3748" after FW update to V2J37S7 #1012
Comments
@JelmerT: Have you tried to overwrite the firmware on the programmer again? |
@Nightwalker-87 do you mean re-flashing the st-link clone to 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) |
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 |
@JelmerT: I don't know if a downgrade is possible. Maybe you can try an older version of the firmware updater? |
Same problem here! $ st-info --probe
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. |
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 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.
|
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. |
I'm using mac, it only happen with my STM32H743, not my STM32F4xx using V2J37S7. 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 |
It looks like a reset issue. The fix can be checked in this branch: https://github.com/Ant-ON/stlink/tree/try_h7_debug |
When compiling try_h7_debug I get the following errors:
|
@2ni Now all the changes are merged in |
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:
I hoped to get rid of cubeIDE... |
Programmer/board type: V2 clone
|
I managed to solve this problem, by following what has been stated here and here Windows (ST-Link Utility)Using ST-Link Utility
Using
|
@geocine |
@Ant-ON
|
So this reads as if this issue is about to be resolved very soon... |
I think I derailed the issue a little bit, the way I understood the original issue is
|
Experiencing some issue with GD32F105RBT6. I was able to flash once, but I get unknown chip id! 0x4278b7 ever since then. |
|
@salacpavel Try add |
|
@salacpavel --connect-under-reset affects reset pin, but we do not have it. |
libusb error? try "apt install stlink-tools" in ubuntu |
@salacpavel Are you using stlink v1? |
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. |
@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. |
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:
|
@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 |
This reason for the appearance of |
@digitalentity @geocine What is the current state of this by now? |
@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 |
The input by @geocine has been added to our tutorial in commit 229c721. 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. |
Commandline-Output:
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 versionV2J37S7
.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 firmwareV2J37S7
. So I have no clue what's going wrong here.The text was updated successfully, but these errors were encountered: