This page has moved to https://docs.px4.io/master/zh/hardware/porting_guide.html.
Click here if you are not redirected.
本主题主要针对希望将 PX4 移植到 新 飞控硬件平台上的开发人员。
PX4 consists of two main layers: The board support and middleware layer on top of the host OS (NuttX, Linux or any other POSIX platform like Mac OS), and the applications (Flight Stack in src/modules). 更多有关详细信息请参阅： PX4 系统架构概述 。
本指南仅关注主机操作系统和中间件，因为 应用层/飞行控制栈 可以在任何目标平台上运行。
Board startup and configuration files are located under /boards in each board's vendor-specific directory (i.e. boards/VENDOR/MODEL/)).
例如，对于 FMUv5 飞控硬件平台：
- (All) Board-specific files: /boards/px4/fmu-v5.
- Build configuration: /boards/px4/fmu-v5/default.cmake.
- Board-specific initialisation file: /boards/px4/fmu-v5/init/rc.board_defaults
- 如果在飞控板平台目录下可以找到 init/rc.board 文件，则针对该飞控板平台的初始化文件将会自动包含在启动脚本中。
- 该文件用于启动仅存在于特定主板上的传感器 (和其他东西)。 它也被用于完成对飞控板的默认参数、 UART 映射关系和其它特殊情况的设定。
- For FMUv5 you can see all the Pixhawk 4 sensors being started, and it also sets a larger LOGGER_BUF.
This section describes the purpose and location of the configuration files required for each supported host operating system to port them to new flight controller hardware.
Linux boards do not include the OS and kernel configuration. These are already provided by the Linux image available for the board (which needs to support the inertial sensors out of the box).
- boards/px4/raspberrypi/default.cmake - RPI cross-compilation.
This section describes the various middleware components, and the configuration file updates needed to port them to new flight controller hardware.
- The start script is located in posix-configs/.
- The OS configuration is part of the default Linux image (TODO: Provide location of LINUX IMAGE and flash instructions).
- The PX4 middleware configuration is located in src/boards. TODO: ADD BUS CONFIG
- Reference config: Running
make eagle_defaultbuilds the Snapdragon Flight reference config.
It is generally recommended to connect RC via separate RX and TX pins to the microcontroller. If however RX and TX are connected together, the UART has to be put into singlewire mode to prevent any contention. This is done via board config and manifest files. One example is px4fmu-v5.
The PX4 project supports and maintains the FMU standard reference hardware and any boards that are compatible with the standard. This includes the Pixhawk-series (see the user guide for a full list of officially supported hardware).
Every officially supported board benefits from:
- PX4 Port available in the PX4 repository
- Automatic firmware builds that are accessible from QGroundControl
- Compatibility with the rest of the ecosystem
- Automated checks via CI - safety remains paramount to this community
- Flight testing
We encourage board manufacturers to aim for full compatibility with the FMU spec. With full compatibility you benefit from the ongoing day-to-day development of PX4, but have none of the maintenance costs that come from supporting deviations from the specification.
Manufacturers should carefully consider the cost of maintenance before deviating from the specification (the cost to the manufacturer is proportional to the level of divergence).
We welcome any individual or company to submit their port for inclusion in our supported hardware, provided they are willing to follow our Code of Conduct and work with the Dev Team to provide a safe and fulfilling PX4 experience to their customers.
It's also important to note that the PX4 dev team has a responsibility to release safe software, and as such we require any board manufacturer to commit any resources necessary to keep their port up-to-date, and in a working state.
If you want to have your board officially supported in PX4:
- Your hardware must be available in the market (i.e. it can be purchased by any developer without restriction).
- Hardware must be made available to the PX4 Dev Team so that they can validate the port (contact email@example.com for guidance on where to ship hardware for testing).
- The board must pass full test suite and flight testing.
The PX4 project reserves the right to refuse acceptance of new ports (or remove current ports) for failure to meet the requirements set by the project.
You can reach out to the core developer team and community on the official Forums and Chat.