Custom Audio cape with TLV320AIC3107 codec.

305 views
Skip to first unread message

prakash....@gmail.com

unread,
Sep 14, 2014, 2:09:24 PM9/14/14
to beagl...@googlegroups.com
Hi,

I have made custom Audio cape using TLV320AIC3107. Here is a circuit diagram : 


I make it same  ( Pin configurations and all ) as what is available at CircuitCO using TLC320AIC3104 codec. I follow All steps like Disable HDMI and Load Device Tree BB-BONE-AUDI-02-00A0.dts  and I it works fine.

But my problem is when I run speaker-test system hangs (freezes) and I have to Hard Reset BeagleBone.

Here is what i did and what I get in dmesg.


root@beaglebone:~# speaker-test 

speaker-test 1.0.25

Playback device is default
Stream parameters are 48000Hz, S16_LE, 1 channels
Using 16 octaves of pink noise
Rate set to 48000Hz (requested 48000Hz)
Buffer size range from 128 to 32768
Period size range from 8 to 2048
Using max buffer size 32768
Periods = 4


And in Dmesg : 

[  205.540653] omap_i2c 4819c000.i2c: Arbitration lost
[  206.572921] omap_i2c 4819c000.i2c: controller timed out
[  206.580024] omap_i2c 4819c000.i2c: Arbitration lost
[  207.611983] omap_i2c 4819c000.i2c: controller timed out
[  207.618668] omap_i2c 4819c000.i2c: Arbitration lost
[  212.626062] omap_i2c 4819c000.i2c: Arbitration lost
[  213.658853] omap_i2c 4819c000.i2c: controller timed out
[  213.666881] omap_i2c 4819c000.i2c: Arbitration lost
[  214.699867] omap_i2c 4819c000.i2c: controller timed out
[  214.707912] omap_i2c 4819c000.i2c: Arbitration lost
[  215.740887] omap_i2c 4819c000.i2c: controller timed out
[  215.748952] omap_i2c 4819c000.i2c: Arbitration lost


I also cross check device tree file and I found that it also works for TLV320AIC3107 codec So I think it is not issue.

An one have Idea what is wrong Please Help ME !!!!


Thanks & Regards 

Prakash P.


liyaoshi

unread,
Sep 15, 2014, 10:31:19 AM9/15/14
to beagl...@googlegroups.com
Have you config the i2c pin pulled up ?
and 
whats the speed of your i2c bus ?

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

liyaoshi

unread,
Sep 15, 2014, 10:34:31 AM9/15/14
to beagl...@googlegroups.com
Can you show the waveform of your i2c clock and data ?

Valentin Le bescond

unread,
Sep 15, 2014, 10:45:09 AM9/15/14
to beagl...@googlegroups.com
I'm very interested in how you would solve this issue. We are having a similar problem with a "basic" AIC3104 codec and no idea how to debug the situation.

Subhendu Biswas

unread,
Sep 15, 2014, 11:21:43 AM9/15/14
to beagl...@googlegroups.com
Definitely it's a problem with the i2c lines, cross check your connections with i2c lines or as suggested above to check the pullups. Issue the following command to see if the chip is detected on the i2c bus or not -
i2cdetect -y -r <i2c_bus_no> 

On Mon, Sep 15, 2014 at 8:15 PM, Valentin Le bescond <valentin....@gmail.com> wrote:
I'm very interested in how you would solve this issue. We are having a similar problem with a "basic" AIC3104 codec and no idea how to debug the situation.

prakash....@gmail.com

unread,
Sep 15, 2014, 1:45:26 PM9/15/14
to beagl...@googlegroups.com
Hi ,
Thanks for Reply.

I checked it and chip is detected.

     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

Here 0x18 is chip i2c address.

root@beaglebone:~# cat /sys/bus/i2c/devices/1-0018/name 
tlv320aic3x

I don't what is wrong.

Any Idea ??
Thanks & Regards,
Prakash P.

prakash....@gmail.com

unread,
Sep 15, 2014, 1:46:57 PM9/15/14
to beagl...@googlegroups.com
HI,
Thanks For reply.

Can you please tell me how I can Do that ?


Thanks & Regards,
Prakash P.

Prakash Parmar

unread,
Sep 15, 2014, 1:52:40 PM9/15/14
to beagl...@googlegroups.com
frequency of i2c bus as specified in dts is 100 kHz.


On Monday, September 15, 2014 8:01:19 PM UTC+5:30, liyaoshi wrote:

Prakash Parmar

unread,
Sep 15, 2014, 1:58:15 PM9/15/14
to beagl...@googlegroups.com
Hi, 
I think in Device tree, i2c pin is pulled up. here is part of Tree.

