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.

DS90UB949-Q1: Analog LaunchPAD Not Recognizing DS90UB949-Q1 EVM

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

Hi support team,


I am having issues connecting Serializer (DS90UB949-EVM) to Analog LaunchPAD. Software doesn’t recognize serializer profile. However, the message on the footage, ALP Framework - says “Hardware Connected”. I have followed steps for troubleshooting suggested in User’s Guide (Pages 21 – 25) by manually selecting the right profile, still not working.

I have added some pictures to help you understand my setup. Let me know if I have missed anything. 

My goal is to establish communication between Serializer (DS90UB949 – Evaluation Board) and Deserializer DS90UH498 (a personalise board). 

As rule of thumb, I am checking one thing at the time – starting with Serializer (DS90UB949-EVM), where I fund this issue.


Hardware setup:

1 – the Evaluation board B949 Jumpers were left as default (see pictures)

2 – The MODE_Sel 0,1 straps were left was default

3 – 12V, 5A power supply was used


Software Setup:

1 – Download and installed

1.1   – ALP_setup_v_1_57_0010

Board shows D4 LED solid green 

Image below you shows that the information tab is providing Device information selected.  

I have manually selected device mode serial number as showed in image below. 

Your help will be very much appreciated. 

Thanks in advance.

  • Hello,

    Thanks for sharing a photo of your board setup. We have seen ALP connection issues when board power or jumper settings is not proper.  It looks to me none of the jumpers are configured to default as defined in the user guide. Please see 

    Could you make sure the jumpers and switch settings are as above and try again? Sorry if you had received the board without proper (default) jumper settings from our store.



  • Hi Vishy,

    Thank you for your reply, it did help a lot. 

    I have double checked the Jumpers position I have found that J37 was placed way round.

    Now I can get communication with Serializer and Deserializer  as expected.

    Great job :-)!

    Many thanks.

  • Great! Thanks for confirming you got the communication going. I will close this ticket. 



  • Hi,

    I have a different question but relate to same setup.

    What are the main configuration that I should be looking to get some images on the display? If using the following setup:

    -        Communication between Laptop to Serializer: HDMI cable

    -        Serializer to Deserializer: FPD-Link (Dacar 535 4-Core coaxial cable)

    -        Display resolution: 1920x720

    -        Serializer Configuration Select: Mode_Sel0 = Strap 1, Mode_Sel1 = Strap 6 (to match Deserializer)

    Many thanks

  • Hello,

    You can use Pattern Generator in our SERDES devices to verify the individual links. For example, use the Deserializer patgen and test/debug if you can successfully send a color bar pattern to the display. Then you can test/debug the fpdlink connection between 949/948 by using the patgen in 949. FYI, in ALP there's a patgen tab you can use and test this. There's also an app note on our website on Patgen



  • Hi,


    It was able to communicate for short period, after cycling power couple of times. I lost communication with Deserializer.

    From serializer (DS90UB949-EVM) side I have checked all the jumpers and Mode_Sel (S2, S3 and S6) all seems to be configured as default suggested by User Guide manual. I have added pictures for your observation.

    From Deserializer side I have checked powers going to Deserializer and it seems to receiving 3.3V, 1.2V and 12V the board.


    Have you ever experienced similar issue where you can advise things to try?

    I haven’t changed any configuration on the software ALP apart from USB2ANY/Aardvark Setup to select the right profile.


    DS90UB949-EVM physical configuration set (Jumpers + DIP8 S2, S3 and S6):


    Screenshot of both boards (Ser & Des) communicate before lost communication:



    Screenshot below which shows Deserializer not detected: 

    Any help will be very much appreciate. 

    thank you in advance. 

  • Hello,

    Connect ALP to 948EVM also through another usb port. You should see a second USB2ANY selection on the left side. Now choose 948 profile and then in Registers Tab set register 0x34 bit 6 (RX_LOCK_MODE) to 1. This will assert RX_LOCK when device is linked to Serializer.

    Let me know if this helped. Also, make sure the fpdlink cable is properly connected and also the strap selection through switches match your setup.



  • Hello Vishy,


    Thank you again for getting back with your suggestion. I should mention that I am not using 948EVM, I am just using 948 chipset implemented in customized board to convert FPD-link data from serializer to LVDS. The customized board is designed without usb / usb hub circuit.

    I was expecting to configure 948 from 949EVM through FPD-Link.

    Though there is no USB circuit on the customized board, there is a pin header (see below) with some pins available to access 948 chip. Do you think I can read/write address directly using some of this pin?

     Given my circumstance, is there any other alternative? For example, reset the 949EVM to default.


  • Hello Dilson,

    I don't see I2C pins of 948 on the header so we can't use an external usb2any for register access. In this case, can you go to ALP remote registers window of 949 and see if you are able to access 948 registers. If so, then program the register 0x34 bit 6 to 1 as suggested above and let me know. I think assuming everything is coming up correct the link should be there only because this bit is not set ALP is not showing. Please try and let me know



  • Hi Vishy,

    Thank you for your advice. A small progress was made but still experience issues.

    I realized that Deserializer 948 pin 48 (PDB) was not receiving the right voltage (3.3V) therefore the ALP was not detecting.

    By ensuring the right voltage, we have seeing some communication between Serializer and Deserializer, but the odd is that the ALP is detecting wrong Deserializer Device information. It is detecting DS90UH926 steady of DS90UH948. However, the I2C address of both Ser_949 and Des_948 seems to matches with datasheet (IDX address) according to my configuration. I have attached screenshot for your reference, please see below.


    Current Hardware configuration:


    • MODO_SEL 0: p1 = ON
    • MODE_SEL 1: p2 = ON
    • IDX: p1 = ON

     Deserializer (of personalized board):

    • MODE_SEL 0: R1 = Open, R2 = 10k
    • MODE_SEL 1: R1 = 73k, R2 = 15k
    • IDX: R1 = Open, R2 = 10k


    Serializer - Mode select tables:



    Deserializer - Mode select tables:

    ALP GUI – It shows communication with Deserializer (right I2C Addr) but not the expected Device information (Des_948).

    Serializer 949 Hardware configuration:


    I had look in Remote Register, but registers don’t match with datasheet of the Des_948, which I assume it is giving me the registers of Des_926 steady.

    I have attached log file of Remote Register and Register for your reference. 

    Base on the information provided can you please tell me if I am missing anything?

    Any advice will be very much appreciate.

    Register Display - ALP Nano 1 - DS90UH926, Connector 1
    Register	Data	Name
    0x0000	0x00	I2C Device ID
    0x0001	0x00	Reset
    0x0002	0x00	General Configuration 0
    0x0003	0x00	General Configuration 1
    0x0004	0x00	BCC Watchdog Control
    0x0005	0x00	I2C Control 1
    0x0006	0x00	I2C Control 2
    0x0007	0x00	REMOTE ID
    0x0008	0x00	SlaveID[0]
    0x0009	0x00	SlaveID[1]
    0x000A	0x00	SlaveID[2]
    0x000B	0x00	SlaveID[3]
    0x000C	0x00	SlaveID[4]
    0x000D	0x00	SlaveID[5]
    0x000E	0x00	SlaveID[6]
    0x000F	0x00	SlaveID[7]
    0x0010	0x00	SlaveAlias[0]
    0x0011	0x00	SlaveAlias[1]
    0x0012	0x00	SlaveAlias[2]
    0x0013	0x00	SlaveAlias[3]
    0x0014	0x00	SlaveAlias[4]
    0x0015	0x00	SlaveAlias[5]
    0x0016	0x00	SlaveAlias[6]
    0x0017	0x00	SlaveAlias[7]
    0x0018	0x00	CRC Errors THRESHOLD
    0x0019	0x00	CRC Errors THRESHOLD
    0x001A	0x00	CRC Errors
    0x001B	0x00	CRC Errors
    0x001C	0x00	General Status
    0x001D	0x00	GPIO[0] Config
    0x001E	0x00	GPIO[1] and GPIO[2] Config
    0x001F	0x00	GPIO[3] and GPIO[4] Config
    0x0020	0x00	GPIO[5] and GPIO[6] Config
    0x0021	0x00	GPIO[[7] and GPIO[8] Config
    0x0022	0x00	Datapath Control
    0x0023	0x00	RX Mode Status
    0x0024	0x00	BIST Control
    0x0025	0x00	BIST ERROR COUNT
    0x0026	0x00	SCL High Time
    0x0027	0x00	SCL Low Time
    0x0028	0x00	UNUSED
    0x0029	0x00	FRC Control
    0x002A	0x00	White Balance Control
    0x002B	0x00	I2S Control
    0x002C	0x00	SSCG Test Mode
    0x002D	0x00	SSCG Test Mode
    0x002E	0x00	SSCG Test Mode
    0x002F	0x00	SSCG Test Mode
    0x0030	0x00	SSCG Test Mode
    0x0031	0x00	SSCG Test Mode
    0x0032	0x00	OSC CLOCK DIVIDER
    0x0033	0x00	BC START SEQUENCE
    0x0034	0x00	UNUSED
    0x0035	0x00	AEQ TEST
    0x0036	0x00	DIGITAL DEBUG 1
    0x0037	0x00	CAD DEBUG
    0x0038	0x00	Reserved
    0x0039	0x00	DFT TEST MODES
    0x003A	0x00	I2S_DIVSEL
    0x003B	0x00	Adaptive EQ status
    0x003C	0x00	DIGITAL DEBUG 2
    0x003D	0x00	General Status
    0x003E	0x00	RESERVED
    0x003F	0x00	ANALOG DEBUG 2
    0x0040	0x00	LOCK TIME
    0x0041	0x00	LINK ERROR COUNT
    0x0042	0x00	DCA STATUS WAIT TIME
    0x0043	0x00	UNUSED
    0x0044	0x00	ADAPTIVE EQ
    0x0045	0x00	ADAPTIVE EQ MIN MAX
    0x0046	0x00	ADAPTIVE DE-EMPH
    0x0047	0x00	ADAPTIVE DE-EMPH MIN MAX
    0x0048	0x00	LOCK RE-TRY
    0x0050	0x00	reg_50
    0x0051	0x00	reg_51
    0x0052	0x00	reg_52
    0x0053	0x00	reg_53
    0x0054	0x00	reg_54
    0x0055	0x00	reg_55
    0x0056	0x00	reg_56
    0x0057	0x00	reg_57
    0x0058	0x00	reg_58
    0x0059	0x00	reg_59
    0x005A	0x00	reg_5a
    0x005B	0x00	reg_5b
    0x005C	0x00	reg_5c
    0x005D	0x00	reg_5d
    0x005E	0x00	reg_5e
    0x005F	0x00	reg_5f
    0x0060	0x00	reg_60
    0x0061	0x00	reg_61
    0x0062	0x00	reg_62
    0x0063	0x00	reg_63
    0x0064	0x00	PGCTL
    0x0065	0x00	PGCFG
    0x0066	0x00	PGIA
    0x0067	0x00	PGID
    0x0068	0x00	PGDBG
    0x0069	0x00	PGTSTDAT
    0x0070	0x00	I2S_WAIT_OV
    0x0071	0x00	I2S_SM_OV
    0x0072	0x00	I2S_PFD_SW
    0x0073	0x00	I2S_VHIGH_SEL
    0x0074	0x00	I2S_VLOW_SEL
    0x0075	0x00	I2S_VMID_SEL
    0x0076	0x00	I2S_VCO_IDN
    0x0077	0x00	I2S_VCO_IUP
    0x0078	0x00	I2S_CP_RDAC
    0x0079	0x00	I2S_DFT
    0x007A	0x00	I2S DEBUG MONITOR
    0x007B	0x00	I2S DEBUG READ
    0x007C	0x00	I2S PPM MATCH LIMIT
    0x0080	0x00	RX_BKSV0
    0x0081	0x00	RX_BKSV1
    0x0082	0x00	RX_BKSV2
    0x0083	0x00	RX_BKSV3
    0x0084	0x00	RX_BKSV4
    0x0090	0x00	TX_KSV0
    0x0091	0x00	TX_KSV1
    0x0092	0x00	TX_KSV2
    0x0093	0x00	TX_KSV3
    0x0094	0x00	TX_KSV4
    0x0098	0x00	TX_AN0
    0x0099	0x00	TX_AN1
    0x009A	0x00	TX_AN2
    0x009B	0x00	TX_AN3
    0x009C	0x00	TX_AN4
    0x009D	0x00	TX_AN5
    0x009E	0x00	TX_AN6
    0x009F	0x00	TX_AN7
    0x00C0	0x00	HDCP_DBG
    0x00C1	0x00	HDCP_DBG2
    0x00C4	0x00	HDCP_STS
    0x00C5	0x00	HDCP_TEST
    0x00C8	0x00	NVM_CTL
    0x00C9	0x00	NVM_DATA
    0x00CA	0x00	NVM_ADDR0
    0x00CB	0x00	NVM_ADDR1
    0x00CC	0x00	NVM_TEST
    0x00E0	0x00	RPTR_TX0
    0x00E1	0x00	RPTR_TX1
    0x00E2	0x00	RPTR_TX2
    0x00E3	0x00	RPTR_TX3
    0x00F0	0x00	HDCP_RX_ID0
    0x00F1	0x00	HDCP_RX_ID1
    0x00F2	0x00	HDCP_RX_ID2
    0x00F3	0x00	HDCP_RX_ID3
    0x00F4	0x00	HDCP_RX_ID4
    0x00F5	0x00	HDCP_RX_ID5
    0x00F6	0x00	SIL_REV
    0x00F8	0x00	RAMBIST_CTL
    0x00F9	0x00	RAMBIST_ERR_DATA


    Register Display - ALP Nano 1 - DS90UB949, Connector 1
    Register	Data	Name
    0x0000	0x18	I2C Device ID
    0x0001	0x00	Reset
    0x0003	0xDA	General Configuration
    0x0004	0x80	Mode Select
    0x0005	0x00	I2C Master Config
    0x0006	0x58	DES ID
    0x0007	0x00	SlaveID[0]
    0x0008	0x00	SlaveAlias[0]
    0x0009	0x00	Reserved
    0x000A	0x2B	Back Channel CRC Errors
    0x000B	0x00	Back Channel CRC Errors
    0x000C	0x03	General Status
    0x000D	0x10	GPIO[0] Config
    0x000E	0x00	GPIO[1] and GPIO[2] Config
    0x000F	0x00	GPIO[3] Config
    0x0010	0x00	GPIO[5] and GPIO[6] Config
    0x0011	0x00	GPIO[7] and GPIO[8] Config
    0x0012	0x00	Datapath Control
    0x0013	0x98	General Purpose Control
    0x0014	0x00	BIST and DOPL Control
    0x0015	0x01	I2C_VSELECT
    0x0016	0xFE	BCC Watchdog Control
    0x0017	0x1E	I2C Control
    0x0018	0x7F	SCL High Time
    0x0019	0x7F	SCL Low Time
    0x001A	0x01	Datapath Control 2
    0x001B	0x00	BIST BC Error Count
    0x001C	0x00	GPI Pin Status 1
    0x001D	0x00	GPI Pin Status 2
    0x001E	0x01	TX_PORT_SEL
    0x001F	0xFA	Frequency Counter
    0x0020	0x0F	Deserializer Capabilities 1
    0x0021	0x00	Deserializer Capabilities 2
    0x0022	0x25	Reserved
    0x0023	0x00	Reserved
    0x0024	0x00	Reserved
    0x0025	0x00	Reserved
    0x0026	0x00	Link Detect Control
    0x0027	0x00	Reserved
    0x0028	0x01	Reserved
    0x0029	0x20	Reserved
    0x002A	0x20	Reserved
    0x002B	0xA0	Reserved
    0x002C	0x00	Reserved
    0x0030	0x00	SCLK_CTRL
    0x0031	0x00	AUDIO_CTS0
    0x0032	0x00	AUDIO_CTS1
    0x0033	0x00	AUDIO_CTS2
    0x0034	0x00	AUDIO_N0
    0x0035	0x00	AUDIO_N1
    0x0036	0x00	AUDIO_N2_COEFF
    0x0037	0x00	CLK_CLEAN_STS
    0x0038	0x00	Reserved
    0x0039	0x00	Reserved
    0x003A	0x00	Reserved
    0x003B	0x00	Reserved
    0x003C	0x00	Reserved
    0x003D	0x00	Reserved
    0x003E	0x00	Reserved
    0x003F	0x00	Reserved
    0x0040	0x14	Reserved
    0x0041	0x55	Reserved
    0x0042	0x00	Reserved
    0x0043	0x00	Reserved
    0x0044	0x80	Reserved
    0x0045	0x00	Reserved
    0x0046	0x00	Reserved
    0x0047	0x00	Reserved
    0x0048	0x00	APB_CTL
    0x0049	0x00	APB_ADR0
    0x004A	0x00	APB_ADR1
    0x004B	0x00	APB_DATA0
    0x004C	0x00	APB_DATA1
    0x004D	0x00	APB_DATA2
    0x004E	0x00	APB_DATA3
    0x004F	0x00	BRIDGE_CTL
    0x0050	0x07	BRIDGE_STS
    0x0051	0xA1	EDID_ID
    0x0052	0x1E	EDID_CFG0
    0x0053	0x00	EDID_CFG1
    0x0054	0x08	BRIDGE_CFG
    0x0055	0x0C	AUDIO_CFG
    0x0056	0x00	TMDS_FIFO
    0x0057	0x00	reserved
    0x0058	0x00	reserved
    0x0059	0x00	reserved
    0x005A	0x02	DUAL_STS
    0x005B	0x20	DUAL_CTL1
    0x005C	0x02	DUAL_CTL2
    0x005D	0x06	FREQ_LOW
    0x005E	0x44	FREQ_HIGH
    0x005F	0x00	HDMI_FREQ
    0x0060	0x22	SPI_TIMING1
    0x0061	0x02	SPI_TIMING2
    0x0062	0x00	SPI_CONFIG
    0x0064	0x10	PGCTL
    0x0065	0x00	PGCFG
    0x0066	0x0D	PGIA
    0x0067	0x16	PGID
    0x0068	0x30	Reserved
    0x0069	0x00	Reserved
    0x006A	0x00	Reserved
    0x006B	0x00	Reserved
    0x006C	0x00	Reserved
    0x0070	0x00	SlaveID[1]
    0x0071	0x00	SlaveID[2]
    0x0072	0x00	SlaveID[3]
    0x0073	0x00	SlaveID[4]
    0x0074	0x00	SlaveID[5]
    0x0075	0x00	SlaveID[6]
    0x0076	0x00	SlaveID[7]
    0x0077	0x00	SlaveAlias[1]
    0x0078	0x00	SlaveAlias[2]
    0x0079	0x00	SlaveAlias[3]
    0x007A	0x00	SlaveAlias[4]
    0x007B	0x00	SlaveAlias[5]
    0x007C	0x00	SlaveAlias[6]
    0x007D	0x00	SlaveAlias[7]
    0x0080	0x00	Reserved
    0x0081	0x00	Reserved
    0x0082	0x00	Reserved
    0x0083	0x00	Reserved
    0x0084	0x00	Reserved
    0x0090	0x00	Reserved
    0x0091	0x00	Reserved
    0x0092	0x00	Reserved
    0x0093	0x00	Reserved
    0x0094	0x00	Reserved
    0x0098	0x00	Reserved
    0x0099	0x00	Reserved
    0x009A	0x00	Reserved
    0x009B	0x00	Reserved
    0x009C	0x00	Reserved
    0x009D	0x00	Reserved
    0x009E	0x00	Reserved
    0x009F	0x00	Reserved
    0x00A0	0x00	Reserved
    0x00A1	0x00	Reserved
    0x00A2	0x00	Reserved
    0x00A3	0x00	Reserved
    0x00C0	0x00	Reserved
    0x00C1	0x00	Reserved
    0x00C2	0xA8	Reserved
    0x00C3	0x00	Reserved
    0x00C4	0x48	Reserved
    0x00C5	0x00	Reserved
    0x00C6	0x00	HDCP_ICR
    0x00C7	0x40	HDCP_ISR
    0x00C8	0x40	Reserved
    0x00C9	0x00	Reserved
    0x00CA	0x00	Reserved
    0x00CB	0x00	Reserved
    0x00CC	0x00	Reserved
    0x00CE	0xFF	Reserved
    0x00D0	0x00	Reserved
    0x00D1	0x00	Reserved
    0x00D2	0x00	Reserved
    0x00D3	0x00	Reserved
    0x00E0	0x00	Reserved
    0x00E1	0x00	Reserved
    0x00E2	0xA8	Reserved
    0x00E3	0x00	Reserved
    0x00E4	0x48	Reserved
    0x00E5	0x08	Reserved
    0x00E6	0x00	Reserved
    0x00E7	0x00	Reserved
    0x00F0	0x5F	HDCP_TX_ID0
    0x00F1	0x55	HDCP_TX_ID1
    0x00F2	0x42	HDCP_TX_ID2
    0x00F3	0x39	HDCP_TX_ID3
    0x00F4	0x34	HDCP_TX_ID4
    0x00F5	0x39	HDCP_TX_ID5
    0x00F6	0x00	Reserved
    0x00F8	0x00	Reserved
    0x00F9	0x00	Reserved

  • Dilson,

    A quick input:

    a) On your deserializer board did you check the status of the lock pin? Lock should go high indicating PLL acquired lock to the reference clock input. 

    b) Just as a debug step, did you test with 948EVM and check lock happens and ALP is connecting and stable properly? In case you don't have the EVM, is it possible to match your board configuration to the 948EVM default configuration and check lock happens and everything stable?

    I will review your configuration inputs and get back to you.



  • Dilson,

    Any feedback here? Is the issue resolved?



  • Hi Casey, 

    Hope you are well. Thanks for you input. 

    My ALP still reporting unexpected Deserializer serial number; it is reporting Des_926 steady of Des_948.

    Please find details of my current setup below and results of some measurement I have taken from the configuration pins. Note that at this stage I have not connected display yet as I am just trying to get communication between the Serializer and Deserializer.


    Serializer configuration:

    IDX: S3.1 = High   |   (expected address: 0x18)

    Mode_Sel_0: S2.1 = High

    Mode_Sel_1: S6.4 = High

    Dacar 535 4-Core: Coax cable


    What is Map_Sel [0:1] is used for? Can you please comment of your interpretation?


    Deserializer (customized board) configuration:

    IDX: R1 = Open, R2 = 10K |   (expected 8-bit address: 0x58)

    Mode_Sel_0: R1 = Open, R2 = 10k (Dual OLDI output)

    Mode_Sel_1: R1 = 59k, R2 = 24.9k (20Mbps, coax cable)

    Dacar 535 4-Core: Coax cable


    Deserializer hardware check:

    There are all supplied voltages: 1.2V and 3.3V

    PLL Lock = 0 (unlocked)

    PASS = 0 (Error condition)

    PDB = 1 (Powered ON)

    BISTC/INTB = 0 (BIST mode disable)

    BISTEN = 0 (Normal Op)

    Setup images:

    The result from the ALP:


    Remote register:


    Please could you review my setup and let me know if I am missing anything?


    Initially, I was thinking the problem was coming from the Deserializer. But now that I have check pretty much everything in the Deserializer side.

    Do you think is there any change that the Serializer Evaluation board (SW or HD) would not be configured properly and therefore it is reporting wrong Deserializer serial number?


    Your help will be very much appreciated.


    Best Regards,



  • Dilson,

    You mention above PLL lock = 0 (unlocked). If lock is not there, then ALP cannot read remote registers. Remote registers are read through the back channel which can function only after a valid lock.

    So we have to debug why valid lock is not getting established. 

    When ALP detects no valid lock, it puts out 926 as the default partner device and you see all 0s for remote registers. 

    I looked at your 949 EVM jumper settings. It looks to me some jumpers which need to be set by default are not set. Please correct me if I am wrong

    J14 (RES0 pin of device must be tied to gnd)

    J18 (RES1 pin of device must be tied to gnd)

    There might be a few more.  Please check.



  • Hi Vishy,

    Thank you very much for your reply. 

    With your recommendation, I have corrected all the jumpers on the 949 EVM according to datasheet section (1.8 Default Jumper Setting).

    In the Des_948, I still reading PLL LOCK = 0V, PASS = 0V. 

    I have attached photo with my Jumpers setting. 

    Is there anything else that you would recommend to bring those pins to expected voltages?

    Thanks for your support. 



  • Dilson,

    You have the following

    Serializer configuration:

    IDX: S3.1 = High   |   (expected address: 0x18)

    Mode_Sel_0: S2.1 = High

    Mode_Sel_1: S6.4 = High

    Mode_Sel_1 is S6.4 which means Coax and remote edid load.From the photo, I see you are actually using the STP connector. Suggest you set this as default = S6.1 position which means STP and no edid.

    On the deserializer side also, set resistor network for Mode_Sel1 as STP. with 5Mbps back channel. You can refer our 948EVM user manual Table 1-10 and the schematic.

    Please try and let us know.



  • Hi Vishy,

    Thank you for your suggestion. 

    I have applied the changes you have recommended; for Serializer EVM Mode_Sel1_1 I have selected S6.1 and for Deserializer Mode_Sel_1 I have choose resistors, R1= open and R2=10K (to match default setting).

    Results: I have read voltages from LOCK and  PASS of the deserializer pins both are reading 0V and the ALP is showing default deserializer.

    Is there anything else you would recommend?

    Best regards,



  • Some suggestions:

    a) Please review your 948 custom board against 948EVM schematic. I think I shared before the link to 948EVM user guide. It should have schematic and layout. Also, please check your layout against recommendations in DS and user guide. 

    b) Suggest you connect wires to the I2C pins of 948 and connect ALP to 948. You would need USB2ANY or Aardvark dongle for this. This way you can check if device is alive and responding to register read/writes.

    c) Please post your 948 schematic (if it is not confidential) so I can also review.



  • Hello Dilson,

    Is this issue resolved? It has been several days. 

    Best Regards,