ASCII DIP Pinout Cheatsheet
Terminal-friendly ASCII pinout blocks for common DIP chips, with raw copyable layouts for quick notes and bench work.
TL:DR; this page is for the moments when a plain-text pinout is faster than opening a datasheet PDF.
Sometimes you do not need a polished schematic. Sometimes you just need a plain-text pinout you can drop into a terminal, notes file, README, or repair log without breaking stride.
Reference sheet
Ascii art pinouts for various DIP chips
Terminal-friendly pinouts for the moments where a plain-text diagram is faster than opening a datasheet. These are quick reference blocks, not substitutes for the original pin tables.
ASCII Pinout_ATmega8.txt
ATmega8
+---\/---+
(RESET) PC6 |1 28| PC5 (ADC5 / SCL)
(RXD) PD0 |2 27| PC4 (ADC4 / SDA)
(TXD) PD1 |3 26| PC3 (ADC3)
(INT0) PD2 |4 25| PC2 (ADC2)
(INT1) PD3 |5 24| PC1 (ADC1)
(XCK / T0) PD4 |6 23| PC0 (ADC0)
VCC |7 22| GND
GND |8 21| AREF
(XTAL1 / TOSC1) PB6 |9 20| AVCC
(XTAL2 / TOSC2) PB7 |10 19| PB5 (SCK)
(T1) PD5 |11 18| PB4 (MISO)
(AIN0) PD6 |12 17| PB3 (MOSI / OC2)
(AIN1) PD7 |13 16| PB2 (SS / OC1B)
(ICP1) PB0 |14 15| PB1 (OC1A)
+--------+ ASCII Pinout_ATTiny13.txt
ATTiny13
+---\/---+
PB5 |1* 8| VCC
PB3 |2 7| PB2
PB4 |3 6| PB1
GND |4 5| PB0
+--------+ Where this works well
Terminal windows, README files, commit messages, quick bench notes, and those moments where you only need orientation and signal names, not a whole drawing package.
What makes it useful
The notch is visible, the numbering stays obvious, and the text survives copy-paste almost anywhere. That makes it good for quick reference in places where an image would be clumsy.
Bench use
The plain-text format is most helpful when you are moving quickly:
- confirming pin 1 orientation before wiring
- annotating breadboard or perfboard notes
- posting help requests without drawing a full schematic
- documenting MCU pins in a repo or repair log
- checking signal names before applying power to something fragile
The limitation
ASCII pinouts are great for orientation and quick reference. They are not a replacement for a proper schematic once a project stops being simple.
Good rule: if the “quick note” now needs multiple rails, buses, pull-ups, or anything more complicated than basic orientation, it is time to graduate to a real diagram.