mirror of
https://github.com/PX4/PX4-Autopilot.git
synced 2026-05-27 02:06:27 +08:00
New Crowdin translations - uk (#25163)
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
GitHub
@@ -10,7 +10,7 @@ PX4 enables terminal access to the system through the [MAVLink Shell](../debug/m
|
||||
|
||||
The PX4 _System Console_ provides low-level access to the system, debug output and analysis of the system boot process.
|
||||
|
||||
There is just one _System Console_, which runs on one specific UART (the debug port, as configured in NuttX), and is commonly attached to a computer via an FTDI cable (or some other debug adapter like a [Dronecode probe](https://kb.zubax.com/display/MAINKB/Dronecode+Probe+documentation)).
|
||||
There is just one _System Console_, which runs on one specific UART (the debug port, as configured in NuttX), and is commonly attached to a computer via an FTDI cable (or some other debug adapter like a [Zubax BugFace BF1](https://github.com/Zubax/bugface_bf1)).
|
||||
|
||||
- Used for _low-level debugging/development_: bootup, NuttX, startup scripts, board bringup, development on central parts of PX4 (e.g. uORB).
|
||||
- Зокрема, це єдине місце, де виводиться весь вивід завантаження (включаючи інформацію про програми, які автоматично запускаються при завантаженні).
|
||||
|
||||
@@ -52,7 +52,6 @@ For more information, see: [https://gnu-mcu-eclipse.github.io/debug/jlink/instal
|
||||
|
||||
|
||||
7. Пакети з оновленнями:
|
||||
|
||||
- Click the small icon on the top right called _Open Perspective_ and open the _Packs_ perspective.
|
||||
|
||||
|
||||
@@ -107,7 +106,6 @@ Task-aware debugging (also known as [thread-aware debugging](https://www.segger.
|
||||
Для активації цієї функції в Eclipse:
|
||||
|
||||
1. You first need to enable `CONFIG_DEBUG_TCBINFO` in the NuttX configuration for your build (to expose the TCB offsets).
|
||||
|
||||
- Відкрийте термінал у кореневій теці вихідного коду PX4-Autopilot
|
||||
|
||||
- In the terminal, open `menuconfig` using the appropriate make target for the build.
|
||||
@@ -149,7 +147,7 @@ Adding missing SVD files for the _Peripheral View_:
|
||||
|
||||
|
||||
|
||||
2. Завантажте відсутні пакети з: http://www.keil.com/dd2/Pack/
|
||||
2. Download missing packages from: https://www.keil.arm.com/devices/
|
||||
|
||||
3. Open downloaded pack with a decompression tool, and extract the **.SVD** files from: **/CMSIS/SVD**.
|
||||
|
||||
|
||||
@@ -1,13 +1,13 @@
|
||||
# Black Magic / Dronecode адаптери
|
||||
# Black Magic Probe (and Zubax BugFace BF1)
|
||||
|
||||
The [Black Magic Probe](https://black-magic.org) is an easy to use, mostly plug-and-play, JTAG/SWD debugger for embedded microcontrollers.
|
||||
Оскільки Black Magic Probe є загальним зондом для налагодження, вам знадобиться адаптер для підключення до керуючих пристроїв польоту Pixhawk, який можна придбати тут:
|
||||
|
||||
- [Drone Code Debug Adapter](https://1bitsquared.com/products/drone-code-debug-adapter) (1 BIT SQUARED).
|
||||
|
||||
## Dronecode Probe
|
||||
## Zubax BugFace BF1 {#dronecode-probe}
|
||||
|
||||
The [Dronecode Probe](https://kb.zubax.com/display/MAINKB/Dronecode+Probe+documentation) is a specialization of the Black Magic Probe for debugging PX4 autopilots.
|
||||
The [Zubax BugFace BF1](https://github.com/Zubax/bugface_bf1) (formerly known as "Dronecode Probe") is a specialization of the Black Magic Probe for debugging PX4 autopilots.
|
||||
|
||||
The probe's USB interface exposes two separate virtual serial port interfaces: one for connecting to the [System Console](system_console.md) (UART) and the other for an embedded GDB server (SWD interface).
|
||||
|
||||
@@ -20,17 +20,17 @@ The _6-pos DF13_ connector that comes with the probe cannot be used for SWD debu
|
||||
## Використання зонда
|
||||
|
||||
:::info
|
||||
To debug STM32F7 or later (FMUv5 and newer) the Dronecode probe / Blackmagic probe likely requires a firmware update.
|
||||
To debug STM32F7 or later (FMUv5 and newer) the Zubax BugFace BF1 / Blackmagic probe likely requires a firmware update.
|
||||
You can find how to update the [blackmagic probe here](https://github.com/blacksphere/blackmagic/wiki/Upgrading-Firmware).
|
||||
:::
|
||||
|
||||
Щоб використовувати зонд Dronecode з GDB, запустіть GDB з точним ELF-файлом, який в даний момент прошивається на автопілоті:
|
||||
To use a Zubax BugFace BF1 with GDB, start GDB with the exact ELF file that is currently flashed on the autopilot:
|
||||
|
||||
```sh
|
||||
arm-none-eabi-gdb build/px4_fmu-v5_default/px4_fmu-v5_default.elf
|
||||
```
|
||||
|
||||
Потім вам потрібно вибрати інтерфейс зонду Dronecode, на Linux це, наприклад.:
|
||||
Then, you have to select the Zubax BugFace BF1 interface, on Linux this is e.g.:
|
||||
|
||||
```sh
|
||||
target ext /dev/serial/by-id/usb-Black_Sphere_Technologies_Black_Magic_Probe_f9414d5_7DB85DAC-if00
|
||||
|
||||
@@ -9,7 +9,7 @@ PMSP - це оболонковий сценарій, який працює шл
|
||||
Відмічені трасування стеку додаються в текстовий файл.
|
||||
Once sampling is finished (which normally takes about an hour or more), the collected stack traces are _folded_.
|
||||
The result of _folding_ is another text file that contains the same stack traces, except that all similar stack traces (i.e. those that were obtained at the same point in the program) are joined together, and the number of their occurrences is recorded.
|
||||
The folded stacks are then fed into the visualization script, for which purpose we employ [FlameGraph - an open source stack trace visualizer](http://www.brendangregg.com/flamegraphs.html).
|
||||
The folded stacks are then fed into the visualization script, for which purpose we employ [FlameGraph - an open source stack trace visualizer](https://www.brendangregg.com/flamegraphs.html).
|
||||
|
||||
## Основне використання
|
||||
|
||||
@@ -17,14 +17,14 @@ The folded stacks are then fed into the visualization script, for which purpose
|
||||
|
||||
Профілер покладається на GDB для запуску PX4 на вбудованій цілі.
|
||||
Так що перед профілюванням цілі, вам потрібно мати обладнання, яке ви хочете профілювати, і вам потрібно скомпілювати та завантажити прошивку на це обладнання.
|
||||
You will then need a [debug probe](../debug/swd_debug.md#debug-probes) (such as the DroneCode Probe), to run the GDB server and interact with the board.
|
||||
You will then need a [debug probe](../debug/swd_debug.md#debug-probes) (such as the Zubax BugFace BF1), to run the GDB server and interact with the board.
|
||||
|
||||
### Визначення пристрою відладки
|
||||
|
||||
The `poor-mans-profiler.sh` automatically detects and uses the correct USB device if you use it with a [DroneCode Probe](../debug/probe_bmp.md#dronecode-probe).
|
||||
The `poor-mans-profiler.sh` automatically detects and uses the correct USB device if you use it with a [Zubax BugFace BF1](../debug/probe_bmp.md#dronecode-probe).
|
||||
If you use a different kind of probe you may need to pass in the specific _device_ on which the debugger is located.
|
||||
You can use the bash command `ls -alh /dev/serial/by-id/` to enumerate the possible devices on Ubuntu.
|
||||
Наприклад, наступні пристрої перераховані з підключеними через USB Pixhawk 4 та DroneCode Probe:
|
||||
For example the following devices are enumerated with a Pixhawk 4 and Zubax BugFace BF1 connected over USB:
|
||||
|
||||
```sh
|
||||
user@ubuntu:~/PX4-Autopilot$ ls -alh /dev/serial/by-id/
|
||||
@@ -48,7 +48,7 @@ Then pass in the appropriate device using the `--gdbdev` argument like this:
|
||||
### Запуск
|
||||
|
||||
Основне використання профілера доступне через систему збірки.
|
||||
For example, the following command builds and profiles px4_fmu-v4pro target with 10000 samples (fetching _FlameGraph_ and adding it to the path as needed).
|
||||
For example, the following command builds and profiles px4_fmu-v4pro target with 10000 samples (fetching \_FlameGraph_ and adding it to the path as needed).
|
||||
|
||||
```sh
|
||||
make px4_fmu-v4pro_default profile
|
||||
|
||||
@@ -187,7 +187,7 @@ The M2 connector on the adaptor is 14-pin CN4 STDC14 (see the [STLinkv3-MINIE Us
|
||||
Some SWD [debug probes](#debug-probes) come with adapters/cables for connecting to common Pixhawk [debug ports](#debug-ports).
|
||||
Зонди, про які відомо, що поставляються з роз'ємами, перераховані нижче:
|
||||
|
||||
- [DroneCode Probe](../debug/probe_bmp.md#dronecode-probe): comes with a connector for attaching to the [Pixhawk Debug Mini](#pixhawk-debug-mini)
|
||||
- [Zubax BugFace BF1](../debug/probe_bmp.md#dronecode-probe): comes with a connector for attaching to the [Pixhawk Debug Mini](#pixhawk-debug-mini)
|
||||
|
||||
### Адаптери, специфічні для плати
|
||||
|
||||
|
||||
@@ -72,7 +72,7 @@ screen /dev/ttyXXX BAUDRATE 8N1
|
||||
|
||||
### Windows: PuTTY
|
||||
|
||||
Download [PuTTY](http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html) and start it.
|
||||
Download [PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) and start it.
|
||||
|
||||
Потім виберіть 'серійне підключення' і встановіть параметри порту:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user