No acknowledge from address, Jetson Nano 4gb with EN715 carrier

[tunakayakaan]

Hello,

I’m currently trying to make the ar0144 camera work with my jetson nano, but no matter what I do I get:

tegra-vii2c 546c0000.i2c: no acknowledge from address 0x10

and

ar0144 7-0010: ar0144 write reg failed! errors

Any idea why this happens ?

Thanks.

[DaneLLL]

Hi,
Not sure but you may not set the i2c bus number correctly in device tree. Looks like it cannot communicate with ar0144 through i2c.

[tunakayakaan]

Hi, I decided to change it to a single version instead of dual by using tegra210-p3448-0000-p3449-0000-a02.dts. For now it seems like I progress a little:

[ 1.328223] ar0144 pdp-1
[ 1.328225] ar0144 pdp-2
[ 1.328258] ar0144 7-0010: Pakcell 12
[ 1.328262] ar0144 7-0010: ar0144_power_get func begin
[ 1.328265] ar0144 7-0010: ar0144_power_on func begin
[ 1.328268] ar0144 7-0010: Before ar0144_initialize_controls
[ 1.328272] ar0144 7-0010: ar0144_initialize_controls func begin
[ 1.328293] ar0144 7-0010: After ar0144_initialize_controls

but still no input when I do “gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw, width=2592, height=1944 ! videoconvert ! ximagesink”

[tunakayakaan]

Okay I forgot to add the single sensor file to common device tree. After adding it the no acknowledge problem returned.

and I also don’t see the driver on: v4l2-ctl --all

here is the log:

[ 1.328223] ar0144 pdp-1
[ 1.328225] ar0144 pdp-2
[ 1.328258] ar0144 6-0010: Pakcell 12
[ 1.328262] ar0144 6-0010: ar0144_power_get func begin
[ 1.328265] ar0144 6-0010: ar0144_power_on func begin
[ 1.328268] ar0144 6-0010: Before ar0144_initialize_controls
[ 1.328272] ar0144 6-0010: ar0144_initialize_controls func begin
[ 1.328293] ar0144 6-0010: After ar0144_initialize_controls

then

ar0144 write reg failed! and no acknowledge from adress 0x10

I checked the bus number but its seems correct.

[tunakayakaan]

Little update I change the slave addresses to 0x48 instead of 0x10 (because in tegra210-p3448-common-ar0144.dts I wrote devname = “ar0144 6-0048”; proc-device-tree = “/proc/device-tree/host1x/i2c@546c0000/ar0144_a@48”;)

Now I can see the ar0144 in v4l2-ctl --all and media-ctl -p, as shown:

ar0144 in v4l2-ctl --all:

Driver Info (not using libv4l2):
Driver name : tegra-video
Card type : vi-output, ar0144 6-0048
Bus info : platform:54080000.vi:0
Driver version: 4.9.253
Capabilities : 0x84200001
Video Capture
Streaming
Extended Pix Format
Device Capabilities
Device Caps : 0x04200001
Video Capture
Streaming
Extended Pix Format

media-ctl -p:

• entity 1: nvcsi–1 (2 pads, 2 links)
  type V4L2 subdev subtype Unknown flags 0
  device node name /dev/v4l-subdev0
  pad0: Sink
  ← “ar0144 6-0048”:0 [ENABLED]
  pad1: Source
  → “vi-output, ar0144 6-0048”:0 [ENABLED]

• entity 4: ar0144 6-0048 (1 pad, 1 link)
  type V4L2 subdev subtype Sensor flags 0
  device node name /dev/v4l-subdev1
  pad0: Source
  [fmt:SRGGB12_1X12/1280x720 field:none colorspace:srgb]
  → “nvcsi–1”:0 [ENABLED]

• entity 6: vi-output, ar0144 6-0048 (1 pad, 1 link)
  type Node subtype V4L flags 0
  device node name /dev/video0
  pad0: Sink
  ← “nvcsi–1”:1 [ENABLED]

But I still get ar0144 write reg failed! and no acknowledge from adress 0x48

[ShaneCCC]

Suppose you need to probe the I2C signal to figure why device no ack for the I2C command.

Thanks