Jetson Orin Nano can't load IMX219 device through 15-22 ribbon cable

Autonomous Machines Jetson & Embedded Systems Jetson Orin Nano
,
1

Hello,
I need help as I can’t seem to get the camera IMX219 to work by connecting the 15-22 ribbon cable pin converter to the CSI connecter.
The cable is Raspberry Pi Camera Cable

Jetson Orin Nano can’t even see the camera connected.
I tried checking if the board set up correctly, by running the command dmesg | grep imx219
I get an error that looks like this:
bootdriver.log (522 Bytes)

Here is my set up:

  • Jetson Orin Nano DevKit
  • RPi ribbon cable 22-15 pin converter 200mm that is connected to CAM1 CSI connector
  • Raspberry Pi Camera Module 2(IMX219)
  • Ubuntu 20.04 LTS
  • JepPack 5.1.1

All connected like this:

image1
image11920×2560 465 KB

If anyone knows how to fix this I would greatly appreciate it!

2

Hello,

Welcome to the NVIDIA Developer forums! Your topic will be best served in the Jetson category.

I will move this post over for visibility.

Cheers,
Tom

3

I also ran the command on overlay devicetree file:
dtc -I dtb -O dts tegra234-p3737-overlay.dtbo
Which gave me a bunch of warnings:
warnings_from_dtb.log (3.0 KB)

What caught my eye is the section with I2C_bus having warning with the address and reg
since I2C bus to my knowledge is responsible for CSI connecters:

<stdout>: Warning (i2c_bus_bridge): /fragment@0/__overlay__/i2c@c240000: incorrect #address-cells for I2C bus
<stdout>: Warning (i2c_bus_bridge): /fragment@0/__overlay__/i2c@c240000: incorrect #size-cells for I2C bus
<stdout>: Warning (i2c_bus_bridge): /fragment@1/__overlay__/i2c@c240000: incorrect #address-cells for I2C bus
<stdout>: Warning (i2c_bus_bridge): /fragment@1/__overlay__/i2c@c240000: incorrect #size-cells for I2C bus
<stdout>: Warning (i2c_bus_reg): Failed prerequisite 'i2c_bus_bridge'

If anyone understand what it means and how it causes the problem with camera not connecting I would appreciate it!

5

The log tell failed to communicate to IMX219 via i2c command.
That could be the cable connector problem. Try to reconnected or try connect to another port.

Thanks

6

Hey Shane,
Thank you for responding!

We have only 2 connectors in the Dev Kit, both of which give the same type of error no matter the amount of reconnects you try.
Do you think it could be a problem with driver or hardware?

7

I don’t think the device tree would make i2c failed.
I would suspect it could be HW or cable problem.

Thanks

8

I don’t think the problem can be related to cables as we tested with many different working cables.
If it comes to HW, do you think the problem is with Dev Kit or with Jetson Orin Nano.

Or do you think during the flashing of Jetson OS image the problem could be with The Host OS image?

Thanks!

9

You can try on another devkit if you have.

Thanks

10

Hey,
I tried reflashing the Jetson with different JetPacks 5.1.1, 5.1.2 and 5.1.3 and all of them give us the same error.
Maybe the flashing logs can help?

Thanks
sdkm-2024-05-05-14-31-59.log (2.6 MB)

11

I don’t think the flash log tell any thing about camera.

12

Hey @ShaneCCC,

I tested the IMX219 on Raspberry Pi 4 and it worked fine so the problem can’t be related to the cameras,
just like we discussed it could either be a problem with HW or the drivers

Are you sure its not related to how i2c_bus is loaded or initiated?

Because this error happens regardless if the camera connected to CSI or not.

Thanks a lot

13

The bus should be i2cmux under the i2c@3180000 shouldn’t matter with i2c@c240000

[    7.347351] i2c i2c-2: Added multiplexed i2c bus 9
[    7.352554] i2c i2c-2: Added multiplexed i2c bus 10
[    7.357586] i2c-mux-gpio cam_i2cmux: 2 port mux on 3180000.i2c adapter
14

So its not related to the driver? sorry I’m not sure what exactly it means

15

I think the device tree configuration is correct but the i2c communicated failed while driver probe.

Maybe check the power/clock/reset pin.

16

Hey ShaceCCC sorry for late response.

Can you specify on how to check it?
Thanks!

17

You need scope to probe to make sure of it.

Thanks

18

Do you mean use the oscilloscope probe?

19

Suppose yes. May need HW guide help to check the HW to probe it.

Thanks

20

We don’t have oscilloscope probe. Is there an alternative to check?

Thanks!

22

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.