This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Use of TLV320AIC3101EVM with CC85xxDK

Other Parts Discussed in Thread: TLV320AIC3101

Hello,

I have several CC85xxDK's and want to facilitate a design incorporating the AIC3101 codec, and am thinking of obtaining a TLV3250AIC3101EVM and PDK.  I have several questions:

Q1 - The AIC3101 registers (listed in SLAS520D) have decimal register numbers and binary register values, whereas the Configurator works on Hex register numbers and values.  It is a pain to translate from one system to the other.  This means that the register numbers have to be converted from decimal to hex (no really big deal), and the register values have to be converted from binary to hex (annoying, time-consuming and error prone).  Is there any short cut to this one?

Q2 - Whilst the CC85XXDK Guide (SWRU251) seems to indicate that the TLV3250AIC3101EVM and/or PDK can plug directly together, is this true, and are there any special requirements?

Q3 - Whilst the TLV3250AIC3101EVM User's Guide (SLAU219) gives an explanation of the 'simple scripting language' used by the Command Line Interface (Section 4.13) and examples (Appendix G), I am hoping that any register changes set up in the TLV3250AIC3101EVM GUI can be directly written into the Configuration files of the Configurator so that no manual transfer is necessary.  Is this true, and if not, is there a way of transferring in an easy way from the AC3101EVM to the files used by the Configurator?

Many thanks,

Geoff Pickford

  • Hi Geoff !

    Q1 - I would use a web calculator like : 

    http://www.mathsisfun.com/binary-decimal-hexadecimal-converter.html

    which converts three ways and covers what you need.

    Q2 - This is true, though there are 2 things that must be done. On the PurePath DK the pins for 3.3V, 5.0V and GIO2_RESET on J5 (1-2, 3-4, 9-10) must be shorted with jumpers. This is because the I2C lines are not disrupted when one removes the jumpers from block J5, which leads to problems when using I2C to the board plugged in on top. After that it is plug-and-play.

    Q3 - When you change the settings in the TLV320AIC3101 the Command line interface log is updated with the latest values, I don't have it here so I can see it, but from what I see in the documentation it is the same syntax as used in the PurePath Wireless Configurator.

    Ole A.

  • Saw a fault in my Q2 - answer J5 GIO2_RESET should be pin 15-16 (instead of my 9-10) and you may also connect pin 16 directly to ground to disable the onboard codec entirely.

    Ole A.

  • And it's not J5, it's P15 ;-)

  • Hi,

    Thanks Ole for the answer.  I have any number of convertors available, but still find this process cumbersome.  

    Q1    Does TI have any solution other than third party convertors?

    Q2    Also, could TI please confirm Ole's useful answer that the TLV320AIC3101EVM produces the SAME syntax as the Purepath Configurator, and can therefore directly be used in the Configurator from the EVM?

    Thanks in advance,

    Geoff Pickford

  • Hi Geoff, 

    Ole's answers are to be regarded as TIs answer as he is an external contractor working for the PurePath Wireless team and has been for the past 1+ year.

    Kjetil