docs(i18n): PX4 guide translations (Crowdin) - zh-CN (#26900)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
2026-05-16 22:17:34 +08:00 · 2026-04-01 17:29:06 +11:00
parent 7d392394dd
commit 106907bfd4
34 changed files with 1524 additions and 750 deletions
@@ -25,7 +25,7 @@ See the debug probe documentation for details on how to setup your debug connect

 - [SEGGER J-Link](probe_jlink.md): commercial probe, no built-in serial console, requires adapter.
 - [Black Magic Probe](probe_bmp.md): integrated GDB server and serial console, requires adapter.
- [STLink](probe_stlink): best value, integrated serial console, adapter must be soldered.
+- [STLink](probe_stlink.md): best value, integrated serial console, adapter must be soldered.

 We recommend using the J-Link with the Pixhawk Debug Adapter or the STLinkv3-MINIE with a soldered custom cable.

@@ -5,7 +5,7 @@ PX4 runs on ARM Cortex-M microcontrollers, which contain dedicated hardware for
 The SWD debug interface allows direct, low-level, hardware access to the microcontroller's processor and peripherals, so it does not depend on any software on the device.
 Therefore it can be used to debug bootloaders and operating systems such as NuttX.

-## Debug Signals
+## Debug Signals {#debug-signals}

 Four signals are required for debugging (in bold) while the rest is recommended.

@@ -29,7 +29,7 @@ They are usually not accessible and are typically only used to debug very specif

 ## Autopilot Debug Ports {#debug-ports}

-Flight controllers commonly provide a single debug port that exposes both the [SWD Interface](#debug-signals) and [System Console](system_console).
+Flight controllers commonly provide a single debug port that exposes both the [SWD Interface](#debug-signals) and [System Console](system_console.md).

 The [Pixhawk Connector Standards](#pixhawk-standard-debug-ports) formalize the port that must be used in each FMU version.
 However there are still many boards that use different pinouts or connectors, so we recommend you check the [documentation for your autopilot](../flight_controller/index.md) to confirm port location and pinout.
@@ -91,7 +91,7 @@ There FMU and Pixhawk versions are (only) consistent after FMUv5X.

 ### Pixhawk Debug Mini

-The [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) defines the _Pixhawk Debug Mini_, a _6-Pin SH Debug Port_ that provides access to both SWD pins and the [System Console](system_console).
+The [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) defines the _Pixhawk Debug Mini_, a _6-Pin SH Debug Port_ that provides access to both SWD pins and the [System Console](system_console.md).

 This is used in FMUv4 and FMUv5.

@@ -122,7 +122,7 @@ You can connect to the debug port using a [cable like this one](https://www.digi

 ### Pixhawk Debug Full

-The [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) defines _Pixhawk Debug Full_, a _10-Pin SH Debug Port_ that provides access to both SWD pins and the [System Console](system_console).
+The [Pixhawk Connector Standard](https://github.com/pixhawk/Pixhawk-Standards/blob/master/DS-009%20Pixhawk%20Connector%20Standard.pdf) defines _Pixhawk Debug Full_, a _10-Pin SH Debug Port_ that provides access to both SWD pins and the [System Console](system_console.md).
 This essentially moves the solder pads from beside the [Pixhawk Debug Mini](#pixhawk-debug-mini) into the connector, and also adds an SWO pin.

 该端口指定用于FMUv5x, FMUv6, FMUv6x。
@@ -154,14 +154,14 @@ You can connect to the debug port using a [cable like this one](https://www.digi

 ## Debug Probes for PX4 Hardware {#debug-probes}

-Flight controllers commonly provide a [single debug port](#autopilot-debug-ports) that exposes both the [SWD Interface](#debug-signals) and [System Console](system_console).
+Flight controllers commonly provide a [single debug port](#autopilot-debug-ports) that exposes both the [SWD Interface](#debug-signals) and [System Console](system_console.md).

 There are several debug probes that are tested and supported for connecting to one or both of these interfaces:

 - [SEGGER J-Link](../debug/probe_jlink.md): commercial probe, no built-in serial console, requires adapter.
 - [Black Magic Probe](../debug/probe_bmp.md): integrated GDB server and serial console, requires adapter.
- [STLink](../debug/probe_stlink): best value, integrated serial console, adapter must be soldered.
- [MCU-Link](../debug/probe_mculink): best value, integrated serial console, requires adapter.
+- [STLink](../debug/probe_stlink.md): best value, integrated serial console, adapter must be soldered.
+- [MCU-Link](../debug/probe_mculink.md): best value, integrated serial console, requires adapter.

 An adapter to connect to the debug port may come with your flight controller or debug probe.
 Other options are given below.
@@ -199,7 +199,7 @@ Probes that are known to come with connectors are listed below:

 ### Board-specific Adapters

-Some manufacturers provide cables to make it easy to connect the SWD interface and [System Console](../debug/system_console).
+Some manufacturers provide cables to make it easy to connect the SWD interface and [System Console](../debug/system_console.md).

 - [CUAV V5nano](../flight_controller/cuav_v5_nano.md#debug_port) and [CUAV V5+](../flight_controller/cuav_v5_plus.md#debug-port) include this debug cable:

@@ -213,7 +213,7 @@ You can also create custom cables for connecting to different boards or probes:
 - Connect the VREF pin, if supported by the debug probe.
 - Connect the remaining pins, if present.

-See the [STLinkv3-MINIE](probe_stlink) for a guide on how to solder a custom cable.
+See the [STLinkv3-MINIE](probe_stlink.md) for a guide on how to solder a custom cable.

 :::tip
 Where possible, we highly recommend that you create or obtain an adapter board rather than custom cables for connecting to SWD/JTAG debuggers and computers.