Let me point out that when compiling on nRF Connect SDK 2.5.0, everything works perfectly.
This always happens when the external memory is not initialized yet. I have several of my own prototype boards and the same thing happens on the new nrf52840dk board.
I configure littlefs like this:
in proj.conf:
In pm_static.yml
I use mcuboot so in child_image/mcuboot.conf
In code:
When I compile on SDK 2.5.0, everything is always OK.
When I compile on SDK 2.6.0, I always get error -19 with the fs_mount function, i.e.: ENODEV 19 /* No such device */ (but only if the memory has never been initialized)
Interestingly, when I compile on SDK 2.5.0 and start the memory, it initializes itself correctly, then when I compile on SDK 2.6.0, everything will work correctly, because the memory has already been initialized on 2.5.0. So the problem is only with the first initialization when using the fs_mount function on SDK 2.6.0.
Has something changed in SDK 2.6.0 that requires adding some configuration to be able to initialize external storage from littlefs?
Or do I need to add some flag to the fs_mount_t.flags structure?