Skip to content

zephyr-cp: RP2040/RP2350 boards: Zephyr console only with CONSOLE=1 - #11700

Open
dhalbert wants to merge 1 commit into
adafruit:mainfrom
dhalbert:zephyr-cp-rp2-console
Open

dhalbert wants to merge 1 commit into
adafruit:mainfrom
dhalbert:zephyr-cp-rp2-console

Conversation

@dhalbert

Copy link
Copy Markdown
Collaborator

Change by Claude.

Problem

On the Pico, Pico W, Pico 2, Pico 2 W and Feather RP2040, the Zephyr UART console was always on. Turn it on only when CONSOLE=1.

Fix

On each of the five boards:

  • board.overlay now deletes zephyr,console and zephyr,shell-uart.
  • board.conf now sets CONFIG_UART_CONSOLE=n, which the Zephyr board defconfigs turn on, and CONFIG_LOG_BACKEND_UART=n, as on the other boards.
  • A new console.overlay puts the console back on UART0 in CONSOLE=1 builds.

UART0 stays enabled. With the console gone, it becomes board.UART():

  • Feather RP2040: matches the classic port.
  • Picos: the classic port has no board.UART. A later pin-name cleanup PR will make zephyr-cp board names match the classic ports, which will remove it.

(I am thinking about whether we might add board.UART() and some other defaults to the Pi Picos, changing our policy. I'll investigate further.)

Testing

  • All five boards build. UART console and chosen console are off, and board.UART is present.
  • The Pico CONSOLE=1 build has the console on UART0 and no board.UART.
  • Not tested on hardware.

The Zephyr UART console was always on for the Pico, Pico W, Pico 2,
Pico 2 W and Feather RP2040, on UART0 (GP0/GP1, or TX/RX on the
Feather). Turn it off by default, as on the MacroPad and the nRF52840
boards, so those pins are free for busio.UART. A CONSOLE=1 build puts
it back with a new console.overlay on each board.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
@dhalbert
dhalbert requested a review from tannewt November 1, 2026 02:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant