关于jetson origin nano CSI clock

目前我们参照了nano的设计做了一块板子


但是原先的设计中2lane是以CSI1的clk进行输出,我们的自制板中,我们希望以CSI0的clock进行输出。

硬件接口:
csi0-clkp/n
csi0-d0p/n
csi0-d1p/n
我需要怎么修改软件来匹配硬件的修改

hello 2668729889,

could you please give more details, for example, would you like to have CSI1 data, but using CSI0 clk?

have CSI0 data,using CSI0 clk,

Can I configure it through the software somewhere to take effect,like lane_polarity?

hello 2668729889,

let me have double confirmation,
it’s hardware connected to CSI1, but you like to have SW configure to use CSI0 instead?

I’m sorry I didn’t describe clearing

Our customized board is hardware connected to CSI0,have CSI0 data,using CSI0 clk

but jetson origin nano design it looks like hardware connected to CSI1,have CSI1 data,using CSI1 clk

So, without making any modifications to the device tree,we are encountering issues with receiving now

please see-also Port Index section, you have to update device tree settings accordingly.

When I was browsing this post

It says inside that

is it a customize carrier board?
there’s known issue on developer kit, that 4-lane configure on CAM0 (J20) is NOT working, additional fixes are necessary.

Is there a solution to this problem now?

理论上是能这样配置出流的吧,如果是官方的开发板,应该也能通过配置变成这种模式接收数据吧

hello 2668729889,

CAM0 slot (J20) it’s using CSI1 (i.e. CSI-B) in the diagram. due to some limitation, it’s not support 4-lane configuration.
as you may know, CAM1 slot (J21) it’s using CSI2 (i.e. CSI-C), which able to support 4-lane configuration.

What are some of the restrictions you mentioned? Is it a hardware issue? Performance issues?

Is it impossible to solve it by modifying the software?

hello 2668729889,

it’s an issue on the camera software and also camera firmware side.
we don’t have plan to resolve this yet, please working with CAM1 slot (J21) to support 4-lane configuration.

I’m sorry, I may not have expressed myself clearly earlier. Let me describe my needs again.
We have now made a carrier board ourselves.

Our current hardware connection status is like this:

How can I receive 4LANE from two CAM ports?
How can I resolve what you said about it’s an issue on the camera software and also camera firmware side?

hello 2668729889,

as you’re using customize carrier board. please specify 4-lane camera sensor for using CSI-A in device tree.

Sorry, this is my first time debugging this


Is it necessary to modify this part of the content? tegra_sinterface?

this is DT used by reference driver, you should have your customize sensor device tree to report the settings.

tracer: nop

entries-in-buffer/entries-written: 4/4 #P:6

_-----=> irqs-off

/ _----=> need-resched

| / _—=> hardirq/softirq

|| / _–=> preempt-depth

||| / delay

TASK-PID CPU# |||| TIMESTAMP FUNCTION

| | | |||| | |

 kworker/1:2-117     [001] ....   196.847753: rtcpu_vinotify_event: tstamp:6895657643 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:220651050784 data:0x759d580010000000
 kworker/1:2-117     [001] ....   196.847757: rtcpu_vinotify_event: tstamp:6895657936 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:220651060544 data:0x0000000031000001
 kworker/1:2-117     [001] ....   196.847757: rtcpu_vinotify_event: tstamp:6895658221 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:220651166592 data:0x759d550010000000
 kworker/1:2-117     [001] ....   196.847757: rtcpu_vinotify_event: tstamp:6895658468 cch:0 vi:0 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:220651176480 data:0x0000000031000002

What is your opinion on this part of printing? My Cam0 port 4lane printing only has these

but my CAM1 log has

tracer: nop

entries-in-buffer/entries-written: 44/44 #P:6

_-----=> irqs-off

/ _----=> need-resched

| / _—=> hardirq/softirq

|| / _–=> preempt-depth

||| / delay

TASK-PID CPU# |||| TIMESTAMP FUNCTION

