DS90UB953-Q1: DS90UB953

what should be i2c voltage level for register 0x02? I2C_STRAP_MODE was 0 by default. I reprogrammed it to 1. camera capture didn't work in both cases.

Hi Shival,

Thanks for reaching out with this question. Based on my understanding this system consists of a UB960 (based on related thread) paired with UB953. For my understanding, is the concern here that the video is not passed through to the SOC downstream?

Based on the initial register dumps provided one concern from my side is the read back of 0x5E showing a number of errors in CSI data lane 0. It's possible that the serializer may not be receiving valid data on this lane.

Would it be possible for you to provide a complete register dump from the UB953 along with the applicable deserializer register dump for the port which is used here?

Best,

Thomas

Hi Thomas,

following is the dmesg log with ub960 and ub953 register settings.

[ 5.954408] ub960 2-0036: ub960 read u32 csi-lane-count
[ 5.958806] ub960 2-0036: ub960 read u32 csi-continuous-clock
[ 5.964571] ub960 2-0036: csi speed:1472-1664 lanes:1 continuous-clock:yes

[ 6.065103] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x5f
[ 6.065116] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x55
[ 6.065126] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x42
[ 6.065137] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x39
[ 6.065167] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x36
[ 6.065172] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x30
[ 6.065340] ub960 2-0036: UB960_PGEN_RESERVED REGISTER ADDRESS=0x00, VALUE=0X6C

[ 6.074344] ub960 2-0036: UB960_REG_CSI_PLL_CTL register address=0x1f, value=0x04
[ 6.206975] ub960 2-0036: UB960_REG_IO_CTL register address=0x0d, value=0x00
[ 6.207243] ub960 2-0036: UB960_REG_RX_PORT_CTL register address=0x0c, value=0x00
[ 6.207502] ub960 2-0036: UB960_REG_CSI_PORT_SEL register address=0x32, value=0x01
[ 6.207760] ub960 2-0036: UB960_REG_FWD_CTL1 register address=0x20, value=0x00
[ 6.208020] ub960 2-0036: UB960_REG_HIGH_LOW_TIME_1 register address=0x19, value=0x61
[ 6.208278] ub960 2-0036: UB960_REG_FS_HIGH_TIME_0 register address=0x1a, value=0xa8
[ 6.208536] ub960 2-0036: UB960_REG_FS_LOW_TIME_1 register address=0x1b, value=0xe3
[ 6.208796] ub960 2-0036: UB960_REG_FS_LOW_TIME_0 register address=0x1c, value=0xdd
[ 6.209053] ub960 2-0036: UB960_REG_FS_CTL register address=0x18, value=0x80

[ 6.209320] ub960 2-0036: UB960_REG_FPD3_PORT_SEL register address=0x4c, value=0x24
[ 6.209582] ub960 2-0036: UB960_REG_BCC_CONFIG reg. address=0x58, value=0x5e, for port=0x02
[ 6.210288] ub960 2-0036: UB960_REG_AEQ_CTL register address=0x42, value=0x71
[ 6.210437] ub960 2-0036: UB960_REG_SFILTER_CFG register address=0x41, value=0xa9
[ 6.210585] ub960 2-0036: UB960_REG_LINK_ERROR_CNT register address=0xb9, value=0x33
[ 6.210733] ub960 2-0036: UB960_REG_BC_GPIO_CTL0 register address=0x6e, value=0x10
[ 6.210736] ub960 2-0036: ub960 serializer and sensor. 18 4e 36 6e
[ 6.210994] ub960 2-0036: UB960_REG_FPD3_PORT_SEL register address=0x4c, value=0x24
[ 6.211252] ub960 2-0036: UB960_REG_CSI_PORT_SEL register address=0x32, value=0x01
[ 6.211509] ub960 2-0036: UB960_REG_CSI_CTL1 register address=0x33, value=0x72

[ 6.212931] ub960 2-0036: UB960_REG_PORT_CONFIG register address=0x6d, value=0x7c
[ 6.212934] ub960 2-0036: UB960_REG_CSI_VC_MAP channel id=0x02, value=0xaa
[ 6.213189] ub960 2-0036: UB960_REG_CSI_VC_MAP register address=0x72, value=0xaa
[ 6.213441] ub960 2-0036: UB960_REG_PORT_CONFIG2 register address=0x7c, value=0x00
[ 6.213713] ub960 2-0036: UB960_REG_AEQ_MIN_MAX register address=0xd5, value=0xf2
[ 6.214126] ub960 2-0036: UB960_REG_INTERRUPT_CTL register address=0x23, value=0x04
[ 6.214535] ub960 2-0036: UB960_REG_PORT_ICR_LO register address=0xd9, value=0x01
[ 6.214681] ub960 2-0036: UB960_REG_PORT_ICR_HI register address=0xd8, value=0x00
[ 6.215307] ub960 2-0036: UB960_REG_RX_PORT_CTL register address=0x0c, value=0x04

[ 7.241311] ub960 2-0036: ub960 device status register=04, value=d0
[ 7.241581] ub960 2-0036: ub960 device status register=02, value=1e
[ 7.241848] ub960 2-0036: ub960 device status register=03, value=40
[ 7.242115] ub960 2-0036: ub960 PAR_ERR_THOLD_HI register=05, value=01
[ 7.242385] ub960 2-0036: ub960 PAR_ERR_THOLD_LO register=06, value=00
[ 7.242654] ub960 2-0036: ub960 GPIO_PIN_STS register=0e, value=f0

