Open nvlsianpu opened 7 years ago
cc @carlescufi
Downside, is that this will eat an MPU region index. But it's doable. Is this something still needed @nvlsianpu ?
So fare I didn't received any request for this - this would be must have for critical devices which are not zephyr target today. Optionally for such protection we can use other SoC resource than MPU (on some targets).
For development purpose advantage of having that is help on identification of bugs caused by over/under-run flash write., but situation is more complex as in the same time need to allow writes to DFU image-collection area/s.
Hi @agross-oss, @ioannisg,
This issue, marked as an Enhancement, was opened a while ago and did not get any traction. Please confirm the issue is correctly assigned and re-assign it otherwise.
Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.
@nvlsianpu you are also encouraged to help moving this issue forward by providing additional information and confirming this request/issue is still relevant to you.
Thanks!
Currently there is possible to allow write to whole FLASH or not allow writing to FLASH at all (CONFIG_MPU_ALLOW_FLASH_WRITE). It should be possibile to have option which will allow writing to flash area which is specific for data Storage. Thanks to that e.g. program flash will be stil preserve while e.g. file system will might operate propellery.