# Firmware picker
Choose what the board will do, then let the picker reduce the release assets
to one recommended firmware. The first guided board is Station G2 because its
standard, logging, FULL, LoRa-OTA, MQTT, bridge, room-server, and Companion
profiles are easy to confuse.
The picker reads public release metadata from GitHub. It does not upload any
device information.
Station G2 shortcut
If the G2 normally stays connected to a computer and you want USB packet
logs, choose USB logging repeater. The recommended image
is the expanded FULL logging profile. The smaller legacy
logging image is mainly a compatibility fallback, not the normal choice
for a computer-powered logger.
This search is for uncommon hardware variants and expert recovery. A
filename match is not a board-identity check.
## What FULL means for a USB logger
A Station G2 that is powered from and monitored by a computer normally should
use the FULL logging profile:
1. Save its name, radio settings, keys, and other configuration.
2. Download the exact Station G2 `full-logging-ota` merged image recommended
above.
3. Flash that `-merged.bin` over USB once. It installs the expanded partition
table as well as the application.
4. Reconnect the serial terminal at 115200 baud and restore any settings that
were not retained.
5. Leave the data-capable USB connection attached to collect logs. Use
`set usb.logging off` temporarily if the runtime output needs to be quiet.
Choose the standalone or lean OTA repeater instead when the board is normally
battery/solar powered, has no computer collecting USB output, or must retain a
known legacy partition layout.
## Can a Heltec V4 partition be expanded by OTA?
No. WiFi OTA and LoRa OTA write an application into the inactive application
partition. They do not replace the partition table at flash offset `0x8000`.
Allowing a running application to move its own active/inactive partitions
would risk overwriting the running image, staged image, NVS, or filesystem.
The current Heltec V4 definition already uses its 16 MiB flash efficiently:
| Region | Size |
|---|---:|
| Application slot A | `0x640000` (6.25 MiB) |
| Application slot B | `0x640000` (6.25 MiB) |
| SPIFFS | `0x360000` (3.375 MiB) |
That is much larger than current MeshCore V4 applications. A different layout
is possible only as a custom build, and it requires a one-time exact-board
merged-image flash over USB. Expanding the app slots further would shrink or
remove SPIFFS, or remove the second slot and therefore remove safe OTA.
After installing a new partition table over USB, later WiFi or LoRa updates
must use a non-merged application built for the same board, role, and partition
signature. Never use an app-only FULL image to try to migrate a device that is
still running another partition layout.
## Merged versus non-merged files
| File | Use |
|---|---|
| `-merged.bin` | First install, recovery, role/profile migration, or partition-table change over USB |
| `.bin` without `-merged` | Browser/WiFi application update when the installed partition layout already matches |
| `.mota` | LoRa OTA package for the exact target identity and installed partition layout |
When uncertain, back up the configuration and use the exact-board merged image
over USB. Do not send a merged image through browser OTA or LoRa OTA.