[ 7.242915] ub960 2-0036: ub960 0x21 register=21, value=03
[ 7.243163] ub960 2-0036: ub960 0x22 register=22, value=00
[ 7.243411] ub960 2-0036: ub960 0x34 register=34, value=00
[ 7.243685] ub960 2-0036: ub960 0x35 register=35, value=00
[ 7.243955] ub960 2-0036: ub960 0x36 register=36, value=00
[ 7.244223] ub960 2-0036: ub960 0x37 register=37, value=10
[ 7.244482] ub960 2-0036: ub960 0x40 register=40, value=00
[ 7.244786] ub960 2-0036: ub960 0x43 register=43, value=01
[ 7.245473] ub960 2-0036: ub960 0x44 register=44, value=00
[ 7.251103] ub960 2-0036: ub960 0x45 register=45, value=00
[ 7.256446] ub960 2-0036: ub960 0x46 register=46, value=20
[ 7.261685] ub960 2-0036: ub960 0x47 register=47, value=00
[ 7.267286] ub960 2-0036: ub960 0x48 register=48, value=00
[ 7.272555] ub960 2-0036: ub960 0x49 register=49, value=00
[ 7.278310] ub960 2-0036: ub960 0x4f register=4f, value=64
[ 7.283591] ub960 2-0036: ub960 0x50 register=50, value=00
[ 7.289080] ub960 2-0036: ub960 0x51 register=51, value=00
[ 7.294584] ub960 2-0036: ub960 0x52 register=52, value=00
[ 7.300372] ub960 2-0036: ub960 0x53 register=53, value=02
[ 7.305624] ub960 2-0036: ub960 0x54 register=54, value=06
[ 7.311394] ub960 2-0036: ub960 0x55 register=55, value=00
[ 7.316626] ub960 2-0036: ub960 0x56 register=56, value=00
[ 7.322410] ub960 2-0036: ub960 0x57 register=57, value=00
[ 7.327909] ub960 2-0036: ub960 0x70 register=70, value=ab
[ 7.333188] ub960 2-0036: ub960 0x71 register=71, value=ac
[ 7.338684] ub960 2-0036: ub960 0x73 register=73, value=00
[ 7.344466] ub960 2-0036: ub960 0x74 register=74, value=05
[ 7.349960] ub960 2-0036: ub960 0x75 register=75, value=86
[ 7.355496] ub960 2-0036: ub960 0x76 register=76, value=22
[ 7.360727] ub960 2-0036: ub960 0x7b register=7b, value=c1
[ 7.366512] ub960 2-0036: ub960 0xd2 register=d2, value=94
[ 7.372021] ub960 2-0036: ub960 0xd3 register=d3, value=02
[ 7.377548] ub960 2-0036: ub960 0xd4 register=d4, value=60
[ 7.382779] ub960 2-0036: ub960 0xd5 register=d5, value=f2
[ 7.388568] ub960 2-0036: ub960 0xd6 register=d6, value=00
[ 7.393799] ub960 2-0036: ub960 0xd7 register=d7, value=02
[ 7.399328] ub960 2-0036: ub960 0xda register=da, value=00
[ 7.404825] ub960 2-0036: ub960 0xdb register=db, value=6b
[ 7.410619] ub960 2-0036: ub960 GPIO_INPUT_CTL register=0f, value=ff
[ 7.417163] ub960 2-0036: ub960 GPIO0_PIN_CTL register=10, value=00
[ 7.423482] ub960 2-0036: ub960 GPIO0_PIN_CTL register=10, value=00
[ 7.430288] ub960 2-0036: ub960 INTERRUPT STATUS register=24, value=84
[ 7.436714] ub960 2-0036: ub960 HANDLE PORT 2
[ 7.441420] ub960 2-0036: UB960_REG_FPD3_PORT_SEL register address=0x4c, value=0x24
[ 7.449494] ub960 2-0036: ub960 RX_PORT_STS1: 4d, value=0x93,port=0x02
[ 7.455612] ub960 2-0036: ub960 RX_PORT_STS2: 4e, value=0xcd, port=0x02
[ 7.462448] ub960 2-0036: ub960 CSI_RX_STS: 7a, value=0x0f, port=0x02


[ 7.724982] ub960 2-0036: UB960_REG_FPD3_PORT_SEL register address=0x4c, value=0x24
[ 7.725566] ub960 2-0036: ub960 RX_PORT_STS1: 4d, value=0x83,port=0x02
[ 7.725684] ub960 2-0036: ub960 RX_PORT_STS2: 4e, value=0x04, port=0x02
[ 7.725809] ub960 2-0036: ub960 CSI_RX_STS: 7a, value=0x00, port=0x02
[ 7.725917] ub960 2-0036: ub960 CHECK LOCK: locked=1, port->locked=0

[ 7.727453] ub953 2-004e: ub953 register 0x02 =02, value=43
[ 7.727717] ub953 2-004e: ub953 register 0x03=03, value=48
[ 7.727967] ub953 2-004e: ub953 register 0x04=04, value=00
[ 7.729431] ub953 2-004e: ub953 register 0x05=05, value=03
[ 7.734873] ub953 2-004e: ub953 register 0x06=06, value=41
[ 7.740104] ub953 2-004e: ub953 register 0x07=07, value=28
[ 7.745719] ub953 2-004e: ub953 register 0x32=32, value=09
[ 7.751031] ub953 2-004e: ub953 register 0x50=50, value=20
[ 7.756552] ub953 2-004e: ub953 register 0x51=51, value=c0
[ 7.762044] ub953 2-004e: ub953 register 0x52=52, value=65
[ 7.767395] ub953 2-004e: ub953 register 0x55=55, value=00
[ 7.772736] ub953 2-004e: ub953 register 0x56=56, value=00
[ 7.778168] ub953 2-004e: ub953 register 0x5b=5b, value=02
[ 7.783568] ub953 2-004e: ub953 register 0x5c=5c, value=ff
[ 7.788918] ub953 2-004e: ub953 register 0x5d=5d, value=0f
[ 7.794159] ub953 2-004e: ub953 register 0x5e=5e, value=0c
[ 7.799944] ub953 2-004e: ub953 register 0x5f=5f, value=00
[ 7.805440] ub953 2-004e: ub953 register 0x60=60, value=00
[ 7.810987] ub953 2-004e: ub953 register 0x61=61, value=ff
[ 7.816334] ub953 2-004e: Waiting for data vc... (VC=3, Data ID=3f)
[ 7.822555] ub953 2-004e: ub953 register 0x62=62, value=09
[ 7.828292] ub953 2-004e: ub953 register 0x63=63, value=00
[ 7.833800] ub953 2-004e: ub953 register 0x64=64, value=80

[ 7.863578] ub953 2-004e: Setting logical output of GPIO's: 0x1
[ 7.869744] ub953 2-004e: enabling input and output of GPIO's: 0xf0
[ 7.896676] ub953 2-004e: probe success
[ 7.900864] ub960 2-0036: UB960_REG_CSI_CTL1 reg. address=0x33, value=0x73
[ 7.907682] ub960 2-0036: probe success
tonbo@ubuntu:~/d3-jetson-bsp$

