Allow debug directives to reference Pluggable Discovery properties

[PaulStoffregen]

Describe the request

Pluggable Discovery may be able to automatically configure debugging on some platforms.

This feature request is simply to allow debugger configuration directives to reference the Pluggable Discovery properties for the selected board.

By allowing Pluggable Discovery properties, platform designers may extend custom discovery tools to automatically detect debugger hardware and pass that information to the debugging tools for automatic configuration.

Describe the current behavior

Today debug directives are able to reference build properties, such as {build.board}. But the Pluggable Discovery properties like {upload.port.address} or {upload.port.properties.name} do not work. For example, if this line is used in platform.txt:

debug.server.openocd.script=myconfig {build.board} {upload.port.address}

The result is this:

Remote debugging using | "/home/paul/teensy/debug/server/tdebug" -s "unused" --file "myconfig TEENSY41 {upload.port.address}" -c "gdb_port pipe" -c "telnet_port 0"

The {build.board} property does result in "TEENSY41", but {upload.port.address} is copied verbatim rather than substituted with the address property of the currently selected board.

Please add the Pluggable Discovery "upload" properties to the list of properties which can be utilized in debugger configuration directives.

Arduino CLI version

arduino-cli Version: 1.5.2-rc.1 Commit: fef6e48 Date: 2026-07-23T11:13:39Z

Operating system

Linux

Operating system version

Fedora 44

Additional context

No response

Issue checklist

• I searched for previous requests in the issue tracker
• I verified the feature was still missing when using the nightly build
• My request contains all necessary details