fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-20 19:23:34 +08:00
Code Issues Packages Projects Releases Wiki Activity

New Crowdin translations - ko

Browse Source
This commit is contained in:
Crowdin Bot
2025-07-07 09:03:49 +10:00
committed by Hamish Willee
parent 389b76bd3a
commit 29a40f37e2
163 changed files with 798 additions and 676 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/ko/advanced_config/bootloader_update.md
+5 -5
View File
@@ -78,7 +78,7 @@ arm-none-eabi-objcopy -O ihex build/px4_fmu-v6x_bootloader/px4_fmu-v6x_bootloade
### PX4 Bootloader FMUv5X and earlier
PX4 boards up to FMUv5X (before STM32H7) used the [PX4 bootloader](https://github.com/PX4/Bootloader) repository.
PX4 boards up to FMUv5X (before STM32H7) used the [PX4 bootloader](https://github.com/PX4/PX4-Bootloader) repository.
The instructions in the repo README explain how to use it.
@@ -117,7 +117,7 @@ The following steps explain how you can "manually" update the bootloader using a
:::
4. The _gdb terminal_ appears and it should display the following output:
4. The _gdb terminal_ appears and it should display (something like) the following output:
```sh
GNU gdb (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 8.0.50.20171128-git
@@ -129,9 +129,9 @@ The following steps explain how you can "manually" update the bootloader using a
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/>.
<https://www.sourceware.org/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
<https://www.sourceware.org/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from px4fmuv5_bl.elf...done.
@@ -148,7 +148,7 @@ The following steps explain how you can "manually" update the bootloader using a
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).
If using a Zubax BugFace BF1 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).
:::