PTN3460I - PC Recognizes Monitor, But Unable to Connect/Send Video

cancel
Showing results for 
Search instead for 
Did you mean: 

PTN3460I - PC Recognizes Monitor, But Unable to Connect/Send Video

221 Views
Contributor II

Hello!

I'm running into an issue using a PTN3460I to convert DP to LVDS in EDID Emulation mode.  Specifically, when I try to connect the display to my Windows 10 PC, I am able to see that a display is connected in the "Display Settings", but I am unable to enable it.  When I choose "Extend desktop to this display" from the Multiple Displays dropdown menu, I see a brief flicker as if it is attempting to connect, but it never actually sends video, and the Multiple Displays dropdown returns to "Disconnect this display".

It's worth noting, the DP is being run through a DP to USB-C converter, then being converted back to DP before entering the PTN3460I.  Like so:

pastedImage_1.png

I assume at least some of information is transmitting properly via the AUX lines, since Windows is seeing a display, but why would it not be able to send video to the PTN3460I?  I should be able to at least put video out to the PTN3460I regardless of if the video controller/LCD Panel on the other side is receiving, correct? 

Could it be the EDID itself?  I have attached the bin file I am using for use with an AUO G215HVN1.0.  The actual block of EDID and Config data I am sending (I2C via microcontroller) is as follows:

static const uint8_t EDID_Bytes[EDID_SIZE] =
 /*00*/{0x00, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0xFF, 0x00, 0x3B, 0x10, 0x02, 0x00, 0x00, 0x00, 0x00, 0x00,
 /*10*/ 0x01, 0x1E, 0x01, 0x04, 0xA5, 0x4F, 0x00, 0x00, 0x00, 0x9A, 0xD5, 0xA3, 0x55, 0x55, 0x9F, 0x27,
 /*20*/ 0x0C, 0x50, 0x54, 0x00, 0x00, 0x00, 0x59, 0xC0, 0x01, 0x00, 0x01, 0x00, 0x01, 0x00, 0x01, 0x00,
 /*30*/ 0x01, 0x00, 0x01, 0x00, 0x01, 0x00, 0x01, 0x1C, 0xC0, 0x64, 0x30, 0x38, 0x28, 0x40, 0x00, 0x00,
 /*40*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x18, 0x00, 0x00, 0x00, 0x10, 0x00, 0x00, 0x00, 0x00,
 /*50*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x10, 0x00, 0x00,
 /*60*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
 /*70*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xE7,
/*EDID ENDS @ 0x7F*/
 /*ADDITIONAL CONFIG*/
 /*80*/ 0x00, 0x0B, 0x01, 0x01, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x08, 0x00, 0x00,
 /*90*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
 /*A0*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
 /*B0*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
 /*C0*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
 /*D0*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
 /*E0*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x12, 0x34, 0x56, 0x78,
 /*F0*/ 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
};‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

This should be a match for the bin file.

Could the conversion to USB-C be causing the problem?  I had thought the conversion was OK since I am able to see the monitor in Windows, but maybe I am mistaken?

Any thoughts/suggestions are greatly appreciated.

Thanks!

Labels (1)
5 Replies

118 Views
NXP TechSupport
NXP TechSupport

Hello Kyle,

I have contacted an application engineer dealing with PTN3460, but I haven't received an answer yet. As soon as I will receive one I will definitely reply to you. 

Thank you for your patience.

With Best Regards,

Jozef

0 Kudos

118 Views
Contributor II

Jozef,

Thank you for looking into it.  I also have a ticket for the issue up: Case #00286817.

I will also update here if I get any additional info.

0 Kudos

118 Views
NXP TechSupport
NXP TechSupport

Hello Kyle,

I have an information, that you have already received answer in the Case #00286817, where is the same question asked. So I don't have to double answer in here. 

Please confirm it to avoid a misunderstanding. 

With Best Regards,

Jozef

0 Kudos

118 Views
Contributor II

Jozef,

I have received a couple suggestions in case #00286817, mostly revolving around the DP AUX lines being properly terminated, but still no luck as of yet figuring out the exact problem.  We did discover an issue on our end regarding our termination resistors for the AUX+ and AUX- lines, which should now be resolved.

We also had adjustments made to our EDID to hopefully better reflect our AUO G215HVN1.0 panel.  The current EDID is below:

pastedImage_2.png

With this new EDID, the display appears in the device manager as "Generic Non-PnP Monitor", and still cannot be enabled in display settings.

After taking scope measurements of the AUXN and AUXP lines, we are finding that we should be in spec according to the datasheet, with a Common Mode voltage of about 1.2V and a peak to peak differential voltage of around 500mV.  We are noticing a little bit of swing in the common mode voltage (see attached scope captures).  Would that potentially cause an issue?

full.png

pt1.png

Vcm_swing.png

118 Views
NXP TechSupport
NXP TechSupport

Hello Kyle,

I apologize for late reply. I have sent your questions to an application engineer and he informed me, that he has already answered the same questions to other person. He also informed me, that we shouldn't have two threads to discuss same question with one customer.

Thank you for your understanding and I apologize for inconvenience.

With Best Regards,

Jozef

0 Kudos