hello,
cool if you have a proper storage system :)
The STM32F4 also has these variable sector sizes, and IIRC it is not
accessible as MTD.
Yes, usually, the write size is much smaller than the erase size.
Sebastien
Le 08/07/2021 à 16:47, Fotis Panagiotopoulos a écrit :
The pagesize should
> The pagesize should be the same as the erase block size.. 4k.
If it is so (which makes sense, regardless of what the comments say), then
what is the purpose of up_progmem_erasesize ?
It should return the same thing I guess?
The function up_progmem_erasesize was what made me think that
Hello
Note that in "real" field-deployed product this sector512 layer should
NOT be used since it will wear the flash much faster than using a real
MTD filesystem.
One thing to keep in mind is that flash takes a significant time to
erase and write, and that if interrupted, a flash memory
The pagesize should be the same as the erase block size.. 4k.
You will probably want 512b sectors (pages, or whatever we call them
now) at the file system interface. You can also read-modify-write
operations to "simulate" smaller erase blocks. Most MTD drivers do
that. In that case they
Still looking at this driver, and how to improve it.
The LPC1769 needs data to be written in 256 bytes chunks, but Flash sectors
are erased in 4k or 32k sizes.
So, a couple of questions:
1. What should up_progmem_pagesize return , 256 or 4k/32k?
By the description I suppose it should be 256.
Oh, that's great. That should definitely make the interface better.
But nevertheless, I tried to "ignore" the terms, and still I can't make any
sense of it.
This is what I try to do (which works fine on an STM32F4):
int write_data(intptr_t addr, BootData_t * data){
if
Here has some discussion about the naming:
https://github.com/apache/incubator-nuttx/pull/3834
On Fri, Jul 2, 2021 at 6:28 PM Fotis Panagiotopoulos
wrote:
> Hello,
>
> I am porting an old application to NuttX.
> This is running on a hardware board that uses the NXP LPC1769 MCU.
> I am in need
Hello,
I am porting an old application to NuttX.
This is running on a hardware board that uses the NXP LPC1769 MCU.
I am in need of the up_progmem interface.
Unfortunately, I see that this driver is broken. It is not working, always
returning an error.
I checked its internals, but it is quite a