• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 34 subscribers
  • Views 345 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.

DS90UB936-Q1: DS90UB936-Q1 Cable Fault

Chun Youngsu
Expert 2485 points
Part Number: DS90UB936-Q1


Dear TI Team,

I have a question about the cable fault.

When a cable fault occurs, I want to use interrupt function using GPIO5 pin.

We've identified the following:

Cable fault understood that the Cable Fault register changes according to the FEQ_STABLE / FREQ_DET_STL / FREQ_LO_THR settings.

We confirmed that there is no setting for Cable Fault in interrupt setting of GPIO setting register.

To use the GPIO5 pin as an interrupt pin in the event of a cable fault, we set the register as shown below.

0x23-> 0x81 setting
0x15-> 0xB1 setting
0x4C-> 0x01 setting
0x0F-> 0x00 setting

Check for cable fault by reading 0x24 register when interrupt occurs

Is there any problem in using GPIO5 pin as interrupt pin when Cable Fault occurs with the above setting?

Thanks.

  • 0
    TI__Mastermind 30515 points

    Hi Yongsu,

    To enable the interrupt correctly in side UB936, you need two steps:

    1. enable FPD-Link port interrupt ICR, pls check d/s for thi (0x23, 0xD8/0XD9, etc), the ICR item can be unlock since the cable default is detected based on your system design feature.

    ///////////////////in d/s/////////////

    To enable interrupts from one of the Receive port interrupt sources:
    1. Enable the interrupt source by setting the appropriate interrupt enable bit in the PORT_ICR_HI or
    PORT_ICR_LO register
    2. Set the RX Port X Interrupt control bit (IE_RXx) in the INTERRUPT_CTL register
    3. Set the INT_EN bit in the INTERRUPT_CTL register to allow the interrupt to assert the INTB pin low
    To clear interrupts from one of the Receive port interrupt sources:
    1. (optional) Read the INTERRUPT_STS register to determine which RX Port caused the interrupt
    2. (optional) Read the PORT_ISR_HI and PORT_ISR_LO registers to determine source of interrupt
    3. Read the appropriate RX_PORT_STS1, RX_PORT_STS2, or CSI_RX_STS register to clear the interrupt.
    The first two steps are optional. The interrupt could be determined and cleared by just reading the status
    registers.

    //////////// in d/s //////////

    2. to pull the INTB pin status to GPIO5: pls check d/s "Table 8. GPIOx Output Function Programming" as below:

     Device interrupt active high 101 X 1
    Device interrupt active low 110 X 1

    best regards,

    Steven

  • 0 in reply to Steven(Shenzhen) Shi
    Expert 2485 points

    Hi

    Thank you for answer.

    one more question.

    We want to receive an interrupt when the cable is disconnected.

    Maxim products have a separate cable falut feature.

    What is the recommended setting for implementing the above functions in registers 0xD8 ~ D9?

    IE_CSI_RX_ERR bit? or IE_LOCK_STS bit?

    Thanks.

  • 0 in reply to Chun Youngsu
    TI__Mastermind 30515 points

    Hi,

    TI provides many phy layer error detections including the cable disconnection detection which can help design one more robust system. If cable is disconnected, both CSI_rx_ERR and IE_LOCK-STS would report error and can generate interrupt  signal . 

    regards,

    Steven