The imx214 sensors are configured using the ‘default’ sequence from the reference design, but at a lower PLL frequency around 54 MHz. Both sensors are started synchronously.
Single camera configuration
This setup uses the single camera bit file provided from Helion Vision.
- Framing errors occur early in the entire video stream, then it runs stable for a very long time (recorded up to 150’000 frames)
Dual camera configuration
This setup uses the stereo camera reference design from the Lattice website (DualCSI2toRaw10_impl1.bit).
- Framing very unstable, right image shows interesting color shift
- Offset changing from frame to frame, displaying as above
The reason for the occuring DEMUX errors from the JPEG encoder is occasional invalid framing. Frames are then dropped and the image is out of sync.
- Framing from sensor is wrong (critical sensor configuration mode)
- Framing from Sensor correct, but translation hickups inside CrossLink
- Irregular timing (too short Hblank time) stressing the JPEG encoder FIFOs
(1) can not be verified without a MIPI timing debugger. (2) can not be simulated due to closed source of CrossLink Firmware.
For (3), the LINE_VALID (blue) and FRAME_VALID (yellow) signals, both routed to external debug header display as follows:
The above behaviour of two subsequent pixel lines with short blanking time occur in the current Stereo and single sensor CrossLink firmware configuration.
Sorted by ascending complexity:
- Find magic setting for more regular MIPI data transfer
- Use another sensor (parallel interface)
- Try to fix irregular timing by a ‘sanity checker’ interface with line buffer
- Revisit Crosslink firmware (consider fixes by third party)