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.
Thi
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 repo
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 zon
> 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 pagesize
Hi,
I contributed the board level CAN driver support for Nucleo F446RE board few
months ago and I did some tests of receiving and transmitting CAN messages
with a low cost WCMCU-230 transceiver (https://www.aliexpress.com/item/
32686393467.html). It was working fine, actually if you configure