not getting any video data from v4l2 device /dev/video0 which is created after successful probe.   this is the error I am getting when capturing from /dev/video0

tegra194-vi5 15c10000.vi: uncorr_err: request timed out after 2500 ms
tegra194-vi5 15c10000.vi: err_rec: attempting to reset the capture channel
t194-nvcsi 15a00000.nvcsi: PH_CHK_CTRL = 0
t194-nvcsi 15a00000.nvcsi: PH_CHK_CTRL = 0
tegra194-vi5 15c10000.vi: err_rec: successfully reset the capture channel

please let me know any specific registers information you want for ub953. i am only printing following registers values.

[ 7.727453] ub953 2-004e: ub953 register 0x02 =02, value=43
[ 7.727717] ub953 2-004e: ub953 register 0x03=03, value=48
[ 7.727967] ub953 2-004e: ub953 register 0x04=04, value=00
[ 7.729431] ub953 2-004e: ub953 register 0x05=05, value=03
[ 7.734873] ub953 2-004e: ub953 register 0x06=06, value=41
[ 7.740104] ub953 2-004e: ub953 register 0x07=07, value=28
[ 7.745719] ub953 2-004e: ub953 register 0x32=32, value=09
[ 7.751031] ub953 2-004e: ub953 register 0x50=50, value=20
[ 7.756552] ub953 2-004e: ub953 register 0x51=51, value=c0
[ 7.762044] ub953 2-004e: ub953 register 0x52=52, value=65
[ 7.767395] ub953 2-004e: ub953 register 0x55=55, value=00
[ 7.772736] ub953 2-004e: ub953 register 0x56=56, value=00
[ 7.778168] ub953 2-004e: ub953 register 0x5b=5b, value=02
[ 7.783568] ub953 2-004e: ub953 register 0x5c=5c, value=ff
[ 7.788918] ub953 2-004e: ub953 register 0x5d=5d, value=0f
[ 7.794159] ub953 2-004e: ub953 register 0x5e=5e, value=0c
[ 7.799944] ub953 2-004e: ub953 register 0x5f=5f, value=00
[ 7.805440] ub953 2-004e: ub953 register 0x60=60, value=00
[ 7.810987] ub953 2-004e: ub953 register 0x61=61, value=ff
[ 7.816334] ub953 2-004e: Waiting for data vc... (VC=3, Data ID=3f)
[ 7.822555] ub953 2-004e: ub953 register 0x62=62, value=09
[ 7.828292] ub953 2-004e: ub953 register 0x63=63, value=00
[ 7.833800] ub953 2-004e: ub953 register 0x64=64, value=80

when I was able to capture video from sensor successfully following were registers settings for ub953. let me know what could have possibly changed.

ub953 2-004d: ub953 register 0x02 =02, value=33
[ 6.693355] ub953 2-004d: ub953 register 0x03=03, value=48
[ 6.693507] ub953 2-004d: ub953 register 0x04=04, value=00
[ 6.693662] ub953 2-004d: ub953 register 0x05=05, value=03
[ 6.693817] ub953 2-004d: ub953 register 0x06=06, value=41
[ 6.693971] ub953 2-004d: ub953 register 0x07=07, value=28
[ 6.694125] ub953 2-004d: ub953 register 0x32=32, value=09
[ 6.694279] ub953 2-004d: ub953 register 0x50=50, value=20
[ 6.694433] ub953 2-004d: ub953 register 0x51=51, value=c0
[ 6.694587] ub953 2-004d: ub953 register 0x52=52, value=65
[ 6.694742] ub953 2-004d: ub953 register 0x55=55, value=00
[ 6.694897] ub953 2-004d: ub953 register 0x56=56, value=00
[ 6.695053] ub953 2-004d: ub953 register 0x5b=5b, value=00
[ 6.695206] ub953 2-004d: ub953 register 0x5c=5c, value=ff
[ 6.695360] ub953 2-004d: ub953 register 0x5d=5d, value=00
[ 6.695514] ub953 2-004d: ub953 register 0x5e=5e, value=04
[ 6.695669] ub953 2-004d: ub953 register 0x5f=5f, value=00
[ 6.695821] ub953 2-004d: ub953 register 0x60=60, value=00
[ 6.695976] ub953 2-004d: ub953 register 0x61=61, value=00
[ 6.695979] ub953 2-004d: Waiting for data vc... (VC=0, Data ID=0)
[ 6.696131] ub953 2-004d: ub953 register 0x62=62, value=00
[ 6.696284] ub953 2-004d: ub953 register 0x63=63, value=00
[ 6.696448] ub953 2-004d: ub953 register 0x64=64, value=00
[ 6.696566] ub953 2-004d: ub960 reset 3

Hi Shivlal,

In the UB953 register dumps provided, there was a change in register 0x02 from 0x02=0x33 to 0x02=0x43. With 0x02=0x43, the serializer is set to one lane of incoming CSI data in continuous mode. The original setting was with 3-lane CSI data in non-continuous mode. Would you be able to confirm if this change is intended? 

Best,

Zoe

its one lane sensor. I don't know how it worked with register value 0x02=0x33 earlier. I guess value 0x33 means 4 lane sensor?

Hi Shivlal, 

Is the one lane sensor in non-continuous CSI clock mode? If so, register 0x02 should be set to 0x03. The change was in CSI clock mode setting and lane configuration. 

Best,

Zoe

not working. tried both continuous and non continuous mode. I see register value for 0x5e is 0x0c which is a problem. it was 0x00 when video was coming. what could be the reason? using same configuration and setup. 

also register value for 0x60 is 0x02 occasionally? it means a clk lane error? why is that? 

Hi Shivlal, 

Thanks for the update. Would you be able to confirm the configuration of the sensor being used in this case? Register 0x5E and 0x60 denote errors detected on the CSI input of the UB953. One potential cause is due to incorrect configurations in register 0x02. 

Best,

Zoe

tried all combinations and permutations of values for register 0x02. i.e 4 lane, 1 lane, continuous and non continuous mode but 0x5e value always remains same(0x0c). any possible reason?

