Hi.
We have 2 articles failing, the failure reported by my Eng. team is : lack of video signal or failure to communicate in dual mode.
The serial numbers are:
SN1 = 5455500020
SN2 = 5455500035
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.
Hi.
We have 2 articles failing, the failure reported by my Eng. team is : lack of video signal or failure to communicate in dual mode.
The serial numbers are:
SN1 = 5455500020
SN2 = 5455500035
Hi Kagin,
are you talking the 948EVM board issue? For the EVM board, it has no video input. you need input the video through the FPD-Link channel.
best regards,
Steven
Hi Steven.
Find a better explanation from my Eng. team about the faulty boards, I hope this is more clear to help us:
Basically, we have an unexpected status in the boardcard (deserializer) in dual link mode.
We are using TestStand to do this kind of test with an especific command.
Using the SYNC.Api.Device - Get Display Deserializer Status, we obtain following:
Serial Number |
Measurment |
Expected |
5455500020 |
0xffffffff |
0x30 |
5455500035 |
0x20 |
0x30 |
Kagin,
sorry we still can't understand what is your measurement. pls check TI's EVM information, this is one FPD-Link input and LVDS output board which can decode the FPD-Link signal from the serializer.
you can check the webtsite http://www.ti.com/tool/DS90UB948-Q1EVM?keyMatch=ds90ub948&tisearch=Search-EN-Everything for more clear UB948 EVM board.
regards,
Steven
Hi.
this is the new answer from my Eng:
We added a new test, before the code drop to next step, that evaluates the status of the 948 Deserializer card in the station to confirm that it’s communicating over I2C and that the proper dual link/single link setup is present. We’ve observed that dual link devices (12” or 947 serializer) are not connecting in dual link mode, and only in single link mode. In short this means that we are only testing half of the data path on. This negotiation is automatic between the serializer in the unit and deserializer, but the output results would be the same from our station side on the image with just a single link as it would with a dual link, so we think that there is a station issue preventing the device from properly negotiating a dual-link connection.
The test that is failing is “Deserializer Status”, and it will fail with a value of 0x20 (SN: 5455500035 ). This value is a masked version of register 0x0C on the 948. Our pass status is 0x30 for a 947 device, indicating both the FPD-Link Transmit port (the OLDI interface to the frame grabber) is in dual link mode, and that the Receiver is in dual link mode for FPD-LINK III (connection to the UUT).
The other card fails with the value 0xffffffff (SN: 5455500020) in the same test : “Deserializer Status”.
Please confirm
Hello,
thanks for your message.
May I have your help to reply below questions:
1. how do you test UB948-Q1EVM board? please help provide one block diagram her.
2. what items do you want to test based on UB948Q1-EVM board?
3. regarding the reg. 0x03C on UB948, it is "salveID[4]", what is the value here do you read on UB949? this reg. is on slave ID setting.
0x0C | SlaveID[4] | |||||
7:1 | SLAVE ID4 | RW | 0 | 7-bit Remote Slave Device ID 4 Configures the physical I2C address of the remote I2C Slave device attached to the remote Serializer. If an I2C transaction is addressed to the Slave Alias ID4, the transaction will be remapped to this address before passing the transaction across the Bidirectional Control Channel to the Serializer. |
||
0 | RESERVED | R/W | 0 | Reserved. |
4. for dual/single FPD-Link setting, pls check DS90ub947's reg. 0x5B, this is on how to set the dual or single FPD-Link.
0x5B | DUAL_CTL1 | |||||
7 | FPD3_COAX_MODE | RW | Strap | FPD3 Coax Mode: Enables configuration for the FPD3 Interface cabling type 0 : Twisted Pair 1 : Coax This bit is loaded from the MODE_SEL1 pin at power-up. |
||
6 | DUAL_SWAP | RW | 0 | Dual Swap Control: Indicates current status of the Dual Swap control. If automatic correction of Dual Swap is disabled via the DISABLE_DUAL_SWAP control, this bit may be modified by software. |
||
5 | RST_PLL_FREQ | RW | 0 | Reset FPD3 PLL on Frequency Change: When set to a 1, frequency changes detected by the Frequency Detect circuit will result in a reset of the FPD3 PLL. |
||
4 | FREQ_DET_PLL | RW | 0 | Frequency Detect Select PLL Clock: Determines the clock source for the Frequency detection circuit: 0 : OLDI clock (prior to PLL) 1: OLDI PLL clock |
||
3 | DUAL_ALIGN_DE | RW | 0 | Dual Align on DE: In dual-link mode, if this bit is set to a 1, the odd/even data will be sent on the primary/secondary links respectively, based on the assertion of DE. If this bit is set to a 0, data will be sent on alternating links without regard to odd/even pixel position. |
||
2 | DISABLE_DUAL | RW | 0 | Disable Dual Mode: During Auto-detect operation, setting this bit to a 1 will disable Dual FPD-Link III operation. 0: Normal Auto-detect operation 1: Only Single or Replicate operation supported This bit will have no effect if FORCE_LINK is set. |
||
1 | FORCE_DUAL | RW | 0 | Force Dual Mode: When FORCE_LINK bit is set, the value on this bit controls single versus dual operation: 0: Single FPD-Link III Transmitter mode 1: Dual FPD-Link III Transmitter mode. |
||
0 | FORCE_LINK | RW | 0 |
Force Link Mode:
|
regards,
Steven
Hello:
I can not give you more information about it and I am not able.
With not changes in the programming, we test a different card and it works.
we roll back the old card and the issue was present again.
We avoid any wiring, harness and any device.
We have a big project with our important client and we want to know what happed to these boards.
Could you help me with the RMA, please.
Best Regards
Hi Jeremiah,
We understand your urgency. but unfortunately, we can't understand what is your problem. from your below description, we don't know it from our UB948 device or our UB948EVM board. so can you pls contact TI's local team or please provide the detail block diagram and issue description, such as UB948's register value? lock status of UB948?
Using the SYNC.Api.Device - Get Display Deserializer Status, we obtain following:
Serial Number |
Measurment |
Expected |
5455500020 |
0xffffffff |
0x30 |
5455500035 |
0x20 |
0x30 |
best regards,
Steven