fly316/PX4-Autopilot
7
0
Fork 0
mirror of https://gitee.com/mirrors_PX4/PX4-Autopilot.git synced 2026-10-03 12:48:53 +08:00
Code Issues Packages Projects Releases Wiki Activity

New Crowdin translations - zh-CN (#25483)

Browse Source 
Co-authored-by: Crowdin Bot <support+bot@crowdin.com>
This commit is contained in:
PX4 Build Bot
2025-09-11 08:29:25 +10:00
committed by GitHub
co-authored by Crowdin Bot
parent 472e0657b5
commit 2e84e55d93
123 changed files with 2858 additions and 2621 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/zh/hardware/board_support_guide.md
+2 -2
View File
@@ -33,8 +33,8 @@ The general requirements for all supported boards are:
6. Adequate documentation, which includes, but is not limited to:
- A complete pinout made available publicly that maps PX4 pin definitions to:
1. Microcontroller pins
2. Physical external connectors
1. Microcontroller pins
2. Physical external connectors
- A block diagram or full schematic of the main components (sensors, power supply, etc.) that allows to infer software requirements and boot order
- A manual of the finished product detailing its use
docs/zh/hardware/porting_guide_nuttx.md
+14 -14
View File
@@ -62,30 +62,30 @@ First you will need a bootloader, which depends on the hardware target:
2. Download the source code and make sure you can build an existing target:
```sh
git clone --recursive https://github.com/PX4/PX4-Autopilot.git
cd PX4-Autopilot
make px4_fmu-v5
```
```sh
git clone --recursive https://github.com/PX4/PX4-Autopilot.git
cd PX4-Autopilot
make px4_fmu-v5
```
3. Find an existing target that uses the same (or a closely related) CPU type and copy it.
For example for STM32F7:
For example for STM32F7:
```sh
mkdir boards/manufacturer
cp -r boards/px4/fmu-v5 boards/manufacturer/my-target-v1
```
```sh
mkdir boards/manufacturer
cp -r boards/px4/fmu-v5 boards/manufacturer/my-target-v1
```
Change **manufacturer** to the manufacturer name and **my-target-v1** to your board name.
Change **manufacturer** to the manufacturer name and **my-target-v1** to your board name.
Next you need to go through all files under **boards/manufacturer/my-target-v1** and update them according to your board.
1. **firmware.prototype**: update the board ID and name
2. **default.px4board**: update the **VENDOR** and **MODEL** to match the directory names (**my-target-v1**).
Configure the serial ports.
Configure the serial ports.
3. Configure NuttX (**defconfig**) via `make manufacturer_my-target-v1 menuconfig`: Adjust the CPU and chip, configure the peripherals (UART's, SPI, I2C, ADC).
4. **nuttx-config/include/board.h**: Configure the NuttX pins.
For all peripherals with multiple pin options, NuttX needs to know the pin.
They are defined in the chip-specific pinmap header file, for example [stm32f74xx75xx_pinmap.h](https://github.com/PX4/NuttX/blob/px4_firmware_nuttx-8.2/arch/arm/src/stm32f7/hardware/stm32f74xx75xx_pinmap.h).
For all peripherals with multiple pin options, NuttX needs to know the pin.
They are defined in the chip-specific pinmap header file, for example [stm32f74xx75xx_pinmap.h](https://github.com/PX4/NuttX/blob/px4_firmware_nuttx-8.2/arch/arm/src/stm32f7/hardware/stm32f74xx75xx_pinmap.h).
5. **src**: go through all files under **src** and update them as needed, in particular **board_config.h**.
6. **init/rc.board_sensors**: start the sensors that are attached to the board.