Hi Shivlal,

From your previous response, it seemed setting register 0x02=0x33 would have the data received and output by the UB960 in the system? Are there any errors present in this configuration? Would you be able to share the sensor configuration - CSI lane speed, clock setting? Additionally, how was each setting tested? Was the register reconfigured while video data was active with no power cycle to the serializer? 

Best,

Zoe

setting ub953 register 0x02  to any value have no effect. register 0x5e value is always 0x0c. is it a sensor problem? is there any specific register needs to be configured for ub953? how do I probe it? which registers to look at to confirm valid data from sensor?

yes I am reconfiguring 0x02 when ub953 in being initialized. correct value should be 0x43. one lane, synchronous mode, 1.8v i2c voltage. default value is not 0x43 for register 0x02. what is correct way to reconfigure it?  

Hi Shivlal,

Thanks for confirming the use case here. Taking a look at the logs it appears that the issue is video data is being transmitted as the UB960 has 

shivlal dhundhwal said:

[ 7.896676] ub953 2-004e: probe success
[ 7.900864] ub960 2-0036: UB960_REG_CSI_CTL1 reg. address=0x33, value=0x73
[ 7.907682] ub960 2-0036: probe success

Referring to the logs it appears that the CSI forwarding initialization sequence is not being followed. Enabling forwarding in register 0x20 should be the final step in configuring forwarding. The recommended sequencing for enabling CSI forwarding is as follows: 

1. Disable forwarding in FWD_CTL1 (Register 0x20)
2. Configure CSI port settings 
3. Enable CSI forwarding in CSI_CTL (Register 0x33)
4. Enable forwarding in FWD_CTL1 (Register 0x20)

Has pattern generator from the UB960 been tested in this configuration?

shivlal dhundhwal said:

is it a sensor problem? is there any specific register needs to be configured for ub953? how do I probe it? which registers to look at to confirm valid data from sensor?

To check for data being transmitted from the sensor, port pass can be read from 0x35[0] on the UB960. When PORT_PASS is set to 1, video data is available on the UB960 CSI output. Registers 0x73-0x76 will show the line count and line length of the video data received on that port. Would you be able to confirm what the value of register 0x35 is? 

shivlal dhundhwal said:

what is correct way to reconfigure it?  

The best way to reconfigure register 0x02 is to reconfigure prior to video data being input on the serializer. 

Would you be able to provide a complete register dump of the 935 and 960? The current dumps do not contain all the registers. 

Best,

Zoe

register 0x35 value is 0 for ub960. also register 0x73 to 0x76 dumps random incorrect values.  I have modified driver code to execute UB960_REG_CSI_CTL1 and FWD_CTL1 in the same order that you suggested but no change. everything was working one month back with same driver code and settings.

please let me know how do I debug sensor  on serializer side? 

I have register dump for following ub960 and ub953 registers. if you want me to print any specific registers please let me know.

[ 5.954408] ub960 2-0036: ub960 read u32 csi-lane-count
[ 5.958806] ub960 2-0036: ub960 read u32 csi-continuous-clock
[ 5.964571] ub960 2-0036: csi speed:1472-1664 lanes:1 continuous-clock:yes

[ 6.065103] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x5f
[ 6.065116] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x55
[ 6.065126] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x42
[ 6.065137] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x39
[ 6.065167] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x36
[ 6.065172] ub960 2-0036: UB960_REG_FPD3_RX_ID0 register address=0xf0, value=0x30
[ 6.065340] ub960 2-0036: UB960_PGEN_RESERVED REGISTER ADDRESS=0x00, VALUE=0X6C

[ 6.074344] ub960 2-0036: UB960_REG_CSI_PLL_CTL register address=0x1f, value=0x04
[ 6.206975] ub960 2-0036: UB960_REG_IO_CTL register address=0x0d, value=0x00
[ 6.207243] ub960 2-0036: UB960_REG_RX_PORT_CTL register address=0x0c, value=0x00
[ 6.207502] ub960 2-0036: UB960_REG_CSI_PORT_SEL register address=0x32, value=0x01
[ 6.207760] ub960 2-0036: UB960_REG_FWD_CTL1 register address=0x20, value=0x00
[ 6.208020] ub960 2-0036: UB960_REG_HIGH_LOW_TIME_1 register address=0x19, value=0x61
[ 6.208278] ub960 2-0036: UB960_REG_FS_HIGH_TIME_0 register address=0x1a, value=0xa8
[ 6.208536] ub960 2-0036: UB960_REG_FS_LOW_TIME_1 register address=0x1b, value=0xe3
[ 6.208796] ub960 2-0036: UB960_REG_FS_LOW_TIME_0 register address=0x1c, value=0xdd
[ 6.209053] ub960 2-0036: UB960_REG_FS_CTL register address=0x18, value=0x80

[ 6.209320] ub960 2-0036: UB960_REG_FPD3_PORT_SEL register address=0x4c, value=0x24
[ 6.209582] ub960 2-0036: UB960_REG_BCC_CONFIG reg. address=0x58, value=0x5e, for port=0x02
[ 6.210288] ub960 2-0036: UB960_REG_AEQ_CTL register address=0x42, value=0x71
[ 6.210437] ub960 2-0036: UB960_REG_SFILTER_CFG register address=0x41, value=0xa9
[ 6.210585] ub960 2-0036: UB960_REG_LINK_ERROR_CNT register address=0xb9, value=0x33
[ 6.210733] ub960 2-0036: UB960_REG_BC_GPIO_CTL0 register address=0x6e, value=0x10
[ 6.210736] ub960 2-0036: ub960 serializer and sensor. 18 4e 36 6e
[ 6.210994] ub960 2-0036: UB960_REG_FPD3_PORT_SEL register address=0x4c, value=0x24
[ 6.211252] ub960 2-0036: UB960_REG_CSI_PORT_SEL register address=0x32, value=0x01
[ 6.211509] ub960 2-0036: UB960_REG_CSI_CTL1 register address=0x33, value=0x72

