i.MX for Android car head unit – suitability, BSP Part number: i.MX 8M Plus / i.MX 95 / i.MX 8QuadXPlus / i.MX 8QuadMax Hello, We are evaluating NXP i.MX applications processors (i.MX 8M Plus, i.MX 95, i.MX 8QuadXPlus / 8QuadMax) for an Android-based aftermarket car head unit. We would like to understand which part best meets our requirements, along with pricing and support terms. If none of these is suitable, please suggest an alternative part from NXP's portfolio for our development. PRODUCT REQUIREMENTS Platform - Android (AOSP) 13 or later, with BSP source (bootloader, kernel, HALs) - 4 GB DDR4/LPDDR4, 64 GB eMMC - Octa-core class CPU (or equivalent performance) - Industrial (-40 to 85 °C) or automotive (AEC-Q100) temperature grade preferred Display - 9" 1280×800 panel, LVDS preferred (MIPI DSI acceptable) - Capacitive touch over I2C - Display colour adjustment (contrast, saturation, colour temperature) Camera and video - 4 × AHD 720p/1080p cameras via an external 4-channel decoder on MIPI CSI-2 (virtual channels), for 360° surround view - CVBS reverse camera, front/right camera and AV-IN video via a CVBS decoder - H.264/H.265 1080p decode; multi-stream H.264 encode for front/rear recording (e.g. 4 × 720p) - GPU capability for 2D/3D 360° stitching Audio - I2S/TDM (at least one 8-channel TDM port, 3 ports in total) for a multi-channel codec, FM/AM tuner and Bluetooth voice - S/PDIF output - Audio processing for an 8-band EQ, crossover, subwoofer filter and echo cancellation (please advise whether the HiFi4 DSP and its software framework can be used for this under Android) Connectivity and I/O - 3 × USB 2.0 (one OTG) for phone projection, media and accessories - SDIO for a Wi-Fi/Bluetooth module (2.4/5 GHz, BT 5.0 dual connection) - 5 × UART (vehicle interface box, accessory, BT HCI, GNSS, debug) - 3 × I2C, 1 × SPI, 2+ SAR-ADC channels, 3 × PWM, ~20 GPIO - Optional: 4G LTE (integrated or via USB/PCIe module) Application features (please indicate any software available or licensable on your platform) - Apple CarPlay and Android Auto (wired/wireless), phone mirroring - 360° surround view (AVM) library - Audio DSP / sound-effect packages INFORMATION REQUESTED 1. Suitability of each part above against our requirements, and the part you recommend 2. Datasheet, hardware design guide, reference schematics and recommended PMIC/memory 3. Android BSP: available versions (AOSP and Android Automotive), kernel version, roadmap, source availability, and how it is provided (public download, NDA, licence agreement) 4. Any SDK licence fees or per-unit royalties (including HiFi4 DSP software) 5. Evaluation kit / SOM availability, price and lead time 6. Unit pricing for the SoC (or SOM) at 10K, 50K and 100K units per year, plus MOQ and lead time 7. Product longevity / supply commitment 8. Technical support model, and design partners or distributors in India Thank you. Best regards, Shijomon Thomas Re: i.MX for Android car head unit – suitability, BSP Hello, Based on the requirements described, I would shortlist the i.MX 95 and i.MX 8QuadMax. The best choice depends mainly on whether camera/video performance or HiFi4/audio and automotive software maturity has the highest priority.
i.MX95 The i.MX 95 is the strongest candidate for the camera and video workload. It provides:
Up to six Cortex-A55 application cores
4K H.264/H.265 video encode and decode
An ISP supporting multiple 1080p streams and up to eight cameras through MIPI virtual channels
Two four-lane MIPI-CSI interfaces, LVDS display support, and MIPI-DSI display support
Multiple UART and I2C interfaces, ADC inputs, 15-lane I2S/TDM, and S/PDIF
Automotive and extended-industrial temperature options
This makes it a good fit for a four-channel AHD decoder, CVBS decoder inputs, surround-view processing, and multi-stream recording, provided that the selected decoders expose their streams through a supported CSI-2/V4L2 or Android camera interface.
Points to verify before selecting it:
The exact AHD/CVBS decoder and its Android camera or EVS driver support
Whether the camera configuration uses CSI virtual channels within the available lane bandwidth
The MIPI-CSI/DSI multiplexing if MIPI-DSI is selected for the display; LVDS may leave more CSI resources available
The requirement for three PWM outputs, since the processor documentation lists two Timer/PWM blocks
HiFi4 DSP availability. The i.MX 95 documentation does not list a HiFi4 DSP, so audio algorithms may need to run on the application or real-time cores, or on an external audio DSP
Product information: i.MX 95
i.MX8QM The i.MX 8QuadMax is the better fit when automotive qualification, HiFi4 audio processing, peripheral coverage, and Android Automotive enablement are the main priorities. It provides:
Two Cortex-A72 and four Cortex-A53 application cores, plus two Cortex-M4F cores
Automotive AEC-Q100-qualified ordering options
Hardware video, graphics, and camera processing, with support for multiple camera inputs
HiFi4 DSP, multiple SAI/ESAI interfaces, and S/PDIF for the multi-channel audio design
Sufficient UART, I2C, SPI, PWM, and ADC resources for the stated vehicle-interface requirements
NXP Android Automotive support on the i.MX 8QuadMax MEK
The main trade-off is that it is an older architecture than the i.MX 95, so the available video-processing and CPU headroom should be measured with the complete four-camera, CVBS, surround-view, and recording workload. The exact camera decoder, simultaneous stream count, and Android camera integration must also be checked.
Product information: i.MX 8 applications processors i.MX8MPlus The i.MX 8M Plus is attractive for industrial multimedia designs because it includes HiFi4, LVDS/MIPI-DSI, two MIPI-CSI interfaces, and 1080p-class H.264/H.265 video support. However, it has four Cortex-A53 cores, industrial rather than automotive qualification, and only two CSI camera interfaces. It is therefore less suitable for the complete multi-camera head-unit requirement than the i.MX 95 or i.MX 8QuadMax.
Product information: i.MX 8M Plus i.MX8QXP The i.MX 8QuadXPlus provides four Cortex-A35 cores and one Cortex-M4F core, together with multimedia, display, camera, and HiFi4 capabilities. However, its CPU performance is below the requested class. It is also not the preferred current Android Automotive platform compared with the i.MX 8QuadMax and i.MX 95.
Android BSP NXP's public Android BSP page currently lists Android 16 support for the i.MX 8M Plus, i.MX 8QuadMax/8QuadXPlus, and i.MX 95 evaluation platforms. Build-source packages and documentation are provided through the NXP software portal. The exact source and binary coverage, license terms, and production redistribution rights should be confirmed for the selected release.
The current public Android Automotive materials focus on the i.MX 8QuadMax and i.MX 95 platforms. Android Automotive support should be distinguished from Android Auto phone projection.
Android BSP for i.MX applications processors
Android Automotive BSP for i.MX applications processors
Apple CarPlay, Android Auto phone projection, wireless connectivity, AVM/surround-view libraries, audio-effect packages, and HiFi4 software frameworks may require separate certification, partner software, professional services, or commercial licenses. They should not be assumed to be included solely because the SoC supports the required hardware interfaces. In summary the path for selection would be:
Select i.MX 8QuadMax if HiFi4, automotive qualification, audio I/O, PWM resources, and the established Android Automotive path are the primary decision factors.
Select i.MX 95 if camera/video performance, future processing headroom, and virtual-channel camera support are more important, and an external audio DSP or software audio implementation is acceptable.
Keep i.MX 8M Plus and i.MX 8QuadXPlus as secondary options only if the camera count, performance, and automotive requirements are reduced.
Best regards/Saludos, Aldo.
View full article