hello richardcusolito1,
it looks there’s no validate frame packets recognize by VI engine,
please double check your sensor driver, or, please arrange hardware resources to probe the MIPI signaling if that’s possible.
FYI,
let me give you an example of VI tracing logs with a success image capture.
here must be one pair of CHANSEL_PXL_SOF/CHANSEL_PXL_EOF to indicate a frame has detected by VI engine.
afterwards, it’s ATOMP_FRAME_DONE to indicate it’s complete writing a frame to memory.
for instance,
rtcpu_vinotify_event: tstamp:4058867917 cch:-1 vi:0 tag:CSIMUX_STREAM channel:0x00 frame:0 vi_tstamp:129874754944 data:0x0000000000000001
rtcpu_vinotify_event: tstamp:4059206674 cch:0 vi:0 tag:ATOMP_FS channel:0x00 frame:1 vi_tstamp:129891804896 data:0x0000000800000000
rtcpu_vinotify_event: tstamp:4059206818 cch:0 vi:0 tag:CHANSEL_PXL_SOF channel:0x23 frame:1 vi_tstamp:129891808928 data:0x0000000000000001
rtcpu_vinotify_event: tstamp:4059206976 cch:0 vi:0 tag:VIFALC_ACTIONLST channel:0x23 frame:1 vi_tstamp:129891815424 data:0x0000000008020001
rtcpu_vinotify_error: tstamp:4060164160 cch:0 vi:0 tag:CSIMUX_FRAME channel:0x00 frame:1 vi_tstamp:129925171392 data:0x00000000000000a0
rtcpu_vinotify_event: tstamp:4060166846 cch:0 vi:0 tag:CHANSEL_PXL_EOF channel:0x23 frame:1 vi_tstamp:129923836800 data:0x0000000004370002
rtcpu_vinotify_event: tstamp:4060167015 cch:0 vi:0 tag:ATOMP_FRAME_DONE channel:0x23 frame:1 vi_tstamp:129923837312 data:0x0000000000000000
Thank you for the info of what that correct trace should look like.
I have attached the probe of the data line. I included one of the differential signals in case I had any additional interference.
The red waveform is the differential as you probably assumed.
Please try other scope with enough bandwidth. Your waveform looks not correct.
Here is a zoomed in version of the differential signal.
After increasing the bandwidth the probes here is the previous screenshot
Is this another scope? It does not show details of waveform. You can check the signals by yourself based on the MIPI specification. That would be more efficient.
This is the highest bandwidth scope I have (200 MHz @ 1 GS/s). Unfortunately I don’t have access to the MIPI specification.
Is there another way you could help me diagnose the issue?
200 MHz @ 1 GS/s is not enough for MIPI signal test. You need to find another scope with bandwidth no less than 4GHz for test.
I was able to get a hold of a 4 GHz scope. Please let me know if there are any improvements I need to make to the waveform so you can help.
What is this waveform? Can you check that first by yourself based on mipi spec?
It is a zoomed in waveform of the photos previously sent.
I don’t have access to the MIPI specification otherwise I would have tried to validate the waveform.
Trumany
January 10, 2025, 3:35am
36
The waveform looks not good. MIPI spec is necessary for the design, please do check base on that or some related tests setting of scope.
jbzp00y
February 17, 2025, 8:50am
38
Hi @richardcusolito1 ,
I have some issues to implement OAH0428 with OV6946. Registers are not the same as OV426.
Can you share you oah0428_mode_tbls.h too ?
Thank you,
system
Closed
March 3, 2025, 8:50am
39
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.