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
STM32F7 Flash Dual Bank support #6955
Comments
@ARMmbed/team-st-mcd Please review |
Hi |
Thanks for clarification @jeromecoutant |
@jeromecoutant What would take to enable that ? Are there any limitations to be aware of , drawbacks or? |
Can you please verify if this PR solves your issue ? and close it if ok. Thanks |
ARM Internal Ref: MBOTRIAGE-23 |
@dhwalters423 Can you please review? |
@0xc0170 can you please add the |
Description
In order to support sensible SOTP and NV Store values, the STM32F7 platforms should have dual bank flash support.
At the moment this is not supported:
mbed-os/targets/TARGET_STM/TARGET_STM32F7/flash_api.c
Line 109 in 79640c6
Impact:
In order to support drag and drop programming of devices with Mbed Cloud Client, we need to set the SOTP regions to the end of the bank. This allows consistent device identity and the ability to use the RoT in the SOTP sector.
Example:
The NUCLEO_F746ZG platform has 1Mb of flash. The flash sectors at the end of the single bank are 256kb a piece (at 0x08080000 and 0x080C0000). Therefore SOTP is taking up more than half the available flash on the board. By enabling dual bank flash sectors, the end sectors would only be 128kb, thus taking up 25% rather than 50% of the available flash memory.
Issue request type
[ ] Question
[X ] Enhancement
[ ] Bug
The text was updated successfully, but these errors were encountered: