Hi Jared!

When running you external flash sample on the nrf9160 feather board on your latest v2.3 branch I get the following build error. Have you seen this before? I’m using a debugger with west flash to upload the code.


Area 1 at 0x0 for 4194304 bytes                                                                                                                 

Erasing flash area ... 0                                                                                                                        

[00:00:10.146,118] <inf> littlefs: LittleFS version 2.5, disk version 2.0                                                                       

[00:00:10.154,205] <inf> littlefs: FS at w25q32jv@0:0x0 is 1024 0x1000-byte blocks with 512 cycle                                               

[00:00:10.163,482] <inf> littlefs: sizes: rd 16 ; pr 16 ; ca 64 ; la 32                                                                         

[00:00:10.171,112] <err> littlefs: WEST_TOPDIR/modules/fs/littlefs/lfs.c:1234: Corrupted dir pair at {0x0, 0x1}                                 

[00:00:10.181,854] <wrn> littlefs: can't mount (LFS -84); formatting                                                                            

[00:00:10.309,936] <inf> littlefs: /lfs mounted                                                                                                 

/lfs mount: 0                                                                                                                                   

/lfs: bsize = 16 ; frsize = 4096 ; blocks = 1024 ; bfree = 1022                                                                                 

/lfs/boot_count stat: -2                                                                                                                        

FAIL: open /lfs/boot_count: -16                                                                                                                 

[00:00:10.328,216] <inf> littlefs: /lfs unmounted                                                                                               

/lfs unmount: 0 `

    Hi danieasv

    Yes this is common for a first time use or if LFS is corrupted for some reason. Did you reboot after seeing all of that to see if the boot count is incrementing correctly?

      Got it working now after using a different fname. Maybe something in LFS got corrupted on the first try.

      Terms and Conditions | Privacy Policy