jimcq
1
I am using the OV428 bridge chip to make it work on the jetson orin nano. When I took a picture I got the following error
[ 643.553662] bwmgr API not supported
[ 646.284993] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 646.297756] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 646.307452] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 646.315230] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=0, csi_port=0
[ 646.325936] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 646.334157] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
run v4l2-ctl -d /dev/video0 --verbose --set-fmt-video=width=1500,height=1500 --steam-mmap --stream-count=10 log
v4l2-ctl-2879 [000] .... 1089.814050: tegra_channel_open: vi-output, ov428 10-0036
v4l2-ctl-2879 [000] .... 1089.837310: tegra_channel_set_power: ov428 10-0036 : 0x1
v4l2-ctl-2879 [000] .... 1089.837317: tegra_channel_set_power: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2-ctl-2879 [000] .... 1089.837322: csi_s_power: enable : 0x1
v4l2-ctl-2879 [002] .... 1089.838271: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt 9
v4l2-ctl-2879 [002] .... 1089.846117: tegra_channel_set_stream: enable : 0x1
v4l2-ctl-2879 [002] .... 1089.847470: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2-ctl-2879 [002] .... 1089.847475: csi_s_stream: enable : 0x1
v4l2-ctl-2879 [002] .... 1089.847807: tegra_channel_set_stream: ov428 10-0036 : 0x1
kworker/1:3-922 [001] .... 1089.857635: rtcpu_string: tstamp:35483108060 id:0x04010000 str:"VM0 activating."
kworker/1:3-922 [001] .... 1089.857640: rtcpu_vinotify_event: tstamp:35483589000 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1135464570304 data:0x759d580010000000
kworker/1:3-922 [001] .... 1089.857641: rtcpu_vinotify_event: tstamp:35483589283 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1135464576800 data:0x0000000031000001
kworker/1:3-922 [001] .... 1089.857641: rtcpu_vinotify_event: tstamp:35483589555 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1135464637440 data:0x759d550010000000
kworker/1:3-922 [001] .... 1089.857642: rtcpu_vinotify_event: tstamp:35483589777 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1135464643968 data:0x0000000031000002
vi-output, ov42-2881 [003] .... 1092.602353: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt 9
kworker/1:3-922 [001] .... 1092.612100: rtcpu_vinotify_event: tstamp:35569521880 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1138221035424 data:0x759d580010000000
kworker/1:3-922 [001] .... 1092.612103: rtcpu_vinotify_event: tstamp:35569522103 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1138221041856 data:0x0000000031000001
kworker/1:3-922 [001] .... 1092.612103: rtcpu_vinotify_event: tstamp:35569522365 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1138221102560 data:0x759d550010000000
kworker/1:3-922 [001] .... 1092.612104: rtcpu_vinotify_event: tstamp:35569522608 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:1138221109088 data:0x0000000031000002
vi-output, ov42-2881 [003] .... 1096.189257: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt 9
kworker/1:3-922 [001] .... 1102.521094: rtcpu_string: tstamp:35877609996 id:0x04010000 str:"VM0 deactivating."
Is there any configuration missing from my device tree below
/dts-v1/;
/plugin/;
/ {
compatible = "nvidia,p3768-0000+p3767-0001\0nvidia,p3767-0001\0nvidia,tegra234\0nvidia,tegra23x";
overlay-name = "My OV428 Overlay Example";
jetson-header-name = "Jetson 24pin CSI Connector";
fragment@0 {
target-path = "/cam_i2cmux/i2c@1";
__overlay__ {
status = "okay";
#address-cells = <1>;
#size-cells = <0>;
cam_ov428@36 {
compatible = "ovti,ov428";
status = "okay";
reg = <0x36>;
clock-frequency = <24000000>;
ports {
#address-cells = <0x01>;
#size-cells = <0x00>;
status = "okay";
port@0 {
status = "okay";
reg = <0x00>;
ov428_to_mipi_csi2: endpoint {
port-index = <0x01>;
bus-width = <0x01>;
data-lanes = <1>;
status = "okay";
remote-endpoint = <&mipi_csi2_in>;
};
};
};
};
};
};
fragment@1 {
target-path = "/host1x@13e00000/nvcsi@15a00000/channel@1";
__overlay__ {
status = "okay";
reg = <1>;
ports {
status = "okay";
#address-cells = <0x01>;
#size-cells = <0x00>;
port@0 {
status = "okay";
reg = <0x00>;
mipi_csi2_in: endpoint {
status = "okay";
remote-endpoint = <&ov428_to_mipi_csi2>;
clock-lanes = <0>;
port-index = <0>;
bus-width = <1>;
};
};
port@1 {
reg = <0x01>;
status = "okay";
mipi_csi2_out: endpoint {
remote-endpoint = <&csi_to_vi>;
status = "okay";
};
};
};
};
};
fragment@2 {
target-path = "/tegra-capture-vi";
__overlay__ {
status="okay";
ports {
#address-cells = <1>;
#size-cells = <0>;
status = "okay";
port@1 {
status = "okay";
reg = <1>;
csi_to_vi: endpoint {
status = "okay";
port-index = <0>;
bus-width = <1>;
remote-endpoint = <&mipi_csi2_out>;
};
};
};
};
};
fragment@3 {
target-path = "/tegra-camera-platform/modules/module1/";
__overlay__ {
status="okay";
drivernode0 {
status = "okay";
pcl_id = "v4l2_sensor";
devname = "ov428 09-0036";
proc-device-tree = "/proc/device-tree/cam_i2cmux/i2c@1/cam_ov428@36";
};
};
};
};
Some other information
edia controller API version 5.10.192
Media device information
------------------------
driver tegra-camrtc-ca
model NVIDIA Tegra Video Input Device
serial
bus info
hw revision 0x3
driver version 5.10.192
Device topology
- entity 1: 13e40000.host1x:nvcsi@15a00000- (2 pads, 0 link)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev0
pad0: Sink
pad1: Source
- entity 4: 13e40000.host1x:nvcsi@15a00000- (2 pads, 2 links)
type V4L2 subdev subtype Unknown flags 0
device node name /dev/v4l-subdev1
pad0: Sink
<- "ov428 10-0036":0 [ENABLED]
pad1: Source
-> "vi-output, ov428 10-0036":0 [ENABLED]
- entity 7: ov428 10-0036 (1 pad, 1 link)
type V4L2 subdev subtype Sensor flags 0
device node name /dev/v4l-subdev2
pad0: Source
[fmt:RGB888_1X24/1500x1500@100/3000
crop:(0,0)/1500x1500]
-> "13e40000.host1x:nvcsi@15a00000-":0 [ENABLED]
- entity 9: vi-output, ov428 10-0036 (1 pad, 1 link)
type Node subtype V4L flags 0
device node name /dev/video0
pad0: Sink
<- "13e40000.host1x:nvcsi@15a00000-":1 [ENABLED]
I want to ask what is missing is my device tree information
Try connect to another port and modify the port-index to 2
jimcq
4
I tried to set the port-index of i2c nvcsi vi to 2 with the same error
In which stage do you think the mistake I encountered most likely occurred
jimcq
6
kworker/0:0-5 [000] .... 252.725144: rtcpu_string: tstamp:9368208771 id:0x04010000 str:"VM0 deactivating."
v4l2-ctl-2604 [003] .... 274.673395: tegra_channel_open: vi-output, ov428 10-0036
v4l2-ctl-2604 [003] .... 274.687612: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt c4
v4l2-ctl-2604 [003] .... 274.695987: tegra_channel_set_stream: enable : 0x1
v4l2-ctl-2604 [003] .... 274.699961: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2-ctl-2604 [003] .... 274.699966: csi_s_stream: enable : 0x1
v4l2-ctl-2604 [003] .... 274.700353: tegra_channel_set_stream: ov428 10-0036 : 0x1
kworker/0:0-5 [000] .... 274.736553: rtcpu_string: tstamp:10055119953 id:0x04010000 str:"VM0 activating."
kworker/0:0-5 [000] .... 274.736560: rtcpu_vinotify_event: tstamp:10055800274 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:321769516128 data:0x759e240010000000
kworker/0:0-5 [000] .... 274.736560: rtcpu_vinotify_event: tstamp:10055800578 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:321769522592 data:0x0000000031000001
kworker/0:0-5 [000] .... 274.736560: rtcpu_vinotify_event: tstamp:10055800858 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:321769588320 data:0x759e210010000000
kworker/0:0-5 [000] .... 274.736561: rtcpu_vinotify_event: tstamp:10055801080 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:321769594880 data:0x0000000031000002
vi-output, ov42-2606 [002] .... 277.341357: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt c4
kworker/0:0-5 [000] .... 277.368425: rtcpu_vinotify_event: tstamp:10138266356 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:324415520224 data:0x759e240010000000
kworker/0:0-5 [000] .... 277.368427: rtcpu_vinotify_event: tstamp:10138266582 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:324415581632 data:0x0000000031000001
kworker/0:0-5 [000] .... 277.368428: rtcpu_vinotify_event: tstamp:10138266841 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:324415595232 data:0x759e210010000000
kworker/0:0-5 [000] .... 277.368428: rtcpu_vinotify_event: tstamp:10138267060 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:324415659552 data:0x0000000031000002
vi-output, ov42-2606 [003] .... 280.928347: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt c4
v4l2-ctl-2604 [000] .... 286.256894: tegra_channel_close: vi-output, ov428 10-0036
v4l2-ctl-2604 [000] .... 286.256922: tegra_channel_set_stream: enable : 0x0
v4l2-ctl-2604 [000] .... 286.256923: tegra_channel_set_stream: ov428 10-0036 : 0x0
v4l2-ctl-2604 [000] .... 286.257108: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x0
v4l2-ctl-2604 [000] .... 286.257112: csi_s_stream: enable : 0x0
kworker/0:0-5 [000] .... 287.056002: rtcpu_string: tstamp:10440424044 id:0x04010000 str:"VM0 deactivating."
jimcq
7
dmesg
[ 701.286552] ------------[ cut here ]------------
[ 701.291372] Invalid rtcpu response id 65535
[ 701.291429] WARNING: CPU: 0 PID: 5 at /dvs/git/dirty/git-master_linux/kernel/nvidia/drivers/platform/tegra/rtcpu/capture-ivc.c:350 tegra_capture_ivc_worker+0xcc/0xe0
[ 701.306605] Modules linked in: ov428(OE) xt_conntrack xt_MASQUERADE nvidia_modeset(O) nf_conntrack_netlink nfnetlink iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype iptable_filter br_netfilter lzo_rle lzo_compress zram overlay ramoops reed_solomon loop bnep iwlmvm mac80211 snd_soc_tegra186_asrc snd_soc_tegra210_ope snd_soc_tegra186_dspk snd_soc_tegra210_mvc snd_soc_tegra210_iqc snd_soc_tegra186_arad snd_soc_tegra210_afc snd_soc_tegra210_dmic snd_soc_tegra210_adx snd_soc_tegra210_admaif snd_soc_tegra210_amx snd_soc_tegra210_mixer snd_soc_tegra210_i2s snd_soc_tegra210_sfc snd_soc_tegra_pcm aes_ce_blk crypto_simd cryptd btusb aes_ce_cipher ghash_ce btrtl btbcm sha2_ce btintel sha256_arm64 sha1_ce snd_soc_spdif_tx snd_soc_tegra_machine_driver iwlwifi snd_soc_tegra210_adsp snd_soc_tegra210_ahub snd_hda_codec_hdmi snd_soc_tegra_utils userspace_alert snd_soc_simple_card_utils fusb301 cfg80211 tegra_bpmp_thermal tegra210_adma nvadsp snd_hda_tegra snd_hda_codec
[ 701.306740] nv_imx219 snd_hda_core r8168 spi_tegra114 nvidia(O) binfmt_misc ina3221 pwm_fan nvgpu nvmap ip_tables x_tables [last unloaded: mtd]
[ 701.306774] CPU: 0 PID: 5 Comm: kworker/0:0 Tainted: G W OE 5.10.192-tegra #1
[ 701.306776] Hardware name: NVIDIA Orin NX Developer Kit (DT)
[ 701.306783] Workqueue: events tegra_capture_ivc_worker
[ 701.306788] pstate: 60c00009 (nZCv daif +PAN +UAO -TCO BTYPE=--)
[ 701.306791] pc : tegra_capture_ivc_worker+0xcc/0xe0
[ 701.306793] lr : tegra_capture_ivc_worker+0xcc/0xe0
[ 701.306795] sp : ffff800010083d70
[ 701.306797] x29: ffff800010083d70 x28: ffffc080b2a06000
[ 701.306801] x27: ffff10216e8d3830 x26: ffff10216e8d37e0
[ 701.306805] x25: 0000000000000000 x24: ffff102002f960d0
[ 701.306808] x23: 0000000000000000 x22: ffffc080b24d0398
[ 701.306812] x21: ffff10200410ac40 x20: ffff10200410ac00
[ 701.306816] x19: ffff102002f96080 x18: 0000000000000000
[ 701.306819] x17: 0000000000000000 x16: ffffc080b1ef2ed0
[ 701.306823] x15: ffff102000164f30 x14: ffffffffffffffff
[ 701.306826] x13: ffffc080b2d29e28 x12: ffffc080b2d29a62
[ 701.306830] x11: ffff102019870920 x10: 0000000000000ab0
[ 701.306834] x9 : ffff800010083d70 x8 : 692065736e6f7073
[ 701.306837] x7 : 6572207570637472 x6 : c0000000ffffefff
[ 701.306840] x5 : ffff10216e8c1978 x4 : ffffc080b2a27ba8
[ 701.306844] x3 : 0000000000000001 x2 : ffff10216e8c1980
[ 701.306847] x1 : 0000000000000000 x0 : 0000000000000000
[ 701.306852] Call trace:
[ 701.306855] tegra_capture_ivc_worker+0xcc/0xe0
[ 701.306865] process_one_work+0x1c4/0x4c0
[ 701.306867] worker_thread+0x54/0x450
[ 701.306869] kthread+0x148/0x170
[ 701.306877] ret_from_fork+0x10/0x18
[ 701.306880] ---[ end trace 5ba1f5a76bf33c5b ]---
[ 701.316889] bwmgr API not supported
[ 704.028296] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 704.041052] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 704.050665] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 704.058401] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[ 704.069061] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 704.077826] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: successfully reset the capture channel
[ 706.588482] tegra-camrtc-capture-vi tegra-capture-vi: uncorr_err: request timed out after 2500 ms
[ 706.597659] tegra-camrtc-capture-vi tegra-capture-vi: err_rec: attempting to reset the capture channel
[ 706.607259] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 706.614994] t194-nvcsi 13e40000.host1x:nvcsi@15a00000: csi5_stream_close: Error in closing stream_id=2, csi_port=2
[ 706.625675] (NULL device *): vi_capture_control_message: NULL VI channel received
[ 707.644138] tegra194-vi5 13e40000.host1x:vi1@14c00000: capture control message timed out
[ 707.652486] tegra194-vi5 13e40000.host1x:vi1@14c00000: vi_capture_control_send_message: failed to send IVC control message
[ 708.668090] tegra194-vi5 13e40000.host1x:vi1@14c00000: capture control message timed out
[ 708.676479] tegra-camrtc-capture-vi tegra-capture-vi: vi capture setup failed
[ 708.683849] tegra-camrtc-capture-vi tegra-capture-vi: fatal: error recovery failed
[ 711.812297] bwmgr API not supported
[ 712.891954] tegra194-vi5 13e40000.host1x:vi1@14c00000: capture control message timed out
[ 712.903909] tegra194-vi5 13e40000.host1x:vi1@14c00000: csi_stream_release: failed to disable nvcsi tpg on stream 2 virtual channel 0
The error is in tegra_capture_ivc_worker
It’s JP6.0? Enable the trace log by below command.
sudo su
modprobe rtcpu_debug
echo 1 > /sys/kernel/debug/tracing/tracing_on
echo 30720 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/tegra_rtcpu/enable
echo 1 > /sys/kernel/debug/tracing/events/freertos/enable
echo 3 > /sys/kernel/debug/camrtc/log-level
echo 1 > /sys/kernel/debug/tracing/events/camera_common/enable
echo > /sys/kernel/debug/tracing/trace
cat /sys/kernel/debug/tracing/trace
jimcq
9
Jetpack 5.1.3
root@ubuntu:/home/user# modprobe rtcpu_debug
modprobe: FATAL: Module rtcpu_debug not found in directory /lib/modules/5.10.192-tegra
JP5 don’t need modprobe rtcpu_debug
jimcq
12
This is the log I got by enabling trace, no other information
kworker/0:0-5 [000] .... 252.725144: rtcpu_string: tstamp:9368208771 id:0x04010000 str:"VM0 deactivating."
v4l2-ctl-2604 [003] .... 274.673395: tegra_channel_open: vi-output, ov428 10-0036
v4l2-ctl-2604 [003] .... 274.687612: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt c4
v4l2-ctl-2604 [003] .... 274.695987: tegra_channel_set_stream: enable : 0x1
v4l2-ctl-2604 [003] .... 274.699961: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x1
v4l2-ctl-2604 [003] .... 274.699966: csi_s_stream: enable : 0x1
v4l2-ctl-2604 [003] .... 274.700353: tegra_channel_set_stream: ov428 10-0036 : 0x1
kworker/0:0-5 [000] .... 274.736553: rtcpu_string: tstamp:10055119953 id:0x04010000 str:"VM0 activating."
kworker/0:0-5 [000] .... 274.736560: rtcpu_vinotify_event: tstamp:10055800274 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:321769516128 data:0x759e240010000000
kworker/0:0-5 [000] .... 274.736560: rtcpu_vinotify_event: tstamp:10055800578 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:321769522592 data:0x0000000031000001
kworker/0:0-5 [000] .... 274.736560: rtcpu_vinotify_event: tstamp:10055800858 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:321769588320 data:0x759e210010000000
kworker/0:0-5 [000] .... 274.736561: rtcpu_vinotify_event: tstamp:10055801080 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:321769594880 data:0x0000000031000002
vi-output, ov42-2606 [002] .... 277.341357: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt c4
kworker/0:0-5 [000] .... 277.368425: rtcpu_vinotify_event: tstamp:10138266356 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:324415520224 data:0x759e240010000000
kworker/0:0-5 [000] .... 277.368427: rtcpu_vinotify_event: tstamp:10138266582 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:324415581632 data:0x0000000031000001
kworker/0:0-5 [000] .... 277.368428: rtcpu_vinotify_event: tstamp:10138266841 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:324415595232 data:0x759e210010000000
kworker/0:0-5 [000] .... 277.368428: rtcpu_vinotify_event: tstamp:10138267060 cch:2 vi:1 tag:VIFALC_TDSTATE channel:0x21 frame:0 vi_tstamp:324415659552 data:0x0000000031000002
vi-output, ov42-2606 [003] .... 280.928347: tegra_channel_capture_setup: vnc_id 0 W 1500 H 1500 fmt c4
v4l2-ctl-2604 [000] .... 286.256894: tegra_channel_close: vi-output, ov428 10-0036
v4l2-ctl-2604 [000] .... 286.256922: tegra_channel_set_stream: enable : 0x0
v4l2-ctl-2604 [000] .... 286.256923: tegra_channel_set_stream: ov428 10-0036 : 0x0
v4l2-ctl-2604 [000] .... 286.257108: tegra_channel_set_stream: 13e40000.host1x:nvcsi@15a00000- : 0x0
v4l2-ctl-2604 [000] .... 286.257112: csi_s_stream: enable : 0x0
kworker/0:0-5 [000] .... 287.056002: rtcpu_string: tstamp:10440424044 id:0x04010000 str:"VM0 deactivating."
Doesn’t looks like get any validate data from the sensor.
Maybe probe the signal to confirm sensor output.
jimcq
14
The oscilloscope detects that the sensor has output. Could it be a clock problem? Can you share a correct log
jimcq
16
/dts-v1/;
/plugin/;
/ {
compatible = "nvidia,p3768-0000+p3767-0001\0nvidia,p3767-0001\0nvidia,tegra234\0nvidia,tegra23x";
overlay-name = "My OV428 Overlay Example";
jetson-header-name = "Jetson 24pin CSI Connector";
fragment@0 {
target-path = "/cam_i2cmux/i2c@1";
__overlay__ {
status = "okay";
#address-cells = <1>;
#size-cells = <0>;
cam_ov428@36 {
compatible = "ovti,ov428";
status = "okay";
reg = <0x36>;
clock-frequency = <24000000>;
ports {
#address-cells = <0x01>;
#size-cells = <0x00>;
status = "okay";
port@0 {
status = "okay";
reg = <0x00>;
ov428_to_mipi_csi2: endpoint {
port-index = <2>;
bus-width = <2>;
clock-lanes = <0>;
data-lanes = <1 2>;
status = "okay";
remote-endpoint = <&mipi_csi2_in>;
};
};
};
};
};
};
fragment@1 {
target-path = "/host1x@13e00000/nvcsi@15a00000/channel@1";
__overlay__ {
status = "okay";
reg = <1>;
ports {
status = "okay";
#address-cells = <0x01>;
#size-cells = <0x00>;
port@0 {
status = "okay";
reg = <0x00>;
mipi_csi2_in: endpoint {
status = "okay";
remote-endpoint = <&ov428_to_mipi_csi2>;
port-index = <2>;
bus-width = <2>;
};
};
port@1 {
reg = <0x01>;
status = "okay";
mipi_csi2_out: endpoint {
remote-endpoint = <&csi_to_vi>;
status = "okay";
};
};
};
};
};
fragment@2 {
target-path = "/tegra-capture-vi";
__overlay__ {
status="okay";
ports {
#address-cells = <1>;
#size-cells = <0>;
status = "okay";
port@1 {
status = "okay";
reg = <1>;
csi_to_vi: endpoint {
status = "okay";
port-index = <2>;
bus-width = <2>;
remote-endpoint = <&mipi_csi2_out>;
};
};
};
};
};
fragment@3 {
target-path = "/tegra-camera-platform/modules/module1/";
__overlay__ {
status="okay";
drivernode0 {
status = "okay";
pcl_id = "v4l2_sensor";
devname = "ov428 10-0036";
proc-device-tree = "/proc/device-tree/cam_i2cmux/i2c@1/cam_ov428@36";
};
};
};
};
Can you double check the device tree for me? Is it possible that the sensor output data, but transmitted it to the wrong channel in the device tree
Thanks
You can dump the device tree to confirm the port-index.
sudo dtc -I fs -O dts -o extracted_proc.dts /proc/device-tree
jimcq
19
extracted_proc.dts.log (429.4 KB)
This is my device tree, please help to check.
And there’s a hardware problem, too.
Do CAM0_MCLK and CAM0 PWRDWN pins need to be connected? I am not connected now
You have confirm with HW designer.
jimcq
21
The problem comes from the HW designer, who is not sure if the two pins need to be connected
jimcq
22
HW designer wants to ask CAM0_MCLK and CAM0_PWRDWN pins need to be connected
If depend on your sensor needed or not.
