-
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
[STM32WLE]: Erase flash fails on second page #1305
Comments
@victor-dryad : Just for a better understanding: What happens, if you change |
Unfortunately looks no improvement. However one more thing fixed:
The trials made under Ubuntu Mint 21.1
|
Actually, the OS info in detail is not too important, apart from the system type (windows, linux) because behaviour within different flavours of debian based distributions is usually very similar, if not the same. Also we do test the toolset on debian based systems regularly. More detailed USB debug info appears not to be trivial to implement from my point of view. Here we mostly rely on the external I'll check the log above in more detail soon. |
related to #1310 |
@victor-dryad Perhaps is write protection set? |
Kind of blind research:
This hack solves the issue in my case.
|
@victor-dryad When looking at the if-clause in L1071 in |
Talking about testing branch: stlink/src/stlink-lib/common_flash.c Line 1105 in fc99064
As far as I can see, the code for another boards differ. |
Well, they are similar - only the HEX-values differ. |
A way to create a mask is (may be almost) the same. the values differ. |
... the respective reference manuals? I'd try the one for the ST32WLE device you have at hand (section 3.10.5) and then extend research to STM32G491 or any G0 device (section 3.7.5), taking into account related sections of interest. |
@victor-dryad I still don't see the point that is actually leading to this. 😞 |
We need more contributors here with similar hardware for further investigation and testing. |
@victor-dryad You may give it another try with the latest |
--> This is wrong: The WLE does not have a |
Experiencing the same issue on a NUCLEO-WL55JC1 with STM32WL55 MCU
The data between 0x0800 0000 and 0x0800 0800 did get ereased succesfully. The data in other memory regions wasn't erased. I've tried removing the Unfortunately I'm not capable to help debug this issue, but I'm more than happy to test or try any suggestions on the hardware that I have. |
@victor-dryad I believe to have found a bug in
|
Commit 7dcb130 fixes the obvious bug above. |
Commandline output:
The text was updated successfully, but these errors were encountered: