• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 33 subscribers
  • Views 837 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.

Original question:

Linux/DS90UB954-Q1: UB954 colorbar output signal issue

Linux/DS90UB954-Q1: About UB954 Pattern Generation reg .CSI_CTL

l w1
Prodigy 30 points

Part Number: DS90UB954-Q1
Other Parts Discussed in Thread: ALP, USB2ANY

Tool/software: Linux

HI,

I enable Pattern Generation ，when I set reg.0x33(CSI_CTL) to 0x01,Pattern Generation work well ,csi2 clk lane and data lane both have signal and I can cee color bar.

But when I set reg.0x33(CSI_CTL) to 0x03,Pattern Generation not work. I've checked the signal of csi2 clk lane and data lane. data lane have signal ,.but csi2 clk lane no signal  and can't see color bar.


When I enable Pattern Generation  with  CSI continuous clock mode. Do I need to set up other registers? or Are there other places to pay attention to?

Below is my register settings：

## PatternGenerationOn954.py
#
# RAW10 1920*1080
#
# I2C_ADDR 0x7A
#
#
## # # # # # # ##

# CSI sel and CSI enable
i2c_write 8 0x7A 0x32 0x01 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0x33 0x01 0x1 0x1 # Enable CSI continuous clock mode
usleep 10000

# enable pat gen
i2c_write 8 0x7A 0xB0 0x00 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB1 0x01 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x01 0x1 0x1 #enable pattern generator

usleep 10000
i2c_write 8 0x7A 0xB1 0x02 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x35 0x1 0x1 #Color Bar pattern ,8 color bars block,Block size of 5 Byte

usleep 10000
i2c_write 8 0x7A 0xB1 0x03 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x2B 0x1 0x1 #CSI Data Identifier ( 0x24 = RGB888  0x2C = RAW12  0x2B = RAW10)

usleep 10000
i2c_write 8 0x7A 0xB1 0x04 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x09 0x1 0x1 #line size (15:8) 1920*10/8=2400=0x960
usleep 10000
i2c_write 8 0x7A 0xB1 0x05 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x60 0x1 0x1 #line size (7:0) 1920*10/8=2400=0x960

usleep 10000
i2c_write 8 0x7A 0xB1 0x06 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x01 0x1 0x1 #bar size (15:8) 1920*10/8/8=300=0x12C
usleep 10000
i2c_write 8 0x7A 0xB1 0x07 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x2C 0x1 0x1 #bar size (7:0) 1920*10/8/8=300=0x12C

usleep 10000
i2c_write 8 0x7A 0xB1 0x08 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x04 0x1 0x1 #active lines per frame (15:8) 1080
usleep 10000
i2c_write 8 0x7A 0xB1 0x09 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x38 0x1 0x1 #active lines per frame (7:0) 1080

usleep 10000
i2c_write 8 0x7A 0xB1 0x0a 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x04 0x1 0x1 #total lines per frame (15:8) 1125
usleep 10000
i2c_write 8 0x7A 0xB1 0x0b 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x65 0x1 0x1 #total lines per frame (7:0) 1125

usleep 10000
i2c_write 8 0x7A 0xB1 0x0c 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x0B 0x1 0x1 #line period (15:8) 1/(30*1125*10ns)=2963
usleep 10000
i2c_write 8 0x7A 0xB1 0x0d 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x93 0x1 0x1 #line period (7:0) 1/(30*1125*10ns)=2963

usleep 10000
i2c_write 8 0x7A 0xB1 0x0e 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x21 0x1 0x1 #vertical back porch 33
usleep 10000
i2c_write 8 0x7A 0xB1 0x0f 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x0a 0x1 0x1 #vertical front porch 10
usleep 10000


usleep 10000
i2c_write 8 0x7A 0xB1 0x10 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0xff 0x1 0x1 #1st byte of fixed color
usleep 10000
i2c_write 8 0x7A 0xB1 0x11 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x00 0x1 0x1 #2nd byte of fixed color
usleep 10000
i2c_write 8 0x7A 0xB1 0x12 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0xff 0x1 0x1 #3rd byte of fixed color
usleep 10000
i2c_write 8 0x7A 0xB1 0x13 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x00 0x1 0x1 #4th byte of fixed color
usleep 10000
i2c_write 8 0x7A 0xB1 0x14 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0xff 0x1 0x1 #5th byte of fixed color
usleep 10000
i2c_write 8 0x7A 0xB1 0x15 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x00 0x1 0x1 #6th byte of fixed color
usleep 10000
i2c_write 8 0x7A 0xB1 0x16 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0xff 0x1 0x1 #7th byte of fixed color
usleep 10000
i2c_write 8 0x7A 0xB1 0x17 0x1 0x1
usleep 10000
i2c_write 8 0x7A 0xB2 0x00 0x1 0x1 #8th byte of fixed color
usleep 10000




Best Regards.


  • 0
    TI__Mastermind 21685 points

    Hello,

    There are a number of sample patgen scripts available as part of the ALP Install folder. Please install latest ALP from TI.com and take a look a the following folder.

    Thanks,

    Vishy

  • 0 in reply to Vishy Viswanathan
    Prodigy 30 points
    hi,
    thank you for your reply,I checked these script files.
    Now I have another question about the connection between ub953 & ub954.
    I am debug on our custom ub954 & ub953 board.but LOCK pin and PASS pin of ub954 is low.I want to ask:
    1.When I connect 954 and 953, does the 954 LOCK pin and PASS pin automatically change to a high level?Need me to modify the register?
    2.When I connect our custom ub954&ub953 board,The LOCK pin and PASS pin of ub954 is low ,But the clk_out of ub953 have signal.( Our ub953 work in CSI-2 Synchronous mode;ub954 work in CSI-2 Synchronous Back Channel mode.) Does this indicate that 953 & 954 both are working properly?
  • 0 in reply to l w1
    TI__Mastermind 21685 points
    Hello,

    1.When I connect 954 and 953, does the 954 LOCK pin and PASS pin automatically change to a high level?Need me to modify the register?

    a) Make sure IDX and mode pin selections are proper (both 954 and 953 side). See EVM user guide for example
    www.ti.com/.../snlu223
    www.ti.com/.../snlu224
    b) Make sure 954 PDB pin state is high so device is enabled
    c) Is 953 powered by POC circuit? Please check POC circuit is working fine and 953 power is stable
    d) If 953 is connected to Port 1 of 954 then you have to change default port selection from Port 0 to Port 1
    e) You can use TI ALP software and connect to your 954 device (using USB2ANY or Aardvark). Then ALP can communicate to the hardware and check / display device status as explained in EVM user guide.

    2.When I connect our custom ub954&ub953 board,The LOCK pin and PASS pin of ub954 is low ,But the clk_out of ub953 have signal.( Our ub953 work in CSI-2 Synchronous mode;ub954 work in CSI-2 Synchronous Back Channel mode.) Does this indicate that 953 & 954 both are working properly?
    Not necessary. Please check items mentioned above.

    Thanks,
    Vishy
  • 0 in reply to Vishy Viswanathan
    TI__Mastermind 21685 points

    Hello,

    When you connect with ALP tool and check your board for successful SERDES setup you should see as shown in sample screen shot below.

    Thanks,

    Vishy