| | | |||| | |

 kworker/1:2-117     [001] ....   206.878302: rtcpu_dbg_set_loglevel: tstamp:7208331459 old:2 new:2
 kworker/1:2-117     [001] ....   211.029784: rtcpu_vinotify_event: tstamp:7338673260 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234827355744 data:0x759e300010000000
 kworker/1:2-117     [001] ....   211.029788: rtcpu_vinotify_event: tstamp:7338673553 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234827365472 data:0x0000000031000001
 kworker/1:2-117     [001] ....   211.029788: rtcpu_vinotify_event: tstamp:7338673844 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234827471520 data:0x759e2d0010000000
 kworker/1:2-117     [001] ....   211.029789: rtcpu_vinotify_event: tstamp:7338674090 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234827481408 data:0x0000000031000002
 kworker/1:2-117     [001] ....   211.029791: rtcpu_nvcsi_intr: tstamp:7338790804 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000010
 kworker/1:2-117     [001] ....   211.029792: rtcpu_nvcsi_intr: tstamp:7338794169 class:GLOBAL type:PHY_INTR0 phy:1 cil:0 st:0 vc:0 status:0x00000110
 kworker/1:2-117     [001] ....   211.029792: rtcpu_nvcsi_intr: tstamp:7338794788 class:GLOBAL type:PHY_INTR0 phy:1 cil:1 st:0 vc:0 status:0x00000010
 kworker/1:2-117     [001] ....   211.029794: rtcpu_vinotify_error: tstamp:7338798684 cch:-1 vi:1 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:234841345312 data:0x0000000000000100
 kworker/1:2-117     [001] ....   211.029794: rtcpu_vinotify_event: tstamp:7339013828 cch:-1 vi:1 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:234841345312 data:0x0000000000000100
 kworker/1:2-117     [001] ....   211.029796: rtcpu_vinotify_event: tstamp:7339354557 cch:0 vi:1 tag:FS channel:0x00 frame:217 vi_tstamp:234856077120 data:0x000000d900000012
 kworker/1:2-117     [001] ....   211.029796: rtcpu_vinotify_event: tstamp:7339354851 cch:0 vi:1 tag:ATOMP_FS channel:0x00 frame:217 vi_tstamp:234856077152 data:0x0000000800000000
 kworker/1:2-117     [001] ....   211.029796: rtcpu_vinotify_event: tstamp:7339355100 cch:0 vi:1 tag:CHANSEL_PXL_SOF channel:0x23 frame:217 vi_tstamp:234856108640 data:0x0000000000000001
 kworker/1:2-117     [001] ....   211.029797: rtcpu_vinotify_event: tstamp:7339355378 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:217 vi_tstamp:234856110944 data:0x0000000008020001
 kworker/1:2-117     [001] ....   211.085771: rtcpu_vinotify_event: tstamp:7339935917 cch:0 vi:1 tag:CHANSEL_PXL_EOF channel:0x23 frame:217 vi_tstamp:234876409056 data:0x0000000007570002
 kworker/1:2-117     [001] ....   211.085772: rtcpu_vinotify_event: tstamp:7339936201 cch:0 vi:1 tag:ATOMP_FRAME_DONE channel:0x23 frame:217 vi_tstamp:234876409984 data:0x0000000000000000
 kworker/1:2-117     [001] ....   211.085772: rtcpu_vinotify_event: tstamp:7339936451 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:217 vi_tstamp:234876414304 data:0x0000000002020001
 kworker/1:2-117     [001] ....   211.085772: rtcpu_vinotify_event: tstamp:7339936730 cch:0 vi:1 tag:FE channel:0x00 frame:217 vi_tstamp:234876410912 data:0x000000d900000022
 kworker/1:2-117     [001] ....   211.085773: rtcpu_vinotify_event: tstamp:7339936988 cch:0 vi:1 tag:ATOMP_FE channel:0x00 frame:217 vi_tstamp:234876410944 data:0x0000000800000000
 kworker/1:2-117     [001] ....   211.085773: rtcpu_vinotify_event: tstamp:7339937266 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:217 vi_tstamp:234876423712 data:0x0000000000020001
 kworker/1:2-117     [001] ....   211.085773: rtcpu_vinotify_event: tstamp:7339937513 cch:0 vi:1 tag:FS channel:0x00 frame:218 vi_tstamp:234877806336 data:0x000000da00000012
 kworker/1:2-117     [001] ....   211.085774: rtcpu_vinotify_event: tstamp:7340240290 cch:0 vi:1 tag:ATOMP_FS channel:0x00 frame:218 vi_tstamp:234877806368 data:0x0000000800000000
 kworker/1:2-117     [001] ....   211.085774: rtcpu_vinotify_event: tstamp:7340240545 cch:0 vi:1 tag:CHANSEL_PXL_SOF channel:0x23 frame:218 vi_tstamp:234877837888 data:0x0000000000000001
 kworker/1:2-117     [001] ....   211.085775: rtcpu_vinotify_event: tstamp:7340240824 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:218 vi_tstamp:234877840160 data:0x0000000008020002
 kworker/1:2-117     [001] ....   211.085775: rtcpu_vinotify_event: tstamp:7340241070 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234877954016 data:0x759e300010000000
 kworker/1:2-117     [001] ....   211.085775: rtcpu_vinotify_event: tstamp:7340241346 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234877963904 data:0x0000000031000003
 kworker/1:2-117     [001] ....   211.085776: rtcpu_vinotify_event: tstamp:7340580908 cch:0 vi:1 tag:CHANSEL_PXL_EOF channel:0x23 frame:218 vi_tstamp:234898138304 data:0x0000000007570002
 kworker/1:2-117     [001] ....   211.085776: rtcpu_vinotify_event: tstamp:7340581191 cch:0 vi:1 tag:ATOMP_FRAME_DONE channel:0x23 frame:218 vi_tstamp:234898139264 data:0x0000000000000000
 kworker/1:2-117     [001] ....   211.085776: rtcpu_vinotify_event: tstamp:7340581441 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:218 vi_tstamp:234898143584 data:0x0000000002020002
 kworker/1:2-117     [001] ....   211.085777: rtcpu_vinotify_event: tstamp:7340581719 cch:0 vi:1 tag:FE channel:0x00 frame:218 vi_tstamp:234898140192 data:0x000000da00000022
 kworker/1:2-117     [001] ....   211.085777: rtcpu_vinotify_event: tstamp:7340581974 cch:0 vi:1 tag:ATOMP_FE channel:0x00 frame:218 vi_tstamp:234898140192 data:0x0000000800000000
 kworker/1:2-117     [001] ....   211.085777: rtcpu_vinotify_event: tstamp:7340582250 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:218 vi_tstamp:234898152992 data:0x0000000000020002
 kworker/1:2-117     [001] ....   211.085778: rtcpu_vinotify_event: tstamp:7340616104 cch:0 vi:1 tag:FS channel:0x00 frame:219 vi_tstamp:234899535584 data:0x000000db00000012
 kworker/1:2-117     [001] ....   211.085778: rtcpu_vinotify_event: tstamp:7340616401 cch:0 vi:1 tag:ATOMP_FS channel:0x00 frame:219 vi_tstamp:234899535616 data:0x0000000800000000
 kworker/1:2-117     [001] ....   211.085778: rtcpu_vinotify_event: tstamp:7340616654 cch:0 vi:1 tag:CHANSEL_PXL_SOF channel:0x23 frame:219 vi_tstamp:234899567072 data:0x0000000000000001
 kworker/1:2-117     [001] ....   211.085779: rtcpu_vinotify_event: tstamp:7340616932 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:219 vi_tstamp:234899569344 data:0x0000000008020003
 kworker/1:2-117     [001] ....   211.085779: rtcpu_vinotify_event: tstamp:7340617179 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234899671552 data:0x759e2d0010000000
 kworker/1:2-117     [001] ....   211.085779: rtcpu_vinotify_event: tstamp:7340955581 cch:0 vi:1 tag:VIFALC_TDSTATE channel:0x23 frame:0 vi_tstamp:234899700800 data:0x0000000031000004
 kworker/1:2-117     [001] ....   211.085779: rtcpu_vinotify_event: tstamp:7341296280 cch:0 vi:1 tag:CHANSEL_PXL_EOF channel:0x23 frame:219 vi_tstamp:234919867488 data:0x0000000007570002
 kworker/1:2-117     [001] ....   211.085780: rtcpu_vinotify_event: tstamp:7341296566 cch:0 vi:1 tag:ATOMP_FRAME_DONE channel:0x23 frame:219 vi_tstamp:234919868384 data:0x0000000000000000
 kworker/1:2-117     [001] ....   211.085780: rtcpu_vinotify_event: tstamp:7341296817 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:219 vi_tstamp:234919872736 data:0x0000000002020003
 kworker/1:2-117     [001] ....   211.085780: rtcpu_vinotify_event: tstamp:7341297101 cch:0 vi:1 tag:FE channel:0x00 frame:219 vi_tstamp:234919869344 data:0x000000db00000022
 kworker/1:2-117     [001] ....   211.085781: rtcpu_vinotify_event: tstamp:7341297355 cch:0 vi:1 tag:ATOMP_FE channel:0x00 frame:219 vi_tstamp:234919869376 data:0x0000000800000000
 kworker/1:2-117     [001] ....   211.085781: rtcpu_vinotify_event: tstamp:7341297640 cch:0 vi:1 tag:VIFALC_ACTIONLST channel:0x23 frame:219 vi_tstamp:234919882176 data:0x0000000000020003

hello 2668729889,

VI tracing log indicate the frame packet status,
there should be logs reported by CHANEL (channel selector) when packets has arrived.
for instance, those logs with CHANSEL_PXL_SOF and CHANSEL_PXL_EOF represent a start-of-frame and end-of-frame.