[ 6.212931] ub960 2-0036: UB960_REG_PORT_CONFIG register address=0x6d, value=0x7c
[ 6.212934] ub960 2-0036: UB960_REG_CSI_VC_MAP channel id=0x02, value=0xaa
[ 6.213189] ub960 2-0036: UB960_REG_CSI_VC_MAP register address=0x72, value=0xaa
[ 6.213441] ub960 2-0036: UB960_REG_PORT_CONFIG2 register address=0x7c, value=0x00
[ 6.213713] ub960 2-0036: UB960_REG_AEQ_MIN_MAX register address=0xd5, value=0xf2
[ 6.214126] ub960 2-0036: UB960_REG_INTERRUPT_CTL register address=0x23, value=0x04
[ 6.214535] ub960 2-0036: UB960_REG_PORT_ICR_LO register address=0xd9, value=0x01
[ 6.214681] ub960 2-0036: UB960_REG_PORT_ICR_HI register address=0xd8, value=0x00
[ 6.215307] ub960 2-0036: UB960_REG_RX_PORT_CTL register address=0x0c, value=0x04

[ 7.241311] ub960 2-0036: ub960 device status register=04, value=d0
[ 7.241581] ub960 2-0036: ub960 device status register=02, value=1e
[ 7.241848] ub960 2-0036: ub960 device status register=03, value=40
[ 7.242115] ub960 2-0036: ub960 PAR_ERR_THOLD_HI register=05, value=01
[ 7.242385] ub960 2-0036: ub960 PAR_ERR_THOLD_LO register=06, value=00
[ 7.242654] ub960 2-0036: ub960 GPIO_PIN_STS register=0e, value=f0

[ 7.242915] ub960 2-0036: ub960 0x21 register=21, value=03
[ 7.243163] ub960 2-0036: ub960 0x22 register=22, value=00
[ 7.243411] ub960 2-0036: ub960 0x34 register=34, value=00
[ 7.243685] ub960 2-0036: ub960 0x35 register=35, value=00
[ 7.243955] ub960 2-0036: ub960 0x36 register=36, value=00
[ 7.244223] ub960 2-0036: ub960 0x37 register=37, value=10
[ 7.244482] ub960 2-0036: ub960 0x40 register=40, value=00
[ 7.244786] ub960 2-0036: ub960 0x43 register=43, value=01
[ 7.245473] ub960 2-0036: ub960 0x44 register=44, value=00
[ 7.251103] ub960 2-0036: ub960 0x45 register=45, value=00
[ 7.256446] ub960 2-0036: ub960 0x46 register=46, value=20
[ 7.261685] ub960 2-0036: ub960 0x47 register=47, value=00
[ 7.267286] ub960 2-0036: ub960 0x48 register=48, value=00
[ 7.272555] ub960 2-0036: ub960 0x49 register=49, value=00
[ 7.278310] ub960 2-0036: ub960 0x4f register=4f, value=64
[ 7.283591] ub960 2-0036: ub960 0x50 register=50, value=00
[ 7.289080] ub960 2-0036: ub960 0x51 register=51, value=00
[ 7.294584] ub960 2-0036: ub960 0x52 register=52, value=00
[ 7.300372] ub960 2-0036: ub960 0x53 register=53, value=02
[ 7.305624] ub960 2-0036: ub960 0x54 register=54, value=06
[ 7.311394] ub960 2-0036: ub960 0x55 register=55, value=00
[ 7.316626] ub960 2-0036: ub960 0x56 register=56, value=00
[ 7.322410] ub960 2-0036: ub960 0x57 register=57, value=00
[ 7.327909] ub960 2-0036: ub960 0x70 register=70, value=ab
[ 7.333188] ub960 2-0036: ub960 0x71 register=71, value=ac
[ 7.338684] ub960 2-0036: ub960 0x73 register=73, value=00
[ 7.344466] ub960 2-0036: ub960 0x74 register=74, value=05
[ 7.349960] ub960 2-0036: ub960 0x75 register=75, value=86
[ 7.355496] ub960 2-0036: ub960 0x76 register=76, value=22
[ 7.360727] ub960 2-0036: ub960 0x7b register=7b, value=c1
[ 7.366512] ub960 2-0036: ub960 0xd2 register=d2, value=94
[ 7.372021] ub960 2-0036: ub960 0xd3 register=d3, value=02
[ 7.377548] ub960 2-0036: ub960 0xd4 register=d4, value=60
[ 7.382779] ub960 2-0036: ub960 0xd5 register=d5, value=f2
[ 7.388568] ub960 2-0036: ub960 0xd6 register=d6, value=00
[ 7.393799] ub960 2-0036: ub960 0xd7 register=d7, value=02
[ 7.399328] ub960 2-0036: ub960 0xda register=da, value=00
[ 7.404825] ub960 2-0036: ub960 0xdb register=db, value=6b
[ 7.410619] ub960 2-0036: ub960 GPIO_INPUT_CTL register=0f, value=ff
[ 7.417163] ub960 2-0036: ub960 GPIO0_PIN_CTL register=10, value=00
[ 7.423482] ub960 2-0036: ub960 GPIO0_PIN_CTL register=10, value=00
[ 7.430288] ub960 2-0036: ub960 INTERRUPT STATUS register=24, value=84
[ 7.436714] ub960 2-0036: ub960 HANDLE PORT 2
[ 7.441420] ub960 2-0036: UB960_REG_FPD3_PORT_SEL register address=0x4c, value=0x24
[ 7.449494] ub960 2-0036: ub960 RX_PORT_STS1: 4d, value=0x93,port=0x02
[ 7.455612] ub960 2-0036: ub960 RX_PORT_STS2: 4e, value=0xcd, port=0x02
[ 7.462448] ub960 2-0036: ub960 CSI_RX_STS: 7a, value=0x0f, port=0x02


[ 7.724982] ub960 2-0036: UB960_REG_FPD3_PORT_SEL register address=0x4c, value=0x24
[ 7.725566] ub960 2-0036: ub960 RX_PORT_STS1: 4d, value=0x83,port=0x02
[ 7.725684] ub960 2-0036: ub960 RX_PORT_STS2: 4e, value=0x04, port=0x02
[ 7.725809] ub960 2-0036: ub960 CSI_RX_STS: 7a, value=0x00, port=0x02
[ 7.725917] ub960 2-0036: ub960 CHECK LOCK: locked=1, port->locked=0

