MQX v5 will support select Kinetis® and i.MX Cortex™-M subsystems. Support will focus on devices that have been introduced after the MQX v4.2 release, but some devices covered by MQX Classic will be brought into MQX v5 as well. The initial list of supported devices is still being compiled and will be based primarily on user inputs – The list of supported processors will be published on the MQX v5 product page.
Customers can also purchase ports of MQX for any processor in the Kinetis®, i.MX, Power Architecture, ColdFire®. or Qorivva families – even if it’s part of the MQX v5 main release. These ports may incur a higher license fee, based on the level of effort to do the porting—see Professional Services for details.
MQX v5.0 (and subsequent releases) will be similar in architecture to v4.2 and will include the same libraries. In addition to supporting some newer microcontrollers and processors, MQX v5.0 will have bug fixes and enhancements. The updates list for v5.0 is being compiled now and users are encouraged to help influence the roadmap.
MQX v5 will be based on MQX Classic (i.e. v4.x) which means that it will have the IO Subsystem and full set of drivers. Compared to Kinetis SDK there will be differences in the API for the drivers, though the API to kernel functions is completely identical. MQX-Lite is a scaled down version of MQX Classic and the API for kernel and driver calls between the two is identical. MQX v5.0 will be just as scalable as MQX v4.2 and therefore, by disabling unnecessary features through the configuration files, the footprint of MQX v5.0 can get to the same range achievable by MQX-Lite. Note that MQX for Kinetis SDK and MQX-Lite are not recommended for new designs.
Access to maintenance updates for the first year is provided with a license to MQX 5.0. Following the first year, annual maintenance contracts may be purchased. See MQX v5 Software Solutions for details. Free technical support is available in the MQX Community and professional support is available for a fee—see Professional Support for details. Also, custom development work can be contracted—see Professional Services for details
Yes, MQX has been designed to support a multi-processor environment since day one (over 25 years ago). This allows tasks on one CPU to interact with tasks on another CPU (e.g. synchronizing with a semaphore or to send a message). On multi-core processors MQX v5.0 can be set up to manage the boot sequence and access resources shared between different cores.
Included with MQX v5.0 is a Task- Aware Debugging (TAD) DLL for IAR Embedded Workbench and Keil uVision from Arm. The TAD DLL allows the user to easily gain access to kernel level information within the IDE via a pull down menu. The TAD menu provides access to such information as the task list, stack levels, CPU utilization and the status of all resources. A ´check for errors´ window provides information on possible coding errors and socket information is provided via the RTCS pull down menu.
MQX v4.2 is the last release in the MQX Classic product line. MQX Classic is feature set frozen and no new devices are being added. All new development is in the MQX v5 product line. Note that MQX v4 is still a supported product with support available in in the MQX Community. Professional Support is also available and custom development work can be contracted through Professional Services.
Yes, you can a buy a license of a pre-tested release for your chosen processor through Embedded Access Inc. Users are not authorized to create their own port from other NXP MQX RTOS-enabled processor releases. NXP will not provide technical support to users who create their own port.
SSL is supported by the NXP MQX Software Solutions.
MQX Classic products are available via digital download at MQX v5 Software Solutions. MQX v5 products will be made available via direct download for your specified device(s) following the purchase of an MQX v5 license and completion of product registration. See MQX v5 Software Solutions for details.
Yes, you can use NXP MQX RTOS in a commercial project. The source code is provided with the NXP device and you are free to modify it for your specific application.
Even if your application does not require formal certification, the robustness of the MQX™ RTOS helps provide a rock-solid platform proven in thousands of time-critical, sophisticated applications. For those who must follow a formal certification process, the MQX RTOS platform has a record of past certifications in medical specifications (CFR 820.30 Part 21, IEC 60601-1) and the aerospace requirements listed under DO-178b. Safety critical applications based on MQX RTOS include eye surgery equipment, drug injection equipment, radiation dose monitoring equipment, aircraft braking systems and aircraft navigation equipment.