Stm32 flash update #4980
Merged
Stm32 flash update #4980
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
First add the flash_data.h that describe the flash memory topology, and also activate FLASH support for the corresponding targets.
First add the flash_data.h that describe the flash memory topology, and also activate FLASH support for the corresponding targets.
First add the flash_data.h that describe the flash memory topology, and also activate FLASH support for the corresponding targets.
First add the flash_data.h that describe the flash memory topology, and also activate FLASH support for the corresponding targets. This is a 1,5MB flash memory device which contains 15 sectors, where sectors 12 to 15 are 128KB sectors. So flash_api.c needed has been updated to differentiate between this flash memory and the 2MB ones by checking existence of sector 16 instead of sector 12.
Users of FlashIAP usually get the minimum programable size by calling flash.get_page_size(), so let's return the minimum to allows a most efficient usage of flash. For F4 devices, this is 1 byte. For L0 and L1 devices, this is a word (4 bytes). For L4 devices, this is a double word (8 bytes).
Adding flash API support to STM32F7 family. The code is derived from F4 family one. The memory topology is described in flash_data.h files and the flash_api.c implementation manages the 2 possible memory types (1 or 2 banks).
This was referenced Aug 28, 2017
In case the target supports a page size of 1 byte, i.e. is able to program flash 1 byte at a time, which is the case of STM32 F4 targets, there is no reason for flash_device.program to return an error when trying to write on an "unaligned" address.
LMESTM
force-pushed
the
stm32_flash_update
branch
from
f3d8293
to
9bed429
Compare
There was a comilation error for NUCLeO_F410RB as it does not have a ADDR_FLASH_SECTOR_5.
0xc0170
approved these changes
Aug 31, 2017
|
cc @c1728p9 |
|
/morph test |
Result: FAILUREYour command has finished executing! Here's what you wrote!
OutputExample Build failed! |
|
Above failure was due to jerkins too many files open /morph test |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
OutputAll builds and test passed! |
|
This relies on changes made in #4920 which is scheduled for 5.6 as it changes behaviour. Thus this PR will have to go into 5.6.1 |
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Several updates concerning Flash API support on STM32 targets.
Status
READY
TESTS
tests-mbed_drivers-flashiap and tests-mbed_hal-flash PASSED OK on ARM and GCC-ARM on L0, L1, L4, F4 and F7 STM32 targets.
reports.zip