- 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
- :
- 2392382_en-US
2392382_en-US
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
2392382_en-US
2392382_en-US
Dear Support Team,
We are currently working on integrating two cameras using the i.MX8MP FRDM board.
The camera configuration is as follows:
* CSI2:0 is connected to an OV5640 camera.
* CSI2:1 is connected to a custom camera module.
For both cameras, we configured the device tree so that the image pipeline does not use ISP functionality. The intended pipeline is:
"Sensor → MIPI CSI-2 → ISI → Capture"
The device tree file is attached for your reference: "imx8mp-frdm-ov5640-cusdom.dts"
The issue is that the custom camera driver successfully completes the I2C probe process on I2C3, but a kernel panic occurs when calling "v4l2_async_register_subdev_sensor()".
In summary, the kernel panic occurs because "mxc_isi.1" has not been created or registered at the time when the custom camera is registered.
The related kernel panic log is attached: "panic-log.txt"
We have also attached the probe function implementation of the custom camera driver: "custom_driver_probe.c"
We created "imx8mp-frdm-ov5640-cusdom.dts" by referring to the default device tree configuration of the i.MX8MP FRDM board.
The OV5640 camera is working correctly. However, the custom camera cannot establish the connection with the ISI pipeline, which eventually causes the kernel panic.
After reviewing both the device tree configuration and the custom camera driver, we have not been able to identify the root cause of the issue.
The attached "imx8-media-dev.c" file only contains additional debug messages that we added to determine where the kernel panic occurs.
Our goal is to operate two different cameras simultaneously through the MIPI CSI-2 interfaces on the i.MX8MP platform.
Could you please review the attached device tree and driver code and advise which configuration or implementation part may be incorrect or missing?
Your support and guidance would be greatly appreciated.
Thank you.
Best regards,
Seobi