LP5569 datasheet(32/86 Pages) TI1

32 / 86 page

PWM Register 0

PWM Register 1

PWM Register 2

PWM Register 3

PWM Register 4

PWM Register 5

PWM Register 6

PWM Register 7

PWM Register 8

LED0

LED1

LED2

LED3

LED4

LED5

LED6

LED7

LED8

8-bit [11:4]

12-bit

12-bit PWM

8-bit Current

12-bit

EN=0/1

Engine 1

Engine 2

Engine 3

8-bit

8-bit [11:4]

12-bit

LP5569

SNVSAP8 – JULY 2017

www.ti.com

Product Folder Links: LP5569

Submit Documentation Feedback

NAME

VALUE (d)

DESCRIPTION

prescale

Divide master clock (32.7 kHz) by 16 which means 0.488 ms cycle time.

Divide master clock (32.7 kHz) by 512 which means 15.625 ms cycle time.

time

1–31

Total wait time is = (time) × (prescale). Maximum 484 ms, minimum 0.488 ms.

8.5.2.5 LED Mapping Instructions

These instructions define the engine-to-LED mapping. The mapping information is stored in a table, which is

stored in the lower half of SRAM (program memory of the LP5569 device). The LP5569 device has three

program execution engines which can be mapped to nine LED drivers. One engine can control one or multiple

LED drivers. Execution engine 1 has priority over execution engines 2 and 3, with execution engine 2 having

priority over execution engine 3. If an LED is mapped to more than one execution engine, the higher-priority

engine controls the LED.

LED mapping instructions can be divided to two groups:

•

Instructions that activate LED mapping to a certain row of the table (map_ instructions).

•

Instructions that DO NOT activate the actual LED mapping but just shift the mapping-table pointer (load_

instructions).

Activating instructions are map_start, map_sel, map_clr, map_next, map_prev and map_addr. Instructions

load_start, load_end, load_next, load_prev and load_addr do not activate the LED mapping. Mapping table and

master fader bits can be read from I2C registers 70h–75h but are written only via engine instructions.

When an engine is actively mapped to the LEDs, the engine takes over the LED PWM control, and PWM control

registers have no effect. Register control is returned when the engine is mapped to another LED. See Figure 19

for a simplified diagram of LED-engine data flow. The engine does not push a new PWM value to the LED driver

output before the set_pwm or ramp instruction is executed. If the mapping has been released from an LED, the

value in the PWM register still controls the LED brightness, and PWM register value remains in the last engine

state.

Actual PWM control resolution of the LED engines is 12 bits, but only the 8 highest bits are visible in the I2C

registers. Also, engine commands use the 8 high bits for control, and the 4 low bits are used for smoother ramps.

Figure 19. LED Data Flow

All LED mapping instructions use the SRAM bit to LEDx pin mapping as shown in Table 10.

LP5569 датащи(PDF) 32 Page - Texas Instruments

LP5569 датащи(HTML) 32 Page - Texas Instruments

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86

датащи скачать

ссылки URL