Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
Camera Streaming Issues on Toradex Hardware
Based on the available documentation, here are the key areas to investigate for camera streaming issues:
Device Tree Configuration
For proper camera operation, you need to ensure the device tree overlays are correctly configured (1). The camera should be detected on the expected I2C bus - if you’re seeing detection on I2C bus 2 with address 0x3C, verify this matches your device tree configuration (1).
Registry Configuration (Windows CE)
If you’re working with Windows CE on iMX6 modules, the camera driver requires specific registry entries to be loaded (2):
[HKEY_LOCAL_MACHINE\Drivers\IPU\Camera]
"Dll"="_ipuv3camera.dll"
[HKEY_LOCAL_MACHINE\Software\Microsoft\DirectX\DirectShow\Capture1]
"Dll"="_ipuv3camera.dll"
You also need to configure a plugin that handles the camera module (2). For testing purposes, you can use the CSI Test mode plugin (2):
[HKEY_LOCAL_MACHINE\Drivers\IPU\Camera]
"PluginDll"="CSITESTMODE.dll"
Hardware Interface Verification
Check that your camera interface connections are properly configured. The Colibri iMX6ULL supports camera input data signals on specific pins (3). Verify your hardware connections match the pinout specifications in section 5.7.1 of the datasheet (3).
Firmware and Driver Issues
Camera firmware issues can prevent proper streaming even when the device is detected (1). Ensure you have the correct firmware version and that the camera initialization completes successfully without timeout errors (1).
Troubleshooting Steps
- Verify the device tree overlay is properly applied and matches your hardware configuration
- Check kernel logs for any camera-related errors during initialization
- Confirm the I2C communication is working correctly with the detected address
- Ensure the camera plugin/driver is properly configured for your specific camera module
The detection on I2C bus 2 suggests the hardware communication path is working, so the issue likely lies in the media pipeline configuration or driver initialization.
Best regards, Toradex AI Assistant.
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.