[beagleboard] Custom Audio cape with TLV320AIC3107 codec.
Hi, I have made custom Audio cape using TLV320AIC3107. Here is a circuit diagram : http://e2e.ti.com/cfs-file.ashx/__key/telligent-evolution-components-attachments/00-64-01-00-01-29-55-62/audio.png 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. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Custom Audio cape with TLV320AIC3107 codec.
HI, Thanks For reply. Can you please tell me how I can Do that ? Thanks Regards, Prakash P. On Monday, September 15, 2014 8:01:19 PM UTC+5:30, liyaoshi wrote: Have you config the i2c pin pulled up ? and whats the speed of your i2c bus ? 2014-09-15 2:09 GMT+08:00 prakash@gmail.com javascript:: Hi, I have made custom Audio cape using TLV320AIC3107. Here is a circuit diagram : http://e2e.ti.com/cfs-file.ashx/__key/telligent-evolution-components-attachments/00-64-01-00-01-29-55-62/audio.png 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. -- 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 javascript:. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] Custom Audio cape with TLV320AIC3107 codec.
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. On Monday, September 15, 2014 8:51:43 PM UTC+5:30, sbodd05 wrote: 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 javascript: 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. -- 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 javascript:. For more options, visit https://groups.google.com/d/optout. -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[beagleboard] Re: custom cape i2c bus
Hi !! I'm facing problem with Custom I2C cape. It's I/o Expander using NXP's PCF8574T Expander chip. I'm unable to detect it. I tried every thing available on web. Can you help me ? please ? Here is some output. root@beaglebone:~# uname -a Linux beaglebone 3.8.13 #1 SMP Wed Sep 4 09:09:32 CEST 2013 armv7l GNU/Linux root@beaglebone:~# i2cdetect -y -r 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- UU -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- 34 -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: UU -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- root@beaglebone:~# i2cdetect -y -r 1 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: -- -- -- -- -- -- -- -- root@beaglebone:~# i2cdetect -y -r 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: 20 -- 22 -- 24 -- 26 -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- I'm using Beaglebone Black Rev B. Hope Listen form you soon. Thanks. On Thursday, July 17, 2014 9:17:40 PM UTC+5:30, Johan Korten wrote: I managed to make my own cape (for two XBee modules). It works very well (even sending between the two modules and to the third one on the computer), but: if I use node ./eeprom.js I suspect that my cape is expected to be connected to the fourth (or third if you start counting at 0) i2c bus: /sys/bus/i2c/drivers/at24/3-0057/eeprom instead of /sys/bus/i2c/drivers/at24/1-0057/eeprom So should I fix that in my cape (my cape is default at /sys/bus/i2c/drivers/at24/1-0057 but can be configured to go from /sys/bus/i2c/drivers/at24/1-0054 .. /sys/bus/i2c/drivers/at24/1-0057) Apart from that, I managed to program the eeprom and get it working, but since it uses UART 2 and UART 5 I needed to change /boot/uboot/uEnv.txt to get that working (BBB Rev B so that is why I needed to change /boot/uboot/uEnv.txt instead of /media/BEAGLEBONE/uEnv.txt), but do I need to supply that with my final version somewhere or is it enough to put that in the manual? Sincerely, Johan -- 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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
