TAS3002 datasheet(39/74 Pages) TI

39 / 74 page

6–5

6.4.3

Wait States

If separate I2C/SMBus commands are sent too frequently, the TAS3002 device can generate a bus wait state. This

happens when the device is busy while performing smoothing operations and changing volume, bass, and treble.

The wait occurs after the bus acknowledge on the first data byte and can exceed the maximum allowable time allowed

according to the SMBus specification (worst case 200 ms).

The following is a possible bus wait state scenario:

CODE

Start

Stop

ACTUAL

Start

Wait†

Stop

† If the master does not recognize bus waiting or if the master times out on a long wait, the master must not send consecutive I2C/SMBus commands

without a time interval of 200 ms between transactions.

6.4.4

TAS3002 SMBus Readback

The TAS3002 device supports a subset of SMBus readback. When an SMBus read command is sent to the device

(LSB = high), it answers with the subaddress and the last six bytes written.

SMBus

Command

Byte

Count

SENT

Start

69h

xxh

07h

Stop

RECEIVED

Start

07h

aah

ddh

Stop

Byte

Count

Where:

xxh

= Command byte. It is a don’t care because the response contains only the subaddress and the

last six bytes of data written to the TAS3002 device.

aah

= The last subaddress accessed in the device

ddh

= Data bytes from the TAS3002 device

NOTE: Use read sequence defined in 6.3.2

TAS3002 датащи(PDF) 39 Page - Texas Instruments

TAS3002 датащи(HTML) 39 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

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

ссылки URL