KevsRobots Learning Platform
36% Percent Complete
By Kevin McAleer, 5 Minutes
This is the moment the two identical boards become two different things. Node 1 gets repeater firmware; node 2 gets companion firmware. Everything else in the course follows from this choice.
At flasher.meshcore.io you will be offered several builds for the Heltec V3. The ones that matter to us:
| Variant | What it is for |
|---|---|
| Repeater | Node 1. Forwards packets, no phone attached, full CLI |
| Companion (BLE) | Node 2. Pairs to a phone over Bluetooth |
| Companion (USB Serial) | Node 2 alternative. Talks to a computer over USB instead |
| Room Server | A message store - not used in this course |
| Sensor | Telemetry node - not used in this course |
Which companion build? Choose Companion (BLE) if you want to use your phone, which is what most people want. Choose Companion (USB Serial) if you plan to drive it from a laptop with the web client at app.meshcore.nz. You can always reflash later.
/dev/cu.usbserial-xxxx or /dev/cu.SLAB_USBtoUARTIf nothing appears in the port list, jump to the Common Issues at the bottom of this lesson.
Exactly the same process, with one change:
Look at the OLED screen.
MeshCore-a1b2 to begin with), plus uptime and packet countersIf the screen is blank but the board is warm, the flash probably failed part way - just flash it again.
The flasher page has a built in console feature. This is how we will configure the repeater in lesson 7, so it is worth finding it now: flash the repeater, then look for the console or terminal option on the same page and connect to the board.
Type ver and press enter. If you get a firmware version back, you have a working console and the hard part is over.
There are two other ways to reach the same commands, and you may prefer them:
screen, minicom, PuTTY, or the Arduino IDE serial monitorver, board and stats-core. What is the board reporting for uptime?Problem: The browser shows no serial ports at all.
Solution: Try a different USB-C cable first, then a different USB port.
Why: Charge-only cables have no data lines. This is by far the most common cause.
Problem: βWebUSB is not supportedβ or the Flash button does nothing.
Solution: Use Chrome or Edge on a desktop.
Why: Firefox, Safari, and mobile browsers do not implement WebUSB.
Problem: The flash fails partway through or the board keeps rebooting.
Solution: Hold the BOOT button (marked PRG on some V3 boards) while plugging the USB cable in, then release it and flash again.
Why: This forces the ESP32-S3 into its bootloader instead of running whatever half-written firmware is on it.
Problem: I flashed the wrong variant.
Solution: Just flash it again with the right one.
Why: Nothing is permanent here. The only cost is a minute of your time.
You can use the arrows β β on your keyboard to navigate between lessons.
Comments