[ 7.727453] ub953 2-004e: ub953 register 0x02 =02, value=43
[ 7.727717] ub953 2-004e: ub953 register 0x03=03, value=48
[ 7.727967] ub953 2-004e: ub953 register 0x04=04, value=00
[ 7.729431] ub953 2-004e: ub953 register 0x05=05, value=03
[ 7.734873] ub953 2-004e: ub953 register 0x06=06, value=41
[ 7.740104] ub953 2-004e: ub953 register 0x07=07, value=28
[ 7.745719] ub953 2-004e: ub953 register 0x32=32, value=09
[ 7.751031] ub953 2-004e: ub953 register 0x50=50, value=20
[ 7.756552] ub953 2-004e: ub953 register 0x51=51, value=c0
[ 7.762044] ub953 2-004e: ub953 register 0x52=52, value=65
[ 7.767395] ub953 2-004e: ub953 register 0x55=55, value=00
[ 7.772736] ub953 2-004e: ub953 register 0x56=56, value=00
[ 7.778168] ub953 2-004e: ub953 register 0x5b=5b, value=02
[ 7.783568] ub953 2-004e: ub953 register 0x5c=5c, value=ff
[ 7.788918] ub953 2-004e: ub953 register 0x5d=5d, value=0f
[ 7.794159] ub953 2-004e: ub953 register 0x5e=5e, value=0c
[ 7.799944] ub953 2-004e: ub953 register 0x5f=5f, value=00
[ 7.805440] ub953 2-004e: ub953 register 0x60=60, value=00
[ 7.810987] ub953 2-004e: ub953 register 0x61=61, value=ff
[ 7.816334] ub953 2-004e: Waiting for data vc... (VC=3, Data ID=3f)
[ 7.822555] ub953 2-004e: ub953 register 0x62=62, value=09
[ 7.828292] ub953 2-004e: ub953 register 0x63=63, value=00
[ 7.833800] ub953 2-004e: ub953 register 0x64=64, value=80

[ 7.863578] ub953 2-004e: Setting logical output of GPIO's: 0x1
[ 7.869744] ub953 2-004e: enabling input and output of GPIO's: 0xf0
[ 7.896676] ub953 2-004e: probe success
[ 7.900864] ub960 2-0036: UB960_REG_CSI_CTL1 reg. address=0x33, value=0x73
[ 7.907682] ub960 2-0036: probe success

when I was getting video from sensor. registers 0x35, 0x73...0x76 were all 0's for ub960.

Hi Shivlal, 

Register 0x73-0x76 are port specific registers, reading from the correct port should be selected to confirm these values. 

Would you be able to provide results for the following conditions: 

1. Pattern generator enabled from the 960 with forwarding enabled
2. Pattern generator enabled on the 953 with forwarding enabled on the 960

Best,

Zoe

I connected a 4 lane working sensor to same port. I am able to capture from it. also 0x73 to 0x76 are all 0 for this working sensor also. even after selecting port through register 0x4c.  same ub953 and ub960 driver. only this 1 lane sensor has stopped working which was working a few weeks back. 

Hi Shivlal, 

Would you be able to provide register dumps for the following conditions: 

1. Pattern generator enabled from the 960 with forwarding enabled
2. Pattern generator enabled on the 953 with forwarding enabled on the 960

For the register dump, please provide all register for the 953 and 960. 

Would you be able to provide the specification for the one lane sensor including the speed per lane? We would recommend confirming the sensor to the CSI specifications by connecting the CSI lines directly to a oscilloscope. 

Best,

Zoe

its one lane sensor. data rate is around 735 mbps. confirmed with oscilloscope. how to enable pattern generator? what it does? my concern is, register 0x5e value is not changing with different settings. its always 0x0c.

Hi Shivlal,

The register value of 0x0C in register 0x5E denotes the sensor data seen by the serializer is not meeting the SOT criteria set in the CSI-2 standard. 

Pattern generator creates video data to output when enabled on the deserializer. When enabled on the serializer, the serializer will generate the data and transfer it over the link. I recommend referring to the device datasheet for configuration examples. This will help confirm the SoC is correctly processing the data and it is not being impacted by link. 

Best,

Zoe

how to set values in the following equation for this one lane sensor with data rate 735mbps.

CLK_OUT =  FC * M /HS_CLK_DIV * N. 

Hi Shivlal, 

What are you trying to set the CLK_OUT frequency to and for what purpose? 

Best,

Zoe

Hi Zoe,

I have enabled pattern generation on ub953 with following example. How do I validate and verify on ub960 to make sure link is functioning properly. Do I need to set anything else apart from following registers? I am still getting registers 0x73 to 0x76 values as 0 on ub960. port is selected through 0x4c

#Patgen RGB888 1920x1080p30 Fixed 8 Colorbar

WriteI2C(0xB0,0x00)  # Indirect Pattern Gen Registers

WriteI2C(0xB1,0x01)  # PGEN_CTL WriteI2C(0xB2,0x01)

WriteI2C(0xB1,0x02) # PGEN_CFG

WriteI2C(0xB2,0x33)

WriteI2C(0xB1,0x03) # PGEN_CSI_DI

WriteI2C(0xB2,0x24) # RGB888

WriteI2C(0xB1,0x04) # PGEN_LINE_SIZE1

WriteI2C(0xB2,0x16)

WriteI2C(0xB1,0x05) # PGEN_LINE_SIZE0

WriteI2C(0xB2,0x80)

I verified link is working as expected. registers 0x73 to 0x76 values matching with values set with pattern generator on ub953. will check without pattern generator enabled.

Hi Shivlal,

Great, thanks for the verification. Let me know if there are any updates regarding using the sensor. 

Best,

Zoe

getting ecc and checksum errors on serializer side. registers 0x73 to 0x76 dumps same values that were written during pattern generation on ub953. although I have disabled pattern generation now. register 0x35 is always zero. 

