• General commands
  • Beginner
  • 5 min
  • Serial CLI

Recipe · Beginner · General commands

How to create command aliases

Use the global alias utility to create shortcuts for commands or command chains you repeat often.

Terminal shell showing a command prompt.
Aliases are useful when the same setup or scan command is used all day.
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

  • Open alias from the global prompt.
  • Keep the first alias simple, such as a read-only scan.
  • Document aliases used in a project note so another user understands the session.

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.

Command alias FAQ

What should I turn into an alias?

Alias commands that are safe, common and easy to recognize, such as a known scan setup or a status command. Avoid hiding risky writes or erases behind short names.

How should I name aliases for a repeatable bench?

Use names that describe the action and target, such as a specific scan, probe or read step. Clear names make logs and shared project notes easier to understand later.

Should aliases replace saved profiles?

No. Use profiles for known pin mappings and setup state, and aliases for command shortcuts. They complement each other, but they solve different problems.

Go deeper