i.MX6 Solo X Maximum LVDS Resolution

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

i.MX6 Solo X Maximum LVDS Resolution

Jump to solution
1,711 Views
robertberringto
Contributor II


I configured my DTS file for a resolution of 1080x1024p @ 60 Hz. This requires a pixel clock of 109.19 MHz. Once I pass the LVDS signal through a de-serialize I confirm the pixel clock is ~114.679 MHz, so within 5%.

When I read the Reference Manual, I see a Serializer clock limitation of 595 MHz. If I simply take my pixel clock of 109.19 MHz and multiply it by 7 (as implied by other threads Single Channel LVDS Display with 1920x1080@60Hz ), I get 764.33 MHz, which exceeds the specification.

I'm successfully getting video through my system. What gives?

By the way, I configured my DTS file for full 1920x1080p @ 60 Hz, and the system hung while loading the kernal.

Tags (2)
0 Kudos
1 Solution
1,051 Views
igorpadykov
NXP Employee
NXP Employee

Hi Robert

right this spec is over PVT range, that is "max guaranteed" parameter for timing/temperature

range/unit-to-unit production variance.

~igor

View solution in original post

0 Kudos
3 Replies
1,051 Views
igorpadykov
NXP Employee
NXP Employee

Hi Robert

with clock limitation of 595 MHz (595/7) :

1.jpg

in i.MX6Q (with two lvds channels) for larger resolutions it is necessary to use split

mode with patch

https://community.freescale.com/message/525359#525359

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 Kudos
1,051 Views
robertberringto
Contributor II

igor,

Thanks for confirming my assumptions regarding the relationship between LVDS clock and pixel clock ... however, I have a Solo X at my desk where we are de-serializing the LVDS, and I'm getting 1080x1024p @ 60 Hz where my actual measured pixel clock is 114.679 MHz. Even if I use the target 109.19 MHz, multiply that by 7, and I get 764.33 MHz. This is on a single LVDS interface. That's nearly 30% over the specification!

Is the Solo X specification of 595 MHz simply a "max guaranteed" parameter for timing/temperature range/unit-to-unit production variance?

0 Kudos
1,052 Views
igorpadykov
NXP Employee
NXP Employee

Hi Robert

right this spec is over PVT range, that is "max guaranteed" parameter for timing/temperature

range/unit-to-unit production variance.

~igor

0 Kudos