Hi all,
We have a NOR-flash chip connected via SPI to the micro-controller.
We want to separate the available memory space of this chip into different volumes.
This separation is static and will never be changed.
One volume shall be mounted read-only to avoid accidentally deleting it.
A separate "log volume" shall ensure the "root file system" can not be filled up by log files.
My question is: which is the way to go?
a) Use a Master Boot Record, or
b) call FS_NOR_BM_Configure() multiple times with varying StartAddr and NumBytes, or
c) is there a better way to split a single NOR-flash into separate volumes?
Volumes might be used from different threads simultaneously.
Is there anything to be considered regarding locking of the shared resource SPI bus in scenarios a) or b)?
Thanks
Stefan
We have a NOR-flash chip connected via SPI to the micro-controller.
We want to separate the available memory space of this chip into different volumes.
This separation is static and will never be changed.
One volume shall be mounted read-only to avoid accidentally deleting it.
A separate "log volume" shall ensure the "root file system" can not be filled up by log files.
My question is: which is the way to go?
a) Use a Master Boot Record, or
b) call FS_NOR_BM_Configure() multiple times with varying StartAddr and NumBytes, or
c) is there a better way to split a single NOR-flash into separate volumes?
Volumes might be used from different threads simultaneously.
Is there anything to be considered regarding locking of the shared resource SPI bus in scenarios a) or b)?
Thanks
Stefan