Changing Flash parameters in overlay file

[CktDesigner]

My project is using nRF52840.   Early software development used an nRF52840-DK to develop most of the software.   Software is based on Zephyr using nRF Connect version 1.6.1.     I'm using the "littlefs" file system.   I got most things working using the nRF52840-DK.     I now have my custom board and it uses a slightly different (and larger) qspi-nor flash device.   

I'm still using the nRF52840-DK board file, but "modify" some of the parameters using an overlay file.    I know I need to change some of the parameters w.r.t. the flash.    I was able to modify the jedec-id for the new device, but am looking for some documentation that defines the parameters (keywords) in the board definition file (what some of them mean and format of values)   

Can you point me to these definitions (so I don't have to read through a lot of code :-))?

Thanks!

[Simonr]

Hi

It's been a while, so just to make sure we're on the same page. You're still using an nRF52840, the S25FL external flash, and you're still having error -5 (I/O error) when trying to mount the external board. Is that correct? 

This could be due to the mount process already being in progress when this is called somehow. You can try waiting for the SD card to be detected before starting the mount process. You can also check out this case where my colleague Torbjørn provided a possible fix to a mount error like this.

Best regards,

Simon

[CktDesigner]

Hi Simon,

Yes...    

Still using nRF52840 and S25FL external flash connected via QSPI, so it is not an SD card (your referenced case deals with SD cards).

I've also moved to NCS 2.0.2 (the latest released version of NCS).

I've had trouble finding any detailed documentation on the structure/internals of littleFS.    But I've traced through the code and the error appears to occur when the CRCs are being checked during the formatting process.     I saw one post that implied that the config statement "CONFIG_APP_WIPE_STORAGE=y" should be included in prj.conf, but if I do so, the build process fails, indicating that this configuration variable was not found.

I assume the physical interface to the chip works since it reads the jedec-id (I had to change the listed on in the .dts file to expect the one in the S25FL device.).    As I mentioned earlier, I had the software running on the -DK board, but am struggling to get it working on my custom board with a different (larger) QSPI device.

Thanks...