I’m developing a board based on Jetson TK1 with a video decoder that uses MIPI CSI-2 interface. The idea is to capture video from HDMI to process on board. I’ve got a Jetson now with a Raspberry Pi camera hooked up as best as I could based on some old information from posts from the days when CSI didn’t apparaently work (mid-late 2014). I’ve hooked up the CSI lanes to CSI A, 3.3V to 3.3V_SYS, camera’s poweron to jetson’s GPIO57 and I2C to GEN2-I2C which should correspond to i2c1 port. Some people seem to connect 3.3V i2c to CAM_I2C but these lines are pulled up to 1.8V on the jetson side. Anyone can clarify here? Seems like pins are 3V3-tolerant but jetson isn’t because of these pullups.
The Jetson has L4T 21.3 with latest grinch kernel and I seem to be able to powerup the camera (set GPIO 57 to 1 and camera regulators start running) but i2cdetect says no device is detected on i2c1. I’ll scope the signals and see what’s going on as soon as I can.
If I try to start gstreamer or Cheese after modprbing tegra_camera the board hangs and I have to hard-reset it. I suppose that’s normal because the camera is not configured. I would want to get the raspberry pi camera running as an example to understand how video4linux camera drivers work so then I could implement the driver for the HDMI capture IC. I’ve written device-tree based ALSA drivers for audio codec’s on other platforms where you get the platform’s audio interface driver (for example I2S, equivalent to MIPI CSI2 here) and you have to write the specific codec driver and a third “glue” driver for your specific board. Is it similar on v4l2?
Thanks in advance