A 7-segment display hexadecimal encoding maps the 16 base-16 values (0-9, A-F) to specific combinations of seven LED segments (a-g) to visually represent hexadecimal data. When you add hex support to a display circuit, it fundamentally changes your decoding logic: you can no longer rely on simple Binary Coded Decimal (BCD) hardware, forcing a shift to microcontroller lookup tables or specialized hex-to-segment drivers. The most common mistake makers and junior engineers make is confusing standard BCD decoders (like the classic CD4511B) with true hexadecimal decoders; feed a CD4511B a binary 1010 (Hex A), and it will blank the display entirely rather than lighting the correct segments.
The Hexadecimal 7-Segment Truth Table
To drive a 7-segment display with hexadecimal values, you need a reliable lookup table. The table below maps every hex digit to its physical segments and provides the exact byte values needed for both Common Cathode (where a HIGH bit turns the segment ON) and Common Anode (where a LOW bit turns the segment ON) displays. Bookmark this reference for your firmware const uint8_t arrays.
| Hex Value | Binary Input (DCBA) | Segments Illuminated | Common Cathode Byte | Common Anode Byte |
|---|---|---|---|---|
| 0 | 0000 | a, b, c, d, e, f | 0x3F | 0xC0 |
| 1 | 0001 | b, c | 0x06 | 0xF9 |
| 2 | 0010 | a, b, d, e, g | 0x5B | 0xA4 |
| 3 | 0011 | a, b, c, d, g | 0x4F | 0xB0 |
| 4 | 0100 | b, c, f, g | 0x66 | 0x99 |
| 5 | 0101 | a, c, d, f, g | 0x6D | 0x92 |
| 6 | 0110 | a, c, d, e, f, g | 0x7D | 0x82 |
| 7 | 0111 | a, b, c | 0x07 | 0xF8 |
| 8 | 1000 | a, b, c, d, e, f, g | 0x7F | 0x80 |
| 9 | 1001 | a, b, c, d, f, g | 0x6F | 0x90 |
| A | 1010 | a, b, c, e, f, g | 0x77 | 0x88 |
| b | 1011 | c, d, e, f, g | 0x7C | 0x83 |
| C | 1100 | a, d, e, f | 0x39 | 0xC6 |
| d | 1101 | b, c, d, e, g | 0x5E | 0xA1 |
| E | 1110 | a, d, e, f, g | 0x79 | 0x86 |
| F | 1111 | a, e, f, g | 0x71 | 0x8E |
Note on typography: Hex values 11 and 13 are intentionally mapped to lowercase 'b' and 'd'. See the "Driver Quirks" section below for the engineering reason behind this.
Worked Example: Sizing Resistors and Bitmasking for Hex 'A'
Let’s move from theory to the workbench. Suppose you are wiring a Kingbright SC56-11SRWA (a standard 0.56-inch red common cathode display) directly to a 5V Arduino Nano GPIO pin to display the hex character A.
1. Current Limiting Resistor Calculation
First, we must protect the LED segments and the microcontroller's GPIO pins. The Kingbright datasheet specifies a forward voltage (Vf = 2.1V) at a test current of 20mA. However, driving 20mA continuously can overheat the display's internal bond wires and exceed the ATmega328P's absolute maximum per-pin rating. We will target a safer If = 15mA.
Using Ohm’s Law:
- R = (Vcc - Vf) / If
- R = (5.0V - 2.1V) / 0.015A
- R = 2.9V / 0.015A = 193.3 Ω
The nearest standard 1% E96 series resistor is 191 Ω, but stepping up to a 200 Ω resistor is the standard bench practice here. It drops the current to a very safe 14.5mA, slightly reducing brightness but vastly improving thermal reliability and MCU pin safety.
2. Bitmask Generation
To display 'A', segments a, b, c, e, f, and g must illuminate, while d and the decimal point (dp) remain off. Assuming a standard bit-mapping where Bit 0 is 'a' and Bit 7 is 'dp':
- dp (Bit 7) = 0
- g (Bit 6) = 1
- f (Bit 5) = 1
- e (Bit 4) = 1
- d (Bit 3) = 0
- c (Bit 2) = 1
- b (Bit 1) = 1
- a (Bit 0) = 1
Reading this as a binary byte gives 01110111. Converted to hexadecimal, your firmware lookup table must output 0x77 to the GPIO port to render the character 'A' on a common cathode display. If you were using a common anode display, you would apply a bitwise NOT operation (~0x77 & 0xFF) to get 0x88.
Where You Meet Hexadecimal 7-Segments in Practice
You won't typically see hex displays on consumer appliances, but they are ubiquitous in engineering, networking, and low-level hardware debugging. Common real-world applications include:
- MAC Address Sniffers: Network diagnostic tools often use 12-digit 7-segment arrays to display the last 6 bytes of a MAC address during packet capture.
- EEPROM Programmers: Benchtop chip programmers use hex displays to show the current memory address being written (e.g.,
0x0F4A). - RF Frequency Counters: High-frequency test equipment displays synthesized local oscillator frequencies in hex when interfacing with PLL configuration registers.
- Automotive OBD-II Scanners: Raw CAN bus data frames are frequently output to hex displays on standalone diagnostic dongles before being parsed by a smartphone app.
Hardware Driver Quirks: MAX7219 vs. TM1637
When scaling up to multiplexed 4-digit or 8-digit displays, driving individual GPIO pins becomes impractical. You will inevitably use a dedicated LED driver IC. However, not all drivers handle hexadecimal gracefully.
The MAX7219 "Code B" Trap
The Maxim Integrated (now Analog Devices) MAX7219 is a legendary 8-digit LED driver. It features an internal font ROM accessible by setting the "Decode Mode" register to Code B. However, Code B only supports digits 0-9 and a dash. If you send a hex value like 0x0A to a Code B decoded digit, the MAX7219 will display a blank or an undefined garbage pattern. To display true hexadecimal on a MAX7219, you must disable Code B decoding in the firmware and send the raw segment bytes (from the truth table above) directly to the digit registers.
The TM1637 and the "Uppercase B/D" Problem
The TM1637 is a wildly popular, ultra-cheap I2C-like 4-digit driver found in thousands of clock modules. It has no internal font ROM; your microcontroller must send the raw segment bytes. This exposes a fundamental physical limitation of the 7-segment display format when rendering hex.
To solve this ambiguity, the universal engineering standard (adopted by SparkFun's Serial 7-Segment displays and most open-source TM1637 libraries) is to render hex 11 as a lowercase 'b' (segments c, d, e, f, g) and hex 13 as a lowercase 'd' (segments b, c, d, e, g). If you are writing your own TM1637 Arduino library, ensure your hex-to-segment lookup table explicitly uses the lowercase bitmasks (0x7C and 0x5E) for these values, or your users will be unable to distinguish a hex payload from standard decimal integers.
Frequently Asked Questions
Can I use a CD4511 BCD decoder for hexadecimal?
No. The Texas Instruments CD4511B is strictly a BCD-to-7-segment decoder. According to its datasheet, any binary input from 1010 (10) to 1111 (15) will force all segment outputs LOW, blanking the display. You must use a microcontroller or a programmable logic array (PAL/GAL) for hex decoding.
How do I handle the decimal point (dp) when displaying hex?
The decimal point is mapped to Bit 7 (the most significant bit) of your segment byte. If you want to display 'A' with the decimal point illuminated on a common cathode display, you simply add 0x80 to your base segment byte: 0x77 | 0x80 = 0xF7.
What happens if I exceed the GPIO current limit when multiplexing?
If you are multiplexing 4 digits and rely on the microcontroller's common pin to sink the combined current of all 7 segments, you will exceed the ATmega328P's 200mA total package limit and likely burn out the GPIO port. Always use a driver IC (like the MAX7219) or external NPN transistors (like the 2N2222) to handle the common cathode/anode sinking and sourcing currents.
