WORLDTECH NEWS Global technology intelligence.Contact
Robotics SINGLE SOURCE

NXP Launches Modular Robotics Platform for Physical AI Development

Detailed view of a cutting-edge industrial robotic arm in action.
Illustrative photo.Photo by Freek Wolsink on Pexels

What happened

The company said pre-integrated software and validated subsystem interoperability can cut the months developers often spend integrating and validating robotic subsystems to days or weeks. A developer can begin with a motor-control subsystem tested with the SDK (the toolkit a developer builds on a platform with), then add AI-based perception, flight control and navigation to build an autonomous drone.

Jerome Legros, the company’s robotics vice president and general manager, identified those properties, real-time control and full-lifecycle reliability as the foundation for trusted physical AI systems. NXP Semiconductors said on November 9, 2026, that its new modular robotics platform for physical AI systems can deliver initial drone functionality within 30 minutes out of the box, using a unified package of processors, open-source software and reference designs.

Its underlying Neural Axis Architecture is a distributed foundation for securely connecting sensing, real-time control, AI processing and communications across robotic systems. The workflow is intended to let teams scale from individual functions to complete physical AI systems in one validated development environment.

Open Software and Drone Hardware The Robotics SDK supplies supported drivers, middleware integration, reference applications, configuration tools and reusable components.

Key facts

  • A developer can begin with a motor-control subsystem — tested: with the SDK, then add AI-based perception, flight control and navigation to build an autonomous drone
  • Its listed software — includes: ROS 2 Jazzy, PX4 autopilot, CogniPilot Cerebri, Zephyr RTOS, NuttX and AM32 electronic-speed-controller firmware, with eIQ Toolkit and Ara SDK for edge-AI work
  • Middleware and connectivity support — includes: Zenoh and rmw_zenoh with zenoh-pico, MAVLink, uORB, DShot, 100BASE-T1 automotive Ethernet and RPMsg inter-core communication
  • The documented build environment — uses: Linux with Docker, the west meta-tool, the Arm GNU toolchain, CMake and Ninja, while prebuilt artifacts require a Nexus user token

Sources & evidence