Create Account
Search
You are here: TDG Forum  >>  Freescale / NXP SOMs and Development Kits  >>  MCF5329 ColdFire Starter Development Kit  >>   no LCD_MDISP pulses

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 11 Oct 2007 02:46 PM by  hindenbu
no LCD_MDISP pulses
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages
hindenbu
New Member
New Member
Posts:


--
05 Oct 2007 03:11 PM
    While attempting to connect up an Optrex display, we've verified our HSYNC, VSYNC, and other assorted timings and everything looks great--except, that we get no pulses at all for the LCD_MDISP at the baseboard connector pin 35. Our display requires the presence of the OE signal provided by LCD_MDISP.

    I am aware of a PCN pertaining to problems involving the LCD_MDISP signal, and have looked at the affected part numbers documented in the PCN. Our Fire Engine board (1005095 rev. A) isn't listed there, but that could be because the PCN itself may be older than our Fire Engine? Should the PCN be updated to include the 1005095?

    We checked pin 37 (LCD_VDDEN) to see if the expected signal might be there instead; it wasn't.

    Our panel configuration register (LCD_PCR) is set up as 0xCAEC8082, if that may shed any light on this. We're trying to run a TFT, color, 640x480 10.4" Optrex.

    Does anyone else have suggestions on what we could configure to allow the LCD_MDISP to come through?
    hindenbu
    New Member
    New Member
    Posts:


    --
    11 Oct 2007 02:46 PM
    This turned out to be unrelated to anything mentioned above. It had to do with a configuration of one of the GPIO registers, the PAR_LCDCTL register. Ours came preconfigured with a value of 0x00ef, which means that all of the register bits were set up to work nicely with the LCD controller, except for two--the LCD ACD/OE function (critical to our problem), and a contrast control bit. These were configured to be used as GPIO instead.

    I reconfigured the register using the write command:

    w /h 0xfc0a405e 0x01ef

    and, voila, we now get our LCD_MDISP signal and our display is pretty-much working.

    Weird. Did I miss somewhere in the documentation, where it might be specified that to get any OE-dependent display to work with the EVB, that register needed to be reconfigured from the default? It seems like LogicPD should consider having the software configure the register differently on initialization, maybe. Something to consider, anyway.
    You are not authorized to post a reply.

    Forums Freescale / NXP SOMs and Development Kits MCF5329 ColdFire Starter Development Kit