Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →NXP’s Platform Accelerator combines MICROEJ VEE software containers with standard APIs so developers can reuse embedded applications across supported NXP microcontrollers, crossover processors and application processors. The aim is to reduce device-specific software work—not to make every application run unchanged on every chip.
What is the NXP Platform Accelerator?
Announced by NXP and MicroEJ on January 3, 2024, the Platform Accelerator is a joint software platform built around MICROEJ VEE. It targets NXP RTOS-based microcontrollers and Linux-based application processors, with a common execution environment and APIs intended to make application development more consistent across hardware classes.
In conventional embedded development, moving an application to a different device can mean adapting its low-level software, operating-system integration and middleware to the new processor. The container approach aims to put more of the application above those hardware and operating-system differences. NXP describes potential uses including downloadable applications, microservices, sandboxed deployment and partial or complete over-the-air updates.
How does VEE make an application portable?
The virtual execution environment
MICROEJ VEE provides a virtual execution environment between an application and the underlying processor and operating system. MicroEJ describes VEE as supporting MCUs, MPUs and SoCs running systems including FreeRTOS, Zephyr, ThreadX and Linux, as well as proprietary RTOSes and bare-metal configurations.
#1 Best Overall
- POWERFUL PERFORMANCE: Featuring an NXP Kinetis K64 MCU with 120 MHz ARM Cortex-M4 core, 128 KB RAM and 1 MB Flash memory for robust processing.
- COMPREHENSIVE CONNECTIVITY: Integrated USB, Ethernet, CAN, UART, I2C, SPI and other interfaces enable seamless communication with various devices and networks.
- USER-FRIENDLY DESIGN: The small form factor board and simple hookup headers make prototyping intuitive on the breadboard or custom PCB. Status LEDs provide debugging assistance.
- BROAD COMPATIBILITY: Works and Mbed development environments for quick coding and testing of IoT, industrial, medical and other embedded applications.
- DURABLE CONSTRUCTION: Rigorously tested components and robust assembly ensure reliable, long-lasting operation in diverse industrial environments and prototypes.
Standard APIs and device features
For NXP devices, the Platform Accelerator adds standard APIs and access to processor capabilities such as power management and 2D/3D graphics. This is meant to let developers reuse more application code while still using hardware features appropriate to each device.
Portability is therefore conditional: an application can be reused where the target has a compatible VEE port and provides the APIs and capabilities the application needs. A binary should not be assumed to run on every NXP chip, or to behave identically across devices with different performance, memory, graphics or power characteristics.
Rank #2
- HIGH-PERFORMANCE MICROCONTROLLER: Features an ARM Cortex-M7 processor at 600MHz (can be overclocked), with a NXP iMXRT1062 chip, the most powerful microcontroller available today
- ARDUINO-COMPATIBLE: The Teensy is compatible with the Arduino IDE programming environment as well as many of the existing Arduino libraries, so it is easy to get programmed and running
- RAM: 1024K RAM (512K is tightly coupled); 2048K Flash (64K reserved for recovery & EEPROM emulation)
- MULTIPLE I/O: 2 USB ports, both 480 MBit/sec; 3 CAN Bus (1 with CAN FD); 31 PWM pins; 40 digital pins, all interrupt capable; 14 analog pins, 2 ADCs on chip; 2 I2S Digital Audio
- LOCKABLE PROGRAM CODE OPTION: The LOCKABLE version of the Teensy 4.0 is suitable for commercial products and secure applications to protect your program code from unauthorized access and copying. When code security is not required, we recommend the STANDARD NON-LOCKABLE version.
What the memory figure means
NXP stated in 2023 that MICROEJ VEE requires less than 40KB of memory to package binary applications. This is a vendor-stated packaging figure, not an independent benchmark or a statement of the total memory required by an application and its complete system. The cited materials do not establish a universal performance or power guarantee.
How this differs from per-device firmware
| Area | MICROEJ VEE container approach | Conventional per-device firmware |
|---|---|---|
| Portability scope | Designed to support binary reuse across NXP MCU, crossover and MPU classes where a compatible VEE port and required APIs are available. | Typically requires device-specific adaptation; the extent depends on the firmware and hardware. |
| Host operating systems | MicroEJ lists FreeRTOS, Zephyr, ThreadX, Linux, proprietary RTOSes and bare metal as VEE host options. | Depends on each device’s firmware and operating-system integration. |
| Memory | NXP’s 2023 vendor statement gives less than 40KB to package binary applications; total system requirements are not established by that figure. | Not stated as a comparable value in the cited materials. |
| Isolation and updates | NXP describes sandboxed applications, downloadable apps and partial or complete over-the-air updates as supported use cases. | Not stated as a comparable capability in the cited materials. |
| Graphics and hardware APIs | Platform Accelerator APIs are intended to provide access to capabilities such as power management and 2D/3D graphics. | Depends on the device-specific firmware and software stack. |
| Development tools | NXP describes simulation, virtual device management, a multi-language framework and collaborative development support. | Not stated as a comparable toolset in the cited materials. |
| Long-term support and licensing | Terms and support duration are not stated in the cited materials. | Not stated as a comparable value in the cited materials. |
The practical trade-off is an added portability layer in exchange for a chance to reuse application software and manage it more uniformly. Whether that is worthwhile depends on the application’s resource budget, required hardware features, compatible ports and the vendor terms available for the intended product.
Can the same application run on different NXP chips?
Potentially, if each target has a compatible VEE port and the application uses APIs and resources available on both. NXP’s earlier description of its 32-bit edge work names i.MX RT1050, i.MX RT500, i.MX RW600 and i.MX6 as supported hardware examples. That list is evidence of named examples, not a promise that every application is portable among all four devices.
Before planning a multi-chip product, check the specific device and board port, SDK and VEE versions, required peripherals, memory and performance needs, and any differences in the target operating system. Applications that depend on a device-specific feature may need conditional code or adaptation even when their core logic is reusable.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Which board can you use to evaluate VEE?
MicroEJ’s January 5, 2024 forum announcement named the NXP i.MX RT595 and i.MX RT1170 as the first available VEE ports and linked evaluation-kit repositories for both. These are the clearest starting points identified in that announcement; confirm the current port, SDK compatibility and board revision before buying hardware or following an older repository workflow.
Quick Recap
Best Value
- HIGH-PERFORMANCE MICROCONTROLLER: Features an ARM Cortex-M7 processor at 600MHz (can be overclocked), with a NXP iMXRT1062 chip, the most powerful microcontroller available today
- ARDUINO-COMPATIBLE: The Teensy is compatible with the Arduino IDE programming environment as well as many of the existing Arduino libraries, so it is easy to get programmed and running
- RAM: 1024K RAM (512K is tightly coupled); 2048K Flash (64K reserved for recovery & EEPROM emulation)
- MULTIPLE I/O: 2 USB ports, both 480 MBit/sec; 3 CAN Bus (1 with CAN FD); 31 PWM pins; 40 digital pins, all interrupt capable; 14 analog pins, 2 ADCs on chip; 2 I2S Digital Audio
- LOCKABLE PROGRAM CODE OPTION: The LOCKABLE version of the Teensy 4.0 is suitable for commercial products and secure applications to protect your program code from unauthorized access and copying. When code security is not required, we recommend the STANDARD NON-LOCKABLE version.
- i.MX RT595: one of the first evaluation-platform VEE ports named by MicroEJ.
- i.MX RT1170: the other first port named in the announcement; search for “NXP i.MX RT1170 EVK development board” when locating evaluation hardware, and verify the seller and revision.
What to verify before adopting the platform
- That VEE has a supported port for the exact NXP device and board revision you intend to use.
- That the required APIs and peripherals are available on every target in your product family.
- That total application memory, runtime behavior and power use fit the actual device budget; the packaging figure alone does not establish these.
- That the development workflow, simulation and debugging tools fit your team’s needs.
- That licensing, pricing, update responsibilities and long-term vendor support meet your commercial and maintenance requirements; these terms are not stated in the cited materials.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors
