PIC RGB Video – Technical Details

This page summarizes the technical details behind my PIC LCD video project.  This is a basic tutorial on how to generate analog RGB video using a PIC16F628 microcontroller.

Previous posts on this project:

Materials needed:

  • An LCD screen like the Sharp 4L-U4EB that accepts a noninterlaced NTSC analog RGB video signal (red/green/blue and composite sync all as separate signals).  Poor quality datasheet here.
  • (1) PIC16F628 (the PIC16F628A should be a drop-in replacement.  Sorry, I have old PICs lying around.)
  • A PIC programmer – I am using a K128, but support for it has been discontinued.  Microchip’s PICkit2 is probably your best bet, but I haven’t used one (yet).
  • MPLAB – the free Microchip IDE, or a compatible PIC assembler
  • (1) 20MHz crystal (HC-18 or whatever fits your breadboard)
  • (2) 22pF ceramic capacitors
  • (3) 470 Ohm 1/8W resistors
  • (5) 10K 1/8W resistors
  • A 1K potentiometer for brightness control (if needed, my LCD needs one to display anything)
  • A regulated 5V supply for the PIC, and my LCD needed an 8V supply of its own
  • Anything else specific to your LCD – hopefully not much.



(click to enlarge)


Theory of Operation:

The LCD I chose for this project needs four main electrical signals to display video.  Three of them carry color information – red, green, and blue.  These three signals can vary from 0V (black) to 0.7V (full brightness).  To achieve this, I placed 470 ohm resistors in series with each, as shown in the schematic.  The LCD terminates each color signal with a 75 ohm resistor, so the 470 ohm series resistors serve to convert the 5V output of the PIC to a 0.7V max signal for the LCD (using a resistive divider).

The other signal the LCD needs is CSYNC – an inverse TTL composite sync signal.  This signal provides both the horizontal and vertical sync for the LCD.  Without these sync signals the image rolls across the display because the LCD doesn’t know where the image starts or ends.  Composite sync seems to be a little bit unusual – most RGB video signals have separate horizontal and vertical sync signals on separate wires.

A horizontal line of NTSC video is roughly 64μs long. (μs = microseconds)  At the beginning of each line, CSYNC is held low for 4us, then set high again.  The RGB lines are held low during sync and stay low for 8μs after sync, then set to the desired levels display the desired image on that line.  2μs before the end of the line, RGB are set low again to signal the end of the visible image.  At 64μs, the program loops back to start another line.

You can generate video like this but there would be no vertical hold – the image would be stable in the horizontal direction because we are generating a horizontal sync but not in the vertical direction.

To create a stable image with vertical sync, you have to create a valid “field” of video.  We’re creating non-interlaced video, so every field is the same (in contrast with ordinary interlaced video used in television.)  A field is composed of 262 horizontal lines.  The first line is blank, with CSYNC set low for the entire line.  This is the vertical sync.  The next 17 lines are called the “blanking interval” and occur above the visible image, during these lines horizontal sync is applied but no RGB signals.  The next line is the first visible line and consists of both a horizontal sync and RGB signals as discussed earlier.  243 lines later, we write one blank line, then loop back and repeat the process all over again.  Now we have a valid non-interlaced analog RGB video signal.

The blank lines are mostly due to compatibility with old television sets that needed time to reset the electron gun for the next field.  The nice thing is that they give us time to do housekeeping before displaying the next field.  For example, during the blanking interval I load the image to display into memory so it can be easily read back later.

The critical thing with regards to timing is that the PIC needs to execute the same number of instructions each time it loops, such that the sync signals always occur at the right time.  This is why there are a lot of ‘nop’ instructions in my code – to pad the program execution in the right spots and maintain sync.  I started by counting instructions to figure out where to put the ‘nop’s, but by the end of writing the program I was using MPLAB’s builtin “Stopwatch” feature instead.

That’s it for now!  If you have any questions, make use of these routines in your own projects, or just find this interesting, please leave a comment!

3 thoughts on “PIC RGB Video – Technical Details”

  1. Hi there. Do you recall how you hooked up the LCD. Seems these are available on eBay now, lots of them! Is the data sheet correct t in that it was 8v DC for the inverter? Such a poor scan..

  2. awesome project!

    What kind of resolution can you get with this? For example if the total time of a horizontal line (of 262) is 62.us, how fast can you change the output?

    I suppose in theory with a 20Mhz clock (.2us/inst), the pic could change the dac 325 times during the 62us… or with a 64mhz clock you could have 900 transitions. Obviously though, there is no way your eye could see “pixels” like this, so what in practice can be the resolution?

    Also, if you did run the pic at 64mhz, could the code be done in ‘c’?

    1. Russel,

      The code I wrote is very simple – I am only displaying a few large “pixels” per line (maybe 7 or 8, I’d have to look back at the code).

      I can’t remember what the limit for my program was, but it wasn’t very good because I didn’t optimize the code very much. It was not very impressive, maybe a dozen pixels at most.

      The ~300 pixel limit you refer to is based on clock speeds alone and is not easily achievable because many clock cycles are wasted with housekeeping tasks. Simple things like pointer or loop counter increments eat up precious cycles. Take a look at the code and start counting cycles – you’ll see what I mean (and maybe come up with some improvements!)

      I don’t think C is well suited for generating video because of the timing requirements. You could write the higher level functions in C and then write an interrupt handler in assembly that actually toggles the IO lines. This is what is done on some more sophisticated projects – take a look at the Fuzebox. It uses an AVR but you might get some ideas for the PIC.

Leave a Reply