Datasheet

www.ti.com
Kit Operation
In each case, the TAS1020 will return, in an HID interrupt packet, the following:
[0] interface byte | status
status:
REQ_ERROR 0x80
INTF_ERROR 0x40
REQ_DONE 0x20
[1] for I
2
C interfaces, the I
2
C address as sent
for SPI interfaces, the read back data from SPI line for transmission of the corresponding byte
[2] length as sent
[3] for I
2
C interfaces, the reg address as sent
for SPI interfaces, the read back data from SPI line for transmission of the corresponding byte
[4..60] echo of data packet sent
If the command is sent with no problem, the returning byte [0] should be the same as the sent one
logically or'd with 0x20 - in our first example above, the returning packet should be:
[0] 0x31
[1] 0xA0
[2] 0x02
[3] 0x05
[4] 0xAA
[5] 0x55
If for some reason the interface fails (for example, the I
2
C device does not acknowledge), it would come
back as:
[0] 0x51 --> interface | INTF_ERROR
[1] 0xA0
[2] 0x02
[3] 0x05
[4] 0xAA
[5] 0x55
If the request is malformed, that is, the interface byte (byte [0]) takes on a value which is not described
above, the return packet would be:
[0] 0x93 --> you sent 0x13, which is not valid, so 0x93 returned
[1] 0xA0
[2] 0x02
[3] 0x05
[4] 0xAA
[5] 0x55
Examples above used writes. Reading is similar:
Read two bytes from device starting at register 5 of an I
2
C device with address A0:
[0] 0x01
[1] 0xA0
[2] 0x02
[3] 0x05
SBAU113 – November 2005 TLV320AIC32EVM and TLV320AIC32EVM-PDK User's Guide 33