I meant your IMX sensor driver.
I setup datatypes again as followings and test it.
- Header Embedded Data: 0x12
- Optical Black(OB) : 0x14
- Active area Data : 0x2D (RAW14 format)
- Footer Embedded Data: 0x13
(1) configure the
embedded_metadata_heightas same as signal settings
In this case, our frame format is below.
Please note that there are some blinking lines between OB and Active Area, and between Active Area and Footer Embedded Data.
Then, set active_h = N and embedded_metadata_height = 1 in DT.
--------------------------------------------------------
| FS |
--------------------------------------------------------
| Header Embedded Data : Datatype = 0x12(1 line) |
--------------------------------------------------------
| Optical Black : Datatype = 0x14 (L lines) |
--------------------------------------------------------
| |
| |
| Active Area : Datatype = 0x2D (N lines) |
| |
| |
--------------------------------------------------------
| Footer Embedded Data : Datatype = 0x13(M lines) |
--------------------------------------------------------
| FE |
--------------------------------------------------------
- result
1st FS/FE missing issue, SPURIOUS_DATA_STREAM_0 and CHANSEL_NOMATCH for Header Embedded Data(datatype:0x12) appeared.
kworker/0:1-796 [000] .... 62.015508: rtos_queue_send_from_isr_failed: tstamp:2278458878 queue:0x0bcb9ce0
kworker/0:1-796 [000] .... 62.015509: rtos_queue_send_from_isr_failed: tstamp:2278459010 queue:0x0bcbaaa0
kworker/0:1-796 [000] .... 62.015510: rtcpu_nvcsi_intr: tstamp:2278461470 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000001
kworker/0:1-796 [000] .... 62.015512: rtcpu_vinotify_event: tstamp:2278668694 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:4188709888 data:0x10000000
kworker/0:1-796 [000] .... 62.015513: rtcpu_vinotify_event: tstamp:2278668838 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:4188713664 data:0x31000001
kworker/0:1-796 [000] .... 62.015513: rtcpu_vinotify_event: tstamp:2278668982 tag:RESERVED_19 channel:0x23 frame:0 vi_tstamp:4188714656 data:0x07020001
kworker/0:1-796 [000] .... 62.015514: rtcpu_vinotify_event: tstamp:2278669105 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:4188840608 data:0x10000000
kworker/0:1-796 [000] .... 62.015515: rtcpu_vinotify_event: tstamp:2278669245 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:4188844416 data:0x31000002
kworker/0:1-796 [000] .... 62.068239: rtcpu_vinotify_error: tstamp:2280989646 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:2280988980 data:0x00000001
kworker/0:1-796 [000] .... 62.068241: rtcpu_vinotify_event: tstamp:2281172740 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:2280988980 data:0x00000001
kworker/0:1-796 [000] .... 62.068242: rtcpu_vinotify_error: tstamp:2281575140 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:2281574481 data:0x00000249
kworker/0:1-796 [000] .... 62.068243: rtcpu_vinotify_event: tstamp:2281798742 tag:FS channel:0x01 frame:2 vi_tstamp:2281573672 data:0x00000010
kworker/0:1-796 [000] .... 62.068244: rtcpu_vinotify_event: tstamp:2281798866 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:2281574481 data:0x00000249
kworker/0:1-796 [000] .... 62.124236: rtcpu_vinotify_error: tstamp:2282269536 tag:CHANSEL_NOMATCH channel:0x41 frame:3 vi_tstamp:2282268885 data:0x00000249
kworker/0:1-796 [000] .... 62.124239: rtcpu_vinotify_event: tstamp:2282424766 tag:FE channel:0x01 frame:2 vi_tstamp:2282243890 data:0x00000020
kworker/0:1-796 [000] .... 62.124241: rtcpu_vinotify_event: tstamp:2282424892 tag:FS channel:0x01 frame:3 vi_tstamp:2282268074 data:0x00000010
kworker/0:1-796 [000] .... 62.124242: rtcpu_vinotify_event: tstamp:2282425032 tag:CHANSEL_NOMATCH channel:0x41 frame:3 vi_tstamp:2282268885 data:0x00000249
kworker/0:1-796 [000] .... 62.124243: rtcpu_vinotify_error: tstamp:2282963936 tag:CHANSEL_NOMATCH channel:0x41 frame:4 vi_tstamp:2282963287 data:0x00000249
kworker/0:1-796 [000] .... 62.124245: rtcpu_vinotify_event: tstamp:2283050791 tag:FE channel:0x01 frame:3 vi_tstamp:2282938291 data:0x00000020
kworker/0:1-796 [000] .... 62.124246: rtcpu_vinotify_event: tstamp:2283050932 tag:FS channel:0x01 frame:4 vi_tstamp:2282962477 data:0x00000010
kworker/0:1-796 [000] .... 62.124247: rtcpu_vinotify_event: tstamp:2283051057 tag:CHANSEL_NOMATCH channel:0x41 frame:4 vi_tstamp:2282963287 data:0x00000249
kworker/0:1-796 [000] .... 62.124249: rtos_queue_peek_from_isr_failed: tstamp:2283329791 queue:0x0bcbb8b8
kworker/0:1-796 [000] .... 62.180267: rtcpu_vinotify_event: tstamp:2283658254 tag:FE channel:0x01 frame:4 vi_tstamp:2283632693 data:0x00000020
kworker/0:1-796 [000] .... 62.180269: rtcpu_vinotify_event: tstamp:2283658388 tag:FS channel:0x01 frame:5 vi_tstamp:2283657732 data:0x00000010
kworker/0:1-796 [000] .... 62.180272: rtcpu_vinotify_error: tstamp:2283659191 tag:CHANSEL_NOMATCH channel:0x41 frame:5 vi_tstamp:2283658545 data:0x00000249
kworker/0:1-796 [000] .... 62.180273: rtcpu_vinotify_event: tstamp:2283958472 tag:CHANSEL_NOMATCH channel:0x41 frame:5 vi_tstamp:2283658545 data:0x00000249
(2) configure from driver side to fully disable that.
I disabled embedded data output both of header and footer.
In this case, our frame format is below.
Please note that there are some blinking lines between OB and Active Area.
Then, set active_h = N and embedded_metadata_height = 0 in DT.
--------------------------------------------------------
| FS |
--------------------------------------------------------
| Optical Black : Datatype = 0x14 (L lines) |
--------------------------------------------------------
| |
| |
| Active Area : Datatype = 0x2D (N lines) |
| |
| |
--------------------------------------------------------
| FE |
--------------------------------------------------------
- result
1st FS/FE missing issue, SPURIOUS_DATA_STREAM_0 and CHANSEL_NOMATCH for OB(datatype:0x14) appeared.
kworker/1:0-18 [001] .... 99.218782: rtos_queue_send_from_isr_failed: tstamp:3471761086 queue:0x0bcb9ce0
kworker/1:0-18 [001] .... 99.218782: rtos_queue_send_from_isr_failed: tstamp:3471761220 queue:0x0bcbaaa0
kworker/1:0-18 [001] .... 99.218784: rtcpu_nvcsi_intr: tstamp:3471763672 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000001
kworker/1:0-18 [001] .... 99.218786: rtcpu_vinotify_event: tstamp:3471985229 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3720078368 data:0x10000000
kworker/1:0-18 [001] .... 99.218787: rtcpu_vinotify_event: tstamp:3471985360 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3720082176 data:0x31000001
kworker/1:0-18 [001] .... 99.218788: rtcpu_vinotify_event: tstamp:3471985504 tag:RESERVED_19 channel:0x23 frame:0 vi_tstamp:3720083168 data:0x07020001
kworker/1:0-18 [001] .... 99.218789: rtcpu_vinotify_event: tstamp:3471985627 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3720194560 data:0x10000000
kworker/1:0-18 [001] .... 99.218790: rtcpu_vinotify_event: tstamp:3471985769 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3720198368 data:0x31000002
kworker/1:0-18 [001] .... 99.273816: rtcpu_vinotify_error: tstamp:3473912274 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:3473911606 data:0x00000001
kworker/1:0-18 [001] .... 99.273820: rtcpu_vinotify_event: tstamp:3474176264 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:3473911606 data:0x00000001
kworker/1:0-18 [001] .... 99.273821: rtcpu_vinotify_error: tstamp:3474503318 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:3474502659 data:0x00000289
kworker/1:0-18 [001] .... 99.273823: rtcpu_vinotify_event: tstamp:3474802269 tag:FS channel:0x01 frame:2 vi_tstamp:3474501849 data:0x00000010
kworker/1:0-18 [001] .... 99.273824: rtcpu_vinotify_event: tstamp:3474802396 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:3474502659 data:0x00000289
kworker/1:0-18 [001] .... 99.273826: rtcpu_vinotify_error: tstamp:3475197716 tag:CHANSEL_NOMATCH channel:0x41 frame:3 vi_tstamp:3475197062 data:0x00000289
kworker/1:0-18 [001] .... 99.329804: rtcpu_vinotify_event: tstamp:3475428295 tag:FE channel:0x01 frame:2 vi_tstamp:3475163525 data:0x00000020
kworker/1:0-18 [001] .... 99.329806: rtcpu_vinotify_event: tstamp:3475428427 tag:FS channel:0x01 frame:3 vi_tstamp:3475196252 data:0x00000010
kworker/1:0-18 [001] .... 99.329807: rtcpu_vinotify_event: tstamp:3475428568 tag:CHANSEL_NOMATCH channel:0x41 frame:3 vi_tstamp:3475197062 data:0x00000289
kworker/1:0-18 [001] .... 99.329809: rtcpu_vinotify_error: tstamp:3475892112 tag:CHANSEL_NOMATCH channel:0x41 frame:4 vi_tstamp:3475891464 data:0x00000289
kworker/1:0-18 [001] .... 99.329845: rtcpu_vinotify_event: tstamp:3476054316 tag:FE channel:0x01 frame:3 vi_tstamp:3475857927 data:0x00000020
kworker/1:0-18 [001] .... 99.329846: rtcpu_vinotify_event: tstamp:3476054459 tag:FS channel:0x01 frame:4 vi_tstamp:3475890655 data:0x00000010
kworker/1:0-18 [001] .... 99.329848: rtcpu_vinotify_event: tstamp:3476054584 tag:CHANSEL_NOMATCH channel:0x41 frame:4 vi_tstamp:3475891464 data:0x00000289
kworker/1:0-18 [001] .... 99.329849: rtcpu_vinotify_event: tstamp:3476586429 tag:FE channel:0x01 frame:4 vi_tstamp:3476552330 data:0x00000020
kworker/1:0-18 [001] .... 99.329850: rtcpu_vinotify_event: tstamp:3476586556 tag:FS channel:0x01 frame:5 vi_tstamp:3476585910 data:0x00000010
kworker/1:0-18 [001] .... 99.329852: rtcpu_vinotify_error: tstamp:3476587362 tag:CHANSEL_NOMATCH channel:0x41 frame:5 vi_tstamp:3476586721 data:0x00000289
kworker/1:0-18 [001] .... 99.329854: rtos_queue_peek_from_isr_failed: tstamp:3476639482 queue:0x0bcbb8b8
kworker/1:0-18 [001] .... 99.329855: rtcpu_vinotify_event: tstamp:3476899355 tag:CHANSEL_NOMATCH channel:0x41 frame:5 vi_tstamp:3476586721 data:0x00000289
hello tagoshi,
please see-also Topic 235004. I’m now checking internally whether we support SerDes chips (i.e. GMSL) with embedded metadata.
let’s focus on bring-up this by disabling embedded data output both of header and footer.
what did you meant… there are some blinking lines between OB and Active Area.
are they ignored effect pixels?
BTW, please also review the VMAX, HMAX configurations.
Hi JerryChang,
Thank you for reply, I’ll check the link to use embedded data.
Please note that only one CMOS chip is connected to a SerDes chip currently, so I think it can be handled as if a CMOS is directory connected to JETSON CSI bus.
what did you meant… there are some blinking lines between OB and Active Area.
are they ignored effect pixels?
Sorry, I found typo, it’s blanking line…
During this period, only MIPI clock works continuously, and there is no valid MIPI signal on data line.
BTW, please also review the VMAX, HMAX configurations.
Do you mean the value of active_w, active_h, and line_length in DT?
hello tagoshi,
could you please share the signaling for reference,
is it something like high speed signaling drop for a very short period?
ya, please double check those values were all correct. since they’re timing specific signalings.
Hi JerryChang,
This is our sample MIPI data line and blanking line is red rectangle, please note that this data pattern include OB and Header/Footer embedded data.
Blue pattern is MIPI clock.
ya, please double check those values were all correct. since they’re timing specific signalings.
OK, I did double checked. But it seems to be correct…
BTW, is it possible to set V4L2 set-mode-delay parameter just like “set_mode_delay_ms”?
I would like to know how to solve 1st FS/FE missing issue.
In addition to that, I cannot understand why CHANSEL_NOMATCH for frame 3 occurred before FE packet for frame 2 and FS packet for frame 3 arrived.
is this caused by 1st FS/FE missing issue?
kworker/0:1-796 [000] .... 62.068242: rtcpu_vinotify_error: tstamp:2281575140 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:2281574481 data:0x00000249
kworker/0:1-796 [000] .... 62.068243: rtcpu_vinotify_event: tstamp:2281798742 tag:FS channel:0x01 frame:2 vi_tstamp:2281573672 data:0x00000010
kworker/0:1-796 [000] .... 62.068244: rtcpu_vinotify_event: tstamp:2281798866 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:2281574481 data:0x00000249
kworker/0:1-796 [000] .... 62.124236: rtcpu_vinotify_error: tstamp:2282269536 tag:CHANSEL_NOMATCH channel:0x41 frame:3 vi_tstamp:2282268885 data:0x00000249
kworker/0:1-796 [000] .... 62.124239: rtcpu_vinotify_event: tstamp:2282424766 tag:FE channel:0x01 frame:2 vi_tstamp:2282243890 data:0x00000020
kworker/0:1-796 [000] .... 62.124241: rtcpu_vinotify_event: tstamp:2282424892 tag:FS channel:0x01 frame:3 vi_tstamp:2282268074 data:0x00000010
hello tagoshi,
you may tune cil_settletime to adjust THS settle time of the MIPI lane to avoid that blanking line. please refer to Xavier TRM for details.
as above, it can be done by adjust THS settle time of the MIPI lane,
that’s actually couple CHANSEL_NOMATCH reported. you may dig into vi_tstamp.
thanks
BTW,
Spurious data that means VI sees some other packets before FS packet, as VI always expect that 1st packet to be frame start.
Hi, JerryChang,
Thank you for helpful info.
I reviewed CMOS/SerDes settings again, and found that 1st FS missing is the specification of our SerDes device output, sorry for confusing you.
Therefore, I can ignore 1st FS missing issue and SPURIOUS_DATA_STREAM_0.
And please let me confirm FS/FE packet data.
tag:FS channel:0x01 frame:2 vi_tstamp:3474501849 data:0x00000010
tag:FE channel:0x01 frame:2 vi_tstamp:3475163525 data:0x00000020
Is data value of FS(0x00000010) and FE(0x00000020) correct?
By below link, it say bit 1-4 is CTYPE and FS=0x8, FE=0x1.
Then, our FS has 0x8 CTYPE value from data, but FE has 0x0 CTYPE value. Is it OK?
Is CTYPE rule applied to CHANSEL_NOMATCH case only ?
https://elinux.org/Jetson/l4t/Camera_BringUp
Now I focus on CHANSEL_NOMATCH error.
I wonder why CHANSEL_NOMATCH for 0x12 occurred although I set “embedded_metadata_height” = 1 in DT setting.
For this evaluation, datatype settings are as followings.
- Header Embedded Data(1 line): 0x12
- Optical Black(OB) (4 lines) : 0x14
- Blanking area (8lines) : No MIPI Data, NULL
- Active area Data : 0x2D (RAW14 format)
- Blanking area (8lines) : No MIPI Data, NULL
- Footer Embedded Data: 0x13
Just for debugging, I changed “embedded_metadata_height” value as 1, 2 ,3 ,4, and 5.
I confirmed this value is correctly applied in vi5_setup_surface() and vi5_channel_start_streaming(), but result didn’t change at all.
Is there any hint in CSI/VI log?
BTW, could you tell me what does “channel” value mean?
kworker/1:2-1975 [001] .... 47.250449: rtcpu_vinotify_error: tstamp:1899745251 tag:CHANSEL_NOMATCH channel:0x41 frame:11 vi_tstamp:1899744599 data:0x00000249
kworker/1:2-1975 [001] .... 47.250451: rtcpu_vinotify_event: tstamp:1899750698 tag:FE channel:0x01 frame:10 vi_tstamp:1899718749 data:0x00000020
kworker/1:2-1975 [001] .... 47.250452: rtcpu_vinotify_event: tstamp:1899750821 tag:FS channel:0x01 frame:11 vi_tstamp:1899743788 data:0x00000010
kworker/1:2-1975 [001] .... 47.250453: rtcpu_vinotify_event: tstamp:1899750960 tag:CHANSEL_NOMATCH channel:0x41 frame:11 vi_tstamp:1899744599 data:0x00000249
kworker/1:2-1975 [001] .... 47.250454: rtcpu_vinotify_error: tstamp:1900440506 tag:CHANSEL_NOMATCH channel:0x41 frame:12 vi_tstamp:1900439857 data:0x00000249
kworker/1:2-1975 [001] .... 47.250456: rtcpu_vinotify_event: tstamp:1900440768 tag:FE channel:0x01 frame:11 vi_tstamp:1900414007 data:0x00000020```
hello tagoshi,
they’re correct. it’s bit-4 for FS flag and bit-5 for FE flag.
so, FS with 0x10 and FE with 0x20 it means frame-start and frame-end were all received.
BTW,
you may refer to see-also Topic 235004, which mentioned that they can capture frames normally without enable embedded data.
that why I’m checking internally for SerDes chips with embedded metadata.
Hi JerryChang,
they’re correct. it’s bit-4 for FS flag and bit-5 for FE flag.
so,FSwith 0x10 andFEwith 0x20 it means frame-start and frame-end were all received.
Thanks, so FS and FE packets were correctly received. glad to hear that.
you may refer to see-also Topic 235004, which mentioned that they can capture frames normally without enable embedded data.
OK, so how about changing all datatype as 0x2D and setting embedded_metadata_height = 0?
I mean let the CSI/VI engine handle all received data as RAW14 data.
I expect that I can see at least 5 embedded lines(Header Embedded Data + OB) at the top of Image file, and some lines at the bottom of image file.
I have already tried this test in comment #14, but it was before fixing SerDes stream issue.
- Header Embedded Data(1 line): 0x2D
- Optical Black(OB) (4 lines) : 0x2D
- Blanking area (8lines) : No MIPI Data, NULL
- Active area Data : 0x2D (RAW14 format)
- Blanking area (8lines) : No MIPI Data, NULL
- Footer Embedded Data: 0x2D
Unfortunately, CHANSEL_NOMATCH for 0x2D still remained.
From this result, I think it is not related with “embedded metadata”, because there is no embedded metadata whose datatype is 0x12 in this frame.
I would like to know your view on this issue.
--------------------------------------------------------
| FS |
--------------------------------------------------------
| Active Area(dummy data) : Datatype = 0x2D |
--------------------------------------------------------
| blanking line (NULL) |
--------------------------------------------------------
| |
| |
| Active Area : Datatype = 0x2D |
| |
| |
--------------------------------------------------------
| blanking line (NULL) |
--------------------------------------------------------
| Active Area(dummy data) : Datatype = 0x2D |
--------------------------------------------------------
| FE |
--------------------------------------------------------
kworker/1:0-18 [001] .... 150.559764: rtos_queue_send_from_isr_failed: tstamp:5084295581 queue:0x0bcb8f20
kworker/1:0-18 [001] .... 150.559765: rtos_queue_send_from_isr_failed: tstamp:5084295714 queue:0x0bcb9ce0
kworker/1:0-18 [001] .... 150.559765: rtos_queue_send_from_isr_failed: tstamp:5084295848 queue:0x0bcbaaa0
kworker/1:0-18 [001] .... 150.559767: rtcpu_nvcsi_intr: tstamp:5084298304 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000001
kworker/1:0-18 [001] .... 150.559768: rtcpu_vinotify_event: tstamp:5084544158 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3782517344 data:0x10000000
kworker/1:0-18 [001] .... 150.559769: rtcpu_vinotify_event: tstamp:5084544306 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3782521120 data:0x31000001
kworker/1:0-18 [001] .... 150.559770: rtcpu_vinotify_event: tstamp:5084544449 tag:RESERVED_19 channel:0x23 frame:0 vi_tstamp:3782522112 data:0x07020001
kworker/1:0-18 [001] .... 150.559771: rtcpu_vinotify_event: tstamp:5084544573 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3782785696 data:0x10000000
kworker/1:0-18 [001] .... 150.559771: rtcpu_vinotify_event: tstamp:5084544713 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3782789664 data:0x31000002
kworker/1:0-18 [001] .... 150.723739: rtos_queue_peek_from_isr_failed: tstamp:5089190700 queue:0x0bcbb8b8
kworker/1:0-18 [001] .... 150.723745: rtcpu_vinotify_error: tstamp:5089613231 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:5089612567 data:0x00000001
kworker/1:0-18 [001] .... 150.779701: rtcpu_vinotify_event: tstamp:5089865227 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:5089612567 data:0x00000001
kworker/1:0-18 [001] .... 150.779705: rtcpu_vinotify_error: tstamp:5090189332 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:5090188676 data:0x000005a9
kworker/1:0-18 [001] .... 150.779706: rtcpu_vinotify_event: tstamp:5090491242 tag:FS channel:0x01 frame:2 vi_tstamp:5090187864 data:0x00000010
kworker/1:0-18 [001] .... 150.779708: rtcpu_vinotify_event: tstamp:5090491368 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:5090188676 data:0x000005a9
kworker/1:0-18 [001] .... 150.779709: rtcpu_vinotify_error: tstamp:5090883734 tag:CHANSEL_NOMATCH channel:0x41 frame:3 vi_tstamp:5090883081 data:0x000005a9
kworker/1:0-18 [001] .... 150.779711: rtcpu_vinotify_event: tstamp:5091117266 tag:FE channel:0x01 frame:2 vi_tstamp:5090858084 data:0x00000020
kworker/1:0-18 [001] .... 150.779712: rtcpu_vinotify_event: tstamp:5091117392 tag:FS channel:0x01 frame:3 vi_tstamp:5090882268 data:0x00000010
kworker/1:0-18 [001] .... 150.779713: rtcpu_vinotify_event: tstamp:5091117532 tag:CHANSEL_NOMATCH channel:0x41 frame:3 vi_tstamp:5090883081 data:0x000005a9
kworker/1:0-18 [001] .... 150.835683: rtcpu_vinotify_error: tstamp:5091578140 tag:CHANSEL_NOMATCH channel:0x41 frame:4 vi_tstamp:5091577485 data:0x000005a9
hello tagoshi,
umm…
let’s have a try to increase active_h to cover those blanking line and also dummy data.
for example,
Hi, JerryChang,
Thanks, I tried that, but the result didn’t change at all…
In addition to that, I adjusted “cil_settletime”, “pix_clk_hz”, “active_h”, and “line_length”, but it had also No effect to CSI log.
Is there any clue I can get from other part of CSI log?
I would like to narrow down the cause of CHANSEL_NOMATCH.
kworker/1:0-18 [001] .... 150.559765: rtos_queue_send_from_isr_failed: tstamp:5084295848 queue:0x0bcbaaa0
kworker/1:0-18 [001] .... 150.559767: rtcpu_nvcsi_intr: tstamp:5084298304 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000001
kworker/1:0-18 [001] .... 150.559768: rtcpu_vinotify_event: tstamp:5084544158 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:3782517344 data:0x10000000
please refer to a note from GMSL user guide.
“Video pipes generate frame start (FS) and frame end (FE) short packets when streaming video. If two video pipes are carrying two different datatypes (i.e image frames + embedded lines) from the same image, only one of the FS/FE pairs is needed. Generating the extra FS/FE pair without mapping will result in a line buffer overflow.”
hence…
you may review the Ser/Des programming.
Thanks, I’ll review it again and refer to GMSL guide.
And just for debugging, I tried to slow down MIPI clock from SerDes, then I got new PHY_INTR0 message.
Could you tell me what “status:0x00000088 and status:0x00000089” mean?
Is it the same error mentioned in below link?
kworker/0:0-8366 [000] .... 422.878447: rtcpu_nvcsi_intr: tstamp:13548277382 class:GLOBAL type:PHY_INTR0 phy:0 cil:0 st:0 vc:0 status:0x00000089
kworker/0:0-8366 [000] .... 422.878448: rtcpu_nvcsi_intr: tstamp:13548277382 class:GLOBAL type:PHY_INTR0 phy:0 cil:1 st:0 vc:0 status:0x00000088
kworker/0:0-8366 [000] .... 422.934365: rtcpu_vinotify_event: tstamp:13548496298 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:12637826592 data:0x10000000
kworker/0:0-8366 [000] .... 422.934368: rtcpu_vinotify_event: tstamp:13548496442 tag:RESERVED_18 channel:0x23 frame:0 vi_tstamp:12637830368 data:0x31000001
kworker/0:0-8366 [000] .... 422.934369: rtcpu_vinotify_event: tstamp:13548496587 tag:RESERVED_19 channel:0x23 frame:0 vi_tstamp:12637831360 data:0x07020001
kworker/0:0-8366 [000] .... 422.990354: rtcpu_vinotify_error: tstamp:13550204445 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:13550203775 data:0x00000001
kworker/0:0-8366 [000] .... 422.990356: rtcpu_vinotify_event: tstamp:13550374335 tag:CSIMUX_STREAM channel:0x00 frame:1 vi_tstamp:13550203775 data:0x00000001
kworker/0:0-8366 [000] .... 422.990357: rtcpu_vinotify_error: tstamp:13550744663 tag:CHANSEL_NOMATCH channel:0x41 frame:2 vi_tstamp:13550744007 data:0x000005a9
hello tagoshi,
you may download Xavier TRM for checking PHY interrupt messages.
for example,
please looking for [7.2.1.4.8 NVCSI PHY Registers] session for the NVCSI_PHY_0_CILA_INTR_0_STATUS_CILA_0 register.
for example, PHY_INTR0 = 0x89
bit-0, it shows there’s LP sequence error detected on clock lane [A/B];
bit-3 and bit-7 indicate LP sequence error detected on data lane [A/B].
Hi, JerryChang,
I found that virtual channel ID of data stream was incorrect.
In DT, I set vc-id is 0 as following, but actual VC of MIPI data was set as 1.
port@0 {
reg = <0>;
status = "okay";
liimxXXX_vi_in0: endpoint {
vc-id = <0>;
port-index = <0>;
bus-width = <4>;
status = "okay";
remote-endpoint = <&liimxXXX_csi_out0>;
};
};
After fixed VC of MIPI data to 0, CHANSEL_NOMATCH error was resolved and could get RAW14 data from video I/F !!
I’m so grateful for your patient support.
1 Like
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.