Camera Sensor - TC358743 - erreur timeout - frame start syncpt timeout!0

Hello support,

I allow myself to contact you because I encounter an integration problem with TC358743 bridge (bridge device that converts HDMI stream to MIPI CSI-2 TX).

Before contacting you, I took care to check my “integration” as you describe in the documentation (Tegra Linux Driver Package Development Guide/camera_dev.html).

I encounter the following error: (from vi2_fops.c)

[   65.086547] video4linux video0: frame start syncpt timeout!0
[   65.092881] video4linux video0: TEGRA_VI_CSI_ERROR_STATUS 0x00000000
  • Driver integration

My kernel: 4.9.253-tegra (branch l4t-r32.7.1)

According to documentation, I added in drivers/media/i2c/tc358743:

/* frame format */
static const struct camera_common_frmfmt tc358743_frmfmt[] = {
	{{1280,  720}, tc358743_30_60fps, 3, 0, tc358743_MODE_1280X720},
	{{1920, 1080}, tc358743_30_60fps, 3, 0, tc358743_MODE_1920X1080},

and I use:

sd->entity.ops = &tc358743_media_ops;
state->pad.flags = MEDIA_PAD_FL_SOURCE;
err = tegra_media_entity_init(&sd->entity, 1, &state->pad, true, true);
if (err < 0)
  goto err_hdl;


And I looked at your examples, such as:
kernel/nvdia/drivers/media/{imx185.c, imx185_v1.c or tc358840.c}

My dtsi file (tegra210-tc358743.dtsi (4.6 KB))
was added in tegra210-p3448-0000-p3449-0000-b00.dts:

#include "tegra210-porg-p3448-common.dtsi"
//#include "porg-platforms/tegra210-porg-camera-rbpcv3-dual-imx477.dtsi"
//#include "porg-platforms/tegra210-porg-camera-rbpcv2-dual-imx219.dtsi"
#include "porg-platforms/tegra210-porg-pinmux-p3448-0000-b00.dtsi"
#include "porg-platforms/tegra210-porg-gpio-p3448-0000-b00.dtsi"
#include "porg-platforms/tegra210-porg-p3448-emc-a00.dtsi"
#include "tegra210-tc358743.dtsi"
  • Test environment:

For testing, I used a Jetson Nanodev kit and a TC358743 kit before switching to my hardware soon.

The geekworm’s card is functional with a PI3 but no with a Nano.

Here are some elements to help you understand the problem:

media-ctl -p -d /dev/media0
Media controller API version 0.1.0

Media device information
driver          vi
model           NVIDIA Tegra Video Input Device
bus info        
hw revision     0x3
driver version  0.0.0

Device topology
- entity 1: nvcsi--1 (2 pads, 2 links)
            type V4L2 subdev subtype Unknown flags 0
            device node name /dev/v4l-subdev0
        pad0: Sink
                <- "tc358743 6-000f":0 [ENABLED]
        pad1: Source
                -> "vi-output, tc358743 6-000f":0 [ENABLED]

- entity 4: tc358743 6-000f (1 pad, 1 link)
            type V4L2 subdev subtype Sensor flags 0
            device node name /dev/v4l-subdev1
        pad0: Source
                [fmt:UYVY8_1X16/1920x1080 field:none colorspace:smpte170m]
                [dv.caps:BT.656/1120 min:1x1@0 max:10000x10000@165000000 stds:CEA-861,DMT,CVT,GTF caps:progressive,reduced-blanking,custom]
                [dv.detect:BT.656/1120 1920x1080p60 (2200x1125) stds: flags:]
                [dv.current:BT.656/1120 1920x1080p60 (2200x1125) stds: flags:]
                -> "nvcsi--1":0 [ENABLED]

- entity 6: vi-output, tc358743 6-000f (1 pad, 1 link)
            type Node subtype V4L flags 0
            device node name /dev/video0
        pad0: Sink
                <- "nvcsi--1":1 [ENABLED]
v4l2-ctl --list-devices
vi-output, tc358743 6-000f (
v4l2-ctl --device=/dev/video0 --list-ctrls 

User Controls

            audio_sampling_rate 0x00981980 (int)    : min=0 max=768000 step=1 default=0 value=44100 flags=read-only
                  audio_present 0x00981981 (bool)   : default=0 value=0 flags=read-only

Camera Controls

                    bypass_mode 0x009a2064 (intmenu): min=0 max=1 default=0 value=0
                override_enable 0x009a2065 (intmenu): min=0 max=1 default=0 value=0
                   height_align 0x009a2066 (int)    : min=1 max=16 step=1 default=1 value=1
                     size_align 0x009a2067 (intmenu): min=0 max=2 default=0 value=0
               write_isp_format 0x009a2068 (bool)   : default=0 value=0
       sensor_signal_properties 0x009a2069 (u32)    : min=0 max=4294967295 step=1 default=0 [30][18] flags=read-only, has-payload
        sensor_image_properties 0x009a206a (u32)    : min=0 max=4294967295 step=1 default=0 [30][16] flags=read-only, has-payload
      sensor_control_properties 0x009a206b (u32)    : min=0 max=4294967295 step=1 default=0 [30][36] flags=read-only, has-payload
              sensor_dv_timings 0x009a206c (u32)    : min=0 max=4294967295 step=1 default=0 [30][16] flags=read-only, has-payload
               low_latency_mode 0x009a206d (bool)   : default=0 value=0
               preferred_stride 0x009a206e (int)    : min=0 max=65535 step=1 default=0 value=0
                   sensor_modes 0x009a2082 (int)    : min=0 max=30 step=1 default=30 value=30 flags=read-only

Digital Video Controls

                  power_present 0x00a00964 (bitmask): max=0x00000001 default=0x00000000 value=0x00000001 flags=read-only
v4l2-ctl --info
Driver Info (not using libv4l2):
        Driver name   : tegra-video
        Card type     : vi-output, tc358743 6-000f
        Bus info      :
        Driver version: 4.9.253
        Capabilities  : 0x84200001
                Video Capture
                Extended Pix Format
                Device Capabilities
        Device Caps   : 0x04200001
                Video Capture
                Extended Pix Format
v4l2-ctl --query-dv-timings
        Active width: 1920
        Active height: 1080
        Total width: 2200
        Total height: 1125
        Frame format: progressive
        Polarities: -vsync -hsync
        Pixelclock: 148500000 Hz (60.00 frames per second)
        Horizontal frontporch: 0
        Horizontal sync: 280
        Horizontal backporch: 0
        Vertical frontporch: 0
        Vertical sync: 45
        Vertical backporch: 0
v4l2-ctl --device /dev/video0 --stream-mmap --set-fmt-video=width=1920,height=1080,pixelformat=UYVY --stream-to=frame.raw --stream-count=1
[ 2721.846246] video4linux video0: frame start syncpt timeout!0
[ 2721.852582] video4linux video0: TEGRA_VI_CSI_ERROR_STATUS 0x00000000
[ 2722.062229] video4linux video0: frame start syncpt timeout!0
[ 2722.068625] video4linux video0: TEGRA_VI_CSI_ERROR_STATUS 0x00000000

Thank you in advance,
Best regards,

I have something new. I managed to capture an image by changing the “timing” settings.

The image is still not of good quality. I will continue to work on these settings.

hello s.pastor,

what does it means, could you please attach the image for reference,
are you still seeing syncpt timeout failures with abnormal image captures?

Hi support,

I get a good quality video (test.ts (1.2 MB)) by changing the CSI tx timings.

In my tegra210-tc358743.dtsi, I configure the link-frequencies parameter to:

link-frequencies = /bits/ 64 <594000000> → bps per lane: 1188000000 bps

Only with this value, I am in an unknown configuration!
(only 1 configuration is known in the kernel mainline sources, 2 with rpi-5.17.y):

 * The CSI bps per lane must be between 62.5 Mbps and 1 Gbps.
 * The default is 594 Mbps for 4-lane 1080p60 or 2-lane 720p60.
bps_pr_lane = 2 * endpoint->link_frequencies[0];
if (bps_pr_lane < 62500000U || bps_pr_lane > 1188000000U) {
	dev_err(dev, "unsupported bps per lane: %u bps\n", bps_pr_lane);
	goto disable_clk;
if (bps_pr_lane != 594000000U)
		dev_warn(dev, "untested bps per lane: %u bps\n", bps_pr_lane);

It is therefore necessary to update the CSI tx timings:

// 1188000000 bps configuration
state->pdata.pll_fbd        = 176;
state->pdata.lineinitcnt    = 0x1d01;
state->pdata.lptxtimecnt    = 0x008;
state->pdata.tclk_headercnt = 0x2D06;
state->pdata.tclk_trailcnt  = 0x09;
state->pdata.ths_headercnt  = 0xd06;
state->pdata.twakeup        = 0x4883;
state->pdata.tclk_postcnt   = 0x010;
state->pdata.ths_trailcnt   = 0xA;
state->pdata.hstxvregcnt    = 0x5;

I found these values on another post.
But in this post, we end up not knowing what config works (Commented code, #ifdef 0, hardcoded values, etc.).


With the default configuration (bps per lane: 594000000 bps) it is not possible to get an image, I always encountered the following error:

[   33.013202] vi tegra_channel_error_status:error 4000 frame 0
[  233.033183] vi tegra_channel_error_status:error 4000 frame 1
[  233.053218] vi tegra_channel_error_status:error 4000 frame 2
[  233.073247] vi tegra_channel_error_status:error 4000 frame 3
[  233.093233] vi tegra_channel_error_status:error 4000 frame 4
[  233.113408] vi tegra_channel_error_status:error 4000 frame 5

tegra_csi_error: TEGRA_CSI_PIXEL_PARSER_STATUS => 0x4015

It is very difficult to understand these error codes, they are referenced nowhere.
In some posts that I have read, it is even advised with this error code to check the integrity of the CSI signals.
What I have done.

To properly configure these settings, one would need to use the spreadsheet referenced in the sources:

REF_02 - Toshiba, TC358743XBG_HDMI-CSI_Tv11p_nm.xls

This spreadsheet cannot be found on the internet.


I would like to make or obtain a configuration with values that I will be recalculating or whose source is safe (Toshiba, NVIDIA ?).

I will also try to get support from my distributor.

I would like to provide the community with a “clean driver” (Documented values and the process to find them).

Best regards,

hello s.pastor,

may I know which Jetpack release you’re working with?
could you please try to boost the system performance to repo the failure, please check Supported Modes and Power Efficiency for reference,

Hello Jerry,

I used the SDK manager (v1.7.3.9053) to install my linux image on my Nano dev kit (JetPack_4.6.1_Linux_JETSON_NANO_TARGETS).
Today I am working with l4t-r32.7.1 branch of NVIDIA git repositories.

I will look to boost the performance as you request and I will keep you informed.

Best regards,

Originally, I had the problem on my Yocto.
To get in touch with you, I preferred to put myself in a configuration that you know


Compared to the reference image installed by the SDK, I only modified the Linux kernel and the dtb.

Hello Jerry,

By default, my power mode is 0.

/usr/sbin/nvpmodel -q
NVPM WARN: fan mode is not set!
NV Power Mode: MAXN

This is also confirm by GUI.

It looks like I was already in the highest performance mode.

Best regards,

hello s.pastor,

could you please refer to this see-also topic Topic 122615.
there’s github for sharing the workable driver and device tree for reference,

Hi Jerry

Yes thank you, I had already seen the topic.
I don’t know if you’ve tested it, not all configurations work.

It is thanks to this code that I found the right parameters.
I’m not a fan of unexplained values.

For your information:

I also tried the two configurations proposed (with or without RGB selection):

When I had activated the "RGB output selection" configuration,

#define TC358743_VOUT_RGB

I had the following error :

[   33.013202] vi tegra_channel_error_status:error 4000 frame 0
tegra_csi_error: TEGRA_CSI_PIXEL_PARSER_STATUS => 0x4015

Only the second configuration works (Without rgb) :

//#define TC358743_VOUT_RGB

Best regards,

Hi Jerry,

I tried with another camera (and not with the HDMI output of my PC) and it doesn’t work anymore.
I end up with the following error:

[  197.014080] vi TEGRA_CSI_PIXEL_PARSER_STATUS 0x00004001
[  197.020498] vi tegra_channel_error_status:error 4000 frame 0
[  197.034168] vi TEGRA_CSI_PIXEL_PARSER_STATUS 0x00004015
[  197.040827] vi tegra_channel_error_status:error 4000 frame 1
[  197.054034] vi TEGRA_CSI_PIXEL_PARSER_STATUS 0x00004015
[  197.060514] vi tegra_channel_error_status:error 4000 frame 2
[  197.074007] vi TEGRA_CSI_PIXEL_PARSER_STATUS 0x00004015
[  197.080723] vi tegra_channel_error_status:error 4000 frame 3
[  197.094077] vi TEGRA_CSI_PIXEL_PARSER_STATUS 0x00004015
[  197.100553] vi tegra_channel_error_status:error 4000 frame 4
[  197.114006] vi TEGRA_CSI_PIXEL_PARSER_STATUS 0x00004015

During the life of my product, there will be different types of cameras.
My electronics and my software must adapt to it.

The good news of the day is that I was able to get the spreadsheet (TC358743XBG_HDMI-CSI_Tv11p_nm.xls).

It’s quite complex to use, I’ll come back to you to keep you informed.

Best regards,

hello s.pastor,

please check Device Registration session,
it’s by default using Plugin Manager to register camera automatically and links devices when the system kernel boots.
please disable this if your camera module do not has on-board EEPROM.
furthermore, please looking for kernel logs, checking the VI related messages for more details.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.