TLV320AIC3101EVM AND PDK Documentation Errors

Hi Geoff,

Thanks for the heads up on the errors in the data sheet. It looks like your table is correct. I will see that these changes are implemented on the next revision of the data sheet.

In terms of integrating the AIC3101 EVM with the CC85XXDK, you can use the I2S interface on the EVM to interface to any external I2S bus by setting SW2-4 on the Mother board to "External" (Right). This will allow you to pick the I2S signals from any of the headers and interface to an external I2S bus. I2C control will still come from the GUI software. You can also disable USB I2C control by moving SW2-5 to the right, then you can attach the I2C lines to an external master.

Thanks again.

Hello 'Convertor Apps'

Thanks for your reply.

One of my original questions may have been hidden "When trying to set the EVM up, I discovered Table 3 appears to be significantly incorrect as seen in the attached spreadsheet.  Is there an updated document?"  

For example, the attached spreadsheet to my original post showed a seemingly irrelevant code being produced, and also using 'reserved' registers without any explanation from the documentation.

These 'errors' are a little disconcerting because it means that all register settings in the 'Command Line Interface' will have to be checked thoroughly before using them.

I have another question - I happily use the TI Configurator (used for Pure Path CC85XX development) on an Apple Mac using VMWare Fusion.  However, I have tried very hard to get the TLV320AIC3101xEVM Evaluation Tool working on the Mac, but cannot get past the stage of linking to the EVM board.  It shows that the 'device' is not connected, and there is no 'USB-MODEVM' shown in the 'located on' indicator.  It appears that the Mac is not loading up the driver - any way you know of manually installing the driver because Fusion never comes up with 'New Hardware Detected'?

Many thanks,

Geoff Pickford

Hi,

Just wondered if someone would please answer my questions posted on 6 Oct 2012 - it may have got lost in your system,

Many thanks,

Geoff Pickford

Hi Geoff,

We don't have any Macs around so we really don't have any experience or advice to offer. The AIC310x software used Labview for Windows XP. All of the USB drivers were part of the Labview package. Perhaps there is a labview forum somewhere where someone has tried this.

Hi,

One of my original questions posted on Oct 3, 2012 (together with a spreadsheet) has not been answered and may have been hidden:

The spreadsheet to my original post shows a seemingly irrelevant code being produced, and also using 'reserved' registers without any explanation from the documentation.

These 'errors' are a little disconcerting because it means that all register settings in the 'Command Line Interface' will have to be checked thoroughly before using them.

Question 1 - could you please explain the use of reserved registers?

Question 2 - Is there an updated document that corrects these errors?

Question 3 - If the answer to Question 2 is no, do you know when this may be.

Thanks,

Geoff Pickford

Hi Geoff,

1. The AIC3101 is a variant of the AIC3106. They are register compatible so you can compare the AIC3101 datasheet to the AIC3106 datasheet to see what some of the changes to the AIC3101 are. In general, the AIC3101 is a smaller device with fewer inputs and outputs. On the ADC side of the AIC3101, the second line inputs were removed and the third line inputs were renamed. To maintain register compatibility, unavailable features on the AIC3101 are marked reserved. In some cases these registers still exist but serve no purpose. in this case, i think bit D2 can still be used to control the weak common mode.

2. The datasheets on the web are always the latest.

3. In general, there is no specific date to go back and change older datasheets. Most of our efforts are geared toward releasing new products. Once products are many years old and successful in the market, we try not to change the datasheets too often.