[ 6.877316] ub953 2-0040: ub953 UB953_GENERAL_CFG register 0x02 =02, value=43
[ 6.884231] ub953 2-0040: Setting logical output of GPIO's: 0x1
[ 6.890314] ub953 2-0040: enabling input and output of GPIO's: 0xf0
[ 6.897028] ub953 2-0040: ub953 register 0x02 =02, value=43
[ 6.902355] ub953 2-0040: ub953 register 0x03=03, value=48
[ 6.907748] ub953 2-0040: ub953 register 0x04=04, value=00
[ 6.913272] ub953 2-0040: ub953 register 0x05=05, value=03
[ 6.918425] ub953 2-0040: ub953 register 0x06=06, value=41
[ 6.924121] ub953 2-0040: ub953 register 0x07=07, value=25
[ 6.929620] ub953 2-0040: ub953 register 0x32=32, value=09
[ 6.935058] ub953 2-0040: ub953 register 0x50=50, value=20
[ 6.940478] ub953 2-0040: ub953 register 0x51=51, value=c0
[ 6.945919] ub953 2-0040: ub953 register 0x52=52, value=65
[ 6.950983] ub953 2-0040: ub953 register 0x55=55, value=00
[ 6.956501] ub953 2-0040: ub953 register 0x56=56, value=00
[ 6.962172] ub953 2-0040: ub953 register 0x5b=5b, value=02
[ 6.967697] ub953 2-0040: ub953 register 0x5c=5c, value=ff
[ 6.972761] ub953 2-0040: ub953 register 0x5d=5d, value=0f
[ 6.978560] ub953 2-0040: ub953 register 0x5e=5e, value=0c
[ 6.984054] ub953 2-0040: ub953 register 0x5f=5f, value=00
[ 6.989319] ub953 2-0040: ub953 register 0x60=60, value=00
[ 6.994827] ub953 2-0040: ub953 register 0x61=61, value=ff
[ 7.000185] ub953 2-0040: Waiting for data vc... (VC=3, Data ID=3f)
[ 7.006893] ub953 2-0040: ub953 register 0x62=62, value=ff
[ 7.012188] ub953 2-0040: ub953 register 0x63=63, value=3f
[ 7.017966] ub953 2-0040: ub953 register 0x64=64, value=80
[ 7.043780] ub953 2-0040: probe success
[ 7.048129] ub960 2-0030: ub960 input clock freq 1 register=4f, value=64
[ 7.054951] ub960 2-0030: ub960 Input clock freq 2 register=50, value=00
[ 7.061791] ub960 2-0030: ub960 device status register=04, value=d0
[ 7.068085] ub960 2-0030: ub960 device status register=02, value=1e
[ 7.074901] ub960 2-0030: ub960 device status register=03, value=40
[ 7.081453] ub960 2-0030: ub960 PAR_ERR_THOLD_HI register=05, value=01
[ 7.088021] ub960 2-0030: ub960 PAR_ERR_THOLD_LO register=06, value=00
[ 7.095091] ub960 2-0030: ub960 GPIO_PIN_STS register=0e, value=f0
[ 7.101297] ub960 2-0030: ub960 0x21 register=21, value=03
[ 7.106651] ub960 2-0030: ub960 0x22 register=22, value=00
[ 7.111974] ub960 2-0030: ub960 0x34 register=34, value=00
[ 7.117407] ub960 2-0030: ub960 0x35 register=35, value=00
[ 7.122829] ub960 2-0030: ub960 0x36 register=36, value=00
[ 7.128340] ub960 2-0030: ub960 0x37 register=37, value=10
[ 7.133594] ub960 2-0030: ub960 0x40 register=40, value=00
[ 7.139221] ub960 2-0030: ub960 0x43 register=43, value=01
[ 7.144280] ub960 2-0030: ub960 0x44 register=44, value=00
[ 7.149864] ub960 2-0030: ub960 0x45 register=45, value=00
[ 7.154961] ub960 2-0030: ub960 0x46 register=46, value=20
[ 7.160705] ub960 2-0030: ub960 0x47 register=47, value=00
[ 7.166059] ub960 2-0030: ub960 0x48 register=48, value=00
[ 7.171550] ub960 2-0030: ub960 0x49 register=49, value=00
[ 7.177100] ub960 2-0030: ub960 0x4f register=4f, value=64
[ 7.182589] ub960 2-0030: ub960 0x50 register=50, value=00
[ 7.188118] ub960 2-0030: ub960 0x51 register=51, value=00
[ 7.193357] ub960 2-0030: ub960 0x52 register=52, value=00
[ 7.198871] ub960 2-0030: ub960 0x53 register=53, value=03
[ 7.204370] ub960 2-0030: ub960 0x54 register=54, value=06
[ 7.210164] ub960 2-0030: ub960 0x55 register=55, value=00
[ 7.215401] ub960 2-0030: ub960 0x56 register=56, value=00
[ 7.221190] ub960 2-0030: ub960 0x57 register=57, value=00
[ 7.226684] ub960 2-0030: ub960 0x70 register=70, value=2b
[ 7.232217] ub960 2-0030: ub960 0x71 register=71, value=2c
[ 7.237446] ub960 2-0030: ub960 0x73 register=73, value=04
[ 7.243236] ub960 2-0030: ub960 0x74 register=74, value=38
[ 7.248465] ub960 2-0030: ub960 0x75 register=75, value=16
[ 7.254004] ub960 2-0030: ub960 0x76 register=76, value=80
[ 7.259508] ub960 2-0030: ub960 0x7b register=7b, value=00
[ 7.265288] ub960 2-0030: ub960 0xd2 register=d2, value=94
[ 7.270525] ub960 2-0030: ub960 0xd3 register=d3, value=03
[ 7.276315] ub960 2-0030: ub960 0xd4 register=d4, value=60
[ 7.281547] ub960 2-0030: ub960 0xd5 register=d5, value=f2
[ 7.287075] ub960 2-0030: ub960 0xd6 register=d6, value=00
[ 7.292570] ub960 2-0030: ub960 0xd7 register=d7, value=02
[ 7.298143] ub960 2-0030: ub960 0xda register=da, value=00
[ 7.303626] ub960 2-0030: ub960 0xdb register=db, value=63
[ 7.309135] ub960 2-0030: ub960 GPIO_INPUT_CTL register=0f, value=ff
[ 7.315670] ub960 2-0030: ub960 GPIO0_PIN_CTL register=10, value=00
[ 7.322510] ub960 2-0030: ub960 GPIO0_PIN_CTL register=10, value=00
[ 7.329056] ub960 2-0030: UB960_REG_FWD_CTL1 register address before enabling csi_ctl1 =0x20, value=0xf0
[ 7.338783] ub960 2-0030: UB960_REG_CSI_CTL1 reg. address after enabling=0x33, value=0x73
[ 7.347039] ub960 2-0030: UB960_REG_FWD_CTL1 register address after enabling csi ctl1=0x20, value=0x00
[ 7.356238] ub960 2-0030: probe success

Hi Shivlal,

Thanks for the update. This looks to be an issue with the CSI inputs to the serializer in specific. Would you be able to give some more information on the set up you are using? If the serializer is a custom board, would you be able to share the layout? 

Best,

Zoe

I was able to capture from this sensor a few days back. these ecc and crc errors were coming earlier also. but they were not consistent. sometimes there were no errors. video was also not coming consistently on every boot. no change in hardware as well as software settings. Don't know what changed?

is it data synchronization issue between sensor and serializer? if it is how to fix it?

Hi Shivlal, 

These errors reported denote a potential issue with the sensors being used. Since this is a custom board, would you be able to share the layout? The primary thing I am looking to confirm is trace length matching on the CSI inputs. 

In your response, it was described that video did not come consistently on each boot. To help streamline the conversation, would you be able to elaborate if this correlated to any changes in register 0x4D or register 0x73-0x76? Since the video stream is being accessed by an SoC, there are multiple reasons that could contribute to differences between initializations. A register dump of all registers on the UB960 and UB953 in a good case and bad case would be helpful. 

CSI sync errors are seen in the data received. The CSI standards describes the required transmission sequence in relation to the transmitter and receiver. Can you share what sensors are being used? 

Best,

Zoe

I have this schematic layout of tuvi sensor and ub953.

i was not able to save register dump when video capture was working but there were intermittent ecc and crc errors on some boot ups. when there were no errors video was coming. so it could be a sensor initialization issue as you suggested. 

if clock frequency required by sensor is 24000 hz. how to configure  registers on serializer?  

Hi Shivlal, 

For 24MHz CLK_OUT pin from the 953, we recommend the following values: 

This assumes the REFCLK value on the UB960 is 25MHz.

Best,

Zoe

UB960 register 0xa5(REFCLK) is dumping value 0x1C which means 28 mhz. is it expected?

Hi Shivlal,

Yes, this is expected. There will be some variaitions in frequency measurement in register 0xA5. 

Best,

Zoe

no change in status registers on ub953. even if I load some dummy driver for sensor instead of actual driver, I get the same status registers dump(0x5e...). is it likely to be sensor problem? I have already shared sensor and serializer ub953 schematics above.

here is sensor device tree.

ov5693@60 {
status = "disabled";
compatible = "d3,ov5693";
reg = <0x60>;
devnode = "video0";
mclk = "extperiph1";
clocks = <0x4 0x25 0x4 0x66>;
physical_w = "3.674";
physical_h = "2.738";
physical-addr = <0x36>;
avdd-reg = "vana";
iovdd-reg = "vif";
clock-names = "extperiph1";
vana-supply = <0x16e>;
vif-supply = <0x16c>;
reset-gpios = <0x13 0x7d 0x0>;
pwdn-gpios = <0x1b 0x88 0x0>;
clock-frequency = <0x16e3600>;
has-eeprom = [30 00];
sensor_model = "ov5693";
use_decibel_gain = "true";
use_sensor_mode_id = "true";
deserializer = <0x40>;
linux,phandle = <0x17b>;
phandle = <0x17b>;

mode0 {
mclk_khz = "25000";
num_lanes = "1";
tegra_sinterface = "serial_a";
discontinuous_clk = "no";
phy_mode = "DPHY";
dpcm_enable = "false";
cil_settletime = [30 00];
csi_pixel_bit_depth = "16";
active_w = "1280";
active_h = "480";
mode_type = "yuv";
pixel_phase = "yuyv";
readout_orientation = "0";
inherent_gain = [31 00];
line_length = "1280";
mclk_multiplier = "6.67";
pix_clk_hz = "54000000";
serdes_pix_clk_hz = "535000000";
gain_factor = "10";
min_gain_val = "10";
max_gain_val = "160";
step_gain_val = [31 00];
default_gain = "10";
min_hdr_ratio = [31 00];
max_hdr_ratio = [31 00];
framerate_factor = "1000000";
min_framerate = "1816577";
max_framerate = "30000000";
step_framerate = [31 00];
default_framerate = "30000000";
exposure_factor = "1000000";
min_exp_time = "34";
max_exp_time = "550385";
step_exp_time = [31 00];
default_exp_time = "8334";
embedded_metadata_height = [30 00];
};

ports {
#address-cells = <0x1>;
#size-cells = <0x0>;
status = "disabled";

port@0 {
reg = <0x0>;

endpoint {
status = "disabled";
port-index = <0x0>;
bus-width = <0x1>;
remote-endpoint = <0x32>;
linux,phandle = <0x17c>;
phandle = <0x17c>;
};
};
};
};

Hi Shivlal, 

Can you please provide the layout of the 953 board you are using? 

Best,

Zoe

https://ibb.co/TYdDLPc

Hi Shivlal, 

I'm unable to open the link sent. Would you be able to upload the layout to TI Drive through the following link? 

https://tidrive.ext.ti.com/u/p_bVEb321QW19tUC/583ad2f2-f82a-4e7c-aa22-1870c1bf7be5?l

Password: 5y*dNVP2

Please let me know if a different method is preferred. 

Best,

Zoe

I have uploaded the image in previous reply. Because of data transmission errors from sensor, vc I'd and data id is also keep changing. Earlier also it was happening when I was able to capture from sensor successfully. vc_map register 0x72 was taking care of it but it's not working now.

Hi Shivlal, 

The previous pictures were of the schematic, not layout. I am looking to understand the layout and stackup of the board being used in your system, which I do not see provided on my end. 

Here is the TI Drive information again: 

https://tidrive.ext.ti.com/u/1y9mg80vZpjFL2aQ/583ad2f2-f82a-4e7c-aa22-1870c1bf7be5?l

Password: wDH7Ef=7

Best,

Zoe