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.

TLV320AIC3106-Q1: IS TLV320AIC3106-Q1'S I2S DOUT / DIN AVAILABLE AT SAME TIME WHEN USING BLUETOOTH PCM

Part Number: TLV320AIC3106-Q1

We're Designing Car Head Unit With TI Codec TLV320AIC3106-Q1 And Here Are Some Problems About Bluetooth Hands-Free Use Case.

First We Need To Make Sure We Can Use PCM ( In TLV320AIC3106-Q1 Datasheet Page 42 A Block Diagram Points Out PCM Can Be Enabled By Sharing I2S's DOUT As Blow:

It Very Clear No Doubt But Our Questions Are About Bluetooth Hands-Free Application By USB / When We Use Wireless Modem And Especially Which Required For CarPlay Development In MFI Accessory Interface Specification.

1. First When We Using WL1833Q / Similar Module And Here Is A Coming Call The Voice Data Will Split Off And Transform Into PCM Format By I2S Interface.

So We Follow Your Datasheet And Control TLV320AIC3106-Q1 DAC Line-Out To External Amplifier Then Car Speakers.

The Design Is For Listening Purpose.

On The Other Hand We Use Fortemedia FM1388 To Connect External Microphone Array For Speaking.

The FM1388 Will First Pre-Amplify The Line-In Then ADC To Codec Then Through I2S DOUT To System's DIN. The Voice Will Soon Be Packed And Over Bluetooth HSP Profile By Physical Interface UART To The Air. The Question Is How Can We Handle The Speaking / Listening Voice Data At Same Time? It Is To Say We Need To Use I2C Then By Register Control Internal MUX For Switch Out The Input PCM (Listening) To Car Speaker And In The Meanwhile Switch In The Input Speaking Data. Is It Possible? We May Enable FM1388 I2S Directly To Another I2S Of Host Processor And Packed Input Voice Data Over HSP Profile Then Through UART To Bluetooth Module In Stead But When Considering The USB Mode / Wireless Modem Use Case Here Comes New Problem:

2. USB Mode For Example The Mobile Phone Using USB (CarPlay Case) And iAP2 Over USB Requires Parsing Packet Then Split Voice Data To Codec Through I2S For A Listening Call. In The Same Time We May Push Talk And Input Speaking Voice To FM1388 Then To Codec / Directly To Mentioned Design: Another I2S Of Host Processor. The Problem Is How Can We Deal With Input Voice To Codec By Using Same Data Path For Both Of Speaking Voice And Listening Voice By Using The Same DIN?

  • Hi, Bright,

    My colleague has been notified about your question, he will get back to you as soon as possible.

    Best Regards,

      -Diego Meléndez López
       Audio Applications Engineer

  • Hi Bright,
    I think we understand your explanation for most part, but just to make sure i understand it completely, can you please share the block diagram for the overall system you are explaining? I just want to make sure I understand the system before giving you conclusive answers. Thanks.

    Best regards,
    Ravi
  • Hello Ravi

    Here Comes Our Audio Routing / Control Block Diagram For Both Of Bluetooth Hands-Free Use Case And A2DP Use Case And Also For Push Talk Speech Recognition. Please See Below:

    1. First Question We Have To Confirm With You The MFP3 Pin GPIO 1 / GPIO 2 As Described In TLV320AIC3106-Q1 Datasheet Page 42

    Is Our Pin-Out Configuration Right For Your Codec? The MFP3 Pin Can Be Set As / Seen As I2S Interface DIN And The Other 2 GPIOs Can Be Set As WCLK / BCLK?

    2. Second In Your Block Diagram Here Is Only On DOUT PIN For Bluetooth PCM Use

    Does It Mean We Cannot Use I2S And Bluetooth PCM At Same Time?

    3. Third The Hands-Free Use Case Can Be Taken Apart Into 2 Sections. One Is Outgoing Voice Input To Microphone Another Is Incoming Call Voice Split Off From PCM. The 2 Inputs Requires Echo Cancellation And Background Noise Suppression. Probably Incoming Call Voice Doesn't Need. First We Use An DSP To Pre-Amplify And ADC Input Voice When Taking A Call And Speaking To Microphone. Second The DSP Also Take Charge Of Echo Cancellation / Background Noise Suppression. Then Processed Input Will Be Transmit Into Host Processor Through I2S And Bluetooth HFP Profile To HCI UART Back To Phone. So Far Here's No Problem. For Incoming Call Voice We Have To Transmit PCM Format From Bluetooth To DSP For Echo Cancellation Either. If We Don't Have To Process Incoming Call Voice We May Control Codec Bypass For A Lineout. As You See In Our Diagram I Want To Confirm:

    3-1. If We Take Out The MUX Between Bluetooth / DSP / Codec Can We Directly Bridge The Path?

    3-2. If You DOUT PIN Is Occupied By Either Of Host Processor Can Another Path For Hands-Free Can Be Used In The Same Time?