i2c2_pins: pinmux_i2c2_pins {
pinctrl-single,pins = <
0x150 0x72 /*spi0_scl.i2c2_sda,SLEWCTRL_SLOW | INPUT_PULLUP |MODE2*/
0x154 0x72 /*spi0_d0.i2c2_scl,SLEWCTRL_SLOW | INPUT_PULLUP | MODE2*/
>;
};

 

On Monday, September 15, 2014 8:01:19 PM UTC+5:30, liyaoshi wrote:

Maxim Podbereznyy

unread,
Sep 15, 2014, 2:23:06 PM9/15/14
to beagleboard
1) change 10k pull-up resistors to 5.6k as for other capes
2) check if SYS_RESET is actually deasserted and high
3) check if DIN/DOUT are correctly connected and not flipped, because DIN data must go into CODEC, while DOUT must go out and vise versa

use this command to test (not speaker-test). Copy/paste it or be sure to use two "v" with the dash
aplay -vv file.wav

Maxim Podbereznyy

unread,
Sep 15, 2014, 3:05:13 PM9/15/14
to beagleboard
what is exactly not clear for you?

how to change resistors or how to copy/paste commands in a shell?

Prakash Parmar

unread,
Sep 16, 2014, 1:15:08 AM9/16/14
to beagl...@googlegroups.com
Hi,

How I can check this two things ?

2) check if SYS_RESET is actually deasserted and high
3) check if DIN/DOUT are correctly connected and not flipped, because DIN data must go into CODEC, while DOUT must go out and vise versa

I'm not clear about this. Actually I have two Boards one with 10K resistors and one with 4.6K .

Thanks & Regards,
Prakash P.
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/0ickf2E6NNs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard...@googlegroups.com.

Jesse Cobra

unread,
Sep 16, 2014, 9:51:13 AM9/16/14
to beagl...@googlegroups.com
What happens when you try the CircuitCO audio cape?
Does it work fine?

Prakash Parmar

unread,
Sep 16, 2014, 11:53:36 AM9/16/14
to beagl...@googlegroups.com
Hi,

Here CircuitCo cape is not available So we decided to make our own.

Prakash Parmar

unread,
Sep 16, 2014, 12:24:22 PM9/16/14
to beagl...@googlegroups.com
Hi Maxim ,

I try with your suggestion of "aplay -vv test.wav" But still same things. Please find attachment of dmesg log.

Hope listen from you soon. :)

Thanks & Regards,
Prakash P.


dmesg.txt

Jesse Cobra

unread,
Sep 16, 2014, 5:21:29 PM9/16/14
to beagl...@googlegroups.com

OK, and what is different between your board and CircuitCo schematic wise?

Prakash Parmar

unread,
Sep 17, 2014, 12:10:09 AM9/17/14
to beagl...@googlegroups.com
Hi,

Schematic wise both are same.

Jesse Cobra

unread,
Sep 17, 2014, 12:48:47 AM9/17/14
to beagl...@googlegroups.com
Have the schematic posted somewhere?

Prakash Parmar

unread,
Sep 17, 2014, 2:37:45 AM9/17/14
to beagl...@googlegroups.com
Hi, 

PFA of my cape schematic,
audio.png

Prakash Parmar

unread,
Sep 18, 2014, 3:42:19 AM9/18/14
to beagl...@googlegroups.com


audio cape.png

Prakash Parmar

unread,
Sep 18, 2014, 3:43:05 AM9/18/14
to beagl...@googlegroups.com
Hope listen from Experts soon.

Thanks & Regards,
Prakash P.
audio cape.png

Jesse Cobra

unread,
Sep 18, 2014, 4:01:35 AM9/18/14
to beagl...@googlegroups.com
Your device tree and schematic are not the same as the CircuitCo one so I would start with that.


audio cape.png

Prakash Parmar

unread,
Sep 18, 2014, 4:32:16 AM9/18/14
to beagl...@googlegroups.com
Thank you very much.


Regards,
Prakash P.
audio cape.png

Prakash Parmar

unread,
Sep 23, 2014, 3:18:28 AM9/23/14
to beagl...@googlegroups.com
Hi Jesse,

Have you anything for me ?

audio cape.png

federico...@gmail.com

unread,
Jun 17, 2015, 8:22:33 PM6/17/15
to beagl...@googlegroups.com
Hi Prakash,
I've the same problem with custom audio cape.
Have you a solution now?
thanks
regards

Federico 

Prakash Dash

unread,
Jan 4, 2019, 9:09:31 AM1/4/19
to BeagleBoard
Hi All,

Can someone please share me the custom audio cape supported in beaglebone black Rev C board.
if anyone have the picture for the custom audio cape board please share that image.
Along with please share the schematic and datasheet for corresponding.

What will be the kernel driver for this AUDIO device please share also.

Thanks
Prakash
Reply all
Reply to author
Forward
0 new messages