New Crowdin translations - zh-CN (#24563)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
2026-10-18 15:43:34 +08:00 · 2025-03-19 20:59:57 +11:00
parent bd0a59eb1f
commit d04e6695ac
180 changed files with 2417 additions and 2402 deletions
@@ -52,80 +52,80 @@ The following steps explain how you can "manually" update the bootloader using a
 1. Get a binary containing the bootloader (either from dev team or [build it yourself](#building-the-px4-bootloader)).

 2. Get a [Debug Probe](../debug/swd_debug.md#debug-probes-for-px4-hardware).
-   Connect the probe your PC via USB and setup the `gdbserver`.
+  Connect the probe your PC via USB and setup the `gdbserver`.

 3. Go into the directory containing the binary and run the command for your target bootloader in the terminal:

-   - FMUv6X
+  - FMUv6X

-     ```sh
-     arm-none-eabi-gdb px4_fmu-v6x_bootloader.elf
-     ```
+    ```sh
+    arm-none-eabi-gdb px4_fmu-v6x_bootloader.elf
+    ```

-   - FMUv6X-RT
+  - FMUv6X-RT

-     ```sh
-     arm-none-eabi-gdb px4_fmu-v6xrt_bootloader.elf
-     ```
+    ```sh
+    arm-none-eabi-gdb px4_fmu-v6xrt_bootloader.elf
+    ```

-   - FMUv5
+  - FMUv5

-     ```sh
-     ```
+    ```sh
+    ```

-   ::: info
-   H7 Bootloaders from [PX4/PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) are named with pattern `*._bootloader.elf`.
-   Bootloaders from [PX4/PX4-Bootloader](https://github.com/PX4/PX4-Bootloader) are named with the pattern `*_bl.elf`.
+  ::: info
+  H7 Bootloaders from [PX4/PX4-Autopilot](https://github.com/PX4/PX4-Autopilot) are named with pattern `*._bootloader.elf`.
+  Bootloaders from [PX4/PX4-Bootloader](https://github.com/PX4/PX4-Bootloader) are named with the pattern `*_bl.elf`.

 :::

 4. The _gdb terminal_ appears and it should display the following output:

-   ```sh
-   GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.20171128-git
-   Copyright (C) 2017 Free Software Foundation, Inc.
-   License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
-   This is free software: you are free to change and redistribute it.
-   There is NO WARRANTY, to the extent permitted by law.
-   Type "show copying"    and "show warranty" for details.
-   This GDB was configured as "--host=x86_64-linux-gnu --target=arm-none-eabi".
-   Type "show configuration" for configuration details.
-   For bug reporting instructions, please see:
-   <http://www.gnu.org/software/gdb/bugs/>.
-   Find the GDB manual and other documentation resources online at:
-   <http://www.gnu.org/software/gdb/documentation/>.
-   For help, type "help".
-   Type "apropos word" to search for commands related to "word"...
-   Reading symbols from px4fmuv5_bl.elf...done.
-   ```
+  ```sh
+  GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.20171128-git
+  Copyright (C) 2017 Free Software Foundation, Inc.
+  License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
+  This is free software: you are free to change and redistribute it.
+  There is NO WARRANTY, to the extent permitted by law.
+  Type "show copying"    and "show warranty" for details.
+  This GDB was configured as "--host=x86_64-linux-gnu --target=arm-none-eabi".
+  Type "show configuration" for configuration details.
+  For bug reporting instructions, please see:
+  <http://www.gnu.org/software/gdb/bugs/>.
+  Find the GDB manual and other documentation resources online at:
+  <http://www.gnu.org/software/gdb/documentation/>.
+  For help, type "help".
+  Type "apropos word" to search for commands related to "word"...
+  Reading symbols from px4fmuv5_bl.elf...done.
+  ```

 5. Find your `<dronecode-probe-id>` by running an `ls` command in the **/dev/serial/by-id** directory.

 6. Now connect to the debug probe with the following command:

-   ```sh
-   tar ext /dev/serial/by-id/<dronecode-probe-id>
-   ```
+  ```sh
+  tar ext /dev/serial/by-id/<dronecode-probe-id>
+  ```

 7. Power on the Pixhawk with another USB cable and connect the probe to the `FMU-DEBUG` port.

-   ::: info
-   If using a Dronecode probe you may need to remove the case in order to connect to the `FMU-DEBUG` port (e.g. on Pixhawk 4 you would do this using a T6 Torx screwdriver).
+  ::: info
+  If using a Dronecode probe you may need to remove the case in order to connect to the `FMU-DEBUG` port (e.g. on Pixhawk 4 you would do this using a T6 Torx screwdriver).

 :::

 8. Use the following command to scan for the Pixhawk\`s SWD and connect to it:

-   ```sh
-   (gdb) mon swdp_scan
-   (gdb) attach 1
-   ```
+  ```sh
+  (gdb) mon swdp_scan
+  (gdb) attach 1
+  ```

 9. 将二进制文件加载到 Pixhawk 中 ：

-   ```sh
-   (gdb) load
-   ```
+  ```sh
+  (gdb) load
+  ```

 After the bootloader has updated you can [Load PX4 Firmware](../config/firmware.md) using _QGroundControl_.

@@ -146,8 +146,8 @@ Currently only FMUv2 and some custom firmware includes the desired bootloader.

 2. [Update the Firmware](../config/firmware.md#custom) with an image containing the new/desired bootloader.

-   ::: info
-   The updated bootloader might be supplied in custom firmware (i.e. from the dev team), or it or may be included in the latest main branch.
+  ::: info
+  The updated bootloader might be supplied in custom firmware (i.e. from the dev team), or it or may be included in the latest main branch.

 :::

@@ -156,7 +156,7 @@ Currently only FMUv2 and some custom firmware includes the desired bootloader.
 4. [Find and enable](../advanced_config/parameters.md) the parameter [SYS_BL_UPDATE](../advanced_config/parameter_reference.md#SYS_BL_UPDATE).

 5. 重新启动（断开/重新连接飞控板）。
-   Bootloader 更新只需要几秒钟即可完成。
+  Bootloader 更新只需要几秒钟即可完成。

 Generally at this point you may then want to [update the firmware](../config/firmware.md) again using the correct/newly installed bootloader.

@@ -176,25 +176,25 @@ Early FMUv2 [Pixhawk-series](../flight_controller/pixhawk_series.md#fmu_versions
 1. 插入 SD 卡（使能引导日志记录，便于调试任何可能的问题）。

 2. [Update the Firmware](../config/firmware.md) to PX4 _master_ version (when updating the firmware, check **Advanced settings** and then select **Developer Build (master)** from the dropdown list).
-   _QGroundControl_ will automatically detect that the hardware supports FMUv2 and install the appropriate Firmware.
+  _QGroundControl_ will automatically detect that the hardware supports FMUv2 and install the appropriate Firmware.

-   ![FMUv2 update](../../assets/qgc/setup/firmware/bootloader_update.jpg)
+  ![FMUv2 update](../../assets/qgc/setup/firmware/bootloader_update.jpg)

-   等待飞控重启。
+  等待飞控重启。

 3. [Find and enable](../advanced_config/parameters.md) the parameter [SYS_BL_UPDATE](../advanced_config/parameter_reference.md#SYS_BL_UPDATE).

 4. 重新启动（断开/重新连接飞控板）。
-   Bootloader 更新只需要几秒钟即可完成。
+  Bootloader 更新只需要几秒钟即可完成。

 5. Then [Update the Firmware](../config/firmware.md) again.
-   This time _QGroundControl_ should autodetect the hardware as FMUv3 and update the Firmware appropriately.
+  This time _QGroundControl_ should autodetect the hardware as FMUv3 and update the Firmware appropriately.

-   ![FMUv3 update](../../assets/qgc/setup/firmware/bootloader_fmu_v3_update.jpg)
+  ![FMUv3 update](../../assets/qgc/setup/firmware/bootloader_fmu_v3_update.jpg)

-   ::: info
-   If the hardware has the [Silicon Errata](../flight_controller/silicon_errata.md#fmuv2-pixhawk-silicon-errata) it will still be detected as FMUv2 and you will see that FMUv2 was re-installed (in console).
-   在这种情况下，您将无法安装 FMUv3 硬件。
+  ::: info
+  If the hardware has the [Silicon Errata](../flight_controller/silicon_errata.md#fmuv2-pixhawk-silicon-errata) it will still be detected as FMUv2 and you will see that FMUv2 was re-installed (in console).
+  在这种情况下，您将无法安装 FMUv3 硬件。

 :::