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.

MCU for AIC3254/AIC3253?

Other Parts Discussed in Thread: TLV320AIC3253, TLV320AIC3253EVM-K, TLV320AIC3254, TLV320AIC3254EVM-K

Hello

Can someone please walk me through a suitable MCU for AIC3254/AIC3253 audio codec?

From the codec's eval kit, a controller with 32kB mem with I2C/SPI is enough.

Is MSP430G2744 suitable? It has 1kB RAM, 32kB flash, 16MHz and 1 I2C, SPI each.

The codec would not be used for digital audio. Want to keep it simple.

One more thing. Since there isn't much of know-how on this from my end, I would prefer outsourcing the development. Generally speaking, what should I know before committing someone to take the task?

Like 1) Would I also require a separate compiler/development board for the MCU, which would then get later soldered to the codec PCB? Or I can straight way use USB connection on the codec PCB to a PC and then initialize the MCU from their for the first time. And then obviously, download the codec code from Purepath.

Please help before I start talking to a developer.

Thanks.

  • Hello Arjun,

    I do not know enough about the TLV320AIC3254/TLV320AIC3253 devices to be able to properly answer your questions. Referring to the TLV320AIC3254EVM-K/TLV320AIC3253EVM-K boards I see that they have on-chip programmable miniDSPs for operating and controlling the audio codecs. I therefore do not see a reason as to why you require a MSP430 in your design. Your questions may be better answered in the Audio Converters Forum, where their expertise is more-suited towards these devices: e2e.ti.com/.../audio_converters

    You can use the MSP430 product selector tool to find any MSP430 with 32 kB memory and I2C/SPI compatibility, which most devices qualify for with such few parameters: www.ti.com/.../products.page

    The MSP430 introduces its own development environment meaning you will have to use a different connection (depending on the MSP430 development board chosen) as well as a separate compiler to program the MSP430, like CCS or IAR.

    Regards,
    Ryan
  • Arjun,

    Thanks for your interest here. While you are correct that a 32kb MCU would be enough, our MSP430's do not support I2S at this time. However, we do have an app note that covers interfacing with an I2S Device using MSP430 here: 

    With regards to your statement of not using the CODEC for digital audio, can you expand upon what you mean by that statement?


    Arjun Menon said:
    One more thing. Since there isn't much of know-how on this from my end, I would prefer outsourcing the development. Generally speaking, what should I know before committing someone to take the task?

    With regards to this, you will want to make sure that they have had prior experience with 1 if not all of the devices, a proven past with customers and that they work to adhere to the recommended layout guidelines that we provide in our datasheets. Other than that, I find that most people tend to have lots of different opinions on what they prefer from someone to work with, so I would say go with what makes you feel comfortable.

    Arjun Menon said:
    Like 1) Would I also require a separate compiler/development board for the MCU, which would then get later soldered to the codec PCB? Or I can straight way use USB connection on the codec PCB to a PC and then initialize the MCU from their for the first time. And then obviously, download the codec code from Purepath.

    With regards to your specific question, you should contact the Audio Converters forum as my colleague above linked for the best practice here.

  • Following on your "on-chip programmable" point, these codec require a host controller to configure the miniDSP controls, according to their datasheet. But yes, based on all these, it is a bit confusing. If only I exactly knew how to work with those codec and make it ready for production.
  • I2S is primarily used for digital audio, correct. At this stage only parameter required is making it work with analog audio. Nothing else. No other fancy requirement.
    If only TI had not made their chip used in the EVAL-KIT of this codec, obsolete. It would have been pretty easy then.

**Attention** This is a public forum