• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 34 subscribers
  • Views 1688 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.

CCS/DS90UB954-Q1EVM: DS90UB954 EVM + DS90UB953 EVM + OV SENSOR MIPI２but no image

Lawrence He
Genius 3280 points
Part Number: DS90UB954-Q1EVM
Other Parts Discussed in Thread: ALP

Tool/software: Code Composer Studio

Dear,

we use DS90UB954 EVM + DS90UB953 EVM+ OV Sensor MIPI2, we check user`s guied step by step  and IDX PIN and MODE4( COAX/CSI), but didn`t work.

I2S communcation was normal, and we find OVI MIPI signal pass through FPDLINK to 954, but signal was different OVI MIPI signal.

measurement MIPI waveform:

function block:

also we setting:

0x5B -> 0x30 # Set up SER ID

0x5C -> 0x1A # Set up SER Alias ID

0x5D ->0x6C # Set up Camera ID

0x65 -> 0xC4 # Set up Camera Alias ID

 

no pictures on display:


 

if any suggestion, Please advise me.

 

Thanks,

Best regards,

 

Lawrence.

 


 

 

  • 0
    TI__Mastermind 21685 points
    Lawrence,

    Some suggestions below:
    a) Please take a look at the example script "ovt_1280_1080_30fps_REMOTE_RevE2_ID7a.py" included as part of the latest ALP. If you have already installed ALP from TI.com, you can find the script in the following ALP install folder

    C:\Program Files (x86)\Texas Instruments\Analog LaunchPAD v1.57.0010\PreDefScripts\DS90UB954

    Note latest ALP framework and ALP-PROFILE-UPDATE can be installed from the following link

    http://www.ti.com/tool/ALP

    b) Please also check another example initialization sequence below

    e2e.ti.com/.../758458

    c) Note the additional register initializations required on the UB954 and UB953:
    UB954:
    Register 0x4C to setup port
    Register 0x58 to setup back channel config
    Register 0x1F to setup CSI PLL
    Register 0x33 to enable CSI output, CSI clock and number of lanes
    Register 0x20 to enable forwarding
    UB953:
    Register 0x02 to set CSI-2 data input from imager
    Registers 0x0E and 0x0D (GPIO config if needed)


    Thanks,
    Vishy
  • 0 in reply to Vishy Viswanathan
    Prodigy 30 points
    Hi, Vishy

    Thanks for your reply.

    a) I have changed this script to the version I can use before.
    The current situation is that I2C can communicate, but there is a problem with MIPI transmission,no image.
    b) I followed the content and reset it again, but the situation still exists.
    c)
    UB954:
    0x4C --> 0x13 # Set up Port1
    0x5B --> 0x5E
    0x1F --> 0x02 # MIPI 800Mdps
    0x33 --> 0x31 # CSI OUT ENABLE / MIPI 1-lane
    0x20 --> 0x10 # Forwarding enabled for RX Port 1

    UB953:
    0x02 --> 0x43 # Continuous Clock
    # 1-lane configuration
    # Enable Transmitter CRC Generator
    # 1.8 V
    Not using GPIO

    Thanks,
    Best regards,
    Mike.
  • 0 in reply to Mike Lai37
    TI__Mastermind 21685 points
    Mike,

    a) Could you connect ALP software to I2C pins and verify there's valid lock?

    b) You can first debug 954 to ISP communication link. For this you can use Pattern Generator module of 954 and use it. You can run the "954_patgen_fix_colorbar_1280x720p.py" script and verify you see the pattern on your ISP

    c) Then in a similar manner you can turn on 953 patgen (while imager is disconnected) and check 953 to 954 to ISP communication.

    d) Finally connect imager and test the complete link.

    e) Do you have 954, 953 EVMs? 953EVM comes with a OVT10640 image sensor and in ALP you can see valid horizontal and vertical info as discussed in the thread below
    e2e.ti.com/.../2596379

    f) Couple of comments on the register initialization you show above
    - since you are using PORT1, initialize 0x4C to 0x12
    - also make sure register 0x0C is initialized to 0x97
    - I notice you have disabled continuous clock in register 0x33. Please verify gated clock fine for your ISP

    Thanks,
    Vishy
  • 0 in reply to Vishy Viswanathan
    Prodigy 30 points

    Hi, Vishy

    Thank you for your reply.

    I followed your instructions and review my script. I could initialized sensor by 954, and transfer MIPI.

    But there is a problem here,  I found MIPI CLOCK are different between 954 and image sensor.
    Image sensor's MIPI CLK is with Frame Sync, but after FPD-LINK, it was not decoded.
    How can I make him the same as the input?

    Thanks,
    Best regards,


    Mike.

  • 0 in reply to Mike Lai37
    TI__Mastermind 21685 points
    Mike,

    You can use UB954 FrameSync generation feature for this. Please refer UB954 data sheet FrameSync Operation (section 7.4.27). Under GPIO tab of ALP, you can see FrameSync Generator controls.

    Thanks,
    vishy
  • 0 in reply to Vishy Viswanathan
    Prodigy 30 points
    Hi Vishy

    The problem is solved.
    Thanks for your helping.

    Thanks,
    Best regards,

    Mike.