STM32H7 - M4: Flash driver : writing to internal flash sometimes raise STRBERR #76647
Unanswered
mkaricheri
asked this question in
General
Replies: 2 comments 2 replies
-
cc: @erwango @FRASTM @George-Stefan @gautierg-st @ajarmouni-st |
Beta Was this translation helpful? Give feedback.
0 replies
-
Not sure why this happens (even if I'd say it could be linked to use of M4 writing to flash as this is the first time this error is reported), but the fix seems legitimate, so don't hesitate to go ahead to push a PR. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
We are using a STM32H755 SoC and running the application from the Bank 2 on M4. The application runs from lower part (896KiB) and write to a partition which is the last 128KiB of the Bank 2 using the flash write() API. Application write code is based on flash_shell sample application. The write work most of the time. However occasionally it encounters a STRBERR and write fails. However I read following in the reference manual section 4.7.4
So add the following workaround which works great based on our testing. We also readback and verify the flash content. So wondering what causes STRBERR. If we go by the reference manual, we shouldn't return error on this error.
My workaround below is currently done only for Bank 2 write, but if a patch is acceptable, this should be done for Bank 1 as well. So would like to know from experts why this happens and if driver can ignore this as in the commit main...mkaricheri:zephyr:workaround-flash-write-error-strberr
Thanks
Murali Karicheri
S&C Electric company,
Beta Was this translation helpful? Give feedback.
All reactions