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 <
> [email protected] <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 [email protected] <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 [email protected].
For more options, visit https://groups.google.com/d/optout.
