-
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
STM32F103CBT6: Flash verification fails when writing #1105
Comments
@HexF: Please use the latest version of the toolset (currently 1.6.1) when reporting bugs. It would also be helpful to know if the error still occurs in the latest |
Using 9956bde (latest develop commit) I get:
Basically the same, just more text |
Can you try https://github.com/Ant-ON/stlink/tree/flash_loader_rework? I'm trying to improve a work of bootloaders... |
@Ant-ON That seems to have fixed it:
|
@HexF Can you test that in a sequence as well to verify this is not a certain coincidence? |
Yep, running my |
This issue extends on issue STM32F103CB: I could not write bin file on my controller. #1068, which was closed and locked so I can't add to that - hence a new issue.
In order to allow developers and other contributors to isolate and target your respective issue, please take some time to select the check boxes below
and fill out each of the following items appropriate to your specific problem.
The flashing of the processor seems to fail at this point, as in the aforementioned issue.
One technicality that I have noted is that people are assuming the F103C8 and F103CB chips are the same, and infact they are not.
I have tested the exact same command with a C8 chip, and it worked perfectly fine, but upgrading to a CB chip (which I have had ST confirm are genuine and not counterfeits)
I loaded up a Windows PC with the STLink Utility from ST and it flashed the chip perfectly fine. I was then able to confirm that the flash reads back using
st-flash
on my Linux machine fine, and it matched byte-for-byte the built firmware.However, if I ignore the verification failing on Linux, and run the same
read
command - I get completely random data.Any pointers on what to do?
The text was updated successfully, but these errors were encountered: