- Forums
- Product Forums
- General Purpose MicrocontrollersGeneral Purpose Microcontrollers
- i.MX Forumsi.MX Forums
- QorIQ Processing PlatformsQorIQ Processing Platforms
- Identification and SecurityIdentification and Security
- Power ManagementPower Management
- Wireless ConnectivityWireless Connectivity
- RFID / NFCRFID / NFC
- Advanced AnalogAdvanced Analog
- Neural Processing UnitsNeural Processing Units
- MCX Microcontrollers
- S32G
- S32K
- S32V
- MPC5xxx
- Other NXP Products
- S12 / MagniV Microcontrollers
- Powertrain and Electrification Analog Drivers
- Sensors
- Vybrid Processors
- Digital Signal Controllers
- 8-bit Microcontrollers
- ColdFire/68K Microcontrollers and Processors
- PowerQUICC Processors
- OSBDM and TBDML
- S32M
- S32Z/E
-
- Solution Forums
- Software Forums
- MCUXpresso Software and ToolsMCUXpresso Software and Tools
- CodeWarriorCodeWarrior
- MQX Software SolutionsMQX Software Solutions
- Model-Based Design Toolbox (MBDT)Model-Based Design Toolbox (MBDT)
- FreeMASTER
- eIQ Machine Learning Software
- Embedded Software and Tools Clinic
- S32 SDK
- S32 Design Studio
- GUI Guider
- Zephyr Project
- Voice Technology
- Application Software Packs
- Secure Provisioning SDK (SPSDK)
- Processor Expert Software
- Generative AI & LLMs
-
- Topics
- Mobile Robotics - Drones and RoversMobile Robotics - Drones and Rovers
- NXP Training ContentNXP Training Content
- University ProgramsUniversity Programs
- Rapid IoT
- NXP Designs
- SafeAssure-Community
- OSS Security & Maintenance
- Using Our Community
-
- Cloud Lab Forums
-
- Knowledge Bases
- ARM Microcontrollers
- i.MX Processors
- Identification and Security
- Model-Based Design Toolbox (MBDT)
- QorIQ Processing Platforms
- S32 Automotive Processing Platform
- Wireless Connectivity
- CodeWarrior
- MCUXpresso Suite of Software and Tools
- MQX Software Solutions
- RFID / NFC
- Advanced Analog
- Neural Processing Units
-
- NXP Tech Blogs
- Home
- :
- Translated Content
- :
- Multi Source Translation Content
- :
- 2407243_en-US
2407243_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2407243_en-US
2407243_en-US
Hello,
I would like to confirm the following for the FRDM-i.MX95:
Is the FRAMOS FSM:GO-IMX900C-M12-L102B-PM-A1Q1 (Sony IMX900 Color) currently supported on FRDM-i.MX95?
If supported, are the required sensor driver, Device Tree configuration and NEO-ISP tuning files available? Which BSP/SDK version provides this support?
Can this camera operate at 1920×1080 color at 120 FPS or higher through the i.MX95 CSI/ISP pipeline?
Which adapter board and cable are required to connect this exact camera module to FRDM-i.MX95?
Does the i.MX95 hardware VPU support single-stream H.264 encoding at 1920×1080 @ 120 FPS?
With B-frames disabled and low-latency settings, what is the expected input-to-bitstream latency or minimum internal buffering?
Is DMA-BUF zero-copy supported from the camera/ISP pipeline to the H.264 hardware encoder?
If the FRAMOS IMX900 module is not currently supported, could you recommend a supported color, global-shutter MIPI CSI-2 camera capable of 1920×1080 @ 120 FPS or higher on FRDM-i.MX95?
Thank you.
1> It is one of our partners supported sensors, so it is not completely supported by NXP, I would suggest to reach out Framos for this.
2> Same as above for this information please contact Framos
3> 2k@120FPS hits the limit of the ISP bandwidth, 1080p should not have issues but again please check with Framos for the supported features.
4> Please check with Framos for available resource for this.
5> The maximum throughput is 4K@60fps, so it should be doable for 1080p@120fps.
6> We do not provide specific input-to-bitstream latency figures for the i.MX95 VPU in low-latency mode. This must be measured on hardware with the target software configuration.
7> Yes, it is supported.
Best regards/Saludos,
Aldo.