Skip to content

[BUG] [ESP32-S3] Enabling CONFIG_SMP prevents mounting the /data directory at startup using MTD/LittleFS #18469

@engdavidiogo

Description

@engdavidiogo

Description / Steps to reproduce the issue

Description

I noticed a recent issue on ESP32-S3 board configurations related to Wi-Fi (STA/AP): the default esp32s3-devkit:sta_softap configuration does not enable SMP.

When CONFIG_SMP is enabled, board bringup fails during SPI flash storage initialization, and /data (mounted from MTD as non-volatile storage) is not created.

The bringup consistently fails in the flash filesystem setup path.

Base configuration used

./tools/configure.sh esp32s3-devkit:sta_softap

Then SMP was enabled (CONFIG_SMP=y).

Steps to reproduce

  1. Configure with:
    ./tools/configure.sh esp32s3-devkit:sta_softap
  2. Enable SMP (CONFIG_SMP=y).
  3. Build and flash.
  4. Boot and run:
    ls /
  5. Try manual mount:
    mount -t littlefs -o forceformat /dev/esp32s3flash /data

Expected behavior

  • Bringup completes normally.
  • /data is created/mounted from SPI flash MTD.
  • Manual mount with forceformat succeeds if media is empty/corrupted.

Actual behavior

  • Bringup fails in SPI flash filesystem setup.
  • /data is not created.
  • Manual mount fails with error 28.

Relevant logs

littlefs: lfs_mount failed ret=-14
nx_mount: ERROR: Bind method failed: -14

littlefs: forceformat requested
lfs_dir_commitcrc: commitcrc mismatch at crc-tag block=0x0 off=0x30 ...
lfs_dir_compact: Superblock 0x0 has become unwritable
littlefs: lfs_format failed ret=-28
nx_mount: ERROR: Bind method failed: -28

ERROR: Failed to setup littlefs
ERROR: Failed to initialize SPI Flash: -28

Notes

  • Board: ESP32-S3 DevKit
  • Wi-Fi mode: STA + AP
  • Reproducible when SMP is enabled
  • Without SMP, storage bringup path works as expected

On which OS does this issue occur?

[OS: Linux]

What is the version of your OS?

Ubuntu 24

NuttX Version

release 12.12

Issue Architecture

[Arch: xtensa]

Issue Area

[Area: File System]

Host information

No response

Verification

  • I have verified before submitting the report.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Arch: xtensaIssues related to the Xtensa architectureArea: File SystemFile System issuesOS: LinuxIssues related to Linux (building system, etc)Type: BugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions