-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
STM32VL won't flash #579
Comments
Thats weird, i'm not sure what causes the problem as the flash loader is written to RAM and then fails at the end. |
Have you tried with the Boot0 to Vdd before powering the board. This solved the problem for me. |
Please verify if the problem still exists in Release v1.6.0 and/or if the feedback by @Faduf resolves the issue. |
Just got fresh hardware to play with (AZDelivery STM32 STM32F103C8T6 and a Youmile ST-LINK V2 Emulator) and see exactly this behavior when flashing via st-util as gdb server and arm-none-eabi-gdb as client. I can flash the target with st-flash without any problem. It seems to be an issue specific to st-util. How can I help? |
i got some more output from st-util with -v99:
The problem might be that the core is not runningt when flashing the second sector; I'm just guessing here |
before you ask: I'm currently using the master's HEAD (f5d0454) |
@nerdmaennchen: Thanks for the feedback. What is the core ID of your STM32F103C8T6? Can you verify that it is not a CKS32F103C8T6 with a fake marking? We currently face several problems with this sort of chinese clone boards (see Release v1.6.1 Tickets) that appeared on the market from Dec 2019. I would like to rule out that we accidentally mix up different issues. Therefore it would be helpful to either be sure of original ST-Microelectronics chips or have another type of board used to analyse this problem, which is not affected by this product counterfeiting. |
the reported coreid of the target is in the above log:
frankly, I don't know if it's genuine or not (it was very cheap though) |
Looks as if you are lucky, though you caught a cheap board. The affected boards mentioned have Core ID 0x2ba01477, so we should be fine then. Thanks for verifying. 👍 We will keep up with this then, please give us some time to solve this. Of course you may take a closer look as well, if you wish to do so. |
Of course, take the time you need! Kudos! I've been using your tools since five years or so and they are sill my go-to-tools If you need any help, I'd be delighted to do my part. |
It appears that we need a closer look at what happens step by step when |
For some reason the PER bit is set when writing the first word to the second page. However, if I do a mass erase (with st-flash) before programming the device via st-util and gdb everything works smoothly. |
found the problem. cheers |
@nerdmaennchen: Thank you so much for your contribution. I'll review the PR as soon as possible. You are on linux? Can someone else test this with another board (and eventally a different OS) as well - ticket was opened for macOS BTW) to have redundant verification? @bmarvo, @bolorkhuu or @Faduf maybe? |
jep, im an Arch-fanboy (Linux) and I don't have easy acess to other OSes. However, IMHO the fix is entirely OS independent as was the cause for the problem. |
That's what I thought as well, but I feel like that it is always good to have verification on at least a second setup. Don't bother about this too much, you are fine and I believe you spent enough valuable efforts on this. Let somebody else take a look at it and relax. ;-) |
very well then. relax mode: don't worry about my time. I actually enjoyed it quite a lot :D |
Hello,
I'm getting following error on stm32vl discovery board.
Does anyone know, how to solve this?
Thank you,
The text was updated successfully, but these errors were encountered: