Workflow
- Open the Web Serial Terminal or a desktop serial terminal.
- Select the USB CDC or USB serial port.
- Use 115200 baud, 8 data bits, no parity and 1 stop bit.
- Press any key if no banner appears, then run a small command.
Result
What it means
If the command returns the expected output, the firmware and terminal session are ready for the next workflow.
Troubleshooting
- Check that you are connected to the correct serial port.
- Use 115200 baud, 8 data bits, no parity and 1 stop bit.
- Send a key if the welcome banner is not visible.
First serial connection FAQ
Why start with a serial connection before testing Wi-Fi CLI?
The serial prompt proves that the board, USB driver, terminal settings and firmware are responding. Once the CLI is stable, other issues are much easier to separate from connection problems.
What should I expect after the first connection?
A good first connection should show the firmware banner or prompt, then accept simple global commands such as help, system or mode selection before you wire any external target.
What does it mean if the banner appears but commands do not echo correctly?
That usually points to the wrong port, an unstable USB cable, a terminal line-ending issue, or another program already holding the serial device. Reconnect cleanly and test with a simple discovery command before moving on.