Development Platform

No Rating

Please select the operating system and development platform for developing the load device according to the difference in the support of the PSDK function between the operating system and the development platform, the resource occupancy of the load device program, and the toolchain supported by the PSDK.

Select Flight Platform

Aircraft Type Function Difference

PSDK Interfaces includes one top-mounted gimbal port and two bottom-mounted gimbal ports. For details, please refer to Device Connectionopen in new window.

FeatureM30/M30TM300 RTK PSDK InterfaceM300 RTK OSDK Interface
Log Management
Information Management
Basic Camera Features-
Basic Camera Management-
Gimbal Features-
Gimbal Management-
Power Management
Flight Control-
Custom Widget
HMS Function
Time Synchronization
Low-speed Data Transmission
Camera Video Stream-
Media Download and Playback--
Xport Feature--
Camera Stream Liveview-
High-speed Data Transmission-
SDK Interconnection-
Local Upgrade-
Waypoint Mission-

Choose an Operating System

Platform Function Differences

Log Management
Information Management
Basic Camera Features
Camera Management
Gimbal Features
Gimbal Management
Power Management
Flight Control
Custom Widget
HMS Function
Time Synchronization
Low-speed Data Transmission
Camera Video Stream
Media Download and Playback-
Xport Feature
Camera Liveview Stream-
High-speed Data Transmission-
SDK Interconnection-
Local Upgrade
Waypoint Mission

Resource Usage


Use Manifold 2-C to run PSDK sample program on the Linux platform. Resource usage of the program is as follows:

  • Stack: 12288 bytes
  • Heap: 40960 bytes
  • Text: 755359 bytes
  • Data: 3872 bytes
  • Bss: 23848 bytes
  • CPU: 7.2%

Using RTOS on the STM32F407IGH6-EVAL, the resource usage of the payload is as follows:

  • Text: 353620 bytes
  • Data: 1836 bytes
  • Bss: 85620 bytes
  • CPU: 30%

Select development platform

PSDK supports the use of the following tools to compile load devices developed based on PSDK. Please select the correct toolchain according to the selected development platform.

Note: For the detailed description of cross-platform porting, please refer to Cross-platform portingopen in new window.

toolchain nametarget platformtypical chip typerecommended development platform
aarch64-linux-gnu-gccaarch64-linux-gnuNVIDIA Jetson TX2、Rockchip RK3399 proManifold2-G、Rock chip Toybrick board
x86_64-linux-gnu-gccx86_64-linux-gnu64位intel cpu,such as Intel Core i7-8550UManiflod2-C
arm-linux-gnueabihf-gccarm-linux-gnueabihfProcessors that support hardware floating-point operations, such as OK5718-C, etc.-
armcc-cortex-m4Cortex M4/M4F系列MCUSTM32F407IGT6、STM32F405RGT6STM32F407-Eval、STM32F407 Discovery Board
arm-none-eabi-gccCortex M4/M4F Series MCUSTM32F407IGT6、STM32F405RGT6STM32F407-Eval、STM32F407 Discovery Board
arm-linux-androideabi-gccarm-linux-androideabiQualcomm Snapdragon series chipAndroid platform
aarch64-linux-android-gccaarch64-linux-androidQualcomm Snapdragon series chipAndroid platform
arm-himix100-linux-gccarm-himix100-linuxhi3516EV series chip-
arm-himix200-linux-gccarm-himix200-linuxhi3516C series chip-
arm-hisiv300-linux-uclibcgnueabi-gccarm-hisiv300-linux-uclibcgnueabihi3516A series chip-
arm-hisiv400-linux-gnueabi-gccarm-hisiv400-linux-gnueabihi3516A series chip-
arm-hisiv500-linux-uclibcgnueabi-gccarm-hisiv500-linux-uclibcgnueabihi3519 series chip-
arm-hisiv600-linux-gnueabi-gccarm-hisiv600-linux-gnueabihi3519 series chip-
xtensa-esp32-elf-gccxtensa-esp32-elfESP32 series chipESP32-DevkitC

Note: The developer needs to select the static library of the specified compilation chain according to the development platform used. If there is no static library of the required compilation chain in the development package, please provide the development platform model, compiler chain model and compiler chain installation package used to develop the load device and send it to SDK technical support team, we will prepare the corresponding toolchain for you.