NMIoT v0.3.2: Boot loop when TF card is inserted — unable to back up config to TF

[pdvigil64]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

Description

On NMIoT firmware v0.3.2 (flashed via https://flash.nmiot.net/), inserting a TF/microSD card causes the device to enter a boot loop. Without the TF card, the device boots and operates normally. This also prevents backing up configuration settings to the TF card, which is a critical workflow. This issue has been present across previous firmware versions as well — it is not a new regression in v0.3.2.

Hardware

• Board: NM-CYD-C5 (ESP32-C5)
• Firmware: NMIoT v0.3.2 (ESP-Claw based, flashed from flash.nmiot.net)
• TF card: Samsung 4GB, FAT32

Steps to Reproduce

1. Flash NMIoT v0.3.2 via https://flash.nmiot.net/
2. Boot the device without TF card — works normally
3. Power off, insert Samsung 4GB FAT32 TF card
4. Power on — device enters boot loop, never reaches operational state
5. Remove TF card — device boots normally again

Expected Behavior

• Device should boot normally with TF card inserted
• Should be able to back up / write configuration settings to TF card
• FATFS should mount and operate without filling up or crashing

Suspected Cause

This may be related to the upstream ESP-Claw FATFS issue where the filesystem fills to 100% and causes app_claw_start to fail with "Failed to init event router" / "Failed to configure session manager", triggering a reboot loop.

Upstream reference: #84

Additional Context

• Not a regression — this has never worked across previous firmware versions either
• Prevents the TF config backup feature from being usable entirely
• NMMiner skills are affected since they may rely on TF storage

Actual behavior (suspected bug)

Suspected Cause

This may be related to the upstream ESP-Claw FATFS issue where the filesystem fills to 100% and causes app_claw_start to fail with "Failed to init event router" / "Failed to configure session manager", triggering a reboot loop.

Error logs or terminal output

Steps to reproduce the behavior

Steps to Reproduce

1. Flash NMIoT v0.3.2 via https://flash.nmiot.net/
2. Boot the device without TF card — works normally
3. Power off, insert Samsung 4GB FAT32 TF card
4. Power on — device enters boot loop, never reaches operational state
5. Remove TF card — device boots normally again

Project release version

v0.3.2

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Windows

Operating system version

windows 11

Shell

other (details in Additional context)

Additional context

No response

[laride]

Thanks for the report.

The FATFS-related boot-loop issue mentioned in the suspected cause has already been fixed in upstream ESP-Claw.

In this case the firmware you are using is NMIoT v0.3.2, which appears to be based on ESP-Claw but is distributed separately. We are not sure whether NMIoT has modified the ESP-Claw code, configuration, partition layout, FATFS handling, or TF-card-related logic.

Based on the information currently provided, we cannot determine the exact root cause from the ESP-Claw side. It would be helpful to confirm whether the issue can be reproduced with the latest upstream ESP-Claw firmware directly.