• System shell
  • Beginner
  • 5 min
  • Serial CLI

Recipe · Beginner · System shell

How to inspect system status

Use the system shell to check firmware, memory, flash partitions, LittleFS, NVS and network status before debugging.

Diagnostics and troubleshooting checklist.
The system shell gives a quick health snapshot of the board itself.
Step 1

Commands

These commands are documented as global or quick-start commands.

Result

What it means

If the command returns the expected output, the firmware and terminal session are ready for the next workflow.

Troubleshooting

  • If Wi-Fi status is stale, check the Wi-Fi mode from the network entry.
  • If file workflows fail, inspect LittleFS usage first.
  • If RAM is low, reboot and retest with a smaller workflow.

Next steps

  • Try the same workflow on a known safe pin or target.
  • Save the useful command as a note or alias.
  • Move to the protocol-specific recipe once the basics work.

system status shell FAQ

What is the system shell useful for?

It gives a quick firmware and board snapshot: model, version, uptime, flash, memory, partitions, LittleFS, NVS and network state depending on the current build.

When should I check system status?

Check it after flashing, before reporting a bug, when memory looks low, when LittleFS behaves oddly, or before a long bench session that depends on Wi-Fi or files.

Can I change protocol settings from the system shell?

The system shell is mainly for inspection and system-level actions. Use protocol config commands, profile or mode-specific shells for bus pin and peripheral settings.

Go deeper