MIDIbox

User Tools

Site Tools

Trace:
mb_olre16

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
mb_olre16 [2016/09/23 15:31] – [GrayScale Clock] psykhazemb_olre16 [2019/04/21 08:50] (current) – [GrayScale Clock] antichambre
Line 30: Line 30:
 We expect 16 RGB LED rings encoders. So let's do the math : We expect 16 RGB LED rings encoders. So let's do the math :
 **16 Encoders * 32 LEDs * 3 colors = __1536 lines__ ** \\ **16 Encoders * 32 LEDs * 3 colors = __1536 lines__ ** \\
-Let's transpose this to a classical matrixed SRIO chain design:  +Let's transpose this to a classical matrixed SRIO chain design: \\ 
-**3x16=48 inputs + 32 outputs = __6*DIN + 4*DOUT__ **\\ +** 16 * 3 (cathodes) * 32 (anodes)** \\ 
 +**= 48 inputs + 32 outputs ** \\ 
 +**= __6*DIN + 4*DOUT__ **\\
 ==== Core-External Driving Concept : TLC5958 ==== ==== Core-External Driving Concept : TLC5958 ====
  
-In theory it's possible to drive such a SRIO setup but in fact buses and resistors/R networs are very hard to place and will consume a lot of process. \\ +In theory it's possible to drive such a SRIO setup but in fact buses and resistors/R networks are very hard to place and it will consume a lot of contant refresh process. \\ 
 \\ \\
 After a look on the different brands and models of LED driver IC **[[http://www.ti.com/product/TLC5958|Texas Instruments TLC5958]]** appeared as a good compromise to drive a lot of RGB LEDs without overloading the core. Designed to be a LED Display driver, its original purpose and features would allow large-sized RGB-LED-based display setups\\ After a look on the different brands and models of LED driver IC **[[http://www.ti.com/product/TLC5958|Texas Instruments TLC5958]]** appeared as a good compromise to drive a lot of RGB LEDs without overloading the core. Designed to be a LED Display driver, its original purpose and features would allow large-sized RGB-LED-based display setups\\
 +\\ 
 +**<wrap download>{{http://www.ti.com/lit/ds/symlink/tlc5958.pdf|TLC5958 Datasheet}}</wrap>** 
 +\\ 
 +\\
 This Design note from Texas Instruments helps in understanding how to design around the TLC:\\ This Design note from Texas Instruments helps in understanding how to design around the TLC:\\
 **<wrap download>{{:antichambre:slva645_5_.pdf|Build high density, high refresh rate, multiplexing LED panel with TLC5958}}</wrap>** **<wrap download>{{:antichambre:slva645_5_.pdf|Build high density, high refresh rate, multiplexing LED panel with TLC5958}}</wrap>**
Line 97: Line 101:
 ==== Data Transfer ==== ==== Data Transfer ====
      
-A serialized design has been chosen to provide data to TLC. Prototype feature only 2 steps but the CORE works like there's 4 modules of 16 steps connected. In order to benchmark reactivity and Transfer time, Core send data for 4 modules. Through an emulated software SPI bus, for this 64 rings Data Sending __takes less than 5ms__ . Different colors and patterns like relative value(-64/63), keyboard(B&W keys) etc... were tested.\\+A serialized design has been chosen to provide data to TLC. Prototype feature only 2 steps but the CORE works like there's 4 modules of 16 steps connected. In order to benchmark reactivity and Transfer time, Core send data for 4 modules(4*16*32*3*16bit=12KBytes). Through an emulated software SPI bus, for this 64 rings Data Sending __takes less than 5ms__ . Different colors and patterns like relative value(-64/63), keyboard(B&W keys) etc... were tested.\\
  
 {{antichambre:img_3658.jpg?300|}}{{:antichambre:img_3657.jpg?300|}}{{antichambre:img_3656.jpg?300|}}\\ {{antichambre:img_3658.jpg?300|}}{{:antichambre:img_3657.jpg?300|}}{{antichambre:img_3656.jpg?300|}}\\
 {{antichambre:large.img_3754.jpg?300|}}   {{:antichambre:large.3653bd.jpeg?460|}}\\ {{antichambre:large.img_3754.jpg?300|}}   {{:antichambre:large.3653bd.jpeg?460|}}\\
- 
 ==== GrayScale Clock ==== ==== GrayScale Clock ====
  
-Design of External GrayScale Clock for the TLC was tricky. +Design of External GrayScale Clock for the TLC was tricky.\\ 
-257 clock periods and halt for some 1.5~2.5µs are needed for each address line . TLC would receive a VSYNC command at the end of the 32th address line to prepare the new frame datas. \\+\\ 
 +**257 clock periods and halt for some 1.5~2.5µs are needed for each address line** \\ 
 +\\ 
 +TLC would receive a VSYNC command at the end of the 32th address line to prepare the new frame datas. \\
 \\ \\
 The first approach was to provide a PWM at 800KHz and put it back to the LPC on a TMR CAP Input, use 2 MAT outputs to provide a line period and gate(NOR) the PWM with it.\\ The first approach was to provide a PWM at 800KHz and put it back to the LPC on a TMR CAP Input, use 2 MAT outputs to provide a line period and gate(NOR) the PWM with it.\\
-First issue, halting time after the 257 periods wasn't constant and dependent of PWM frequency.2nd issue, much I/O used only for this purpose.\\+\\ 
 +//First issue, halting time after the 257 periods wasn't constant and dependent of PWM frequency. Second issue, much I/O used only for this purpose.//\\
  
  
Line 119: Line 126:
 {{:antichambre:slva645_5_2.png?800|}}\\ {{:antichambre:slva645_5_2.png?800|}}\\
  
-TLC is wired like on an SPI bus to Core Board. Here are equivalences:\\+TLC is wired like on an SPI bus to Core Board. Here are connections equivalences:\\
   * SCLK => SC    * SCLK => SC 
   * DATA => SO    * DATA => SO 
   * LAT => RC    * LAT => RC 
   * FLAGS READ => SI    * FLAGS READ => SI 
 +**[[stm32f4_module#inputs_outputs_ports|STM32F4 I/O Ports]]** 
 +\\ 
 +\\
 //Note: Command is coded by putting LAT active during a defined number of SCLK periods.For example for a VSYNC command, LAT must be high during 3 SCLK pulses.//\\ //Note: Command is coded by putting LAT active during a defined number of SCLK periods.For example for a VSYNC command, LAT must be high during 3 SCLK pulses.//\\
  
Line 131: Line 140:
 **Frame update is needed only when a change occurs, TLC keep all the frame in memory and continue to distribute it to the 32 addresses lines and 16 rgb leds by address **  **Frame update is needed only when a change occurs, TLC keep all the frame in memory and continue to distribute it to the 32 addresses lines and 16 rgb leds by address ** 
 \\ \\
 +
  
 ==== GrayScale Clock ==== ==== GrayScale Clock ====
Line 136: Line 146:
 The TLC needs a GrayScale Clock(GSCLK) and additional control to multiplex 32 addresses (named COMSELx in diagram). The GSCLK signal should be 257 pulses + 1.5~2.5µs of interval between segments . COMSEL management needs 32 multiplexing adress lines for (5 bits coded and decoded directly on the top board).\\ The TLC needs a GrayScale Clock(GSCLK) and additional control to multiplex 32 addresses (named COMSELx in diagram). The GSCLK signal should be 257 pulses + 1.5~2.5µs of interval between segments . COMSEL management needs 32 multiplexing adress lines for (5 bits coded and decoded directly on the top board).\\
  
-=== Clock Schematic ===+=== Clock Schematic version 1 === 
 +\\ 
 +<wrap center round important 60%> 
 +//Note: This circuit is replaced by a simulated one, on a CPLD.// 
 +</wrap>
  
 {{:antichambre:tlc_gsclk.png?800|}}\\ {{:antichambre:tlc_gsclk.png?800|}}\\
Line 145: Line 159:
 CORE provides a regular Clock with PWM @2MHz .The 12bit counter U16 counts until 257 and trigs U1 wich is a monostable, U1 switchs, resets the counter and stops the clock counter input by U17(D-Flipflop). \\ CORE provides a regular Clock with PWM @2MHz .The 12bit counter U16 counts until 257 and trigs U1 wich is a monostable, U1 switchs, resets the counter and stops the clock counter input by U17(D-Flipflop). \\
 \\ \\
-After a certain time given by the RC couple on U1, U1 switch back and restarts the counter. +After a certain time given by the RC couple on U1, U1 switchs back and restarts the counter. 
-By this way we are sure to count the exact 257 Clocks needed and the interval between 2 segments is fixed by the trimpot U19.+By this way we are sure to count the exact 257 Clocks needed and the interval between 2 segments is fixed by the trimpot U19.\\
 \\ \\
 **GSCLK signal is then high during the 257 clocks period and low during the interval**\\ **GSCLK signal is then high during the 257 clocks period and low during the interval**\\
Line 152: Line 166:
 === Multiplexing Schematic === === Multiplexing Schematic ===
  
-{{:antichambre:tlc_gsclk_topb.png?800|}}\\+{{:antichambre:tlc_gsclk_topb.png?500|}}\\
  
 ADDR_x, ADDR_CLK, GSCLK are connected to the top board...\\ ADDR_x, ADDR_CLK, GSCLK are connected to the top board...\\
Line 158: Line 172:
 ADDR_CLK is the multiplexed lines clock . It's used to gate the PWM signal and obtain the GSCLK and of course, as a clock for the ADDR Counter U5. The counter U5 provides the coded ADDR_x lines and an EOF(End Of Frame) when 32 is reached.\\ ADDR_CLK is the multiplexed lines clock . It's used to gate the PWM signal and obtain the GSCLK and of course, as a clock for the ADDR Counter U5. The counter U5 provides the coded ADDR_x lines and an EOF(End Of Frame) when 32 is reached.\\
  
 +
 +=== Clock version 2 ===
 +
 +<wrap center round todo 60%>
 +CPLD/FPGA version
 +</wrap>
  
  
mb_olre16.1474644671.txt.gz · Last modified: 2016/09/23 15:31 by psykhaze