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
STM32G071G8U6/STLINK-V2 issue in flashing #905
Comments
Please update to the latest release first, before we can offer any support. |
I am currently using the 1.5.1 version |
I know, that 's why I asked you to update to the latest version which is 1.6.0. |
Sir, |
Please check your ubuntu package repository first. |
Something is not correct there. Please uninstall this package via the package manager and compile from source as described in the documentation above. I'll take a look at the package - that's another problem. Apart from that: Your device is not detected correctly.
These values should fill out.
These values are not correct for the STM32F103C8. They should be:
Looks to me as if you caught a fake board/chip. |
Sir, |
Please also tell us how you have solved the version issue you had before. Regarding the device identification something is technically NOT correct, even if you use a custom board. Three possibilities:
The M0+ and M3 are physically totally different MCU architectures.
Please understand that we can't help you any further, as long as you don't provide more detailed information about your hardware (maybe even an additional image). Also you should take a look at our project documentation: |
Sir, |
What is your ubuntu version? I'll look at the pkg-version issue then. |
I see - good, but this also shows clearly that you don't have a STM32F103C8 device, so the issue title is wrong. What chip model is it instead? Can you print out the marking? |
... and please run |
I don't think this is the reason.
... and you still didn't tell me your version of Ubuntu, what prevents me from being able to analyse the pkg-error present in the respective repository. I'll continue with this as soon as all these points have been fully addressed. It's hardly possible to look at your problem properly, if one jumps from one point to the other and back again - it does not work that way. Please consider this and proceed stepwise and in somewhat logical order. |
Sir, |
Thanks.
I have a STLink-v2 (clone) here which is definitely working, but when I don't connect it to a device (open SWD-wires, on purpose) I find:
and
Which is somehow similar to your output. I conclude from this that you are facing a connection problem here. Could it be that you have connected wires from the programmer to the device to some wrong pins on the board or anything alike (accidentally, without realising). To me this looks like as if (some/all?) device sided wires are open ends.
|
Very good, so we can rule that out as well. You have the same programmer I use.
|
Sir, |
This leads me to the question if you have access to a second identical board for testing. Currently we can't rule out that an electrostatic discharge (ESD) event occurred somewhen during your testing that has destroyed the board or any key assembly or part on it what now prevents it from reacting to any commands from the programmer. I can't tell from here. |
We are currently in a lock down situation so another board is not practically possible sir. I have a doubt like how the discharge will occur? As it was working properly till it get programmed. |
I can happen with a single touch on the board without further notice if not pre cautious enough. If this should be the reason for the board no longer responding, it is very likely that you can dispose it, as you will hardly ever find out where exactly the event occurred on the board and which components are affected. |
Edit: This may not even have any relation to your programming attempts... |
Actually I didn't do anything else other than programming the board. And it was working fine till it get programmed. |
Yes, maybe, but for that you needed to touch it (e.g. to connect the programmer, etc.). So that could be a possible point in time where such an event could have taken place. I charge up every day at home, and I even feel it sometimes when touching the case of my computer. This is a normal physical effect. Knowing that, I'd at least touch a grounded surface before dealing with any unshielded electronic parts. Usually I use either a grounded discharge mat or an ESD wristband, which is always a good idea to prevent any possible damage. However looking at this I can currently see no problem with the |
Anyway thanks alot for your support sir. |
You are welcome and I hope that you can test with a second identical board soon which then leads to success. I am closing this as resolved, as it doesn't seem that we can do anything to it now. Though we couldn't manage to get it to work, I hope to have given some useful general advice that helps you along for upcoming projects. |
Hey,
I was trying to flash the code to STM32F103C8 with STLINK-V2 in linux enviornment. When i run the code st-info --probe,below was displayed:
arathy@arathy-HP-Laptop-14q-cs0xxx:~$ st-info --probe
Found 1 stlink programmers
serial:
openocd: ""
flash: 0 (pagesize: 0)
sram: 0
chipid: 0x0460
descr: G071/G081 device
The stlink is detecting but is not able detect the sram and flash memory. Can anyone tell me what could be the reason?
And when i tried to burn the code, this is the result.
I am stuck in this problem,Can anyone please help me to get through this?
Thanks in advance.
The text was updated successfully, but these errors were encountered: