• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 83 subscribers
  • Views 497 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux: DS90UB913 --->> DS90UB954

user4035748
Intellectual 280 points

Tool/software: Linux

Hello, this is the image of the camera 913 through 954 on the monitor.Note that the red area of the image is a repeated overlay of the entire image to the right.The following is my configuration initialization script, mainly equipped with 954, camera 913 power on normal work.Why are there duplicate images?

#---------------------------------------- DS90UB913 --->> DS90UB954
i2cset -f -y 1 0x2E 0x4C 0x01 # write enable for RX port 0 register.
i2cset -f -y 1 0x2E 0x0C 0x81 # port 0 receiver enable !
i2cset -f -y 1 0x2E 0x0D 0x49 # 0100 -- IO_CTL
# 5E --- 50Mbps for DS90UB953
i2cset -f -y 1 0x2E 0x58 0x58 # back channel frequency select. 50mbps for DS90UB953
i2cset -f -y 1 0x2E 0x18 0x00 # frameSync generation enable
sleep 1
i2cset -f -y 1 0x2E 0x6D 0x7F
#i2cset -y 1 0x2E 0x6D 0x7F # CSI mode -- ds90ub953:7C, 913:7F
#---------------------------------------------------------
# 30 echo " DS90UB913 B0(58) map to E2(71)"
# 31 echo " Sensor 90(48) map to 62(31)"
#SER_ID --- for DS90UB953
#SER_ALIAS_ID
#i2cset -f -y 1 0x2E 0x5B 0xB0 # remote serializer ID
i2cset -f -y 1 0x2E 0x5C 0x7C # remote serializer alias ID
i2cget -f -y 1 0x2e 0x5c
#SlaveID[0] --- for DS90UB953's SONY sensor
#SlaveAlias[0]
#i2cset -f -y 1 0x2E 0x5D 0x90 # remote slave device ID 0
#i2cset -f -y 1 0x2E 0x65 0x3C # remote slave device alias ID 0
#---------------------------------------------------------
#i2cset -f -y 1 0x2E 0x72 0xE8 # csi-2 virtual channel mapping register
sleep 1
i2cset -f -y 1 0x2E 0x33 0x23 # enable csi output, 2 lanes
#i2cset -f -y 1 0x2E 0x33 0x03
i2cset -f -y 1 0x2E 0x34 0x41 #
i2cset -f -y 1 0x2E 0x21 0x81 # csi replicate mode
i2cset -f -y 1 0x2E 0x20 0x00 # forwarding enabled for RX port
#
#i2cset -f -y 1 0x2E 0x7C 0x01

#i2cset -f -y 1 0x2E 0xBC 0x01
#i2cset -f -y 1 0x2E 0xBA 0x03 # enable fpd-Link encoder crc
#i2cset -f -y 1 0x2E 0x4A 0x10

#
i2cset -f -y 1 0x2E 0x1F 0x00
i2cset -f -y 1 0x2E 0x70 0x2A
#i2cset -f -y 1 0x2E 0x70 0x1E

i2cset -f -y 1 0x2E 0x71 0x2A
#i2cset -f -y 1 0x2E 0x1E 0x0E
i2cset -f -y 1 0x2E 0x7C 0xE0

  • 0
    TI__Intellectual 1930 points

    Hello,

    Please allow me some time to review these settings and get back with a response.

  • 0
    TI__Intellectual 1930 points

    Hello,

    Can you provide some more information about your setup? I see that you are using 2-lane CSI mode and also the CSI replicate output.

    Have you tried to use the pattern generator functionality to check this issue is present/not present?

    I would suggest the following initial debug steps:

    1. Enable pattern generator on 954 and observe the video output.
    2. Verify HSYNC/VSYNC coming from the sensor

    In addition, can you check the frame valid and line valid coming into the part? You can do this by configuring GPIOs on the 954 as indicated in the datasheet section 7.4.13.2