MIDIbox

User Tools

Site Tools

Trace:
display_driver

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
display_driver [2018/03/08 07:53] – [Dimensions] latigid_ondisplay_driver [2018/03/31 13:46] (current) – [Interconnection to Core] latigid_on
Line 8: Line 8:
  
 The second purpose is to use a chain of shift registers to provide chip select (CS) signals. It is functionally equivalent to a DOUT module, but the header is directly compatible with GPIO on the Core. The second purpose is to use a chain of shift registers to provide chip select (CS) signals. It is functionally equivalent to a DOUT module, but the header is directly compatible with GPIO on the Core.
 +
 +
 +The pinout for the display connectors is as follows:
 +
 +{{:dispdriver:header_j1-j2.png?direct&600|}}\\
 +(Power is connected to pin 10.)
 +
 +
 +
 +
  
 ---- ----
Line 127: Line 137:
  
 J15A1/J10B1 chain another Display Driver. Note that the J15 connection should not be mirrored for subsequent boards. J15A1/J10B1 chain another Display Driver. Note that the J15 connection should not be mirrored for subsequent boards.
 +
 +J9 is a power supply input that is sent to the displays over headers J1-J8. It may be better to wire the displays directly to the power supply rather than using the ribbon cable and connectors.
  
  
display_driver.1520495593.txt.gz · Last modified: 2018/03/08 07:53 by latigid_on