Wireless connectivity is essential in modern embedded systems—from connected devices in smart homes to industrial networks. At NXP, we are simplifying wireless software across microcontroller units (MCUs) and microprocessor units (MPUs) to make development faster, more consistent and scalable.
NXP’s wireless software supports a wide range of protocols—Wi-Fi, Bluetooth (Classic and LE), Zigbee, Thread, near field communication (NFC), ultra-wideband (UWB) and even sub-GHz technologies like Wi-SUN and Wireless M-Bus. That coverage is built to match the breadth of our hardware portfolio and development ecosystems.
Whether you are developing on an i.MX Applications Processors or an MCX microcontroller, our wireless stacks are part of the baseline software enablement. That means wireless is integrated into Linux and Android broad support packages (BSPs), MCUXpresso software development kits (SDKs) and Zephyr builds—delivered alongside our tools for graphics, AI, voice processing, and more.
Our approach is simple: connectivity should not be treated as a separate or special case. It should be just as accessible and consistent as any other part of the NXP software ecosystem.
Want to dive deeper into the breakdown of NXP’s wireless software strategy? Listen to the full episode of the EdgeVerse Techcast on Spotify or on YouTube .
Wireless implementations can take many forms depending on your application. In standalone solutions—like the MCX W or RW612—there is a full wireless system on a chip (SoC) with an integrated processor and radio on a single chip. In hostless setups, the radio connects to an external processor running the higher layers of the stack.
Standalone use cases are particularly interesting. These require tight integration of the controller, stack and customer application on a single device, which makes memory management and power optimization critical. To address these constraints, we provide configurable frameworks and low-power libraries that allow developers to fine-tune how our software operates within limited system resources.
Low power has always been a top request, especially for battery-powered devices running protocols like Zigbee and Thread. But recently, a new priority has emerged: long-term software support and security compliance, particularly in light of the European Union’s Cyber Resilience Act (CRA).
This shift has led many customers to explore Zephyr-based ecosystems that offer integrated stacks, community support and clearer pathways for long-term updates. That is the reason NXP supports both traditional MCUXpresso environments and Zephyr, allowing developers to choose the ecosystem that best fits their compliance and product lifecycle needs.
With our latest wireless connectivity software release—version 25.06—we have introduced several important features designed to give developers more flexibility and control.
This new feature allows developers to selectively include only the features they need at build time. Rather than delivering a one-size-fits-all firmware image, a developers can now tailor their build to reduce RAM usage and Flash footprint—especially valuable for MCU-based wireless systems.
We see a growing interest in screen projection and phone-to-device streaming, especially in two-wheelers like electric scooters and motorcycles. Wi-Fi Direct support, now available on i.MX RT crossover MCUs, helps deliver a better user experience for these mobile use cases.
NXP’s MCX W MCUs are among the first to achieve channel sounding certification for Bluetooth 6. This opens the door to precise direction-finding and advanced indoor positioning capabilities.
Perhaps just as important as new features is how we deliver them. NXP is heavily invested in ensuring wireless enablement fits naturally into the NXP development experience. That includes GitHub integration, support for West and CMake and participation in quarterly MCUXpresso SDK and broad support package (BSP) releases.
Wireless middleware now lives in the same build trees and follows the same workflows as our other technologies. If you are already developing with NXP, there is no new toolchain to learn. Everything works together—wireless, graphics, machine learning (ML), voice and security—with the same architecture and delivery model.
This alignment reduces the cost of development, simplifies support and bug tracking and accelerates time to market.
Wireless technology can be complex, but our job is to make it approachable, flexible and scalable for developers. Whether you are building a sensor node with minimal power consumption or a rich multimedia experience with dual radios, NXP's wireless software is designed to meet you where you are.
Development Systems Application Engineer, NXP Semiconductors
Kyle Dando is passionate about helping engineers learn how to use the tools required for their embedded designs. At NXP, Kyle is focused on improving the ways that enablement software is delivered. He is working with the wireless team to simplify how developers get started with NXP wireless microcontrollers. He holds Computer and Electrical Engineering degrees from Purdue University and Santa Clara University. His work experience includes hardware and software design, and teaching countless customer events on various embedded design tools.
Product Management Director, Wireless Connectivity Software, NXP Semiconductors
Max Palumbo leads the product management team that delivers wireless connectivity software for microcontroller and microprocessor products in NXP’s primary software ecosystems (MCUXpresso, Zephyr, Linux, and Android). He joined NXP in 2020, bringing a decade of experience working with Wi-Fi, Bluetooth (Classic and Low Energy), Zigbee, and Thread. In the past, Max has worked as an embedded software architect, a field applications engineer, and has served as vice-chair of the Mesh working group in the Bluetooth SIG. He holds a BASc in nanotechnology engineering from the University of Waterloo.