I modified my u-boot parameters by adding console=ttymxc0,if=RGB24 video=mxcfb0:dev=lcd,1920x1080@60,if=RGB24. The output of the TTL data pins look correct when I probe them while playing a test video using gstreamer gplay. However the pixel clock always remains the same, regardless of whether I am playing something or not. Could this be due a wrong u-boot configuration setting? I've posted a picture of the pixel clock below.
Are you using the parallel TTL output or the LVDS output? That clock looks wrong, but according to the datasheet, the clock to the display is the result of a divided DI_CLK. There is a counter that counts the number of DI_CLKs per pixel clock. Your waveform looks odd - with 2 pulses then a missing pulse.
On Friday, December 6, 2013 6:14:41 PM UTC-5, Joshua Kurland wrote:
--
You received this message because you are subscribed to the Google Groups "Wandboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wandboard+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
TVOUT: YUV444
VGA: BGR24
HDMI: RGB24
CLAA WVGA LCD: RGB565
lcd: LCD (TTL) interface
ldb: LVDS
hdmi: HDMI
1. video=mxcfb0:dev=hdmi,1920x1080M@60,if=RGB24 video=mxcfb1:dev=ldb,LDB-XGA,if=RGB666 HDMI 1080p60, LVDS XGA2. video=mxcfb0:dev=ldb,LDB-XGA,if=RGB666 video=mxcfb1:dev=hdmi,1920x1080M@60,if=RGB24 LVDS XGA, HDMI 1080p603. video=mxcfb0:dev=lcd,CLAA-WVGA,if=RGB666 WVGA RGB display