In short: A 16x2 HD44780 LCD needs only six Arduino pins in 4-bit mode (RS, EN, D4-D7) or two in I2C mode through a PCF8574 backpack, and both work because the controller latches data on the falling edge of EN, so correct wiring, a contrast pot on V0 and the init sequence in LiquidCrystal do the rest.
Why the HD44780 is still the first display you learn
The Hitachi HD44780 controller, and the many clones such as the Sitronix ST7066, drives almost every character LCD sold. A 16x2 module holds 80 bytes of display RAM (DDRAM), a 208-glyph character ROM and eight user-definable 5x8 glyphs in CGRAM. It is slow and simple, which makes it perfect for learning how a parallel bus with a strobe line really behaves. The same ideas of setup time, hold time and edge-triggered capture appear later in SRAM interfaces and in the static timing analysis that tools like Synopsys PrimeTime or Cadence Tempus perform on chips.
If you have already driven discrete outputs in Arduino LED interfacing, this is the next step: instead of one pin per light, you send commands and characters over a shared bus.
The 16 pins and what each really does
- VSS / VDD (1, 2): ground and +5 V.
- V0 (3): contrast. The liquid-crystal bias voltage, not a logic signal.
- RS (4): register select. Low means instruction register, high means data register.
- RW (5): low to write, high to read. Tie to ground if you never read the busy flag.
- EN (6): enable strobe. The chip captures the bus when EN falls.
- D0-D7 (7-14): data bus. In 4-bit mode only D4-D7 are used and D0-D3 float or are grounded.
- A / K (15, 16): backlight anode and cathode, normally through a 100-220 ohm resistor.
RS and EN timing: the heart of the protocol
To write a byte, set RS (command or character), keep RW low, place the data on the bus, then pulse EN high and low. The controller samples the bus on the falling edge. At 5 V the datasheet asks for roughly 40 ns of RS setup before EN rises, 80 ns of data setup before EN falls, an EN pulse at least 230 ns wide and an enable cycle of at least 500 ns. An Arduino digitalWrite takes about 4 microseconds on a 16 MHz ATmega328P, so you pass these limits easily; the real cost is the execution time of the command itself.
Key fact: most commands take about 37 microseconds, but Clear Display and Return Home need about 1.52 ms. Sending the next byte too soon is the classic cause of garbled text.
How 4-bit mode sends one byte in two strobes
On reset the HD44780 assumes an 8-bit bus. To switch, you exploit that the chip reads only D4-D7 while in 8-bit mode: after more than 40 ms of power-up delay, send nibble 0x3 three times (with waits of 4.1 ms and 100 microseconds), then 0x2 to select 4-bit. After that, every byte takes two strobes, high nibble first and then low nibble. This saves four pins at the cost of double the transfer time, which at around 50 microseconds per character is irrelevant for text.
Contrast, the V0 pin and the blank-screen trap
V0 sets the voltage difference between VDD and the LCD drive. Wire a 10 k ohm potentiometer between 5 V and ground with the wiper on V0. Typical modules look best at 0.4-1.0 V on V0, so the wiper is usually near the ground end. Too high gives an empty-looking screen; too low shows solid dark blocks on the first row. Dark blocks on row one with no text usually mean the controller has power but never received the init sequence, which points to wiring or a wrong pin list in code. A fixed 1 k ohm to ground can replace the pot in a finished product, though temperature shifts the ideal value.
Key fact: a blank display with a backlight on does not mean a dead module. Turn the contrast pot through its full range before suspecting code.
The LiquidCrystal library in practice
The library implements the init sequence and the delays for you. The constructor takes RS, EN, then D4-D7:
#include
LiquidCrystal lcd(12, 11, 5, 4, 3, 2); // RS, EN, D4..D7
void setup() {
lcd.begin(16, 2);
lcd.print("CourseTron");
lcd.setCursor(0, 1);
lcd.print(millis() / 1000);
}
void loop() {} Row 1 DDRAM starts at address 0x00 and row 2 at 0x40, which is why setCursor maps rows to those bases. Avoid delay-heavy loops that call clear() repeatedly, since each clear costs about 1.5 ms and causes flicker; overwrite fields with padded strings instead.
I2C mode with a PCF8574 backpack
A backpack is an 8-bit I/O expander wired to the LCD, so the Arduino needs only SDA (A4) and SCL (A5). A typical mapping is P0 = RS, P1 = RW, P2 = EN, P3 = backlight and P4-P7 = D4-D7. The library toggles EN by writing the expander twice per nibble. The 7-bit address is 0x20-0x27 for a PCF8574 and 0x38-0x3F for a PCF8574A; run an I2C scanner first because 0x27 is common but not guaranteed.
| Aspect | 4-bit parallel | I2C backpack |
|---|---|---|
| Arduino pins | 6 | 2 (shared bus) |
| Speed | Fastest | Slower, about 100 kHz bus |
| Library | LiquidCrystal | LiquidCrystal_I2C or hd44780 |
| Extra parts | Pot only | Backpack, pull-ups on board |
#include
#include
LiquidCrystal_I2C lcd(0x27, 16, 2);
void setup() { lcd.init(); lcd.backlight(); lcd.print("Hello I2C"); }
void loop() {} If you later move this idea onto custom silicon, a team at Avecas would model such an interface in RTL and verify its setup and hold margins in static timing sign-off. To learn the firmware side in structured steps, see Arduino I2C bus basics and the CourseTron courses. Hands-on lab training is also offered by ChipXpert.
Debugging checklist
- Nothing on screen: check V0, then the 5 V supply, then the pin order in the constructor.
- Garbage characters: usually a loose D4-D7 wire or a long jumper adding noise on EN.
- I2C shows only blocks: wrong address or contrast pot on the backpack needs adjusting.
- Text works but backlight is dim: the series resistor is too large or the K pin is floating.
Ready to go beyond displays? Join the CourseTron embedded systems course for guided projects on Arduino, I2C, SPI and interrupt-driven firmware.
FAQ
Can I use 3.3 V logic with an HD44780?
Most modules need 5 V on VDD and treat 3.3 V highs as marginal. Use a level shifter or a 3.3 V-rated module. Reading with RW tied low avoids the display driving 5 V back into your pins.
Why does my LCD show only black squares on row one?
The controller is powered but uninitialised. Recheck the pin order passed to LiquidCrystal and make sure the 4-bit init sequence runs after a delay of at least 40 ms.
Do I need the RW pin?
No. Grounding RW and using fixed delays works fine. Using RW to poll the busy flag only speeds up writes slightly.
How do I find the I2C address of my backpack?
Run an I2C scanner sketch with the Wire library. It prints every responding address, typically 0x27 or 0x3F.