Hi Daniel,
No problem, happy to help. I looked back at the project where I used
the larger flash ... it was a Cypress S25FL256 part. For that setup, I
used the part's 64K sector erase size (vs. the 4K sub-sector erase) and
CONIG_MTD_SMART_SECTOR_SIZE=4096.
Looks like the w25.c MTD driver o
vices "out of the box"
and needed some work.
I would be delighted if this is sorted; otherwise I'll be looking at again
sometime in the next few months.
>-Original Message-
>From: Daniel Pereira Carvalho
>Sent: 20 October 2022 13:16
>To: dev@nuttx.apache.org
Hi Ken,
First of all, thanks for your quick response.
One of the first things I tried was to change the values of
MTD_SMART_SECTOR_SIZE [=2048] and MTD_SMART_SECTOR_CACHE_SIZE [=2048] but
the smartfs_mount() is still failing to validate the low-level format. For
reference the struct fs->fs_llform
Hi Daniel,
The SmartFS FS *can* work with devices greater than 16M Bytes. I have
used it with a 256MBit / 32M Byte SPI flash before quite successfully.
But you have to ensure the logical sector size is large enough. One
limitation of the SMART MTD (and therefore SMART FS) implementation is
Hi guys,
I am trying to use the memory W25Q256JVEIQ, with SMARTS FS. To do it I
added the support for this memory in "drivers/mtd/w25.c". I just added the
code below
*..#define W25_JEDEC_CAPACITY_256MBIT 0x19 /* 8192x4096 = 256Mbit memory
capacity */../* 256M-bit / 32M-byte (33,55
