pbl debugserver

Start a GDB server for the firmware.

pbl debugserver

Runs the GDB server of the board’s runner in the foreground, the one pbl debug starts, until Ctrl-C. Anything that speaks the GDB remote protocol attaches to it: GDB, an IDE, or pbl debug from another terminal, which then leaves the server running when GDB quits.

The server listens on the runner’s port, see pbl debug, or on --gdb-port:

pbl debugserver --tty /dev/cu.usbmodem5B7A1355001 --gdb-port 2331

The native runner has no GDB server: the simulator runs under the debugger itself.

Options

pbl debugserver [-h] [-b DIR] [--dry-run] [--gdb-port PORT]
                [-r {native,nrfutil,openocd,phone,probe-rs,qemu,sftool,wasm}]
                [--tty TTY] [--probe VID:PID[:SERIAL]] [--keep-flash-image]
                [--decoration NAME] [--bt-hci CHARDEV] [--http-port HTTP_PORT]
                [--no-browser] [--address ADDRESS] [--adb-serial ADB_SERIAL]

--gdb-port PORT: Port of the gdb server (default: the runner’s)
-r, --runner {native,nrfutil,openocd,phone,probe-rs,qemu,sftool,wasm}: Override the board’s runner
--tty TTY: Serial port for the sftool and probe-rs runners
--probe VID:PID[:SERIAL]: Debug probe for the probe-rs runner
--keep-flash-image: Keep the emulator’s SPI flash image, and the apps and data in it, instead of rebuilding it
--decoration NAME: SDL decoration the emulator draws around the screen, or ‘none’ (default: the board’s first)
--bt-hci CHARDEV: H4 Bluetooth controller for builds with CONFIG_BT_HCI_UART, e.g. the serial port /dev/cu.usbmodem1101
--http-port HTTP_PORT: Port the wasm runner serves the page on (default: 8000)
--no-browser: Do not open the page the wasm runner serves in a browser
--address ADDRESS: Phone address (Developer Connection) for the phone runner; without it, an Android phone is reached over adb
--adb-serial ADB_SERIAL: Serial of the Android phone for the phone runner, when adb sees several

PebbleOS

pbl debugserver

Options